I set up network renaming in /etc/udev/rules.d/10-local.rules like this: KERNEL=="eth*", SYSFS{address}=="00:13:77:ab:cd:ef", NAME="lan" KERNEL=="eth*", SYSFS{address}=="00:13:02:ab:cd:ef", NAME="wlan" (as this is the recommended method in net.example). Since the update to udev-100 (and still in -r1), this doesn't have an effect anymore. At least not on boot. So the network scripts don't work, because there are no interfaces called lan and wlan (but eth0 and eth1). When I call udevstart manually, it works though... (?) By the way: This is the 100th udev release, and perhaps the 100th bug which breaks something...
Try ATTR{address}=="00:13:77:ab:cd:ef", no idea why the backwards compatibility thing doesn't work. :/
Hm... now it also works with SYSFS - I deleted /etc/udev/rules.d/* except 10-local.rules before installing udev-100-r2 again, I think there were some old rules that haven't been deleted due to config-protect. I can't reproduce this behaviour anymore, so I'm marking this bug as invalid. Let's see if somebody else runs into that problem... Cheers, Patrick.
(In reply to comment #2) > Hm... now it also works with SYSFS - I deleted /etc/udev/rules.d/* except > 10-local.rules before installing udev-100-r2 again, I think there were some old > rules that haven't been deleted due to config-protect. > > I can't reproduce this behaviour anymore, so I'm marking this bug as invalid. > Let's see if somebody else runs into that problem... I'd recommend dropping your 10-local.rules file for network devices, and let the scripts create a rule for the network devices automatically. Delete the file (or move it somewhere else, then reboot or just load the network module. Then look in the 70-persistent-net.rules file for the new rules for that network device. If you don't like the name, change it there.
(In reply to comment #3) > I'd recommend dropping your 10-local.rules file for network devices, and let > the scripts create a rule for the network devices automatically. Delete the > file (or move it somewhere else, then reboot or just load the network module. > Then look in the 70-persistent-net.rules file for the new rules for that > network device. If you don't like the name, change it there. I thought about that. But you know, I like to wrap up my customisations in one place, which is then easily maintainable. I prefer not to change a couple of .rules files on every update and every system.
