[...]
> [1] One problem with modules.conf is keeping it up to date with the
> kernel. What about /proc/sys/modules.conf where kernel code can
> register its own special requirements? modprobe reads
> /proc/sys/modules.conf/first then /etc/modules.conf then
> /proc/sys/modules.conf/last to build its database.
No more /proc cruft, please!
How on earth is the kernel to know what it needs (modulewise), as this
depends on the exact setup for the user?
What if modules export/import symbols that just serve for dependencies?
This is cleaner IMVHO, and a distributed solution (no single file that
builds the above /proc stuff that has to be kept up to date, even for
third-party modules)
-- Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513- 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/