Ok; let me describe how this is supposed to work at boot time. - mountall runs at startup, looks around for all the filesystems, and tries to mount them - including any NFS filesystems. The network is almost certainly not up yet, so a "host not found" message typically results. - once the local filesystems are all mounted, dbus and network-manager start up. Since you have a wired network connection, this should immediately bring up your interface via DHCP; once up, network-manager tells upstart. - upstart tells mountall that the network is up, causing mountall to intelligently retry all NFS mounts. - since the network is now up, this succeeds, and the system happily continues booting.
Clearly something in this chain is falling apart, but I don't know why - and this all happily works in my own NFS installation here. I see your bug report was first filed against the beta1 version of mountall. Have you upgraded your system to the beta2 packages, to verify whether the bug is still there? Do you have the 'network-manager' package installed? This may take a few rounds of questions to get to the bottom of the issue you're seeing. -- when mounting NFS, DNS isn't up yet. https://bugs.launchpad.net/bugs/546815 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
