Re: modules

["Monique Y. Herman" <spam@bounceswoosh.org>]

On 2004-02-14, cdummy penned:
>
> If I go to /etc/modutils there are no my sound modules to load. When I 
> take look on my stock kernel config file above sound modules are 
> compiled as modules:
> snip
> # CONFIG_MSNDPIN_HAVE_BOOT is not set
> CONFIG_MSNDPIN_INIT_FILE="/etc/sound/pndspini.bin"
> CONFIG_MSNDPIN_PERM_FILE="/etc/sound/pndsperm.bin"
> CONFIG_SOUND_VIA82CXXX=m
> CONFIG_MIDI_VIA82CXXX=y
> CONFIG_SOUND_OSS=m
> snip
> And they are in /lib/modules. How do they load? Kernel  loads modules 
> automatically? How come they are not in /etc/modutils/aliases

Look at the file /etc/modules.  This is a list of modules that the
kernel will automatically load at boot, and I'm guessing that you will
find your modules there.


> Last kernel I compiled was 2.4.20 and I compiled modules and than added 
> them to /etc/modules so they load. SCSI and IDE I always compile into 

Now I'm confused.  You didn't mention /etc/modules above.  I am pretty
sure /etc/modutils serves a different purpose, but I don't understand
the system well enough to explain it.

> kernel. And there comes my second question. I read 2 articles about 
> compiling Debian specific kernel.:
> http://www.osnews.com/story.php?news_id=2949&page=1
> http://www.tux.org/~tbr/debiankernelpkg/
> But all new kernels are coming with initrd.img. Is this a must or can I 
> compile old way?

I always pull down the Debian kernel-source package for the kernel
version I want, then build in the standard way.  No initrd for me, and
it works fine.  So, no: you don't have to use initrd with debian.

-- 
monique