From c72a27b26a369fa955a1fc746ca3bce803b03125 Mon Sep 17 00:00:00 2001 From: Marja van Waes Date: Sun, 26 Aug 2012 11:46:27 +0000 Subject: improved testfiles from Calenco --- setupBootloader.html | 198 +++++++++++++++++++++++++++++++++++++++++++++++---- 1 file changed, 185 insertions(+), 13 deletions(-) (limited to 'setupBootloader.html') diff --git a/setupBootloader.html b/setupBootloader.html index 65c0494..cb7688c 100644 --- a/setupBootloader.html +++ b/setupBootloader.html @@ -2,46 +2,218 @@ - setupBootloader + Bootloader main options - - -
+
-

setupBootloader +

Bootloader main + options

+ - + - + - -

This page is setupBootloader -

+

If you prefer + different bootloader settings to those chosen automatically by the + installer, you can change them here. +

+ -

Clicking which help button leads to this page? +

You may already have + another operating system on your machine, in which case you need to decide + whether to add Mageia to your existing bootloader, or allow Mageia to create + a new one.

+ +
+ + + + + + + + +
[Tip]
+ +

The Mageia + graphical menu is nice :) +

+ +
+
+ -

.... -

+
+
+
+
+

Using the Mageia + bootloader +

+
+
+
+ + + +

By default Mageia + writes a new GRUB bootloader into the MBR (Master Boot Record) of your + first hard drive. If you already have other operating systems installed, + Mageia attempts to add them to your new Mageia boot menu. +

+ + +

This works + correctly in the majority of cases for Linux and + Windows® + systems. +

+ + +
+ + + + + + + + +
[Warning]
+ +

Linux systems + which use the GRUB2 bootloader (e.g. more recent Debian/Ubuntu + derivatives) are not currently supported and will not be recognised. One + possible solution for this is to follow the steps explained here the section called “Adding a GRUB2 based system + manually” before installing Mageia next to such a + system, however there is no guarantee. +

+ + +

If you are + already installing Mageia without having taken those steps, (and do not + already know the GRUB2 version and/or it's root partition) then install + the Mageia bootloader in the root partition for now (see next section), + and inspect your GRUB2 based system after rebooting at the end of the + installation. Note that you will not yet be able to boot Mageia, however + you will be able to use the Mageia install DVD to perform a quick + "upgrade install" at a later date to correctly install the bootloader to + the MBR. +

+ +
+
+ +
+ +
+
+
+
+

Using an + existing bootloader +

+
+
+
+ + + +

If you decide to + use an existing bootloader then you will need to remember to STOP at the + summary page during the installation and click the Bootloader + Configure button, which will allow you to change + the bootloader install location. +

+ + +

Do not select a + device e.g."sda", or you will overwrite your existing MBR. You must select + the root partition that you chose during the partitioning phase earlier + e.g. sda7. +

+ + +

To be clear, sda + is a device, sda7 is a partition. +

+ + +
+ + + + + + + + +
[Tip]
+ +

Go to tty2 + with Ctrl+Alt+F2 and type df to check where your + / (root) partition is. Ctrl+Alt+F7 takes you back to + the installer screen. +

+ +
+
+ + +

The exact + procedure for adding your Mageia system to an existing bootloader is + beyond the scope of this help, however in most cases it will involve + running the relevant bootloader installation program which should detect + and add it automatically. See the documentation for the operating system + in question. +

+ +
+
+
+
+
+

Bootloader + advanced option +

+
+
+
+ + + +

If you have very + limited disk space for the / partition that contains + /tmp, click on Advanced and + check the box for Clean /tmp at each boot. This helps + to maintain some free space. +

+ +
+
-- cgit v1.2.1