From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Fri, 23 Jan 2004 00:34:08 +0000 Subject: Re: about split the udev Message-Id: <20040123003408.GB16052@kroah.com> List-Id: References: <3ACA40606221794F80A5670F0AF15F8402D4EE96@PDSMSX403.ccr.corp.intel.com> In-Reply-To: <3ACA40606221794F80A5670F0AF15F8402D4EE96@PDSMSX403.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, Jan 23, 2004 at 12:01:29AM +0100, Kay Sievers wrote: > > Here is the next updated updated version to apply to the lastet udev. > I've added infrastructure for getting the state of the IPC queue in the > sender and set the program to exec by the daemon. Also the magic key id > is replaced by the usual key generation by path/nr. Very nice, I applied this. > It looks promising, I use it on my machine and my 4in1 USB-flash-reader > connect/disconnect emits the events "randomly" but udevd is able to > reorder it and calls our normal udev in the right order. Hm, how are you supposed to start up udevd? like: ./udevd ./udev ? > Should we start the daemon if noone listens, when the sender is called? Yes. > Should we convert our udev to a daemon, or stay with the exec? I don't know. I was thinking of turning our udev into the daemon, but with this structure we might not need to. Let's play around with this current structure for a bit now and see how it works out. thanks, greg k-h ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ 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