Subj : Re: How to rebuild vmlinuz and initrd.img from scratch for pxeboot environment
To   : linux.redhat.install,comp.os.linux.redhat,comp.os.linux.setup,comp.os.linux,comp.os.linux.networking
From : Timothy Murphy
Date : Tue Jul 27 2004 02:42 pm

Olivier BOURDON wrote:

> I definitely WANT to compile a new kernel but I need to be sure that
> the associated .config file used to build it will allow me to use it
> in a pxeboot environment
> So my 1st question: are there some mandatory kernel config parameters
> that
> I should set for this particular case?

I don't think so.
As far as I know, any kernel that runs on your computer should work.
But have you read pxeboot.doc in /usr/share/doc/syslinux-<version>/ ?
 
> Having done that, I run the make modules command to get the drivers .o
> files that I need to associate this kernel to the initrd.img
> modules.cgz file
> Will it work as is or are there other things

I think you just compile the kernel in the usual way.
After creating the .config file with "make xconfig" or "make menuconfig"
you say something like "make dep; make clean; make bzImage; make modules"
and then "make modules_install; make install".

> Additionnal question: is there a way to have say a 2.4.22-2215 kernel
> load a 2.4.22-2297 module without complaining about the version ?

With 2.6.* kernels there is a config option
"Module versioning support (EXPERIMENTAL)" to allow this.
I'm not sure if it was there for 2.4.* kernels.

Personally I would compile a vanilla kernel, eg 2.4.26 or whatever,
unless there is a very strong reason not to.

-- 
Timothy Murphy  
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

.