1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
|
<!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=%3C50FBEC69.6000204%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="021853.html">
<LINK REL="Next" HREF="021855.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=%3C50FBEC69.6000204%40zen.co.uk%3E"
TITLE="[Mageia-dev] Grub2 vs. Grub Legacy in M3">zen25000 at zen.co.uk
</A><BR>
<I>Sun Jan 20 14:08:57 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="021853.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3
</A></li>
<LI>Next message: <A HREF="021855.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#21854">[ date ]</a>
<a href="thread.html#21854">[ thread ]</a>
<a href="subject.html#21854">[ subject ]</a>
<a href="author.html#21854">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 20/01/13 12:55, Maurice Batey wrote:
><i> On Sun, 20 Jan 2013 07:41:28 -0500, Frank Griffin wrote:
</I>><i>
</I>>><i> According to this article, grub and grub2 each support chainloading the
</I>>><i> other. So I really don't see why there's a problem
</I>><i>
</I>><i> Note that he says:
</I>><i>
</I>><i> "I then login to that, edit the menu.lst file as desribed above to
</I>><i> add the new Grub2 installation, and then restore Legacy Grub
</I>><i> as the primary bootloader"
</I>><i>
</I>><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.
</I>><i> (Yes, I know GRUB2 boot menus do show options to boot existing
</I>><i> GRUB Legacy installs, but in my experience (with Ubuntu and Mint) they
</I>><i> *fail* to boot them.)
</I>><i>
</I>><i> Despite my requests in various newsgroups, NO ONE has offered a
</I>><i> description of how to get a GRUB2 boot menu to successfully boot a
</I>><i> GRUB Legacy install.
</I>><i>
</I>><i> Can you, please, Frank?
</I>><i>
</I>
There is no problem at all.
Your issues with Ubuntu etc in the past were probably due to a bug in
os-prober which was fixed in version 1.53.
Mageia grub2 will correctly detect and boot legacy grub systems.
If you install the grub2 package (assuming you did not at install time)
then you can test this quite easily.
Installing the grub2 package will not impact your current bootloader in
any way.
Once it's installed read /usr/share/doc/grub2/README.Mageia to find how
to add an entry to your existing menu.lst to boot into the new grub2
menu from your existing legacy grub.
Barry
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="021853.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3
</A></li>
<LI>Next message: <A HREF="021855.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#21854">[ date ]</a>
<a href="thread.html#21854">[ thread ]</a>
<a href="subject.html#21854">[ subject ]</a>
<a href="author.html#21854">[ 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>
|
