Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-07 Thread Martin Wuertele
* Andrew Shadura [2013-01-07 09:15]: > On Mon, 07 Jan 2013 08:42:40 +0100 > Tollef Fog Heen wrote: > > > My suggestion would be to, over the jessie cycle, deprecate (but still > > read) /etc/network/interfaces and for jessie+1 just drop the file and > > only use the .d directory. > > I don't t

Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-07 Thread Tollef Fog Heen
]] Andrew Shadura > > Also, your fix doesn't actually solve the RC bug either: > > Well, it does. No, it doesn't. You're still recreating /etc/network/interfaces if it's not there. Removing a file is a change which must be preserved. -- Tollef Fog Heen UNIX is user friendly, it's just picky

Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-07 Thread Andrew Shadura
Hello, On Mon, 07 Jan 2013 08:42:40 +0100 Tollef Fog Heen wrote: > > I'd like to hear opinions on this idea. > I think you should just get a wheezy-ignore tag from the release team > and solve this properly for jessie. > Also, your fix doesn't actually solve the RC bug either: Well, it does.

Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-06 Thread Tollef Fog Heen
]] Andrew Shadura > I'd like to hear opinions on this idea. I think you should just get a wheezy-ignore tag from the release team and solve this properly for jessie. Also, your fix doesn't actually solve the RC bug either: You Must Preserve All Admin Changes in /etc. Not just the ones you thi

Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-06 Thread Chow Loong Jin
On 07/01/2013 13:23, Petter Reinholdtsen wrote: > You are wrong. Debian Edu also expect /etc/network/interfaces to have > the complete network setup. What package is that? -- Kind regards, Loong Jin signature.asc Description: OpenPGP digital signature

Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-06 Thread Petter Reinholdtsen
[Andrew Shadura] > Well, yes, I forgot about NM. Actually, as far as I know, it's the only > tool affected, everything else either doesn't care to read /e/n/i, or > is already fixed, or this difference is irrelevant and doesn't need to > be urgently patched. Correct me if I'm wrong. You are wrong

Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-06 Thread Andrew Shadura
Hello, On Mon, 07 Jan 2013 02:31:30 +0100 Michael Biebl wrote: > > There are probably more of them, but finding them all is left as an > > exercise for the reader. > You can at least add network-admin from gnome-system-tools to the > list, or external config tools like webmin. > Not counting an

Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-06 Thread Michael Biebl
On 07.01.2013 02:07, Cyril Brulebois wrote: > There are probably more of them, but finding them all is left as an > exercise for the reader. You can at least add network-admin from gnome-system-tools to the list, or external config tools like webmin. Not counting any local scripts written by sysad

Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-06 Thread Andrew Shadura
Hello, On Mon, 07 Jan 2013 00:12:29 +0100 Michael Biebl wrote: > > ifupdown to add that support), so anyone can split their network > > config into small chucks and place them > > under /etc/network/interfaces.d — it's not done by default, > > however, yet. > Please keep in mind that such a set

Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-06 Thread Cyril Brulebois
Andrew Shadura (07/01/2013): > On Mon, 07 Jan 2013 08:50:26 +0800 > Chow Loong Jin wrote: > > > > Please keep in mind that such a setup will break existing tools and > > > scripts, which rely on finding the interface definitions in /e/n/i. > > > E.g. the ifupdown plugin in NetworkManager doesn't

Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-06 Thread Andrew Shadura
Hello, On Mon, 07 Jan 2013 08:50:26 +0800 Chow Loong Jin wrote: > > Please keep in mind that such a setup will break existing tools and > > scripts, which rely on finding the interface definitions in /e/n/i. > > E.g. the ifupdown plugin in NetworkManager doesn't know anything > > about such a so

Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-06 Thread Chow Loong Jin
On 07/01/2013 07:12, Michael Biebl wrote: > Please keep in mind that such a setup will break existing tools and > scripts, which rely on finding the interface definitions in /e/n/i. > E.g. the ifupdown plugin in NetworkManager doesn't know anything about > such a source directive. > If you are goin

Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-06 Thread Andrew Shadura
Hello, On Mon, 07 Jan 2013 00:12:29 +0100 Michael Biebl wrote: > On 06.01.2013 23:48, Andrew Shadura wrote: > > First of all, I'd like to remind that ifupdown supports source > > directive since very long ago (it was actually my very first patch > > to > I've checked the squeeze version of ifup

Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-06 Thread Cyril Brulebois
Hello, Andrew Shadura (06/01/2013): > While there are various opinions on the question raised in that bug, I > don't agree that this is a policy violation, but I propose to resolve > this by enabling the usage of 'source' directive in the default > configuration, and moving 'lo' interface descrip

Re: Ifupdown, loopback interface, /etc/network/interfaces.d

2013-01-06 Thread Michael Biebl
Hi, On 06.01.2013 23:48, Andrew Shadura wrote: > First of all, I'd like to remind that ifupdown supports source > directive since very long ago (it was actually my very first patch to I've checked the squeeze version of ifupdown, and it doesn't seem to support that directive. So calling it suppor