> Ideally yes... but lets leave that to 2.3.x - right now, in the case
> of socket, there are other limits which under some circumstances stop
> an arbitrary socket from being loaded (eg. N_PROTO)
> I'd like to see the module interface more standardized in 2.3.x for
> 2.4.x so that someone may build a kernel with as few options as
> possible and load modules more freely, not so tightly bound to the
> kernel version (within limitations, eg. 2.0.29 -> 2.0.3x something
> change much stuff, so in those cases, we have to accept things will
> break).
This is contradictory... either you compile the kernel so it accepts new
modules later (can't tell beforehand which ones, so "Never" is never an
option), or not. It has been explained here that "Never" is doable, but a
lot more complicated than just leave the possibility open (given by current
"No"); the problem a "Never" would solve is clearly _very_ minor (just
"alias xyz off" in /etc/modules.conf works fine for me, no kernel changes
at all!). So I guess (hope?) it won't be "fixed"
BTW, what you ask for exists: Symbol versioning for modules is in the
kernel for ages now. Sure, you can't load ne2k from 2.1.125 into
2.0.36pre14, but such is life, and the price for kernel advancement.
-- 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/