On 2012.03.05 01:48, Kay Sievers wrote:
On Sun, Mar 4, 2012 at 22:00, Rogutės Sparnuotos<rogutes@xxxxxxxxxxxxxx> wrote:
I have 2 custom rules to rename network interfaces:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:1f:d0:5a:7d:48",
NAME="eth_int"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:50:22:e9:7d:09",
NAME="eth1"
But they aren't triggered on boot (although another rule from the same
file is applied). Now if I run
$ udevadm test --action=add \
/sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/net/eth1
$ udevadm test --action=add \
/sys/devices/pci0000:00/0000:00:1e.0/0000:05:01.0/net/eth0
the interfaces get renamed. What could I do to make these rules work on
boot? Could this be an udev bug caused by a module-less kernel?
Does:
udevadm trigger --action=add
make it work the same way as running 'udevadm test'? Then it's more
likely an issue with your init system/bootup logic and not with udev.
Kay
Thank you for the hint, you were right.
IIRC, a mere `udevadm trigger` used to work and now I see that
Archlinux's initscripts have
udevadm trigger --action=add --type=subsystems
udevadm trigger --action=add --type=devices
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
