On Thu, 2009-10-22 at 04:20 -0400, ken wrote:
> <snip>
> cat /boot/grub/menu.lst
> ...
> title CentOS (2.6.18-164.2.1.el5.plus)
> root (hd0,2)
> kernel /vmlinuz-2.6.18-164.2.1.el5.plus ro
> root=/dev/mapper/luks-3d723b4f-0184-438d-9cb9-9ebff16e683a rhgb quiet
> initrd /initrd-2.6.18-164.2.1.el5.plus.img
> title CentOS (2.6.18-164.el5)
> root (hd0,2)
> kernel /vmlinuz-2.6.18-164.el5 ro
> root=/dev/mapper/luks-3d723b4f-0184-438d-9cb9-9ebff16e683a rhgb quiet
> initrd /initrd-2.6.18-164.el5.img
> title CentOS (2.6.18-128.7.1.el5)
> root (hd0,2)
> kernel /vmlinuz-2.6.18-128.7.1.el5 ro
> root=/dev/mapper/luks-3d723b4f-0184-438d-9cb9-9ebff16e683a rhgb quiet
> initrd /initrd-2.6.18-128.7.1.el5.img
> ...
>
> If your /boot/grub/menu.lst is similar, then you need only select a
> previously installed kernel at the boot menu. You can access this via
> your remote KVM setup, yes?
>
> In the past I've edited menu.lst to change what's booted, i.e., I
> rearranged the order of the stanzas to make the first one, which is the
> default (the one booted if no action is taken at the boot menu), the
> working/desired kernel.
Don't forget htat you can use the default command in the grub.conf, e.g.
"default 1", rather than rearranging all the time.
Use "info grub", select the "index" entry and then look for "default"
>
> hth,
> ken
> <snip sig stuff>
--
Bill
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
