Re: Why are modules and modules.conf not versioned?

[Eric Richardson <eric.richardson@milagrosoft.com>]

Andreas Metzler wrote:

> Eric Richardson <eric.richardson@milagrosoft.com> wrote:
>
> > The background to this question is based on the fact that different 
> > versions of kernels such as 2.2.x and 2.4.x and also different custom 
> > kernels have different module requirements therefore switching between 
> > them is not seemless in the current system. I currently use woody. 
> > Hopefully this message is not totally off base.
> [...]
>
> There is no real need to version modules.conf or the files in
> /etc/modutils/, because
>
> | if `kernelversion` == 2.2
> | ...
> | elseif `kernelversion` == 2.4
> | ...
> | endif
>
> works and should work on non-Debian systems, too. You can use `uname
> -r` if you have to match the exact version.


From a superficial standpoint, I see the file /etc/init.d/modutils on 
boot reading line by line the modules from /etc/modules and calling 
modprobe. Somehow the options must be read from /etc/modules.conf. These 
are the two files I see modconf modifying.

Where does the /etc/modutils/ dir come into the picture?

Is there other documentation I can look at that would let me see a more 
complete picture?

Eric