Yes, that was included in modules-2.0.0 (and can partly still be seen
in the remaining kerneld), but that required changes to all modules that
wanted to use that feature.
It seems not to many people liked the idea... Or perhaps it's because I
left for China for two years... who knows.
I have some long-range hope of trying to coordinate such work with
the PnP-efforts that some people are doing, since that would logically
be part of the same problem (taken a bit loosely).
> Or one can consider
> post-install and pre-remove for doing this but we do not have a standard
> recommened way for this. We probably need a standard
> /proc/module/<module_name>/*
> format that one can read/write to maintain continuity of service for
> the module.
>
> I assume here that I do want the module to be unloaded/loaded and
> not lose any settings (that maybe my post-install used, or my
> application)
> thus allowing transparent unload/reload, so idle-unloads carry far
> less risk.
This would be nice to have, hopefully without having to build additional
features into kmod (or at least as little extra as humanly possible).
Cheers,
Björn
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/