From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev: add rule based program execution
Date: Wed, 30 Mar 2005 20:20:34 +0000 [thread overview]
Message-ID: <1112214034.4631.76.camel@localhost.localdomain> (raw)
In-Reply-To: <20050329145403.GA16544@vrfy.org>
On Wed, 2005-03-30 at 11:21 -0800, Greg KH wrote:
> On Tue, Mar 29, 2005 at 04:54:03PM +0200, Kay Sievers wrote:
> > This patch on top of the current bk-tree allows to specify programs to
> > be executed after the device handling. This is meant as a general
> > replacement for the dev.d/ logic which is known to be the main reason for
> > the boot-time delay on udev systems.
> >
> > This patch introduces the HOTPLUG key. Every matching rule can add one
> > HOTPLUG key to a list of program to be executed after the node is
> > created/removed.
>
> I like this, except for the name of the key. The term "hotplug" is just
> too overloaded these days. Can you change it to something else.
You are right! HOTPLUG says nothing and that key should be renamed.
> Perhaps NOTIFIER? That more explicitly states what this rule is going
> to do.
How does AGENT sound? It's a bit shorter, but hey, NOTIFIER is still
shorter than SUBSYSTEM. :)
Kay
-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/info/Sentarus/hamr30
_______________________________________________
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-30 20: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
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 [this message]
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=1112214034.4631.76.camel@localhost.localdomain \
--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 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.