Comment 14 for bug 448095

Ok I made the upstart script 'restartable', and unified more hardcoded paths into /sbin/resolvconf

- the initialisation of the rundir can now be forced with /sbin/resolvconf -i, and is automatically done by the upstart script when no valid structure is found
- starting and stopping the service now sets the enabled/disabled state via /sbin/resolvconf.
- triggering an update is now only done using /sbin/resolvconf -u
- the rundir can now be queried using /sbin/resolvconf -r

So basically this solves the bug, and also cleans up the scattered resolvconf initialisation

There are probably other scripts in /etc/resolvconf/update.d that still need RW access to other parts of the filesystem, but these updates can be done later in the bootprocess, e.g. calling a resolvconf -u before bind is started, or after /var becomes writable or something similar. I so far only tested the lifecycle of the libc resolver.