When I upgraded systemd sometime in January to 197, I opt in the network renaming. I did as suggested from arch-dev-public through removing dummy file "/etc/udev/rules.d/80-net-name-slot.rules".
Since this time eth0 was and is never renamed due to error message: "error changing net interface name eth0 to enp, Device or Resource busy". From time to time I experience the same with wlan0; "error changing net interface name wlan0 to wlp3so, Device or Resource busy".
My netcfg.service contains
which is necessary to wait for wlp3s0 becoming ready. I did not find anything close on google or here for my problem.
Last edited by kodiak (2013-03-25 12:17:05)
I have never seen a report of such an issue before. Have you asked on the systemd mailing list? I am pretty certain that they would likely be interested in hearing about this.
Alright, I just sent it to systemd-bugs(a)lists.freedesktop.org. and will report back if I get something.
The reply I got:
> Netcfg should better listen to udev events and not kernel network
> netlink itself, when it watches for new devices. Or you need to make
> sure netcfg is started after udev is ready and has renamed the
> It seems it goes out on its own and claims the interfaces right after
> they show up in the kernel, which makes them busy before udev has
> renamed them.
I replaced netcfg with netctl. Netcfg officially does not play well with systemd. I also removed the dhcpcd. All problems are gone. Thx!