[CentOS] new initrd

Cameron Davidson cam73 at aanet.com.au
Tue May 23 14:40:50 UTC 2006


Tom Brown wrote:
> 
>> You built support into the kernel (y), rather than as a module.  
>> That's fine if you want it that way, but then you don't need the 
>> correpsonding entry in /etc/modprobe.conf.
> 
> OK thanks i understand this now - previously i have done a make 
> menuconfig but this time i just edited the .config file as i was advised 
> to do it that way.
> 
> Using just the .config if i want to build something as a module rather 
> than into the kernel when it comes to that section of the .config file 
> do i just
> 
> CONFIG_FUSION=n
> 
> for example?

I think you mean m, not n.

I have learnt the hard way that there are many scripts in a redhat 
system  that break if you try to compile code as built-in, but RH 
initially compiled it as a module.

The mkinitrd script has a few options for modules vs built-in, but
they are of limited flexibiity.



More information about the CentOS mailing list