Re: udev and dbus

[David Zeuthen <david@fubar.dk>]

> I think the dbus people need to work on their "issues" a bit first
> before we go and start changing udev.  Sound ok?
> 

Erh, what "issues" are you talking about? With both proposed changes
dbus support would be removed from udev proper which I think is sane.

What we're really arguing about is where projects higher in the stack
than udev (like hal) should place their scripts. I'm saying /etc/udev.d
and Kay is saying /etc/hotplug.d. FWIW, I can live with both proposals,
though I think it's conceptually clearer to use /etc/udev.d. But let's
not dicsuss the merits of these proposals again.

In either case the situation today is not acceptable. Today, there is no
sane way (e.g. without polling) for projects above udev to get the
information that a device node is created/removed. This is because that
udev ships with dbus support turned off for the various reasons
discussed earlier.

So, Greg, as the udev and hotplug maintainer I think you need to make a
decision on what to do, so we can remedy this situation and udev can
continue to own the world :-)

Anyway, I'm flexible.

Many 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_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