Hi Mathieu, The idea is to do it when the new network-manager installed which listens at 127.01.1 instead of at 127.0.0.1. The old NM worked with an empty or absent /etc/resolv.conf; the new one doesn't.
Yes, it is resolvconf's job to do take care of /etc/resolv.conf, but the sudden termination of name service will only arise when NM is also being used. So it's convenient if network-manager maintainer scripts performs the check. It could also be implement in a resolvconf maintainer script. It doesn't really matter where it's implemented. We are extremely respectful of the nonstandard configuration where /etc/resolv.conf is not a symlink to ../run/resolvconf/resolv.conf. The /sbin/resolvconf program never touches /etc/resolv.conf at all and the resolvconf package makes one and only one attempt to convert /etc/resolv.conf into a symlink, doing this only if an affirmative answer is given to a debconf question. This is all fine. But this respectfulness just expands the problem I am addressing here, the problem of there being a significant number of systems out there which --- unintentionally --- are missing /etc/resolv.conf, which currently have name service via nm-dnsmasq, but which won't have name service after upgrading to 12.10, resulting in some unhappy admins. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1060200 Title: Detect in the postinst that resolvconf is installed but /etc/resolv.conf is not a symlink to ../run/resolvconf/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1060200/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
