From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev: add rule based program execution
Date: Sat, 02 Apr 2005 06:54:48 +0000 [thread overview]
Message-ID: <20050402065448.GC18149@kroah.com> (raw)
In-Reply-To: <20050329145403.GA16544@vrfy.org>
On Fri, Apr 01, 2005 at 09:30:35AM +0200, Kay Sievers wrote:
> On Thu, 2005-03-31 at 16:18 -0800, Greg KH wrote:
> > On Wed, Mar 30, 2005 at 10:20:34PM +0200, Kay Sievers wrote:
> > > 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. :)
> >
> > AGENT is again, a term that is very overloaded in the computing field.
> > I still like NOTIFIER, but if you really don't like that...
>
> Heh, seems we don't have bigger problems these days. :)
> Last try for a shorter key name. What about RUN?
Ok, that's fine with me. Anyone not like this?
thanks,
greg k-h
-------------------------------------------------------
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
prev parent reply other threads:[~2005-04-02 6:54 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
2005-04-01 0:18 ` Greg KH
2005-04-01 7:30 ` Kay Sievers
2005-04-02 6:54 ` Greg KH [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=20050402065448.GC18149@kroah.com \
--to=greg@kroah.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 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).