Excerpts from ilf's message of Fri Oct 14 18:11:56 UTC 2011: > I don't like this behavior. >
Hi ilf, sorry that you're experiencing problems with this change. This behavior is meant to provide a balance between mobile systems and servers/dedicated workstations. The former needs flexible network management, which ifupdown really doesn't provide, and the latter needs to be able to define a reliable network configuration. Your case where a mobile system that does want to use ifupdown to manage a mobile connection instead of network-manager is normally handled by the failsafe boot. A suggested simple workaround is to remove the 'auto eth0' and instead add an upstart job like this: start on net-device-added INTERFACE=eth0 task exec ifup eth0 This will bring up your interface as soon as the hardware is available, but will not block the boot waiting for it to be up. We can't really make this the default and still provide reliable configuration for workstations and servers because we have no way to know that you intend for an interface to be transient if you did not install network-manager. > I have eth0 auto in /etc/network/interfaces, so that it gets auto-enabled > when plugged in. > This being a laptop it gets moved around and doesn't always have an ethernet > connection plugged in. > No I'm supposed to wait two minutes on every boot OR not have the interface > connected? > Both are no real options for me. > > What does this mean? > > only servers and dedicated workstations should have network interfaces > > configured in this way > > How else should I have my interface configured? > BTW, I do not run Gnome, KDE or any other of those desktop environments. I do > not have NetworkManager installed and won't install it for this. > network-manager does not require a GUI. You can use network-manager without a GUI via nmcli and hand edit /etc/NetworkManager/system-connections/*, or you can use connman. Note that if you have X, you can also just install and make use of network-manager-gnome without having to use all of gnome. > I deleted my /etc/init/failsafe.conf for now. > But I really think this behavior shouldn't be forced. > This is going to make it so your system will never boot without eth0 plugged in. I'd suggest the ifup workaround above instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
