> No, it's a 2.5 thing: modules know their own name. This is because
> (1) the names are used to set new-style boot parameters, (2) needing
> to insert two modules is usually wrong, since how would that work if
> the module was built-in?
>
> It also opens us up to the possibility of a list of built-in modules,
> if we wanted to.
The list of built-ins would be really, really nice -- it would
beat the heck out of digging through the .config and/or going
back to the build machine and doing 'make menuconfig' just to
see what's in there.
------
Chuck