From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Filtering drivers and module events
Date: Sun, 03 Jul 2005 11:59:04 +0000 [thread overview]
Message-ID: <20050703115904.GA29752@vrfy.org> (raw)
In-Reply-To: <20050703112530.GA8164@wonderland.linux.it>
On Sun, Jul 03, 2005 at 01:25:30PM +0200, Marco d'Itri wrote:
> # do not call hotplug.d and dev.d for "drivers" and "module" events
> SUBSYSTEM="drivers", OPTIONS="last_rule"
> SUBSYSTEM="module", OPTIONS="last_rule"
>
> # udev_run_hotplugd, udev_run_devd ...
>
> Why are the last_rule rules not working? I see that the events are still
> being logged by the logger script in hotplug.d/default/.
On "non-device events" udev reads only rules with RUN keys defined, so it
ignores the OPTIONS. I will correct this now.
In the meantime, you may use RUN:="" to clear the list and make the RUN
key unchangeable by later rules.
Thanks,
Kay
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2005-07-03 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 11:25 Filtering drivers and module events Marco d'Itri
2005-07-03 11:59 ` Kay Sievers [this message]
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=20050703115904.GA29752@vrfy.org \
--to=kay.sievers@vrfy.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).