I'd like to comment on the remaining differences between Debian resolvconf and Ubuntu resolvconf.
Besides the extensive source-textual differences arising from Debian's use of /etc/resolvconf/run versus Ubuntu's direct use of /run/resolvconf, I see only three substantial differences. 1. The omission of debian/triggers in Ubuntu As mentioned previously (comment 6) I am guessing that this is an oversight. 2. Debconf question resolvconf/link-tail-to-original defaulting to true in Ubuntu versus false in Debian This only makes a difference, and the answer "true" is only useful, when installing resolvconf on a resolvconfless system that already had a handcrafted /etc/resolv.conf file and the admin doesn't want to take the time right away to move the "nameserver" lines from /etc/resolvconf/resolv.conf.d/original to the appropriate place in /etc/network/interfaces. This use case seems very far from the typical circumstances on an Ubuntu system where resolvconf is part of the base system. I'd say drop this difference unless there is a known good reason to preserve it. If there is a reason then please document it somewhere, e.g., in debian/NOTES. 3. dhclient-enter-hooks.d/resolvconf undefining make_resolv_conf() only if /etc/resolv.conf is a symbolic link, in contrast with Debian resolvconf where that script undefines make_resolv_conf() even if /etc/resolv.conf is not a symbolic link. See bug #1385010 for discussion. My position is that this diff should be dropped. It's a feature of resolvconf that when you install it, other programs don't engage in their legacy behavior of overwriting /etc/resolv.conf. With the diff in question here, Ubuntu reactivates dhclient's legacy behavior (which Debian resolvconf had deactivated) of overwriting /etc/resolv.conf if the latter is not a symbolic link. Some people might want that; others do not (bug #1385010). My view is that people who want the legacy behavior should de-install resolvconf to obtain it. The resolvconf package and the symbolic link at /etc/resolv.conf are on the system by default, so the diff in question has no effect on a typical Ubuntu system. So twhat reason is there to depart from Debian in this respect? Perhaps it's a concession to the expectations of admins who are more familiar with other distros. If there is a reason then whatever the reason is, please document it in a comment. Cheers! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1453185 Title: resolvconf: updates are not enabled right after installation Status in resolvconf package in Ubuntu: Fix Released Bug description: Previously, updates were enabled in postinst script, but this enablement was removed in a favour of upstart service (https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/931335). This worked fine till the switch to systemd - no postinst action to activate resolvconf.service right after installation, one needs to reboot node in order to get updates enabled. Description: Ubuntu 15.04 Release: 15.04 resolvconf 1.76ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1453185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp