Steve, It seems as though Network Manager is as big a crock of **** as it ever was -- at least for workstations that are either connected via eth0 or not connected at all.
I purged Network Manager and added the appropriate lines to /etc/network/interfaces and now when I boot I get the same message about being unable to mount NFS filestores and that I should press ESC, but by waiting a few second the message goes away and the boot resumes and has all the NFS mounts as they should be. So now I don't have a blocker problem, but I must say the overall user experience here is very poor. The sequencing of the various boot time events is either not right and/or the error reporting by the various stages need better management. Speaking from a position of deep ignorance about the details, it seems that an attempt is made to mount all the devices in /etc/fstab at a point in the boot sequence when only the connected discs can be mounted as the network is not up yet. So until the network is up no attempt to mount NFS mounts should be made or the error messages redirected to /dev/null. Then when the second attempt to mount stuff is made after the network is up -- assuming Network Manager has been expunged -- then it would be appropriate to have error messages if there were failures. -- retry remote devices when parent is ready after SIGUSR1 https://bugs.launchpad.net/bugs/470776 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
