> Surely it is best not to make the kernel vary according to the
> modules that are being compiled with itš. If we do, then we should
> change the configuration choices from {Yes,No,Module} to
> {Yes,Never,No,Module}.
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).
-cw
-
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/