Comment 20 for bug 89752
Revision history for this message
| Manuel López-Ibáñez (manuellopezibanez) wrote | #20 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
Fixes?
1. Build the kernel with the ac module compiled into the kernel.
2. Modify the initscripts to load the ac module early enough and (it that fails) complain in a message, so users can tell that something went wrong (Failed loading ac module: Cannot determine whether running on batteries). I mean, once you are dumped into fsck, every novice user thinks that something went wrong already, so another scary message can't hurt.
3. ???
Also, that the initscripts have all the logic about running or not fsck when the same logic is already implemented in fsck is totally redundant and a source of confusion (and confusion leads to bugs). Should I report another bug about that?