diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2013-January/022211.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2013-January/022211.html | 95 |
1 files changed, 95 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-January/022211.html b/zarb-ml/mageia-dev/2013-January/022211.html new file mode 100644 index 000000000..5120a8f24 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-January/022211.html @@ -0,0 +1,95 @@ +<!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=%3C5107C524.3050700%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="022162.html"> + <LINK REL="Next" HREF="022212.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=%3C5107C524.3050700%40roadrunner.com%3E" + TITLE="[Mageia-dev] Grub2 vs. Grub Legacy in M3">ftg at roadrunner.com + </A><BR> + <I>Tue Jan 29 13:48:36 CET 2013</I> + <P><UL> + <LI>Previous message: <A HREF="022162.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI>Next message: <A HREF="022212.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#22211">[ date ]</a> + <a href="thread.html#22211">[ thread ]</a> + <a href="subject.html#22211">[ subject ]</a> + <a href="author.html#22211">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 01/28/2013 06:44 PM, Barry Jackson wrote: +><i> My limited understanding is that the code in the 512 byte PBR has to +</I>><i> use block lists to find the core image in /boot, since it is too small +</I>><i> to understand filesystems. This is fragile in that filesystems and +</I>><i> file utilities may move files around on disk invalidating the block +</I>><i> lists, and for this reason the method is discouraged. +</I>><i> +</I>><i> A far as I know the same potential problem exists with grub legacy. +</I> +OK, we've come full circle. This is why I was used to rerunning +install.sh, because historically this has been true of most +bootloaders. They all have to fit in 512 bytes, and they all have to +load the next stage of the boot without support for filesystems. + +That's why I stick with chainloading. PBRs don't move around at the +whim of a filesystem, and if you do something to a root partition that +repositions something critical, you just rebuild the PBR as part of it. + +I wasn't aware of the MBR gap. I guess you're saying that the core.img +that fits in it *is* filesystem-aware ? Otherwise, it seems like you've +just pushed the locate-the-next-stage vulnerability from the MBR to the +MBR gap, as chainloading pushes it from the MBR to the PBR. + +Anyway, my point still stands: for anyone who just wants to have grub +and grub2 partitons coexist on the same disk with either one in the MBR, +chainloading will accomplish this without any downside that isn't +already present in grub legacy. Grub2 may be the way of the future, but +to *require* it to own the MBR is just misleading. +</PRE> + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="022162.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI>Next message: <A HREF="022212.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#22211">[ date ]</a> + <a href="thread.html#22211">[ thread ]</a> + <a href="subject.html#22211">[ subject ]</a> + <a href="author.html#22211">[ 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> |