Confirmed; it was caused by the udev rules update that attempted to only
auto ifup/ifdown interfaces with physical hardware. A slight change to
the udev rule to behave as we intended (udev has a strange behaviour
with S!= rules) fixes this problem and the original problem
** Changed in: ifupdown (Ubuntu)
Status: Confirmed => Fix Released
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
