Well, the current method of turning it off would be:
echo "/bin/false" > /proc/sys/kernel/modprobe
which seems to work well. We will look into this some more,
however.
> An entry in /proc to completely disable module loading (and also unloading)
> would be a vital feature.
Hmm, there is an entry in proc that lets you set the unload time.
I could change it so that 0 or less means never unload unused modules.
> Also, I would miss the persistent storage facility provided by kerneld. Could
> that be managed, too?
Huh, I didn't think anyone used that. My understanding of kerneld's
persistent storage facility is this: it saves the state of a driver so
that when the module gets unloaded and then reloaded, it still has
the same settings (ex: levels on a sound card's mixer).
I think a better method is to use modprobe. We could create a
setting in /etc/modules.conf that lets the user specify a driver state
file.
This file would match a file in /proc. To save, in this
hypothetical example, a mixer's state:
cat /proc/sound/mixer > /etc/drivers/sound/mixer
to restore a drivers state:
cat /etc/drivers/sound/mixer > /proc/sound/mixer
-- Kirk Petersen http://www.speakeasy.org/~kirk/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu