This bug report seems to have been based on a lack of understanding of
the available mountall options. The only filesystems that will block
the start of services like ssh are those mounted at standard FHS mount
points. If you have a filesystem mounted at one of the standard mount
points and you don't want the boot to wait for that one either, you can
use either 'nobootwait' or 'timeout' options for it in /etc/fstab to
express this.
Closing this report as invalid since I don't see anything here that
requires mountall changes.
** Changed in: mountall (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/614662
Title:
A better mountall
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/614662/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
