<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2014-04-21 16:18 GMT+02:00 Matthew Miller <span dir="ltr"><<a href="mailto:mattdm@fedoraproject.org" target="_blank">mattdm@fedoraproject.org</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Thu, Apr 17, 2014 at 10:30:48PM +0200, Miloslav Trmač wrote:<br>
> Writing too fast... you were actually arguing for a situation "2 used by<br>
> default + 1 used but not used by default" I think. In that case your<br>
> argument is right but it's my turn to not accept your premise :) networkd<br>
> was introduced in systemd-209, and F20 ships with -208, I.e. it has never<br>
> shipped in a Fedora release, so it is not "1 used but not used by default";<br>
</div>> it's entirely new to Fedora *in F21*.<br>
<br>
Okay, fair enough. :)<br>
<br>
On reflecting, I think a generator which reads ifcfg-* format, and<br>
ifup/ifdown compat scripts should probably be considered hard prerequisites<br>
for using systemd-networkd by default. That gives a common "language", keeps<br>
current tooling working, and makes an easy path for a user to switch if a<br>
particular need isn't covered.<br></blockquote><br></div>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 <i>would</i> be a blocker for any non-cloud uses).<br>
</div><div class="gmail_extra"> Mirek<br></div></div>