*** Reply to message from dep
if, however, the purpose of the exercise is getting suse running on customers' machines, then acpi defaulting to off, with documentation describing how to turn it on, would seem to be the right thing to do, don't you agree?
It might be, if SuSE also ran a hardware division , but there just aren't enough guys and gals there to monitor everything. Perhaps a lot of newer boards require it ? THAT would really put a crimp into the adoption , if someone , who may be trying to get the company to look at Linux as a solution discovers too late ( and w/ the big boss watching) that the test box wont boot at all until someone realizes that they need the aspci on in order to work. IF it's true that newer hardware ( say the last 5 years or so ) needs to have it on, it's not a bad guess to have it default to on.. w/ relatively easy fix ( emphasis on relatively) to get the older ones up and running. OF course Linux sysadmin has probably read a lot of the pre install info so isn't flustered. OR he knows his boxen need the thing off or on anyway. Can't be said for *most* of the w32 sysadmins I've met tho . <g> -- j Afterthought : If you plan to throw one away, you will throw away two.