Hi Marco,
Sorry for the delay in my response. I tried s/ATTR/SYSFS/ on my eth0
rule, removing the new one, and it worked perfectly at next reboot (as
expected).
I left the rules for the other devices unchanged so I can verify that
the SYSFS-ATTR change is correctly performed on next
On Apr 25, Antonio Fiol anto...@fiol.es wrote:
ATTR and an added ATTR{type}==1). If I understand this correctly, the
missing ATTR{type} would match any ATTR{tpye} so it's not that. Then
it must be that udev stopped understanding the SYSFS syntax ??
Interesting, SYSFS{} is supposed to be
Package: udev
Version: 0.141-1
Severity: important
After upgrading udev from 0.125-7 to 0.141-1 with the rest of available
upgrades, and rebooting, my eth0 (plain ethernet, not wireless) got
renamed to eth3, and thus stopped working.
There seems to have been a change in udev rules checking,
Same here, using kernel 2.6.29-1-686 from unstable.
Old entry in /etc/udev/rules.d/70-persistent-net.rules was
# PCI device 1039:0900 (sis900)
ACTION==add, SUBSYSTEM==net, DRIVERS==?*,
SYSFS{address}==00:0a:e6:d5:5f:99, NAME=eth0
which led, approximately due to the fact that the SYSFS entry is
4 matches
Mail list logo
