Re: [systemd-devel] renamed link
Please don't top-post. Also try no to spam the mailing list with multiple messages… On Fri, May 19, 2017 at 04:09:08PM +0200, Pascal wrote: > and I'm running/testing on version 232 > > 2017-05-19 16:06 GMT+02:00 Pascal: > > > note that it's about version 210 (year 2014) > > > > 2017-05-19 16:04 GMT+02:00 Pascal : > > > >> 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 ? Yes. Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] renamed link
note that it's about version 210 (year 2014) 2017-05-19 16:04 GMT+02:00 Pascal: > 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 : > >> 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
Re: [systemd-devel] renamed link
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: > 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
Re: [systemd-devel] renamed link
and I'm running/testing on version 232 2017-05-19 16:06 GMT+02:00 Pascal: > note that it's about version 210 (year 2014) > > 2017-05-19 16:04 GMT+02:00 Pascal : > >> 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 : >> >>> 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
Re: [systemd-devel] renamed link
On Thu, May 18, 2017 at 11:51:25PM +0200, Pascal wrote: > hi, > > I rename my network cards (with udev rule or systemd .link file) in order > to use their new name everywhere else: sysctl, systemd-networkd, samba, > iptables, etc ... > > unfortunately, sysctl and systemd-networkd are started before the name > change and the defined configurations are not applied to my cards :-( > > is there a way to start the name change before the rest ? it would even > seem more "logical"... That's not possible. Network cards can appear at any time: usb cards can be detected slowly, and hardware can be plugged in at any time, etc. > actualy, I must restart systemd-networkd service and replay sysctl :-( sysctl settings for a network interface can be applied after the interface is detected, see 99-systemd.rules. Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel