Ehh? Changelog of resolvconf doesn't match reality? Or am I looking in the wrong spot?
https://code.launchpad.net/~ubuntu- branches/ubuntu/maverick/resolvconf/maverick * Merge from debian unstable (LP: #605116), remaining changes: - bin/resolvconf: + fail with non-zero exit code when /etc/resolv.conf is not a symlink. - debian/postinst: + use default /var/run. + make sure all run files are sent to /var/run, not /lib/init/rw + update regex to check that /var/run is a tmpfs (LP: #386822) + fix typo in comments - debian/rules: + don't install the init script in runlevels 0 and 6. - debian/postrm: + remove /var/run/resolvconf, not /lib/init/rw/resolvconf + also purge /var/run/resolvconf/interface -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
