You are right. In the Debian version, the script is activated by "test -x /sbin/resolvconf" where the presence of /sbin/resolvconf indicates that the resolvconf package is installed. The convention in Debian is: "If the resolvconf package is installed then disable your default resolv .conf-updating behaviors and instead send the information to /sbin/resolvconf". In Debian the convention is furthermore that other packages should NOT check whether or not /etc/resolv.conf is a symlink and do things to /etc/resolv.conf if it isn't a symlink. In Debian, installing resolvconf and deleting the symlink at /etc/resolv.conf is a way of configuring the system such that the file is not updated by anything.
Unlike Debian, Ubuntu includes resolvconf in the base install. Furthermore Ubuntu has been afflicted by mysterious bug #1000244 which is the problem that in rare cases /etc/resolv.conf fails to be a symlink after resolvconf is installed. So perhaps there was a pragmatic reason for Ubuntu to make a change whose effect is to restore dhclient's default behavior when /etc/resolv.conf is not a symlink. Nevertheless, as the Debian maintainer of resolvconf, I agree with you. :) ** Summary changed: - unexpected behavior: make_resolv_conf not undefined + Unexpected behavior: make_resolv_conf is not undefined if /etc/resolv.conf is not a symlink -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385010 Title: Unexpected behavior: make_resolv_conf is not undefined if /etc/resolv.conf is not a symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1385010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
