<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 9, 2014 at 7:22 PM, Lennart Poettering <span dir="ltr"><<a href="mailto:mzerqung@0pointer.de" target="_blank">mzerqung@0pointer.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, 09.10.14 18:59, Elad Alfassa (<a href="mailto:elad@fedoraproject.org">elad@fedoraproject.org</a>) wrote:<br>
<br>
> On Thu, Oct 9, 2014 at 6:46 PM, Lennart Poettering <<a href="mailto:mzerqung@0pointer.de">mzerqung@0pointer.de</a>><br>
> wrote:<br>
><br>
> > > - no integration with NetworkManager, unaware of NTP servers from<br>
> > > DHCP<br>
> ><br>
> > Well it is not hooked up with NM but it *is* hooked up with networkd<br>
> > via its native API, and hence even picks up manually configured<br>
> > per-connection NTP servers.<br>
><br>
> I really want to see networkd in Fedora by default. What are the<br>
> plans/timeframe for that? How does it play together with NM?<br>
<br>
</span>networkd doesn't do WLAN really (well, you can run it together with<br>
wpa_supplicant, and configure both individually, but that's not<br>
particularly nice. networkd currently also lacks a bus interface<br>
(since it runs in early boot + initrd, where dbus-daemon is not<br>
available currently), and that stalls on kdbus.<br>
<br>
networkd as it is right now is great for servers, or the initrd, to<br>
run inside containers or for a lot of the embedded usecases. It's not<br>
suitable for the desktop usecase.<br>
<div class="HOEnZb"><div class="h5"><br>
Lennart<br>
<br>
--<br>
Lennart Poettering, Red Hat<br>
--<br>
desktop mailing list<br>
<a href="mailto:desktop@lists.fedoraproject.org">desktop@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/desktop" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/desktop</a></div></div></blockquote></div><br></div><div class="gmail_extra">Okay, got it.<br></div><div class="gmail_extra">Speaking of the far future, will networkd ever be suitable for desktop usecases? Will NM interface with it in some way to provide the missing functionality?<br></div><div class="gmail_extra">If networkd is not good (yet?) for desktop, and timesyncd needs it for a functionality that is important for many people, then I guess timesyncd will need to learn to work with NetworkManager if you want to have it in Workstation (or convince people that DHCP-provided NTP servers are not something they want to support).<br><br></div><div class="gmail_extra">For the F21 timeframe I think it would be useful to patch timedatectl to use chrony. Do you agree?<br clear="all"></div><div class="gmail_extra"><br>-- <br><div dir="ltr">-Elad Alfassa.</div>
</div></div>