Today was the day I decided to update my gentoo systems. After merrily installing udev-200, removing all files from /etc/udev/rules.d and rebooting both systems nothing worked. Well to be honest, I should say very little.

Here is what I did to get around the issues:

System 1:
The first problem was that all network interfaces were renamed. Wanting to restore sensibility I had to create /etc/udev/rules.d/70-persistent-net.rules which mapped the MAC address of the nic to the name

which I promptly misread as udev-mount. After disabling udev-mount I was getting errors

Quote:

openpty: No such file or directory

The solution was of course to re-enable udev-mount.

It would have been very helpful if the upgrade instruction made it clearer that the network interface name should be changed, although I am not really sure this is the case. However now I have both systems working again, and all seems good.

System 1:
The first problem was that all network interfaces were renamed. Wanting to restore sensibility I had to create /etc/udev/rules.d/70-persistent-net.rules which mapped the MAC address of the nic to the name

This fixed the issue on that system, but I have no idea if this is the correct or best way to deal with it.

That is the wrong solution. As documented in the news, if you want to disable the renaming behavior and use kernel-chosen names, you should create 80-net-name-slot.rules to override the silly rename behavior. If you want to disable the renaming and use custom names, you should not use names in the eth prefix, because modern udev removed support for that.

Yes, using the kernel-assigned names by default would be the reasonable choice, since most people lack the hardware to benefit from the new scheme. However, to ensure that users with complex topologies discover the feature and begin using it, everyone else gets to suffer through having it enabled by default.

STOP using eth0 and eth1 - those are confusing names, the worst that you can choose for custom rules, because it's not obvious whether your rules have taken effect, or whether udev's default random naming has kicked in, if udev changes in the future.