Re: ifupdown2: debconf followup
On Mon, Aug 01, 2016 at 12:31:14PM +0200, Marco d'Itri wrote:
> On Aug 01, Guus Sliepen <email@example.com> wrote:
> > I see one big drawback of ifupdown2, and that is that it's written in
> > Python. Nothing wrong with that language, but it means it pulls in
> > dependencies which a minimal install currently doesn't require, which is
> > not so nice for people running small VMs or embedded devices.
> Indeed. I strongly believe that this is bad enough to disqualify it as
> the default implementation.
> We should also think hard about switching to a new default since
> currently many other major distributions are moving to NetworkManager
> and/or systemd-networkd (which nowadays is usable, works well for
> simpler use cases and will be installed on every Debian system anyway).
For the latter, "installable only with a certain init implementation, and
not portable to any kernel but Linux" doesn't say "every Debian system" to
An imaginary friend squared is a real enemy.