Re: BoF on hotplugging - summary

[David Brownell <david-b@pacbell.net>]

> A suggestion was made that a demon should be introduced. That was not discussed
> fully. Later discussion with the X people which are to be continued shows
> that the X people would want to introduce an X extension for device discovery
> and notification issues.

How about adding a new kind of hotplug agent:  daemons
that see events delivered through a filesystem socket or
pipe, like /var/run/hotplug/input.agent?  Simple to add.

Easy to integrate with, and lots of people are already
working with similar models.  It'd move the X discussions
to a more useful stage:  here's the device, now what?  :)

I suspect few of those daemons would ever be "part of"
the hotplug system, except in terms of hearing from it
through the /var/run/hotplug/*.agent files.



> Information needed by user space:
> Items of consensus:
> - physical path and all available device ids must be delivered

I'll submit a 2.5 patch to do that for USB, which currently
does not expose that through hotplug.  (PCI does.)  This is a
simple thing to add to 2.4.20, too, so updated user mode tools
(that know about physical paths) wouldn't need 2.5 to run.

- Dave






-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
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