Now to address the bug which all the *duplicates*, except #511314 and #437783, are about, namely, that installing bind9 aborts with "resolvconf: Error: /etc/resolv.conf must be a symlink".
First, resolvconf in Precise no longer returns an error condition if /etc/resolv.conf is not a symlink, so the bind9 initscript will not abort any more once resolvconf has been upgraded. Second, bind9 in Precise no longer defaults to registering 127.0.0.1 with resolvconf on start, so the new bind9 initscript will not abort. I fear, however, that failures will still occur on upgrade when the bind9 preinst stops bind9 and neither bind9 nor resolvconf has been upgraded yet. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/437783 Title: bind9 failed to start : resolvconf: Error: /etc/resolv.conf must be a symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/437783/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
