I agree with some of the voices raised here. I just edited fstab, screwing up the device name of an unimportant data partition, and now I'm left with a non-booting server and no clear indication of what went wrong (well, until I found this).
I think perhaps other than the root partition, a flag like 'forcebootwait' should trigger this behaviour, and the default should be as 'nobootwait' is now. This isn't a horrific bug (no data loss, a quick visit to the console will fix) - but it's a nasty one in areas where everyone is a little jumpy (booting, storage). Keep up the otherwise good work. -- Lucid mountall can cause unexpected hangs https://bugs.launchpad.net/bugs/510415 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
