> 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
I find the auto-unloading of modules very convenient... For instance, I
have the cdrom drivers modularized... If I need to copy a couple of files
from a cd, kmod/kerneld loads and unloads these modules completely
transparently. Same applies for the floppy driver, nfs, ppp compression,
binfmt_aout.o, binfmt_misc.o, lp/parallel drivers, the packet module, etc
etc. Aside from the ppp modules, nearly everything I modularize is simply
because of infrequent use. Having them not auto-unload isn't the end of
the world, but it loses an incredible convenience.
> by default would solve many of the "my mixer settings aren't saved"
Maybe someone should hack the sound module to take initial mixer settings
on startup. (this is why I don't modularize sound =])
+----------------------+----------------------------------------+
| bytor@logicsouth.com | UNIX _is_ user-friendly. It's just not |
| By-Tor@EfNet | ignorant-friendly and idiot-friendly. |
+----------------------+----------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu