On Thu, 17.04.14 01:24, Miloslav Trmač (mitr@xxxxxxxx) wrote: > I don't think we can, or should, have three separate network configuration > systems in Fedora at the same time. We already know how long and painful > the migration to NetworkManager has been—and AFAICS networkd doesn't > support any of the icfg-* files, unlike NetworkManager, so it would mean a > *more* painful migration. Note that it should be relatively straight-forward to implement a generator (even in shell...) that generates native systemd-networkd configuration snippets from ifcfg files at runtime (or upgrade-time), similar to how we convert fstab or crypttab to systemd units. With that in place it a smooth transition from the old networking scripts to networkd should be possible. That said, there are some things ifcfg supports (ISDN, IPX, ...) that we'll never support in networkd, hence we couldn't claim 100% compat with such a scheme. > environment (say, everything via DHCP, no VPNs, no IPSec, no bridges, > nothing else), and telling both users and application developers not to Note that networkd supports static configuration, bridges and some forms of tunnels just fine. Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
