From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sun, 03 Jul 2005 11:59:04 +0000 Subject: Re: Filtering drivers and module events Message-Id: <20050703115904.GA29752@vrfy.org> List-Id: References: <20050703112530.GA8164@wonderland.linux.it> In-Reply-To: <20050703112530.GA8164@wonderland.linux.it> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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_id492&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