Currently, hotplug is not easily extensible. For example, I am working on an ebuild for an ADSL modem that needs to extend /etc/hotplug/usb.usermap. My proposal is as follows: 1. create /etc/hotplug.d where individual applications can add files, e.g. application foo might add /etc/hotplug.d/foo.usb.usermap 2. add the utility hotplug-update which concatenates all files /etc/hotplug.d/*.usb.usermap to create /etc/hotplug/usb.usermap In this fashion, emerging drivers for hotpluggable devices would become a lot simpler. removing them too, of course. I am quite willing to implement this proposal, if it is agreeable. Reproducible: Always Steps to Reproduce: 1. 2. 3.
hmm... I had overlooked the newer support for /etc/hotplug/usb/*.usermap. I don't yet know how it relates to the old way. I'll be investigating.
I take back my proposal. It turns out that indeed hotplug already has this sort of extensibility. Unfortunately, the examples that I looked at where still in the old inconvenient style, hence my confusion. /etc/hotplug/usb.agent already uses all the /etc/hotplug/usb/*.usermap tables. So it is simply a matter of dropping such a table in this directory (this is also where the scripts go). It worked very well for my ebuild. I apologize for the noise
Setting invalid because the reporter has helped himself... It would be a better world if all reporters would do that :)
