bwalex, its ok to try and fail at the mount, that shouldn't *break* anything. If there's no route, there's no danger of a timeout or anything, it will rapidly fail and move on. Rather than trying to pinpoint the exact spot where the network is available, we should instead strive to make these mounts robust through transient network connections since they are used on things like laptops quite often.
Steffen, I think you are referring to bug #611397. The bug is "Incomplete" because we don't feel there's enough information to decide where this bug report should go next. The original reporter hasn't provided more details on what failed for him and what he expected to happen. If anybody has a similar issue to the original one and can provide answers to those questions, then we can move forward with a new status for the bug. Specifically, Barry stated that while he got those errors, the mounts worked and the boot moved forward without any prompts or waiting. Bwalex, it sounds like you have a very different issue. You should open a new bug report (please run 'ubuntu-bug mountall' from a terminal), as I think your issue is quite different. Go ahead and subscribe me (clint- fewbar) to the bug and also comment here with the bug #. -- 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
