Bug#836016: netcfg: Drop unnecessary loopback config in /etc/network/interfaces

On 12/30/2016 12:19 AM, Philipp Kern wrote: > it needs to, yes. Otherwise you end up with the interface being > unmanaged from n-m, despite the n-m snippet having been written. I > suppose what we could do is just empty it out. At least trying that out > was successful for me. I also tested the

Bug#836016: netcfg: Drop unnecessary loopback config in /etc/network/interfaces

Hi, On 08/30/2016 10:17 AM, Martin Pitt wrote: > Please drop it as this is unnecessary extra parsing work at boot. I > attach an untested (only build-tested) initial patch. The main thing > I'm not sure about is whether this actually needs to clear > /etc/network/interfaces when NetworkManager is

Bug#836016: netcfg: Drop unnecessary loopback config in /etc/network/interfaces

Hi Martin, Martin Pitt (2016-08-30): > Package: netcfg > Version: 1.139 > > Hello, > > netcfg still configures a "lo" (loopback) device in > /etc/network/interfaces, although this hasn't been necessary since > ifupdown 0.7.41 in 2013: > > >

Bug#836016: netcfg: Drop unnecessary loopback config in /etc/network/interfaces

Package: netcfg Version: 1.139 Hello, netcfg still configures a "lo" (loopback) device in /etc/network/interfaces, although this hasn't been necessary since ifupdown 0.7.41 in 2013: https://anonscm.debian.org/cgit/collab-maint/ifupdown.git/commit/?id=2127aa19d9416 Please drop it as this is