Hello,

I installed CentOS 3.4 which has kernel 2.4.21-27 on the distro cd's. I did a full yum update which brought the system up to CentOS 3.6 with kernel 2.4.21-37. Everything works fine with this. I then downloaded the latest 2.4.32 kernel src, created a .config file from /boot/config-2.4.21-37.ELsmp and
proceeded with makeing a new kernel with...

make dep
make clean
make bzImage
make modules
make modules_install
mkinitrd -v /boot/initrd-2.4.32.img 2.4.32
make install

After booting with the new kernel, nslookup has a
segmentation fault and ypbind can not start as it can
not locate a NIS domain server. Booting off the prior
kernels everything works fine.

Can anyone give me a hint here why it doesn't work on 2.4.32? I can not go to a kernel 2.6 at this time.

I haven't been able to build a 2.4.32 kernel on CentOs 4.x which is why I went to version 3.4 with the OS.

thank you,
Allan

First CentOS 3 is now at 3.7 and the kernel is at 2.4.21-40 but that's beside the point.

Second using a Red Hat supplied kernel config file is only a starting point you need to configure the vanilla kernel.org further, do this while your in 'make menuconfig' or 'make config' or 'make xconfig' or whichever you choose use.

Third the steps are;

make mrproper
make oldconfig
make menuconfig (this is what Red Hat recommends, see link below)
make dep
make clean
make bzImage
make modules_install
make install

Notice I used 'make menuconfig' this is where and when you adjust or tweak the configuration for your hardware and adjust or fix any missing parts (like the network section) of the configuration.

Finally notice I did not use 'mkinitrd -v /boot/initrd-2.4.32.img 2.4.32' because there is no reason to, the 'make install' command does this and more.

You may find that reading will help also;
http://www.redhat.com/docs/manuals/e...dularized.html

thanks for the response. Strange yum didn't pick up 3.7 for the update.

Anyway, I thought copying over the prior config file from the current booted kernel would put the same options in the new kernel build by doing a make oldconfig and ask questions that have new parameters not built in to the prior kernel????? I use make menuconfig also but didn't think it was needed since I already have a .config file from a prior kernel, not that I have a clue right now what wouldn't be configured in it since the network card is up and I can get to the system, just nslookup and NIS isn't working.

Red Hat kernels and the associated config files do not matchup exactly to vanilla kernels. They are OK to get a starting point for building, but you need to check, verify and adjust. Red Hat and others are known to tweak(backport, add patches and other changes) that are not normally found with the standard kernel.org sources.

Fixed: After searching the web, I saw a blip saying rename /lib/tls to /lib/tls.disabled. Did that, rebooted system and now I'm able to use
the 2.4.32 kernel. nslookup and NIS works fine now.

thanks,
Allan