From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Tue, 15 Apr 2003 19:19:51 +0000 Subject: Re: [RFC] /sbin/hotplug multiplexor - take 2 Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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 > ---------- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ 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