> That was the intention. And the /proc/bus/usb/devices was exactly
> meant to wake up that daemon. Beginnings of such a daemon are
> in the usb.in.tum.de CVS, feel free to continue working on it...
Excellent
> I however fail to see why another userspace daemon talking to
> another magic pipe with another magic format to the X server
> should be less fragile.
You are dealing with policy. That means you want things like scripts the
user can deal with. Lets take some of the things people might want to do
on USB device insertion
- Keyboard
o Load a new keymap
O Tell X11 about a keymap change
But not everyone will do this. I for example use US keymap on UK
keyboards because I hate the quote placements.
You might also need to tell hot-key binding apps using the key
extension stuff to bind things like the extension keys on the new
funkey keyboards
- disk
o Match the file system ID
Mount the disk
Tell the file manager
but if its pictures maybe I want to fire up xv on that new
directory (eg for a camera).
So IMHO its best to follow the PCMCIA model which is
kernel->user message (or poll and scan)
Run the matching script set
Let user policy dictate what gets kicked
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
