This has been tracked down to a bug in the resolvconf package, causing
/etc/network/if-up.d/000resolvconf to fail and taking the rest of the
ifupdown hooks with it.
We can't create the initial /etc/resolv.conf symlink from the upstart
job when using the live installer, because the job is never run until
boot - and at the time it runs (start on mounted MOUNTPOINT=/run), the
root fs is not writable. So this symlinking *must* be done in the
postinst.
Targeting to beta-1 because we don't want to unsettle this for alpha-2.
** Package changed: ifupdown (Ubuntu Precise) => resolvconf (Ubuntu
Precise)
** Changed in: resolvconf (Ubuntu Precise)
Status: Incomplete => Triaged
** Changed in: resolvconf (Ubuntu Precise)
Milestone: None => ubuntu-12.04-beta-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924836
Title:
network-manager does not tell plymouth it has started
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924836/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
