2014-04-21 16:18 GMT+02:00 Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx>:
That might work: note that it still means that any applications depending on NetworkManager APIs are unusable on the cloud images: I suppose you don't want much intelligence inside the cloud image anyway, so that's not a blocker (but would be a blocker for any non-cloud uses).On Thu, Apr 17, 2014 at 10:30:48PM +0200, Miloslav Trmač wrote:> it's entirely new to Fedora *in F21*.
> Writing too fast... you were actually arguing for a situation "2 used by
> default + 1 used but not used by default" I think. In that case your
> argument is right but it's my turn to not accept your premise :) networkd
> was introduced in systemd-209, and F20 ships with -208, I.e. it has never
> shipped in a Fedora release, so it is not "1 used but not used by default";
Okay, fair enough. :)
On reflecting, I think a generator which reads ifcfg-* format, and
ifup/ifdown compat scripts should probably be considered hard prerequisites
for using systemd-networkd by default. That gives a common "language", keeps
current tooling working, and makes an easy path for a user to switch if a
particular need isn't covered.
Mirek
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
