From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Date: Tue, 06 Feb 2001 15:15:17 +0000 Subject: Re: Adding PCMCIA support to the kernel tree -- developers needed. 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 Andrew Morton wrote: > > David Woodhouse wrote: > > > > Er... we can wait for arbitrary lengths of time in execve(). So events > > aren't serialised anyway, and cannot be if you report them by running a > > userspace helper like this. You'd have to have a queue which is read by a > > single userspace process (which could perhaps be spawned when the queue > > becomes non-empty). > > I don't really understand why the /sbin/hotplug callout exists > at all. If instead the kernel were to spit the event strings > out of some FIFO device (character special or whatever) then > hotplugd can perform all its actions nice and serially. > > Plus we can buffer all the "insertion events" which occur > from boot-time scanning so they're available when hotplugd > starts up. I had been thinking the same thing. I think Linus originally said "do it with /sbin/hotplug" and that's the way it went. My suggestion would be a ring buffer that includes a jiffy (or other) timestamp before each event. That way it would be trivial for a hotplugd to replay whatever events it missed... Jeff -- Jeff Garzik | "You see, in this world there's two kinds of Building 1024 | people, my friend: Those with loaded guns MandrakeSoft | and those who dig. You dig." --Blondie _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel