To get it to work, I had to get the UUID's by running "sudo blkid" and then I placed them in grub.cfg like so:
[code]menuentry "Ubuntu, Linux 2.6.28-13-generic" {
set root=(hd0,1)
search --no-floppy --fs-uuid --set $UUID_OF_PARTITION_WITH_/BOOT
linux /vmlinuz-2.6.28-13-generic root=UUID=$UUID_OF_PARTITION_WITH_/ quiet splash
initrd /initrd.img-2.6.28-13-generic
}[/code]
GRUB developers should know that the "Legacy -> GRUB2" process messes up the configuration file (by assuming all partitions are LVM managed) when done this way.
My worry is that when installing new kernels in 9.04, will grub.cfg be updated automatically or do I need to boot into 9.10 every time and run upgrade-from-grub-legacy?
If I have to run upgrade-from-grub-legacy, will it put the actual UUIDs or will it still assume these are LVM managed partitions and incorrectly produce grub.cfg again?
To get it to work, I had to get the UUID's by running "sudo blkid" and then I placed them in grub.cfg like so:
[code]menuentry "Ubuntu, Linux 2.6.28-13-generic" { PARTITION_ WITH_/BOOT 2.6.28- 13-generic root=UUID= $UUID_OF_ PARTITION_ WITH_/ quiet splash img-2.6. 28-13-generic
set root=(hd0,1)
search --no-floppy --fs-uuid --set $UUID_OF_
linux /vmlinuz-
initrd /initrd.
}[/code]
GRUB developers should know that the "Legacy -> GRUB2" process messes up the configuration file (by assuming all partitions are LVM managed) when done this way.
My worry is that when installing new kernels in 9.04, will grub.cfg be updated automatically or do I need to boot into 9.10 every time and run upgrade- from-grub- legacy?
If I have to run upgrade- from-grub- legacy, will it put the actual UUIDs or will it still assume these are LVM managed partitions and incorrectly produce grub.cfg again?