Message-ID: <4015FC93.1060804@nortelnetworks.com>
Date: Tue, 27 Jan 2004 00:52:19 -0500
From: Chris Friesen <cfriesen@nortelnetworks.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204
MIME-Version: 1.0
To: Greg KH <greg@kroah.com>
Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 015 release
References: <20040126215036.GA6906@kroah.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1348
Lines: 37

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

-
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/