Hello, On 27 November 2014 at 16:07, Cyril Brulebois <k...@debian.org> wrote: > Am I correct in assuming that such an /e/n/i file with an older ifupdown > doesn't cause any issues? I'd also like to know whether it can cause any > issues with other tools parsing/using/abusing /e/n/i (n-m notably).
It does. Actually, I've just checked, both current n-m and ifupdown from wheezy support only 'source' directive. The difference between source and source-directory is that the second form doesn't need a glob mask to be specified, as it uses run-parts-style matching. In that case, maybe it's better to change this to: source /etc/network/interfaces.d/* (The other utility parsing interfaces is guessnet, it's current version also supports "source" keyword only.) > Why the first question: just in case we end up backporting netcfg at > some point. Why the second question: we have code to do this or that > depending on whether n-m is getting installed within d-i, but it could > be installed afterwards, so I'd be nice if adding this line didn't cause > any issues later. -- Cheers, Andrew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org