diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2013-January/022212.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2013-January/022212.html | 109 |
1 files changed, 109 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-January/022212.html b/zarb-ml/mageia-dev/2013-January/022212.html new file mode 100644 index 000000000..d0b3102a6 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-January/022212.html @@ -0,0 +1,109 @@ +<!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=%3C5107D5AB.4080700%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="022211.html"> + <LINK REL="Next" HREF="021904.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=%3C5107D5AB.4080700%40zen.co.uk%3E" + TITLE="[Mageia-dev] Grub2 vs. Grub Legacy in M3">zen25000 at zen.co.uk + </A><BR> + <I>Tue Jan 29 14:59:07 CET 2013</I> + <P><UL> + <LI>Previous message: <A HREF="022211.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI>Next message: <A HREF="021904.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#22212">[ date ]</a> + <a href="thread.html#22212">[ thread ]</a> + <a href="subject.html#22212">[ subject ]</a> + <a href="author.html#22212">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 29/01/13 12:48, Frank Griffin wrote: + +><i> I wasn't aware of the MBR gap. I guess you're saying that the core.img +</I>><i> that fits in it *is* filesystem-aware ? +</I> +Yes, depending on the modules built into it, which are normally correct +for our purposes. + +><i> +</I>><i> Anyway, my point still stands: for anyone who just wants to have grub +</I>><i> and grub2 partitons coexist on the same disk with either one in the MBR, +</I>><i> chainloading will accomplish this without any downside that isn't +</I>><i> already present in grub legacy. +</I> +Yes + + Grub2 may be the way of the future, but +><i> to *require* it to own the MBR is just misleading. +</I> +Yes, it only gives that impression. It does not need to be the primary +bootloader. + +To demonstrate this I made a fresh install of Mageia3 with only grub +legacy installed and booted from MBR. +I then installed the grub2 package (nothing more) and added an entry for +the grub2 bootloader to the grub legacy menu.lst. (as in the README) +I then re-booted and selected the grub2 entry from the legacy menu. +The grub2 menu launched and contained all my systems - including the new +Mageia3. +Selecting Mageia3 launched the OS. +Likewise selecting Mageia2 (found automatically during install of grub2) +launched that correctly. + +The MBR has not been touched at all since the installation of grub +legacy by the Mageia installer. + +Note that I do not advocate this as a sensible route to multi-booting, +since it takes no account of kernel updates - it is just a demonstration. + +Barry + + + +</PRE> + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="022211.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI>Next message: <A HREF="021904.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#22212">[ date ]</a> + <a href="thread.html#22212">[ thread ]</a> + <a href="subject.html#22212">[ subject ]</a> + <a href="author.html#22212">[ 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> |