Marco d'Itri <m...@linux.it> wrote:
I do not expect systemd-networkd taking over NM when an interaction
with
a GUI is needed, but OTOH I see no reason to use NM on servers when
(recent) systemd-networkd is available, since it is much leaner.
In the current state of affairs, that’s probably true. In the long run,
however, I don’t think it’s a good idea to have two overlapping
solutions to do the same thing.
We need to answer those two questions:
- what can systemd-networkd do that NM cannot? e.g. initrd support
- what can NM do that networkd cannot? e.g. delegating interface
management to users, what about scripting, infiniband, complex
authentication schemes…
I’d really like to see some convergence on this front. Systemd-networkd
could do the actual job of managing the network, but providing NM the
necessary interfaces to delegate whatever is needed to the user.
--
Joss
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/1432731143.2920.121.ca...@dsp0698014.postes.calibre.edf.fr
