Am 18.02.2015 um 21:12 schrieb Mantas Mikulėnas:
On Wed, Feb 18, 2015 at 10:10 PM, Giancarlo Razzolini <[email protected] <mailto:[email protected]>> wrote:But, in both cases, I need to flush the interface and set it status to DOWN before the initramfs handle the init to systemd. I took a look at the: src/udev/udev-builtin-net_id.c file and it seems indeed that it won't rename an interface that is UP. An error is shown in the journalctl by udev saying the interface couldn't be renamed. I do handle with this already, but I was wondering if systemd-udevd shouldn't rename the interface regardless of it state, since the early userspace It's so much not that udev won't do this – the kernel actually won't let it to: # ip link set eth0 up # ip link set eth0 name fred0 RTNETLINK answers: Device or resource busy
and hopefully that keeps this way * configurations rely on eth0, eth1... exists * they are sane and fine * firewall rules may depend on them
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
