From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Fri, 12 Mar 2004 00:18:44 +0000 Subject: Re: udev and dbus Message-Id: <20040312001844.GB26776@kroah.com> 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, Mar 11, 2004 at 07:56:33PM +0100, Kay Sievers wrote: > On Thu, 2004-03-11 at 19:47, Greg KH wrote: > > On Thu, Mar 11, 2004 at 07:37:16PM +0100, Kay Sievers wrote: > > > On Thu, 2004-03-11 at 19:32, Greg KH wrote: > > > > On Thu, Mar 11, 2004 at 07:12:55PM +0100, Kay Sievers wrote: > > > > > Something like this: > > > > > "Nice, I can mount my USB-stick with udev.d/ right after udev has > > > > > created my partition node, cause the scsi.agent was too fast..." > > > > > > > > No, how can scsi.agent know about what the device node name was? It > > > > can't. > > > > > > udevinfo! That's what it's made for :) > > > > udevinfo will not work for a device node that has just gone away :( > > Why should scsi.agent ask for names on 'remove' events? scsi.agent wouldn't care. But programs that want to watch all scsi devices coming and going would care. I think the dbus people need to work on their "issues" a bit first before we go and start changing udev. Sound ok? thanks, greg k-h ------------------------------------------------------- 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