<div dir="ltr">note that it's about version 210 (year 2014)<br></div><div class="gmail_extra"><br><div class="gmail_quote">2017-05-19 16:04 GMT+02:00 Pascal <span dir="ltr"><<a href="mailto:patatetom@gmail.com" target="_blank">patatetom@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>hi Lennart,<br><br></div>I read this on <a href="https://coreos.com/blog/intro-to-systemd-networkd.html" target="_blank">https://coreos.com/blog/intro-<wbr>to-systemd-networkd.html</a> :<br><br><i>"Also, we should note that networkd is only made aware of new network devices after udev has applied its low-level settings to them, so we can safely match on the new MACAddress and Name that udev has set for our device."</i><br><br><span id="m_4951985675270996607gmail-result_box" class="m_4951985675270996607gmail-" lang="en"><span>if I understand correctly, systemd-networkd operates in a second time, so that we can</span></span><span id="m_4951985675270996607gmail-result_box" class="m_4951985675270996607gmail-" lang="en"><span><span id="m_4951985675270996607gmail-result_box" class="m_4951985675270996607gmail-" lang="en"><span> </span></span><span id="m_4951985675270996607gmail-result_box" class="m_4951985675270996607gmail-" lang="en"><span><span id="m_4951985675270996607gmail-result_box" class="m_4951985675270996607gmail-" lang="en"><span> safely</span></span></span></span> use</span></span><span id="m_4951985675270996607gmail-result_box" class="m_4951985675270996607gmail-" lang="en"><span><span id="m_4951985675270996607gmail-result_box" class="m_4951985675270996607gmail-" lang="en"><span> </span></span>the new name given by udevd.<br><span id="m_4951985675270996607gmail-result_box" class="m_4951985675270996607gmail-" lang="en"><span>I can't find this information in the systemd / udevd documentation : is this information correct ?<br><br></span></span></span></span></div><span id="m_4951985675270996607gmail-result_box" class="m_4951985675270996607gmail-" lang="en"><span><span id="m_4951985675270996607gmail-result_box" class="m_4951985675270996607gmail-" lang="en"><span>regards, lacsaP.<br></span></span></span></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2017-05-19 11:23 GMT+02:00 Lennart Poettering <span dir="ltr"><<a href="mailto:lennart@poettering.net" target="_blank">lennart@poettering.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Fri, 19.05.17 09:02, Pascal (<a href="mailto:patatetom@gmail.com" target="_blank">patatetom@gmail.com</a>) wrote:<br>
<br>
> is udev responsible for linking the system with the hardware?<br>
> in this case, why does renaming not take place at the very first level ?<br>
> which would make new name available for all other levels...<br>
<br>
</span>renaming takes place as part of the udev rule processing, and clients<br>
listeing to udev events will be notified only after the renaming took<br>
place.<br>
<span class="m_4951985675270996607HOEnZb"><font color="#888888"><br>
Lennart<br>
<br>
--<br>
Lennart Poettering, Red Hat<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>