The "bootwait" option is dodgy at best. Seems to have many gotchas depending on the specific hardware configuration (does not work on any of 3 systems here, all different). This behavior BREAKS many existing systems causing untold loss of thousands of human hours. Further, it does not seem to be fully thought out because if it were it wouldn't break so many systems. Lastly it is not obvious and is especially bad for newbies.
The only reasonable conclusion is to revert to the previous stable and predictable behavior until this so-called "feature" can be introduced without breaking systems and wasting people's time. btw - My short-term solution was to warp /etc/init/mountall.conf and remove the --force-fsck and --fsck-fix options from the "exec moutall" line. Ya - you must pay attention and run fsck by hand accordingly ... but at least I know when it's being done and the rest of the system isn't crashing all over the place because it does have the mounts it needs!! -- boot process isn't paused while fsck runs on partition: boot process is completed with fsck running in the background preventing partition from mounting https://bugs.launchpad.net/bugs/439604 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
