> why not just use the KMOD within the kernel itself and use
/etc/modules.conf
> as configuration file?
>
> ...
>
> Is there a problem with this approach?
It sounds too reasonable.
> The ones I see are:
>
> - Not possible to load modules in usb_find_drivers (can we be in an
interrupt?)
> [Is the usb controller is using a thread to detect devices ?]
I think "khubd" ends up doing that.
> - Not possible to express the multitude of triggers class/subclass in easy
> modules.conf aliases.
It'd work for the devices I deal with. Minimizing the number of policy
choices is good, within reason.
- Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
