Bdale Garbee <[email protected]> writes: > Miroslaw Baran <[email protected]> writes:
>> Quoting the author of networkd: > If the existence of this code helps reduce the number of ad-hoc scripts > in the world as the author hopes, then it may add some value. However, > in the Debian context, systemd-networkd seems at first glance to be > purely duplicative? It sounds like it does the same thing as ifupdown for static, simple networks, but doesn't include the more complex stuff. It's an interesting option to have available. I could see possibly using it on servers that don't care about any of the DHCP or wireless complexity, just to have simpler code paths. But I suspect we'd want to leave it turned off by default in Debian for the forseeable future, at least as long as we have active ifupdown maintainers who are still interested in keeping that system working. The transition to something else would be annoying, and it's not clear there would be much benefit. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
