Dual Booting Karmic and Jaunty and then using grub-legacy

What a palava. Grub2 will become the defacto standard in time, but right now I am not quite ready to switch over. Having installed Karmic to a separate partition, and chosen to install grub2 to the local root (not mbr) I could not chainload boot to karmic from grub legacy.

So, bootedup the live cd again and installed Grub2 to the mbr. Instructions on how to do this can be found here.

OK, good. Boot up Karmic now, and run “sudo update-grub” in order to load up all the other OS’s into Grub2 menu.

While you are in Karmic, open up the grub.cfg file and copy out the boot menu info for Karmic (you will need this later to put into your grub-legacy menu.lst) Should look something like this:

“sudo nano /boot/grub/grub.cfg”

menuentry “Ubuntu, Linux 2.6.31-14-generic” {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,10)
search –no-floppy –fs-uuid –set b50237f3-c90c-4af6-a275-892a09165ea3
linux    /boot/vmlinuz-2.6.31-14-generic root=UUID=b50237f3-c90c-4af6-a275-892a09165ea3 ro   quiet splash
initrd    /boot/initrd.img-2.6.31-14-generic

Now reboot, and you should be OK to boot back into Jaunty.

In Jaunty, open up menu.lst, and add the following entry to your “Other Operating Systems” section

title       Xubuntu Karmic Koala
uuid       b50237f3-c90c-4af6-a275-892a09165ea3
kernel    /vmlinuz root=UUID=b50237f3-c90c-4af6-a275-892a09165ea3 ro  quiet splash
initrd    /initrd.img
quiet

You’ll see why you needed the info from grub.cfg to insert the UUID information. This layout, I believe also has the benefit of coping with kernal updates to Karmic.

Save your menu.lst file, and reboot. You should now have an entry for Karmic and it should boot.  :)

Leave a Reply

Your email address will not be published. Required fields are marked *