Re: udev and dbus

[David Zeuthen <david@fubar.dk>]

On Thu, 2004-03-11 at 18:14, Kay Sievers wrote:
> On Thu, 2004-03-11 at 16:06, David Zeuthen wrote:
> > On Thu, 2004-03-11 at 15:30, Kay Sievers wrote:
> > > Sorry, but are you guys getting completely crazy? :)
> > > 
> > > Why you want a stacked hotplug.d/udev.d forking hell or a "serializer"
> > > for the dbus daemon? This is simply unmaintainable and _nobody_ will
> > > understand this. 
> > 
> > What's so difficult with understanding that udev calls a series of
> > programs in /etc/udev.d when it add/remove device nodes?
> 
> Oh, it's not as easy as you might think. Just read this list or
> _your_ yesterdays mail, where you propose that udev should call
> /sbin/hotplug, which is a nice loop, right :)
> 

Oh, come on - it's not like udev should create/remove device nodes on
getting a hotplug event with the single positional parameter being
'udev', right? That would be quite stupid.

I was merely suggesting to use an existing multiplexor mechanishm so
people only need to care about /etc/hotplug.d and not both
/etc/hotplug.d and /etc/udev.d.

> Just make udevsend wait until the nodes are created (we already have a
> patch for it from Chris) and execute udevsend as the first program with
> /sbin/hotplug. All the following programs are sure that the nodes on
> it's place and can query the node names with udevinfo. Easy, clean, nice
> transparent and understandable.
> 

Wearing a purist-hat, I would consider this a bad hack - so you want to
hardcode the requirement that udevinfo needs to run before anything into
whatever hotplug multiplexor is running? 

What if I want to write a hotplug multiplexor that runs a number of
programs in parallel in response to a hotplug event? What if I want to
write another implementation of a device node manager to replace udev? 
(not that I want to at, I really like udev, but I'm against setting
requirements on how a hotplug multiplexor should work).

> udev is a device node manager, nothing more. I _strongly_ disagree on
> making udev a arbitrary hotplug script engine. Please solve the problem
> on it's source not on the first comfortable place :)

No. I'm simply asking that udev executes a program when it add/removes
device nodes, that's all - calling this an arbritary hotplug script
engine is simply not representative of what I ask for. I've said I'm
even willing to write the patch myself :-)

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