Messages in this thread | | | Date | Tue, 15 Apr 2003 12:19:51 -0700 | From | David Brownell <> | Subject | Re: [RFC] /sbin/hotplug multiplexor - take 2 |
| |
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 > ----------
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |