>
> 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
This seems very usefull to me. There could be any number of this being done.
a few examples:
You plug in your usb modem, the script inserts the driver and automatically
starts the pppd daemon and calls up your provider and sets up the appropriate
routes.
You unplug the modem, the script cleans up.
You might have to keep an eye on the module though, so you can unload it when
it's use count becomes 0. This can take a while, especially if you have a
network device with open sockets... you'll have to wait until all the
programs using it have closed their sockets.
This could also be a very usefull feature for devices which need a firmware
download. You can easily download the firmware from userspace using usbdevfs
at plugin. If nescessary, even before the module plugin. This would solve
the problems with devices who change their vendor id's after firmware
download too.
just my 2 cents,
J.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]