On Sun, May 4, 2014 at 10:36 PM, Martin Pitt <mp...@debian.org> wrote: > Hey Cameron, > >> The point taken from this is that the issues you are hitting may be >> because resolvconf needs to start before more than just >> network-manager, and it does so (accidentally) on Upstart systems. > > Again, which issues am I hitting? The only issue I ever mentioned was > that there was a systemd unit missing for resolvconf as otherwise > nothing sets up /etc/resolv.conf and /run/resolvconf properly. That > got fixed by that very patch, i. e. adding one :-) > > So it seems to me we are misunderstanding each other here? From my > end, all is well once resolvconf gets the systemd unit.
Yes, I completely misunderstood you. I thought your comment "no from my side" meant you were not ok, instead of no complaints. Sorry about that. Best, -- Cameron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
