@Sander: took much longer to find some time to fix the /lib/init/rw vs. /var/lib bug. The postinst script is full of checks to handle all kinds of setups. Not sure how much of that is really needed. But as I don't get the idea of all of it, I just leave it. Regarding the comment in the beginning about /lib/init/rw: a few lines below, there is a copy of the same comment with another comment saying it is not valid for ubuntu, as ubuntu provides an early tmpfs... Well, I guess it wouldn't hurt to stay closer to Debian and use /lib/init/rw anyway. I haven't found time to check the initialization part you mentioned...
@Wladimir Mutel: Yes, the resolvconf package in Lucid still has this nasty bug. But Sander van Grieken did code up an upstart based version of it, and I did some packaging.
@Sander: took much longer to find some time to fix the /lib/init/rw vs. /var/lib bug. The postinst script is full of checks to handle all kinds of setups. Not sure how much of that is really needed. But as I don't get the idea of all of it, I just leave it. Regarding the comment in the beginning about /lib/init/rw: a few lines below, there is a copy of the same comment with another comment saying it is not valid for ubuntu, as ubuntu provides an early tmpfs... Well, I guess it wouldn't hurt to stay closer to Debian and use /lib/init/rw anyway. I haven't found time to check the initialization part you mentioned...
@Wladimir Mutel: Yes, the resolvconf package in Lucid still has this nasty bug. But Sander van Grieken did code up an upstart based version of it, and I did some packaging.
You may try my package from my PPA at https:/ /launchpad. net/~huerlisi/ +archive/ ppa. Comments more than welcome.
Will try to mail the last maintainer of resolvconf about this and ask him to either release a fixed version or sponsor an upload of my package...