Workaround [decent]: Move networking further down in the boot process.
I moved networking from rcs.d to rc2.d/rc3.d/... and gave it a priority one lower than GDM. In otherwords 'mv /etc/rcS.d/@##networking /etc/rc2.d/@14networking' So now GDM boots, followed immediatley by networking. By time I'm in a usable desktop networking has completed and I'm good to go. I find this to be a very suitable work-around as I don't need networking loading any sooner and I don't noticed the hang time at all now. This issue only seems to happen when a resource is unavailable.. as in if my NIC isnt jacked in. -- Feisty boot hangs on "Configuring network interfaces" https://bugs.launchpad.net/bugs/102675 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
