From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2013-January/021858.html | 101 ++++++++++++++++++++++++++++ 1 file changed, 101 insertions(+) create mode 100644 zarb-ml/mageia-dev/2013-January/021858.html (limited to 'zarb-ml/mageia-dev/2013-January/021858.html') diff --git a/zarb-ml/mageia-dev/2013-January/021858.html b/zarb-ml/mageia-dev/2013-January/021858.html new file mode 100644 index 000000000..b10f2c865 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-January/021858.html @@ -0,0 +1,101 @@ + + + + [Mageia-dev] Grub2 vs. Grub Legacy in M3 + + + + + + + + + +

[Mageia-dev] Grub2 vs. Grub Legacy in M3

+ James Kerr + jim at jkerr82508.free-online.co.uk +
+ Sun Jan 20 15:39:26 CET 2013 +

+
+ +
On 20/01/2013 13:30, Maurice Batey wrote:
+> On Sun, 20 Jan 2013 13:08:57 +0000, Barry Jackson wrote:
+>
+>> Installing the grub2 package will not impact your current bootloader in
+>> any way.
+>
+>    Installing GRUB2 where, Barry?
+> (MBR or  Root partition?)
+>
+> If - as I did with Ubuntu 12.01 - GRUB2 goes into the MBR, then I can
+> no longer boot from its menu into a GRUB Legacy install, a I said
+> earlier (despite the GRUB2 boot menu purporting to do so).
+>
+
+On a recent install of Beta1, I chose Grub2 and selected to put the 
+boot-loader in the MBR of the boot disk, replacing the legacy grub 
+boot-loader of Mageia2. Grub2 created a boot menu that enables me to 
+successfully boot the pre-existing Mageia2 installation.
+
+Jim
+
+
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1