On Sat, 7 Aug 2010, James Bensley wrote: > To: CentOS mailing list <centos at centos.org> > From: James Bensley <jwbensley at gmail.com> > Subject: Re: [CentOS] ext4? > > [nf5002 at eros boot]$ sudo cat /boot/grub/menu.lst > # grub.conf generated by anaconda > # > # Note that you do not have to rerun grub after making changes to this file > # NOTICE: You have a /boot partition. This means that > # all kernel and initrd paths are relative to /boot/, eg. > # root (hd1,0) > # kernel /vmlinuz-version ro root=/dev/sda1 > # initrd /initrd-version.img > #boot=/dev/sda > default=0 > timeout=5 > splashimage=(hd1,0)/grub/splash.xpm.gz > hiddenmenu > title CentOS (2.6.18-92.el5) > root (hd1,0) > kernel /vmlinuz-2.6.18-92.el5 ro root=LABEL=/ rhgb quiet > initrd /initrd-2.6.18-92.el5.img > > I only have one kernel listen which is why I assume I am behind, I > think yum has been getting new kernels but not building them and > editing the grub meun. vmlinuz-2.6.18-92.el5 and > initrd-2.6.18-92.el5.img is the only kernel in /boot? > > I don't want to be a bother so can point me at a resolution i.e. point > me at some documentation on how to make a new kernel image out of the > resouces in /lib/modules/2.6.18-194.8.1.el5 and I shall do so. FWIW, I have installed GRUB to separate boot partition - not the MBR of the first hard drive. Whenever there is a kernel update, I have to mount and manually edit the /boot/grub/grub.conf file on the boot partition. Yum does not update it, as it doesn't know where it is. I prefer this behaviour, as it means I have total control over which kernel is running, even after a kernel upgrade. I also make backup copies of all kernel files, just in case I need to regress to a previous version, that yum may have removed. HTH Keith Roberts