From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Friesen Date: Tue, 27 Jan 2004 05:52:19 +0000 Subject: Re: [ANNOUNCE] udev 015 release Message-Id: <4015FC93.1060804@nortelnetworks.com> List-Id: References: <20040126215036.GA6906@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Greg KH Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Greg KH wrote: > I've released the 015 version of udev. It can be found at: > kernel.org/pub/linux/utils/kernel/hotplug/udev-015.tar.gz > Also in this release is the start of a udev daemon. It's really in 3 > pieces: > udevsend - sends the hotplug message to the udev daemon > udevd - the udev daemon, gets the hotplug messages, sorts them > in proper order, and passes them off to the udev program > to act apon them. > udev - still the same. I'm curious about the rationale behind breaking it up into multiple chunks. udevsend being separate I assume is so that it can be easily called from a script while still keeping something persistant? I'm not sure I see what separating udev and udevd into different binaries actually buys you. Wouldn't it be just as easy to make udev be the daemon based on runtime options or something? Chris -- Chris Friesen | MailStop: 043/33/F10 Nortel Networks | work: (613) 765-0557 3500 Carling Avenue | fax: (613) 765-2986 Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com ------------------------------------------------------- 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