<!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=%3C50FBEBCB.3050504%40roadrunner.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="021852.html">
<LINK REL="Next" HREF="021854.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Grub2 vs. Grub Legacy in M3</H1>
<B>Frank Griffin</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Grub2%20vs.%20Grub%20Legacy%20in%20M3&In-Reply-To=%3C50FBEBCB.3050504%40roadrunner.com%3E"
TITLE="[Mageia-dev] Grub2 vs. Grub Legacy in M3">ftg at roadrunner.com
</A><BR>
<I>Sun Jan 20 14:06:19 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="021852.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3
</A></li>
<LI>Next message: <A HREF="021854.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#21853">[ date ]</a>
<a href="thread.html#21853">[ thread ]</a>
<a href="subject.html#21853">[ subject ]</a>
<a href="author.html#21853">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 01/20/2013 07:55 AM, Maurice Batey wrote:
><i> So I suspect that he (like me) does not know how to boot a GRUB Legacy
</I>><i> install from a GRUB2 boot menu. (Yes, I know GRUB2 boot menus do show
</I>><i> options to boot existing GRUB Legacy installs, but in my experience
</I>><i> (with Ubuntu and Mint) they *fail* to boot them.) Despite my requests
</I>><i> in various newsgroups, NO ONE has offered a description of how to get
</I>><i> a GRUB2 boot menu to successfully boot a GRUB Legacy install. Can you,
</I>><i> please, Frank?
</I>
I've never used grub2 myself. But the article states that if you have
grub2 on the MBR and define a chainloader menu.lst entry for a partition
that has grub on the PBR, it works.
That makes sense. Chainloading simply means that the MBR bootloader
reads the PBR into memory and passes control to it exactly as the BIOS
reads the MBR into memory and passes control to it. Assuming that both
grub and grub2 support chainloading correctly, neither one of them
should have any idea whether it's an MBR that was loaded by the BIOS or
a PBR that was chainloaded by an MBR.
This glosses over other sources of problems like UEFI and GPT, but it
has always been the case that if you want to support multiple boot
loaders, you have to use a lowest common denomination architecture that
they all support.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="021852.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3
</A></li>
<LI>Next message: <A HREF="021854.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#21853">[ date ]</a>
<a href="thread.html#21853">[ thread ]</a>
<a href="subject.html#21853">[ subject ]</a>
<a href="author.html#21853">[ 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>