summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2013-February/022349.html
blob: cc57230193bf5bef6c1b82b86847890804debdb8 (plain)
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
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
<!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=%3C510CA8BB.30201%40earthlink.net%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="022347.html">
   <LINK REL="Next"  HREF="022350.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Grub2 vs. Grub Legacy in M3</H1>
    <B>Felix Miata</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Grub2%20vs.%20Grub%20Legacy%20in%20M3&In-Reply-To=%3C510CA8BB.30201%40earthlink.net%3E"
       TITLE="[Mageia-dev] Grub2 vs. Grub Legacy in M3">mrmazda at earthlink.net
       </A><BR>
    <I>Sat Feb  2 06:48:43 CET 2013</I>
    <P><UL>
        <LI>Previous message: <A HREF="022347.html">[Mageia-dev] disable a warning as error?
</A></li>
        <LI>Next message: <A HREF="022350.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#22349">[ date ]</a>
              <a href="thread.html#22349">[ thread ]</a>
              <a href="subject.html#22349">[ subject ]</a>
              <a href="author.html#22349">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On 2013-01-28 19:27 (GMT) Barry Jackson composed:

&gt;<i> Grub2 can install it's kernel in the root filesystem which can be booted
</I>&gt;<i> directly. Installing the grub2 package, whether during install or later
</I>&gt;<i> automatically builds /boot/grub/i386-pc/core.img and also creates a
</I>&gt;<i> grub.cfg ready for use.
</I>&gt;<i> Chanloading is un-necessary since an entry in menu.lst on a legacy
</I>&gt;<i> system will boot a grub2 Mageia system using:
</I>
&gt;<i>    	title Mageia via GRUB 2
</I>&gt;<i> 	root (hdx,y)
</I>&gt;<i>    	kernel /boot/grub2/i386-pc/core.img
</I>
&gt;<i> ...as explained in the above README.Mageia
</I>
&gt;&gt;<i> If you do it this way, you can install whatever you want as a bootloader
</I>&gt;&gt;<i> on the MBR, and each partition can have whatever BIOS-compliant
</I>&gt;&gt;<i> bootloader it wants, including grub, grub2, lilo, OS/2, DOS, or Wndows.
</I>
&gt;<i> Yes, I use a small grub2 partition sda1 as &quot;master&quot;.
</I>&gt;<i> To boot into Mageia grub2 systems I use the grub2 multiboot command:
</I>
&gt;<i> 	menuentry 'Mageia-3 multi sda6' {
</I>&gt;<i> 	search --no-floppy --label --set=root mageia-3
</I>&gt;<i> 	multiboot /boot/grub2/i386-pc/core.img
</I>&gt;<i> 	}
</I>
This thread made it register in my brain for the first time that Grub2 can be 
installed on the same / as Grub Legacy without interfering with it. So, on 
one of my two Cauldron systems configured to my whim with Grub Legacy, I did:

	# urpmi grub2

Which tried to intstall

	grub2
	os-prober
	mageia-theme-default
	mageia-theme-common
	plymouth-plugin-label
	plymouth-plugin-script
	plymouth-system-theme

Proceed...? N

	# urpmi --no-suggests grub2

which installed only grub2 and os-prober, and took several minutes to 
complete (which the known lethargic os-prober is obviously responsible for).

I added a stanza to my master bootloader to load /boot/grub2/i386-pc/core.img 
and rebooted, selecting the /boot/grub2/i386-pc/core.img stanza. Results:

Good start:
1-/boot/grub2/i386-pc/core.img in a Grub Legacy stanza succeeds

Not good from then on:
1-Grub2 error message due to not finding some png file

2-25 item Grub 2.00 menu (grub.cfg:
	<A HREF="http://fm.no-ip.com/Tmp/Linux/Mdv/grub.cfg.gx27b-cauldron3-1.txt">http://fm.no-ip.com/Tmp/Linux/Mdv/grub.cfg.gx27b-cauldron3-1.txt</A> ). After 
selecting a selection from a master bootloader, there's no good reason to see 
similar selections as in the previous menu unrelated to the chosen selection. 
IOW, when not a master bootloader (i.e. &quot;chainloaded&quot; via core.img, only 
Mageia entries attributable to selected filesystem hosting core.img should be 
in this menu.

3-Grub2 menu uses same awful spindly-looking font responsible in large part 
for my distaste for *buntu

4-default menu selection for Cauldron causes this cmdline:

	BOOT_IMAGE=/boot/vmlinuz-prv root=UUID=bbe8a402-5fb1-4247-b372-5bb6cff4e18c 
ro splash

which is nothing like the default Grub Legacy menu stanza's cmdline result:

	root=LABEL=22cauldrn splash=verbose noresume video=1152x864 vga=794 3

obviously caused by Grub2 installation disregarding content of pre-existing 
menu.lst, which means

5-semi-legible blue on black graphical progress bar instead of normal 
complement of startup messages when splash=verbose

6-post ESC, startup messages are inappropriately tiny

7-tty text is too tiny to use (same as startup messages; screen's preferred 
mode 1600x1200 used instead of legible mode 1152x864)

8-KDM is on tty2, the location I reserve for certain class of recurring 
activities, instead of where expected on tty7

9-preferred initial runlevel as evidenced by menu.lst cmdline options was not 
specified

10-tty1 cleared before displaying login prompt (even after customizing 
/etc/systemd/sytem/getty.target.wants/<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">getty at tty1.service</A> with 
s/TTYVTDisallocate=yes/TTYVTDisallocate=no/; same problem on Rawhide &amp; 
Factory; OT)

Such displeasures as 1-9 are the reason why in Grub Legacy vs. Grub2 
discussions I point out that Grub2 is still v1.0 software. Just how much of 
these observations are due to upstream decisions or yet-to-dos rather than 
distro implementation decisions, implementor inexperience or bugs I won't try 
to guess.
--
&quot;The wise are known for their understanding, and pleasant
words are persuasive.&quot; Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  <A HREF="http://fm.no-ip.com/">http://fm.no-ip.com/</A>
</PRE>






























<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="022347.html">[Mageia-dev] disable a warning as error?
</A></li>
	<LI>Next message: <A HREF="022350.html">[Mageia-dev] Grub2 vs. Grub Legacy in M3
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#22349">[ date ]</a>
              <a href="thread.html#22349">[ thread ]</a>
              <a href="subject.html#22349">[ subject ]</a>
              <a href="author.html#22349">[ 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>