Hi, Having watched the discussion over the past week or so, I'm left with a few questions:
1) what is lacking in other userspace solutions (NetworkManager, ConnMan, wicked, initscripts, etc) that requires yet-another-network-daemon? 2) do you expect that systemd-networkd will grow to include bridge, bond, and team setup? how about other "enterprise"/"server" interface types like macvlan/vtap, tun/tap, gre, vxlan, ovs, etc? All these are enterprise things that typically won't change during a specific bootup, but which static "servers" increasingly use. If you don't expect these to be supported, why not? 3) Is there expected to be D-Bus interfaces for controlling or monitoring the network interfaces and configuration data? If not, why not? Thanks, Dan _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
