Re: udev and dbus

[Greg KH <greg@kroah.com>]

On Thu, Mar 11, 2004 at 07:12:55PM +0100, Kay Sievers wrote:
> 
> I expect lot of lazy people to put their scripts in there, cause it's so
> comfortable to live inside the serialized hotplug events.

But people want to know about the device node creation and removal, they
don't care about the "raw" hotplug events.  They want udev to handle the
raw hotplug events for them.

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

Lots of people have been asking me about the ability to run "post" type
scripts after udev has named the device (or removed it.)  With this
proposal, people could get those udev messages easily (actually multiple
people could, which is even better.)  It would also allow us to rip out
both the SELinux and DBUS code from udev itself and implement those with
/etc/udev.d/ programs instead.

Which, in the end, would make udev itself simpler, and more resilient
over time for new requests from new programs/system notification
buses/security models/etc...

Does that make more sense?

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_id\x1470&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