Grub2 and multiple boot different ubuntu versions

[NoOp]

On 03/24/2010 07:09 PM, Goh Lip wrote:
> NoOp wrote:
> 
> 
> 
>> So how would you advise a standard multiboot user to edit this:
>> 
> 
> In Collin's case, where he wants Karmic to be the default chosen, cut the 
> whole bunch of karmic's entries and paste it *above* the lucid's entries.
> First entry below the .d10 
> 
> 
>> You see, it will take quite a bit of work to do that, and a single
>> mistake could bork grub2 in the process. Plus, how do you keep it updated?
> 
> True, but always good to copy the original of anything before modifying. 
> Grub.cfg also keeps a back-up file.
>> 
>> While I very much respect your advise & opinions, I seriously doubt that
>> modifying grub2 is easier than the former menu.lst and/or 'not much of a
>> hassle'.
> 
> Somehow, it seems that way to me.

I'll try on a test system tomorrow. However, I think that your advise to
edit the grub.cfg file is mistaken and is dangerous to those without
'test' systems. For instance:

>> ### BEGIN /etc/grub.d/20_memtest86+ ###
>> menuentry "Memory test (memtest86+)" {
>> 	insmod ext2
>> 	set root='(hd0,8)'
>> 	search --no-floppy --fs-uuid --set <snipped>
>> 	linux16	/boot/memtest86+.bin
>> }
>> menuentry "Memory test (memtest86+, serial console 115200)" {
>> 	insmod ext2
>> 	set root='(hd0,8)'
>> 	search --no-floppy --fs-uuid --set <snipped>
>> 	linux16	/boot/memtest86+.bin console=ttyS0,115200n8
>> }
>> ### END /etc/grub.d/20_memtest86+ ###

So would I need to delete all of the above or just the
>> }
>> menuentry "Memory test (memtest86+, serial console 115200)" {
>> 	insmod ext2
>> 	set root='(hd0,8)'
>> 	search --no-floppy --fs-uuid --set <snipped>
>> 	linux16	/boot/memtest86+.bin console=ttyS0,115200n8
>> }
part? Would a standard user have an inkling of how to do the above even
if given clear instructions? Is this even the right place to
edit/modify? Afterall the begining of the file states:

<quote>
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
</quote>

So I think that you are advising users to venture into files that
perhaps the standard user should not. There must be a better/safer way
to do all of this.