*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I cannot use ACPI with *BSD, because a BIOS bug in my laptop version (Aspire 3680-2633) causes resources for ethernet devices to be deallocated by the BIOS when ACPI is enabled. Unfortunately, I don't have APM support either.
This would be fine... Except for one tremendously stupid problem.
In Linux, when ACPI is disabled, the power button works properly. If you hit it, nothing happens. It only turns off the machine when you hold it down for five seconds.
Likewise in Windows: when ACPI is disabled, hitting the power button does nothing, unless you hold it down for five seconds.
In *BSD, though... When ACPI is disabled, the power button shuts down the machine the instant it is hit. In other words, if you accidentally brush the button... Poof. There goes your data. And this is unacceptable.
How can I force *BSD to do nothing when I press the power key, or any other ACPI related key?
(And really... I'm getting a bit fed up with all this. Windows XP is slow and very annoying to maintain, Linux is stupendously buggy, and Solaris doesn't support my hardware. The BSDs, by contrast, are generally pretty well behaved. And this one, utterly stupid bug stands between me and a usable BSD install. Help?)
I don't disagree with you that *any* OS can have "issues".
I just think it's terribly unfair to make such a broad, specious claim without stating any specifics, or giving any justification. Who knows - the problem might have been an application problem having nothing whatsoever to do with the kernel. Or it might have been some "niche" distro (like Oracle's self-serving answer to "This is Not RedHat"). Or it might have been some trivial annoyance the OP just characterized as a "bug".