From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Zeuthen Date: Thu, 11 Mar 2004 17:30:02 +0000 Subject: Re: udev and dbus Message-Id: <1079026201.1576.73.camel@powerbook.fubar.dk> List-Id: References: <20040217214449.GB12411@wonderland.linux.it> In-Reply-To: <20040217214449.GB12411@wonderland.linux.it> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Thu, 2004-03-11 at 18:23, Kay Sievers wrote: > > > This I would recommend against - not every hotplug event makes udev > > > create/remove a device node; networking devices are one example. > > > > Zero argument! You want udev to call scripts for a device it doesn't > > handle itself, with a empty NODES environment? That's definitely nothing > > more than misuse of infrastructure. > > Oh, seems like I did get you wrong? Sorry. > Nevermind, dbus installs it's own hotplug script independend of the udev > dbus connection. Actually it's hal that installs a hotplug script of it's own and hal just happens to use dbus as the transport; this could be another IPC construct. > So maybe these both scripts may be combined into one? > This would require that the udev hotplug script runs before the hal hotplug script which a) isn't the case today; and b) I'm not sure that it's wise to rely on which order the scripts run in; that would, for instance, make it hard to parallelize hotplug events sometime in the future. Thanks, David ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ 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