mdev

[Vladimir Dronnikov]

>
> Its scope is drifting.  The problem with turning into a generic "hotplug"
> daemon is that not everything hotplug does is obvious (firing off a
> filesystem viewer for thumb drives, firing off a picture viever for cameras,
> etc), and if you bolt everything it _might_ do in as C code, it'll never stop
> growing.

Just load supporting modules. That is to run modprobe -q $MODALIAS if
the action is to "add" and $MODALIAS != NULL. Three lines of code.
Could be thrown away at config time. That is my goal.

>
> You're proposing to add module loading.  Did you look at the program I linked
> last message, and notice the large about of parsing it was doing to match
> domain specific vendor ids for various bus types?  Is the kernel doing that
> these days so you don't _need_ to add it to mdev, or are you proposing adding
> all that to mdev?
>

The kernel supplies $MODALIAS. All the helper needs here is to run
modprobe -q $MODALIAS if the action is to "add" and $MODALIAS != NULL.

>> Regards,
>> --
>> Vladimir