[Mageia-dev] Grub2 vs. Grub Legacy in M3

Frank Griffin ftg at roadrunner.com
Mon Jan 28 21:09:12 CET 2013


On 01/28/2013 02:27 PM, Barry Jackson wrote:
> Err...
>
> # grub
> root (hdx,y)
> setup (hdx,y)
> quit
>
> Job done - there is no need to touch install.sh

Err,

[root at ftglap grub]# cat /boot/grub/install.sh
grub --device-map=/boot/grub/device.map --batch <<EOF
root (hd0,5)
setup --stage2=/boot/grub/stage2 (hd0)
quit
EOF

>
> ...this is where we disagree slightly ;)
> Chainloading into grub2 is not the best way, due to the block lists 
> problem people keep mentioning and complaining about.

Could you please explain why ?  The whole MBR/PBR design was set up so 
that whatever gets loaded and receives control doesn't know which way it 
happened.  How does grub2 break this ?

> Chanloading is un-necessary 

I don't claim that it's necessary, just that it's more desirable than 
requiring the MBR code to go poking around in partitons other than the 
one from which it was installed.  If you're interested in keeping 
partitions functionally as separate as they can be, it just makes sense 
to have them booted by their own bootloaders.




More information about the Mageia-dev mailing list