and I'm running/testing on version 232 2017-05-19 16:06 GMT+02:00 Pascal <patate...@gmail.com>:
> note that it's about version 210 (year 2014) > > 2017-05-19 16:04 GMT+02:00 Pascal <patate...@gmail.com>: > >> hi Lennart, >> >> I read this on https://coreos.com/blog/intro-to-systemd-networkd.html : >> >> *"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."* >> >> if I understand correctly, systemd-networkd operates in a second time, so >> that we can safely use the new name given by udevd. >> I can't find this information in the systemd / udevd documentation : is >> this information correct ? >> >> regards, lacsaP. >> >> 2017-05-19 11:23 GMT+02:00 Lennart Poettering <lenn...@poettering.net>: >> >>> On Fri, 19.05.17 09:02, Pascal (patate...@gmail.com) wrote: >>> >>> > is udev responsible for linking the system with the hardware? >>> > in this case, why does renaming not take place at the very first level >>> ? >>> > which would make new name available for all other levels... >>> >>> renaming takes place as part of the udev rule processing, and clients >>> listeing to udev events will be notified only after the renaming took >>> place. >>> >>> Lennart >>> >>> -- >>> Lennart Poettering, Red Hat >>> >> >> >
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
