The indirection via /etc/resolvconf/run dates from the era before /run/. I introduced resolvconf in 2003 as part of a larger effort to make it possible to run Debian with a read-only root filesystem[1] but the project to introduce the /run/ tmpfs into Debian base failed due to lack of consensus about the need for it[2][3] and disagreement about what to call it[4]. (The references are just a few examples out of several long exhausting threads.) Not being even a Debian Developer myself, I shelved the controversial /run project[5] and carried on developing resolvconf which still needed some location for its state files, preferably on a tmpfs. The best available location at first was /dev/shm/. Later /lib/init/rw/ was introduced and I converted resolvconf to use that by default. I knew that /dev/shm/ was a controversial and probably temporary solution and I also wanted to accomodate people who didn't want to use any tmpfs at all, so I made the ultimate location of the state directory configurable by means of the symbolic link /etc/resolvconf/run. When /run/ became part of the Debian base system in 2011[6] the need for this configurability disappeared. Nowadays there is no good reason not to keep the files under /run/resolvconf/. Accordingly, debian/NOTES already includes the following TODO list.
--------------------------- MAINTAINER NOTES for resolvconf TODO ---- * File bug reports against all packages containing suppliers of nameserver information, asking each to add a resolvconf packaging-event hook script. Still to be submitted: dhcpcd5, pump, udhcpc * In Jessie+1, drop the use of /etc/resolvconf/run; use /run/resolvconf directly. -------------------------- When I have a few free hours I will take care of the second item. Writing maintainer script code to transition existing resolvconf-using machines to the new setup without breaking anything is not entirely trivial. :) [1]https://lists.debian.org/debian-devel/2003/04/msg02057.html [2]https://lists.debian.org/debian-devel/2003/05/msg00280.html [3]https://lists.debian.org/debian-devel/2003/05/msg00247.html [4]https://lists.debian.org/debian-devel/2003/04/msg00158.html [5]https://lists.debian.org/debian-devel/2003/05/msg01479.html [6]https://wiki.debian.org/ReleaseGoals/RunDirectory -- 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