From: "Rogutės Sparnuotos" <rogutes@googlemail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: A rule gets applied only after running `udevadm test`
Date: Mon, 05 Mar 2012 11:08:00 +0000 [thread overview]
Message-ID: <jj26qt$q72$1@dough.gmane.org> (raw)
In-Reply-To: <jj0l5p$kl$1@dough.gmane.org>
On 2012.03.05 01:48, Kay Sievers wrote:
> On Sun, Mar 4, 2012 at 22:00, RogutÄ—s Sparnuotos<rogutes@googlemail.com> 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 --actiond \
>> /sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/net/eth1
>>
>> $ udevadm test --actiond \
>> /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 --actiond
> 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 --actiond --type=subsystems
udevadm trigger --actiond --typeÞvices
next prev parent reply other threads:[~2012-03-05 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 21:00 A rule gets applied only after running `udevadm test` Rogutės Sparnuotos
2012-03-04 23:48 ` Kay Sievers
2012-03-05 11:08 ` Rogutės Sparnuotos [this message]
2012-03-05 16:38 ` Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='jj26qt$q72$1@dough.gmane.org' \
--to=rogutes@googlemail.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.