diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2013-January/022146.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2013-January/022146.html | 150 |
1 files changed, 150 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-January/022146.html b/zarb-ml/mageia-dev/2013-January/022146.html new file mode 100644 index 000000000..316f4dd72 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-January/022146.html @@ -0,0 +1,150 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Grub2 vs. Grub Legacy in M3 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Grub2%20vs.%20Grub%20Legacy%20in%20M3&In-Reply-To=%3C5106D138.4080601%40zen.co.uk%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="021895.html"> + <LINK REL="Next" HREF="022148.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Grub2 vs. Grub Legacy in M3</H1> + <B>Barry Jackson</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Grub2%20vs.%20Grub%20Legacy%20in%20M3&In-Reply-To=%3C5106D138.4080601%40zen.co.uk%3E" + TITLE="[Mageia-dev] Grub2 vs. Grub Legacy in M3">zen25000 at zen.co.uk + </A><BR> + <I>Mon Jan 28 20:27:52 CET 2013</I> + <P><UL> + <LI>Previous message: <A HREF="021895.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI>Next message: <A HREF="022148.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#22146">[ date ]</a> + <a href="thread.html#22146">[ thread ]</a> + <a href="subject.html#22146">[ subject ]</a> + <a href="author.html#22146">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 21/01/13 00:01, Frank Griffin wrote: +><i> On 01/20/2013 02:58 PM, Maurice Batey wrote: +</I>>><i> On Sun, 20 Jan 2013 20:04:32 +0200, Thomas Backlund wrote: +</I>>><i> +</I>>>><i> <A HREF="http://svnweb.mageia.org/packages/cauldron/grub2/current/SOURCES/README.Mageia?view=markup">http://svnweb.mageia.org/packages/cauldron/grub2/current/SOURCES/README.Mageia?view=markup</A> +</I>>>><i> +</I>>><i> Many thanks, Thomas! +</I>>><i> +</I>><i> Look, I don't don't want to restate the obvious, but you *do* realize +</I>><i> that in order for chainloader to work, you actually have to install the +</I>><i> secondary bootloader on the PBR of its owing partition ? You can't just +</I>><i> have installed grub on your MBR at some point in the past, then install +</I>><i> grub2 (or anything else, for that matter) on the MBR again, and expect +</I>><i> your original partitions to boot ? +</I>><i> +</I>><i> In MGA install terms, and specific to the case of grub2 on the MBR +</I>><i> trying to boot grub on a PBR, you have to boot the grub partition (or do +</I>><i> the boot-elsewhere/chroot thing), modify the /boot/grub/install.sh to +</I>><i> not target the MBR (stage2=(hd0)) but indicate the PBR (stage2=(hd0,x)) +</I>><i> and rerun install.sh to install grub on the PBR. +</I>Err... + +# grub +root (hdx,y) +setup (hdx,y) +quit + +Job done - there is no need to touch install.sh + +><i> +</I>><i> In terms of the install paradigm, you have to choose to install the +</I>><i> bootloader to the PBR (sdaX) rather than the MBR (sda). Otherwise, when +</I>><i> the MBR bootloader, whether grub2 or grub, boots and chains to the PBR +</I>><i> of the desired partition, there won't be anything there in the PBR to boot. +</I>><i> +</I>True, except as below... + +><i> If you need clarification on this, ask, and give specifics. The +</I>><i> objective of chainloading is to have each PBR (partition) behave as if +</I>><i> it is its own MBR. If you try to point grub2 menu entries to native +</I>><i> partiton grub files, or vice versa, you are just asking for trouble. The +</I>><i> clean way to do it is to use chainloading to link the MBR (whatever it +</I>><i> is) to the PBR (whatever it is), and let the PBR do the bootloading for +</I>><i> its own partition according to its own needs. +</I> +...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. +Grub2 can install it's kernel in the root filesystem which can be booted +directly. Installing the grub2 package, whether during install or later +automatically builds /boot/grub/i386-pc/core.img and also creates a +grub.cfg ready for use. +Chanloading is un-necessary since an entry in menu.lst on a legacy +system will boot a grub2 Mageia system using: + + title Mageia via GRUB 2 + root (hdx,y) + kernel /boot/grub2/i386-pc/core.img + +...as explained in the above README.Mageia +><i> +</I>><i> If you do it this way, you can install whatever you want as a bootloader +</I>><i> on the MBR, and each partition can have whatever BIOS-compliant +</I>><i> bootloader it wants, including grub, grub2, lilo, OS/2, DOS, or Wndows. +</I>><i> +</I>Yes, I use a small grub2 partition sda1 as "master". +To boot into Mageia grub2 systems I use the grub2 multiboot command: + + menuentry 'Mageia-3 multi sda6' { + search --no-floppy --label --set=root mageia-3 + multiboot /boot/grub2/i386-pc/core.img + } + +So IMO all of the FUD about "you can't install grub2 to the PBR" is +pointless since it's just not necessary. + +My 2 cents ;) + +</PRE> + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="021895.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI>Next message: <A HREF="022148.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#22146">[ date ]</a> + <a href="thread.html#22146">[ thread ]</a> + <a href="subject.html#22146">[ subject ]</a> + <a href="author.html#22146">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |