On Tue, 2015-05-26 at 18:54 +0200, Marco d'Itri wrote: > On May 26, Andrew Shadura <andrewsh@debian.org> wrote: > > > In current state ifupdown is probably good enough for what it is used > > for, except a few bugs. For advanced uses, it seems, Python-based > > ifupdown2 may become a good alternative in the future, and some simpler > > things wicd, NM and systemd-network probably do things just well. > Thank you for your work in the last few years, it made ifupdown more > bearable... > > Maybe this is the right time to think hard about what we should do about > network configuration: Red Hat proposes NM for both desktop and servers > (even if they still support their legacy shell scripts), and in stretch > we will have a featureful systemd-networkd. > > Maybe it's just me, but I do not like much the idea of choosing > a Python-based program as the default network configuration system. > For a start it would make python transitively important. I do, it's about time we had a decent scripting language in the base system. Ben. -- Ben Hutchings Unix is many things to many people, but it's never been everything to anybody.
Attachment:
signature.asc
Description: This is a digitally signed message part