Fred wrote:The first thing that I noticed that seems to be missing is the ability to use unique identifiers in the "root" line. We seem to still be stuck with the "hd0,1" drive/partition identifier. In my opinion this was one of the biggest improvements needed in this day of mixed storage devices. I hope I am wrong on this issue, and just missed something.
- (hd0,0)
-Grub1 (legacy grub) - (hd0,1)
-grub 2
--yes they changed the number sequencing, who knows why
This has been looming for awhile, every since Grub2 was announced, and grub legacy was the new name for the older Grub..
Grub2Grub2 --cautions..- Edit grub.cfg or other method..
http://aronzak.wordpress.com/2008/09/30 ... rom-grub2/
- Code: Select all
8. mike_s - 18 May, 2009
well I just got grub2 up and running on my triple boot system. I have ubuntu 9.1, Windows Vista, and a version of OSX using chameleon’s darwin bootloader. Although I agree that grub2 is way more complicated than its legacy, it is definately doable. The people who are telling you to edit the grub.cfg file are full of beans, as a mismatch between the executables in /etc/grub.d and the .cfg seems to royally piss off grub2. you should edit the exe’s in ~/grub.d to make changes and then execute the command: sudo /usr/sbin/update-grub to make those changes flow through into the grub.cfg
...
oh also grub2 doesn’t understand uuid’s so while you are in between you should make sure to edit the menu.ls used by legacy grub to change all uuid’s (except where it says uuid=root) to the respective device and partition or else you will get an error 11 unrecognized device. good luck
Grub 2 caveats..grub.cfg gets updated with each update-grub
For a permanent modification of grub.cfg, you must create a script in /etc/grub.d/
-- script goes into in /etc/grub.d or /etc/default/grub
While it looks quite different using { and } instead of TAB or spaces as the block format
--with some additional menu command names like menuentry
- grub 2
{
command 1
command 2
...
} - grub1
command 1
command 2
...