My apologies, I have to backtrack on my prev statement. I thought to have read
that on LWN
some time in the past, but I cannot find such statement anymore through google.
Fact is, that Debian hasn't moved to upstart OR systemd (or initng for that
matter) yet,
even in unstable, and is using
On Wednesday 15 September 2010 19:27:47 Liraz wrote:
Many thanks to everyone who helped track down this regression, which
effected TurnKey Linux users of the new TurnKey Core Lucid-based beta as
well:
https://bugs.launchpad.net/turnkeylinux/+bug/596560
IMHO, for desktop usage upstart has
Yeah I'm actually stunned that such a design failure is not acted upon by
Ubuntu. Guess
they just capitalize on the work done by Debian, without having to do the hard
work of
actually maintaining a distribution.
However this bug MUST sting on servers and 'old-school' people that use
I think the problem is that there is a significant post-boot delay before
resolv.conf is updated. It took ~ 90sec (after gdm start) on last boot.
But at least it's working
+Reardon
On Mon, Dec 28, 2009 at 5:11 AM, Sander van Grieken san...@3v8.net wrote:
ok, time for a full checklist :)
-
Ok, I've tried with all your latest, and basically nothing has changed, it's
all still broken. On system boot, resolv.conf remains blank (or rather, it
is created, but with no entries, only the top comment lines).
ifdown/ifup fixes the problem. Same as the Ubuntu release problem.
Have you
My mistake this time. It's working properly now with your updated
/sbin/resolvconf
+Reardon
On Sat, Dec 26, 2009 at 7:16 AM, Sander van Grieken san...@3v8.net wrote:
Did you redownload the /sbin/resolvconf replacement? Can you confirm there
are no
differences between your copy and the
Your solution did not work on reboot. Now when I try ''sudo resolvconf -i'
I get a different error
$ sudo resolvconf -i
mkdir: cannot create directory `': No such file or directory
resolvconf: Error: unable to create
+Reardon
On Fri, Dec 25, 2009 at 11:30 AM, Sander van Grieken san...@3v8.net
I've tried your fix Sander and it sort of works. Which is to say that
resolvconf properly runs at boot. HOWEVER, it does not run correctly on
ifdown/ifup:
$ sudo ifdown eth0
[sudo] password for reardon:
resolvconf: Error: /lib/init/rw/resolvconf/interface is not a directory
resolvconf: Error:
I created the directory /lib/init/rw/resolvconf/interface by hand. But no
idea what should go in here. The whole point of installing resolvconf in
the first place was so that vpn clients would work properly (in my case,
vpnc). But no updates to resolv.conf are made when I connect with vpnc
