*** This bug is a duplicate of bug 366967 ***
https://bugs.launchpad.net/bugs/366967
** This bug is no longer a duplicate of bug 264165
Intrepid: resolvconf interface cleanup fails during boot.
** This bug has been marked a duplicate of bug 366967
ifupdown-udev integration should be
*** This bug is a duplicate of bug 264165 ***
https://bugs.launchpad.net/bugs/264165
** This bug has been marked a duplicate of bug 264165
Intrepid: resolvconf interface cleanup fails during boot.
--
/etc/rcS.d/S07resolvconf is too early
https://bugs.launchpad.net/bugs/340071
You
see also #448095
--
/etc/rcS.d/S07resolvconf is too early
https://bugs.launchpad.net/bugs/340071
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
This bug is for Jaunty 9.04. I don't know it's current status.
LP:448095 is for Karmic 9.10, which is very different. Karmic uses
Upstart instead of the older init scripts.
--
/etc/rcS.d/S07resolvconf is too early
https://bugs.launchpad.net/bugs/340071
You received this bug notification
Sorry for misinforming you all. My fault.
Now the problem seems to be fixed in Ubuntu package management scripts. The
directory location is checked and fixed when needed.
Earlier, there were some mess with resolvconf keeping its mutable state in /etc
and requiring /etc (/) to be mounted rw too
Maybe I missed it, but I didn't see any kind of strong recommendation
in the documentation. Who recommends this and where? Won't there also
need to be changes within the package as well as the post-install script
to use the new location? Wladimir Mutel, if you know how the package
should work,
Probably that's why it is strongly recommended to point your
/etc/resolvconf/run to /lib/init/rw/resolvconf
/lib/init/rw is very similar to /var/run , but it is available even earlier in
the boot process, specially for these purposes.
Just look into resolvconf postinstallation script and find
On Fri, 2009-05-08 at 05:51 +, 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
And of course, that /var/run is a tmpfs makes this problem all the more
interesting. I'm not really sure where the popcorn trail on that leads.
--
/etc/rcS.d/S07resolvconf is too early
https://bugs.launchpad.net/bugs/340071
You received this bug notification because you are a member of Ubuntu
