bwalex: Are you saying that the boot is actually waiting for these mounts to timeout with nobootwait? That would be a pretty serious problem, and not related to this bug.
The error message is a result of the fact that mountall just tries to mount *all* filesystems in fstab, similarly to 'mount -a'. If one fails its just noted and will be tried again. The error message from mount.nfs is a bit misleading, as its saying DNS failed but its really that contacting the host failed. dblade, net-device-up is emitted every time a network device is configured properly. This means either it was static and configured by ifupdown, or its dynamic and dhclient configured it. So, the theory here is that every time we get a new network device, we should try again in case all filesystems haven't been mounted yet. start on started networking only means that all static devices have been configured, and all dhclients have been started. Any NetworkManager based connections will be missed entirely. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/586022 Title: nfs mounts happen before network is up -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
