summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--docs/grub-2-guide.xml97
1 files changed, 50 insertions, 47 deletions
diff --git a/docs/grub-2-guide.xml b/docs/grub-2-guide.xml
index ca0bc89..8b587d6 100644
--- a/docs/grub-2-guide.xml
+++ b/docs/grub-2-guide.xml
@@ -10,12 +10,16 @@
<mail link="matej@laitl.cz">Matěj Laitl</mail>
</author>
+<author title="Editor">
+ <mail link="mail@moritz-schlarb.de">Moritz Schlarb</mail>
+</author>
+
<author title="Author">
<mail link="scarabeus"/>
</author>
<abstract>
-This guide shows you how to install and configure GRUB 2 bootloader.
+This guide shows you how to install and configure the GRUB 2 bootloader.
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
@@ -23,7 +27,7 @@ This guide shows you how to install and configure GRUB 2 bootloader.
<license/>
<version>1</version>
-<date>2011-08-26</date>
+<date>2011-10-10</date>
<chapter>
<title>About</title>
@@ -32,7 +36,7 @@ This guide shows you how to install and configure GRUB 2 bootloader.
<p>
GRUB 2 is next generation bootloader that brings many long awaited features
-that were not availible in Grub Legacy (0.9*).
+that were not available in GRUB Legacy (0.9*).
</p>
<p>
@@ -57,9 +61,9 @@ Some examples of new features:
<body>
<p>
-By default grub tries to detect the desired platform during configure from your
+By default, GRUB 2 tries to detect the desired platform during configure from your
toolchain and CPU. If you want support for other platforms or just don't want
-to use the autodetection you should use GRUB_PLATFORMS use expand. This variable
+to use the autodetection, you should use GRUB_PLATFORMS use expand. This variable
should be set in /etc/make.conf.
</p>
@@ -88,31 +92,31 @@ easily render your system impossible to boot.
</section>
<section>
-<title>Configuring GRUB</title>
+<title>Configuring GRUB 2</title>
<body>
<impo>
-Gentoo installs grub renamed to grub2. So if you read any other guide you
+Gentoo installs all grub commands renamed to grub2. So if you read any other guide you
should replace all grub mentions with grub2 <i>(grub-mkconfig -> grub2-mkconfig)</i>.
</impo>
<p>
-Compared to grub-legacy current grub uses automatic generation to generate
+Compared to GRUB Legacy, GRUB 2 uses automatic generation to generate
all the required entries for you to boot. This is handled by <i>grub2-mkconfig</i>
command that probes your system for all the required data. Cooperating with
-<i>sys-boot/os-prober</i> it detects even other OSes on all disks.
+<i>sys-boot/os-prober</i>, it detects even other OSes on all disks.
</p>
<impo>
-If you updated from grub-legacy then your <path>/boot/grub/menu.lst</path>
-Was converted to <path>/boot/grub2/grub.cfg</path> to ensure that your system
+If you updated from GRUB Legacy then your <path>/boot/grub/menu.lst</path>
+was converted to <path>/boot/grub2/grub.cfg</path> to ensure that your system
can boot even if you forget to generate the config. Never the less you should
take time and migrate the configuration to be automatically generated, because
-next time grub2 is installed it will use automatic generation and ignore
-grub-legacy files.
+next time GRUB 2 is installed it will use automatic generation and ignore
+GRUB Legacy files.
</impo>
-<pre caption="Generating the grub2 config">
+<pre caption="Generating the GRUB 2 config">
grub2-mkconfig -o /boot/grub2/grub.cfg
</pre>
@@ -123,14 +127,14 @@ All the options are described in grub2 info pages.
</p>
<note>
-This file is created by Gentoo and if you find interesting option not used
-in there just open bugreport (possibly with a patch).
+This file is created by Gentoo and if you find an interesting option not used
+in there just open a bugreport (possibly with a patch).
</note>
<p>
-Sometimes if automatic detection of grub does not suffice the file <path>
-/etc/grub.d/40_custom</path> should be used to store custom finder. Full
-description how to configure such with example can be find in grub2 info
+Sometimes, if automatic detection of GRUB 2 does not suffice, the file <path>
+/etc/grub.d/40_custom</path> should be used to store custom entries. Full
+description how to configure such with examples can be found in grub2 info
pages.
</p>
@@ -151,16 +155,16 @@ Remember to replace the <i>&lt;UUID&gt;</i> with your device UUID.
</section>
<section>
-<title>Pre-Configuring GRUB to use EFI</title>
+<title>Pre-Configuring GRUB 2 to use EFI</title>
<body>
<p>
Some newer PCs (and all Intel Macs) come with
<uri link="http://en.wikipedia.org/wiki/Extensible_Firmware_Interface">EFI</uri>
-(UEFI to be correct) as a replacement for lagacy
+(UEFI to be correct) as a replacement for legacy
and aging BIOS firmware. EFI usually can emulate BIOS environment for OS, but
that also hides some unique features of EFI such as faster boot times, support
-for GPT partition tables etc. EFI firmware comes in two flavours - 32bit and
+for GPT partition tables, etc. EFI firmware comes in two flavours - 32bit and
64bit and unless you have early Intel-based Mac with 32bit processor, your
firmware will be likely 64bit. Please note that unlike in user-space, <b>64bit
EFI firmware cannot run 32bit EFI bootloader.</b> This section will guide you
@@ -181,20 +185,20 @@ or 3.0 in order to successfully boot.
<p>
One big difference between BIOS and EFI is that EFI is able to read partition
-table (both MBR and GPT formats should be supported) and to read from specially
-labelled FAT32 partition called <b>EFI System Partition</b>. During bootup, EFI
-fimrmware can execute <e>EFI applications</e> stored in files in EFI System
+tables (both MBR and GPT formats should be supported) and to read from a specially
+labeled FAT32 partition called <b>EFI System Partition</b>. During bootup, EFI
+firmware can execute <e>EFI applications</e> stored in files in EFI System
Partition. One special EFI application is a bootloader. You may use the EFI
System Partition as your <c>/boot</c> partition if you don't mind limitations
-of FAT32 filesystem such as no support for symlinks and per-file owner and
+of the FAT32 filesystem such as no support for symlinks and per-file owner and
permissions. The rest of this section assumes that you use <c>/boot</c> for
mounting EFI System Partition.
</p>
<p>
-If you don't already have EFI System Partition, let's create one. The procedure is
-different for GPT and MBR-formatted disks. The partition need not be the first
-one on disk as in our examples. In case it is GPT-partitioned you'll need one
+If you don't already have an EFI System Partition, let's create one. The procedure is
+different for GPT and MBR-formatted disks. The partition does not need to be the first
+one on the disk as in our examples. In case it is GPT-partitioned you'll need one
of the <c>gdisk</c> (CLI, sys-apps/gptfdisk), <c>parted</c> (CLI,
sys-block/parted) or <c>gparted</c> (GUI, sys-block/gparted) partitioning
tools; <c>fdisk</c>, <c>cfdisk</c> and <c>sfdisk</c> do not currently support
@@ -203,8 +207,8 @@ GPT. In the GPT case, create a partition at least 100 MiB in size with
</p>
<note>
-Replace <c>/dev/sda</c> with disk you want to have EFI System Partition on and
-<c>/dev/sda1</c> with partition designated for it in all following samples.
+Replace <c>/dev/sda</c> with the disk you want to have the EFI System Partition on and
+<c>/dev/sda1</c> with the partition designated for it in all following samples.
</note>
<pre caption="EFI System Partion on GPT disk as shown by gdisk">
@@ -220,13 +224,12 @@ Number Start (sector) End (sector) Size Code Name
<comment>(...)</comment>
Number Start End Size File system Name Flags
-<ident> 1 17.4kB 211MB 211MB fat32 boot</ident> <comment># you may have File system field empty</comment>
+<ident> 1 17.4kB 211MB 211MB fat32 boot</ident> <comment># the File system field may be empty</comment>
</pre>
<p>
-In case the disk partition scheme is MBR (MS-DOS), EFI System Partition should
-have type <c>EF</c>. Create or re-type it, again it should be at least 100 MiB
-large.
+In case the disk partition scheme is MBR (MS-DOS), the EFI System Partition should
+have type <c>EF</c>. Create or re-type it, it should be at least 100 MiB large here, too.
</p>
<pre caption="EFI System Partion on MBR disk as shown by fdisk">
@@ -238,7 +241,7 @@ large.
</pre>
<p>
-Next create FAT32 filesystem on it if you already haven't done so. From now on,
+Next, create a FAT32 filesystem on it if you already haven't done so. From now on,
procedure is the same for both GPT and MBR-formatted disks. Program
<c>mkdosfs</c> is from package <c>sys-fs/dosfstools</c>.
</p>
@@ -249,18 +252,18 @@ mkdosfs 3.0.9 (31 Jan 2010)
</pre>
<warn>
-This command erases everything that previously was on <c>/dev/sda1</c>.
+This command erases everything that was previously on <c>/dev/sda1</c>.
</warn>
<p>
The <c>-F 32</c> option tells mkdosfs to create FAT32 filesystem and <c>-n
-efi-boot</c> option tells mkdosfs to set partition label to <c>efi-boot</c>.
-You may use atrbitrary string up to 11 characters long for label or you may not
+efi-boot</c> option tells mkdosfs to set the partition label to <c>efi-boot</c>.
+You may use arbitrary string up to 11 characters long as label or you may not
use it at all.
</p>
<p>
-After you prepared your HDDs you can easily proceed with generating the
+After you have prepared your HDDs, you can easily proceed with generating the
configuration.
</p>
@@ -272,14 +275,14 @@ configuration.
<body>
<p>
-Grub2 itself detects the LVM correctly, with no aditional setup required.
+GRUB 2 itself detects the LVM correctly, with no aditional setup required.
</p>
<impo>
If you placed your root and boot partitions inside LVM make sure that disk
you plan to use as booting one has at least few MBs of space before first
-partition, because grub2 needs more space to store lvm loader. In other
-words if you install it with not enough space it will just break your
+partition, because GRUB 2 needs more space to store lvm loader. In other
+words: If you install it with not enough space it will just break your
partition.
</impo>
@@ -288,23 +291,23 @@ partition.
</chapter>
<chapter>
-<title>Installation of grub2</title>
+<title>Installation of GRUB 2</title>
<section>
<title>Installing on some MBR/GPT directly</title>
<body>
<p>
-Installation of grub2 is similar to installation of grub-legacy.
+Installation of GRUB 2 is similar to installation of GRUB Legacy.
</p>
-<pre caption="Installing grub2 on /dev/sda">
+<pre caption="Installing GRUB 2 on /dev/sda">
grub2-install --no-floppy /dev/sda
</pre>
<impo>
If you get ANY errors during this step do not reboot your computer,
but make sure it is fixed. Your computer won't boot if installation
-fail.
+failed.
</impo>
</body>