From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?B?Um9ndXTEl3MgU3Bhcm51b3Rvcw==?= <rogutes@googlemail.com>
Date: Mon, 05 Mar 2012 11:08:00 +0000
Subject: Re: A rule gets applied only after running `udevadm test`
Message-Id: <jj26qt$q72$1@dough.gmane.org>
List-Id: <linux-hotplug.vger.kernel.org>
References: <jj0l5p$kl$1@dough.gmane.org>
In-Reply-To: <jj0l5p$kl$1@dough.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
To: linux-hotplug@vger.kernel.org

On 2012.03.05 01:48, Kay Sievers wrote:
> On Sun, Mar 4, 2012 at 22:00, Rogut=C4=97s Sparnuotos<rogutes@googlemail.=
com>  wrote:
>> I have 2 custom rules to rename network interfaces:
>>
>> SUBSYSTEM=3D"net", ACTION=3D"add", ATTR{address}=3D"00:1f:d0:5a:7d:48",
>> NAME=3D"eth_int"
>> SUBSYSTEM=3D"net", ACTION=3D"add", ATTR{address}=3D"00:50:22:e9:7d:09",
>> NAME=3D"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=20
Archlinux's initscripts have
   udevadm trigger --action=ADd --type=3Dsubsystems
   udevadm trigger --action=ADd --type=DEvices