[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#770078: ifupdown: interfaces(5) falsely claims that interfaces.d is included by default on new installs

Control: tag -1 patch

Andrew Shadura <andrew@shadura.me> (2014-11-27):
> Hello,
> On 27 November 2014 at 15:26, Cyril Brulebois <kibi@debian.org> wrote:
> > You probably want to look at debcheckout netcfg; write_interface.c is
> > most likely the interesting one, along with base-installer.d/40netcfg
> > and finish-install.d/55netcfg-copy-config which you may want to check
> > as well since they toy with/copy around /e/n/i.
> Thanks. It seems modifying write_interface.c alone should be enough.

That would have been my first guess indeed.

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).

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.


Attachment: signature.asc
Description: Digital signature

Reply to: