03-03-06 11:01 PM
Jesse Benton wrote:
> This is how I have changed it. It still boots to 2.6.9 kernel.Although
> I don't claim to be proficate at Linux I have been using it since RH
> 5.0. Here is my grub.conf
>
> # 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 (hd0,0)
> # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
> # initrd /initrd-version.img
> #boot=/dev/hda
> default=1
> timeout=5
> splashimage=(hd0,0)/grub/splash.xpm.gz
> #hiddenmenu
> title Fedora Core (2.6.12-1.1381_FC3)
> root (hd0,0)
> kernel /vmlinuz-2.6.12-1.1381_FC3 ro root=/dev/VolGroup00/LogVol00
> initrd /initrd-2.6.12-1.1381_FC3.img
> #title Fedora Core (2.6.12-1.1378_FC3)
> root (hd0,0)
> kernel /vmlinuz-2.6.12-1.1378_FC3 ro root=/dev/VolGroup00/LogVol00
> initrd /initrd-2.6.12-1.1378_FC3.img
> #title Fedora Core (2.6.12-1.1372_FC3)
> root (hd0,0)
> kernel /vmlinuz-2.6.12-1.1372_FC3 ro root=/dev/VolGroup00/LogVol00
> initrd /initrd-2.6.12-1.1372_FC3.img
> #title Fedora Core (2.6.9-1.667)
> root (hd0,0)
> kernel /vmlinuz-2.6.9-1.667 ro root=/dev/VolGroup00/LogVol00
> initrd /initrd-2.6.9-1.667.img
> title Win XP PRO
> rootnoverify (hd1,0)
> map (hd1) (hd0)
> map (hd0) (hd1)
> makeactive
> chainloader +1
> boot
> I hope this helps
Of course, remove the '#' from each of the titles you added this to.
If you do not want to boot to an older kernel then remove it;
rpm -qa 'kernel*' ;provides a list of the kernels installed
rpm -e kernel-<version_number> ;removes the unwanted kernel, example;
rpm -e kernel-2.6.12-1.1372_FC3 ;removes kernel-2.6.12-1.1372_FC3
This will also remove the kernel boot choice from the grub.conf file.
What you effectively have as your Linux boot choice;
> title Fedora Core (2.6.12-1.1381_FC3)
> root (hd0,0)
> kernel /vmlinuz-2.6.9-1.667 ro root=/dev/VolGroup00/LogVol00
> initrd /initrd-2.6.9-1.667.img
--
"A personal computer is called a personal computer because it's yours,
Anything that runs on that computer, you should have control over."
Andrew Moss, Microsoft's senior director of technical policy, 2005
[ Post a follow-up to this message ]
|