I subscribed ubuntu-sru to bug 497299 now, and read it. What I wonder about is how machines without a lo interface could have ever worked sensibly -- you will not even get to gdm without one. Is there something else which hardcodes bringing up lo during boot?
Since that seems to have caused real regressions for apparently quite some people (which apparently are not entirely understood yet, i. e. how they ended up with a broken interfaces file in the first place), but fixed regressions for others (this bug), this seems to be between a rock and a hard place, so I wouldn't hectically revert this. As a workaround for karmic, could we wait on lo only if "grep -q 'auto lo' /etc/network/interfaces"? For lucid and onwards, should we add an upstart job somewhere that brings up lo during rcS if it is not brought up by /e/n/i ? -- rc-sysinit job might start before loopback is up https://bugs.launchpad.net/bugs/461725 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
