Wow, that is cool. That was my original design but I never
got it working.
> Caveats:
> o To get automatic unloading of stale modules, you must
> put a line like the following in root's crontab entry:
>
> 0-59/5 * * * * /sbin/rmmod -a
I like the idea of removing the auto unloading code, since it is
something that can certainly be done in user space. An argument *could*
be made that not all systems have cron. But I've been thinking, how
necessary is automatic unloading? I can't think of any good example
where *auto* unloading is necessary. Sure, modules need to be unloaded
at times, but the only examples I can think of involve modules being
unloaded explicitely and immediately. Making modules *not* auto-unload
by default would solve many of the "my mixer settings aren't saved"
problems, too. I'm curious to know peoples thoughts on this matter.
Anyways, I'm running your code at home and it works great, but I
don't have any "tricky" modules. If people don't find any major bugs,
I think it should go into the kernel.
-- 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