From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Thu, 11 Mar 2004 17:23:40 +0000 Subject: Re: udev and dbus Message-Id: <1079025820.1127.119.camel@pim> 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:14, Kay Sievers wrote: > On Thu, 2004-03-11 at 16:06, David Zeuthen wrote: > > > We can rip dbus out and make a external dbus caller, yes that's fine. > > > But dbus should use the /sbin/hotplug multiplexer. Just get the needed > > > information with udevinfo and then fire up the dbus-client. > > > > 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. So maybe these both scripts may be combined into one? Just look at Rob's presentation: http://tech9.net/rml/talks/rml_fosdem_2004.sxi Kay ------------------------------------------------------- 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