Marking as Won't fix, as unfortunately none of the fixes mentioned
before seem to deal with all the cases and they all sound like they
might cause significant breakage if they go wrong.

So far what was mentioned is that somewhere between 8.04 and 10.04, we
switched from having Network Manager ignore /etc/network/interfaces to
having it consider such a declaration as being a "don't touch the
interface".

We then introduced in 11.10 some code waiting for all interfaces defined
in /etc/network/interfaces (and marked auto) to be up before continuing
the boot sequence.

People who would have upgraded their machine all the way from 8.04 with
a similar /etc/network/interfaces would still have a working setup on
12.04 as ifupdown would be doing the dhcp query and Network Manager
would ignore the interface (agreed, not what we WANT, but still a
working setup).

Now the problem is when on top of that, you've changed hardware and eth0
no longer exists. That'd confuse any system, including Network Manager,
but it only slows down the boot when combined with an entry in
/etc/network/interfaces.

Overall, I think this is enough of a corner case that it's not worth
spending time fixing. I scanned other bug reports and it's the only
reported case of that bug with currently 4 people marked as affected.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900903

Title:
  "Waiting for network configuration" due to uncommented 'auto' lines in
  /etc/network/interfaces (historical installer/upgradebug?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/900903/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to