Comment 3 for bug 340071

On Fri, 2009-05-08 at 05:51 +0000, Wladimir Mutel wrote:
> Probably that's why it is strongly recommended to point your /etc/resolvconf/run to /lib/init/rw/resolvconf

*I* should do that? I've never pointed it anywhere. The package has
decided where it should be and put it there.

> /lib/init/rw is very similar to /var/run , but it is available even earlier in the boot process, specially for these purposes.

OK. So why is it not being used, and/or previous installations being
converted to use it?

> Just look into resolvconf postinstallation script and find this out for your self.

Hrm. I don't see that. If everything falls through to the "it's not
there (yet)" case:

  # It's a nonexistent
  # Use /var/run.
  if \
   [ -d /var/run ] \
   && [ -w /var/run ] \
   && grep -qs "^tmpfs[[:space:]]\+/var/run[[:space:]]\+tmpfs[[:space:]]\+\([^[:space:]]\+,\)\?rw" /proc/mounts \
   && { [ -d /var/run/resolvconf ] || mkdir -v /var/run/resolvconf ; } \
   && { [ -d /var/run/resolvconf/interface ] || mkdir -v /var/run/resolvconf/interface ; }
  then
   ln -s /var/run/resolvconf /etc/resolvconf/run
  else
   mkdir -v /etc/resolvconf/run /etc/resolvconf/run/interface
  fi

So that looks to me like it's using /var/run if nothing else.

The only time it appears to use /lib/init/rw/ is if /dev/shm/resolvconf
was being used previously.

> And may be resolvconf postinst script should be more insistent about
> checking where this symlink points and switching it to /lib/init/rw/ in
> case of any violations.

Yes. If all installations are supposed to use /lib/init/rw then IMHO,
the postinst should be moving existing installations there.