From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Love Date: Mon, 12 Jan 2004 16:28:38 +0000 Subject: Re: about split the udev Message-Id: <1073924918.1153.114.camel@localhost> 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 Mon, 2004-01-12 at 08:54, Kay Sievers wrote: > Huhh, what a magic :) > > udev is a part of hotplug. > udev _sends_ DBUS-messages. > HAL receives these messages with the node name _from_ udev. HAL _also_ installs a hotplug script to listen for events and emit a D-BUS signal, because HAL wants to know about all hotplug events, not just ones that udev handles. So I think Martin's idea is actually pretty good. It would mean we end up with a really clean progression for hardware integration: kernel -> hotplug (via /sbin/hotplug) -> hal.hotplug -> udev daemon (via D-BUS) -> HAL daemon (via D-BUS) -> upper levels of the desktop (via D-BUS) Which I like. Robert Love ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ 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