Bug#542095: disabling N-M

[Adam Borowski]

On Wed, Oct 19, 2011 at 11:52:43AM +0200, Michael Biebl wrote:
> Am 19.10.2011 11:11, schrieb Adam Borowski:
> > Even after purge, you end up with everything replaced by empty files with
> > nothing but "# Generated by NetworkManager\n\n" in them.
> > 
> 
> bullshit.

I just tried it again: restored everything to a snapshot from 2011-10-14,
dist-upgraded, stopped n-m.  This is the new content of /etc/resolv.conf, it
stays this way even after purging.  Starting n-m again doesn't restore the
file, either -- it keeps getting replaced by this exact content (almost, I
quoted one \n too much), which makes networking pretty useless.


The old file had this (including commented-out lines):
.-====[ resolv.conf ]
domain angband.pl
search angband.pl
nameserver 2001:6a0:118::1
#nameserver 10.0.1.1
#nameserver 8.8.8.8
`----

I don't expect n-m to override resolver config on a system with a static
address at all, but there's both working DHCP and radv with RDNSS in the
network, in case it wanted to consult either.


So, my point stands: it is not enough to install and disable n-m as it
tramples the configuration before you have a chance to stop it.

-- 
1KB		// Yo momma uses IPv4!