I agree that we should really fix this for Hardy. I'm currently not sure
where the problem is (in upstart, or the usplash integration, etc.).
Incidentally, is it possible to safely fake this situation in order to
test this? Well, I guess temporarily replacing e2fsck with an "exit 4"
shell script should do. :-)
FWIW, I think it would be a bad idea to use something like a "reckless"
fsck repair mode by default. Forcefully mounting and booting a broken fs
might do more damage than the boot is worth, and it invites users to
ignore the error.
** Changed in: upstart (Ubuntu)
Importance: Undecided => High
Target: None => ubuntu-8.04
--
fsck not repairing corruption on boot
https://bugs.launchpad.net/bugs/209416
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
