Hi Marcel
On 6/19/19 5:14 AM, Marcel Holtmann wrote:
Hi Johann,
And frankly IP configuration needs to move into the network technology daemons
like iwd for example.
What's the argument here for that reasoning as in why not consolidate all
network configuration ( ethernet/wifi/vrrp/vpn's etc.. ) to a single place (
networkd )?
Why do you want to keep the network configuration and management space
fragmented ( as opposed to consolidated ) ?
because that is what the standards are doing. WiFi for example can transport
the IP address inline. You just need to confirm it with DHCP later. It is how
the standards are written that you want to really move DHCP one level down. The
same applies to cellular connections where all the IP level configuration comes
via the cellular network and not DHCP.
I see that's what the standard specifies but why not merge IWD/EAD with
systemd ( systemd-wirelessd/systemd-etherauthd and or tightly integrate
it with networkd )?
What are the benefits you see keeping these as separated components as
opposed to be part of the service management framework for consolidated
core/baseOS
The IWD/EAD are Linux only projects right ( as in it's not going to be
replacing wpa supplicant on other *nix like for example the BSD stack )?
Regards
Jóhann B.
_______________________________________________
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
