From: Arnd Bergmann <arnd@arndb.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug for klibc utils
Date: Fri, 27 Feb 2004 16:52:45 +0000 [thread overview]
Message-ID: <200402271752.45559.arnd@arndb.de> (raw)
In-Reply-To: <200402271402.06890.arnd@arndb.de>
On Friday 27 February 2004 15:20, Hannes Reinecke wrote:
> Hmm. But maybe we can be a bit more clever; after all, the default
> script in /etc/hotplug.d/default just calls the appropriate agent. If we
> were to implement this behaviour in the multiplexer, then we can use as
> a block agent 'udev' and scripts for everything else, always assuming
> that the other events are not as numerous.
IFAIR, the current /etc/hotplug.d/default/default.hotplug is simply
what used to be /sbin/hotplug before it did any multiplexing.
It should be easy to just convert the /etc/hotplug/*.agent scripts
to /etc/hotplug.d/*/*.hotplug. At least for new distributions that
don't need to provide support for /etc/hotplug/*.agent, you could
simply leave out /etc/hotplug.d/default/default.hotplug.
Arnd <><
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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:[~2004-02-27 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 13:02 hotplug for klibc utils Arnd Bergmann
2004-02-27 13:29 ` Hannes Reinecke
2004-02-27 13:53 ` Arnd Bergmann
2004-02-27 14:20 ` Hannes Reinecke
2004-02-27 16:52 ` Arnd Bergmann [this message]
2004-02-28 0:19 ` 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=200402271752.45559.arnd@arndb.de \
--to=arnd@arndb.de \
--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.