From: "Kevin P. Fleming" <kpfleming@starnetworks.us>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev: add rule based program execution
Date: Tue, 29 Mar 2005 15:20:22 +0000 [thread overview]
Message-ID: <42497236.8030704@starnetworks.us> (raw)
In-Reply-To: <20050329145403.GA16544@vrfy.org>
Kay Sievers wrote:
> On my box I've removed all scripts from /etc/dev.d and replaced it with
> following rules in the main rules file:
>
> ACTION="add", SUBSYSTEM="sound", HOTPLUG="/etc/udev/scripts/alsa.dev"
> ACTION="add", KERNEL="fd*", HOTPLUG="/etc/udev/scripts/MAKEDEV.dev"
> KERNEL="ttyUSB*", HOTPLUG="/etc/udev/scripts/test-serial-device"
> SUBSYSTEM="tty", OPTIONS="last_rule"
> HOTPLUG="/etc/udev/scripts/pam_console.dev"
> HOTPLUG="/etc/udev/sripts/log.dev"
>
> This cuts down the execution-time of udevstart from ~10 seconds to ~2
> seconds, cause the hundreds of tty events will not call any script.
Very, very nice! Simple, logical, understandable, usually means it's the
right solution :-)
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&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
next prev parent reply other threads:[~2005-03-29 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 14:54 [PATCH] udev: add rule based program execution Kay Sievers
2005-03-29 15:20 ` Kevin P. Fleming [this message]
2005-03-30 7:39 ` Roman Kagan
2005-03-30 12:05 ` Kay Sievers
2005-03-30 14:08 ` Roman Kagan
2005-03-30 17:29 ` Kay Sievers
2005-03-30 19:21 ` Greg KH
2005-03-30 20:20 ` Kay Sievers
2005-04-01 0:18 ` Greg KH
2005-04-01 7:30 ` Kay Sievers
2005-04-02 6:54 ` Greg KH
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=42497236.8030704@starnetworks.us \
--to=kpfleming@starnetworks.us \
--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.