Maarten wrote:
The most important one is: how does one make sure the /dev/ entries survive a reboot (and/or are created when the physical USB connection is made) ?
Should hot- or coldplug handle this (and if so, why doesn't it?)
Other USB inserts do get handled as anticipated; for instance inserting a USB mass storage device triggers loading of sd_mod perfectly fine...
hotplug/coldplug should take care of this. If it isn't, it means that either it isn't running correctly, or that the USB IDs for your device aren't in the database.
The other question is about that pl2303 module, how does the kernel know it is needed ?
If hotplug/coldplug are working correctly, when the device is plugged in the kernel will start the hotplug scripts and send the USB ID along. The usb.agent script will look up the ID in the database and determine what modules handle it and load the module if necessary.
You may have to add some lines to the usb.usermap file if the usb.distmap file doesn't have entries for your device.
-- Manuel A. McLure KE6TAW <[EMAIL PROTECTED]> <http://www.mclure.org> ...for in Ulthar, according to an ancient and significant law, no man may kill a cat. -- H.P. Lovecraft
-- [email protected] mailing list
