From: Arnd Bergmann <arnd@arndb.de>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [RFC] /sbin/hotplug multiplexor
Date: Tue, 15 Apr 2003 00:04:04 +0200 [thread overview]
Message-ID: <200304150004.19213.arnd@arndb.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Oliver Neukum wrote:
> Well, for a little elegance you might introduce subdirectories for each type
> of hotplug event and use only them.
I was just about to propose the same. Please use subdirs or namespaced files
like in:
for I in "${DIR}/$1".* "${DIR}/"default.* ; do
test -x $I && $I $1
done
Note that a single event can not only cause one hotplug event for many devices
but also _multiple_ events for every device. E.g. enabling a dasd devices
will cause hotplug to be called for the local subchannel devices as well as
the actual (remote) disk. Maybe someone adds hotplug calls for partitions
and logical volumes.
Since dasds are usually not larger than 2GB, you are quite likely
to enable many at the same time. Imagine you get 500 disks * 4 events * 10
agents in response to a single user command...
Arnd <><
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+mzBY5t5GS2LDRf4RAiGEAKCDfJCOqc+IwyzN1cFOOiFKuwqfFwCbBiEe
zaWlQP9P0s09DUNoF/xfdLs=
=c6xb
-----END PGP SIGNATURE-----
next reply other threads:[~2003-04-14 21:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 22:04 Arnd Bergmann [this message]
2003-04-14 22:21 ` [RFC] /sbin/hotplug multiplexor Greg KH
2003-04-14 22:23 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2003-04-14 19:00 Greg KH
2003-04-14 19:16 ` Oliver Neukum
2003-04-14 19:54 ` Greg KH
2003-04-14 20:09 ` Oliver Neukum
2003-04-14 20:33 ` Greg KH
2003-04-14 21:11 ` Oliver Neukum
2003-04-14 21:24 ` Kevin P. Fleming
2003-04-14 21:34 ` Greg KH
2003-04-14 21:45 ` Robert Love
2003-04-15 18:17 ` Frank van Maarseveen
2003-04-15 19:59 ` David Brownell
2003-04-14 21:30 ` Greg KH
2003-04-14 21:43 ` Oliver Neukum
2003-04-14 21:52 ` Greg KH
2003-04-14 22:19 ` Oliver Neukum
2003-04-14 22:44 ` 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=200304150004.19213.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.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