public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>
Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [RFC] /sbin/hotplug multiplexor - take 2
Date: Tue, 15 Apr 2003 12:19:51 -0700	[thread overview]
Message-ID: <3E9C5B57.4020106@pacbell.net> (raw)
In-Reply-To: 20030414224607.GC6411@kroah.com

Greg KH wrote:
> Ok, based on the comments so far, how about this proposed version of
> /sbin/hotplug to provide a multiplexor?

It'd be a reduction in functionality.  I could no longer just
type "/sbin/hotplug" to see what agents disabled or missing ...
or notice that since hotplugging was on, the problem had to be
RH9 storing /bin/true into /proc/sys/kernel/hotplug again!  :P

If the idea is just to loosen today's "one agent per event"
rule (I've had that idea too), then wouldn't it be simpler to
just (a1) pay an extra process context, not using "exec" to run
/etc/hotplug/$1.agent, and when it returns (a2) THEN try other
programs?  Or even (b) just modify appropriate agent scripts
to do so, instead of /sbin/hotplug?

I'd think better about this problem if I had a handful of
examples showing why category-specific or event-specific
dispatch wouldn't be preferable.

- Dave



> ----------
> #!/bin/sh
> DIR="/etc/hotplug.d"
> 
> for I in "${DIR}/$1/"* "${DIR}/"all/* ; do
> 	test -x $I && $I $1 ;
> done
> 
> exit 1
> ----------



  reply	other threads:[~2003-04-15 19:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 19:00 [RFC] /sbin/hotplug multiplexor 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
2003-04-14 22:46 ` [RFC] /sbin/hotplug multiplexor - take 2 Greg KH
2003-04-15 19:19   ` David Brownell [this message]
2003-04-16  4:45     ` Greg KH
2003-04-16  6:22   ` Frederic Lepied
2003-04-18 22:19     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2003-04-16  0:01 Perez-Gonzalez, Inaky
2003-04-18 22:21 ` 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=3E9C5B57.4020106@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@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