I believe the correct policy for mountall is to ignore missing
filesystems that are marked with options "owner", "user" or "noauto".
Everything else should properly cause a hang (unless an admin explicitly
says a filesystem isn't required via nobootwait). "noauto" should
already be ignored and "us
@dblade I wasn't taking a stand on the other issues. But I agree not
displaying the message is/was a bug.
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You received this bug notification because yo
After being frustrated with this bug for a while, I grabbed the mountall
source... it's a lot of stuff, but one thing I found was the
"nobootwait" option.
Adding "nobootwait" to all my "auto" mounts allowed my system to boot up
without intervention.
Although the fstab manpage is a little terse de
