diff options
| -rw-r--r-- | docs/grub-2-guide.xml | 58 |
1 files changed, 29 insertions, 29 deletions
diff --git a/docs/grub-2-guide.xml b/docs/grub-2-guide.xml index b1cdd28..42ab32b 100644 --- a/docs/grub-2-guide.xml +++ b/docs/grub-2-guide.xml @@ -27,7 +27,7 @@ This guide shows you how to install and configure the GRUB 2 bootloader. <license/> <version>1</version> -<date>2011-10-11</date> +<date>2011-10-23</date> <chapter> <title>About</title> @@ -62,30 +62,30 @@ Some examples of new features: <body> <p> -Playing with bootloader always brings the danger of leaving your system in -unbootable state. Fortunately no data is lost in most cases and recovery is not +Playing with your bootloader always brings the danger of leaving your system in an +unbootable state. Fortunately, no data is lost in most cases and recovery is not hard, but we recommend you to have a bootable CD, DVD or a USB flash disk with Linux around (<uri link="http://www.gentoo.org/main/en/where.xml">Gentoo LiveDVD</uri> or <uri link="http://www.sysresccd.org/">System Rescue CD</uri> will do) and to backup your current bootloader setup. If your current -bootloader is GRUB legacy, following code sample may help you backing it up. +bootloader is GRUB Legacy, the following code sample will help you backing it up. </p> <pre caption="Backing up GRUB"> -# <comment># copy grub modules and configuration</comment> +# <comment># backup grub modules and configuration</comment> # <i>cp -a /boot/grub <keyword>/path/to/backup</keyword>/</i> # <comment># backup the MBR and GRUB stage 1.5</comment> # <i>dd if=<keyword>/dev/sda</keyword> of=<keyword>/path/to/backup</keyword>/first-sectors count=63</i> </pre> <note> -Replace <c>/dev/sda</c> with device node of the disk you boot from (this is -usually and the whole disk like <e>sda</e>, not a partition like sda1) and -<c>/path/to/backup</c> with path to your favourite backup medium. +Replace <c>/dev/sda</c> with the device node of the disk you boot from (this is +usually the whole disk like <e>sda</e>, not a partition like <e>sda1</e>) and +<c>/path/to/backup</c> with the path to your favourite backup medium. </note> <p> -When something goes wrong, you can restore previous grub installation by +When something goes wrong, you can restore the previous grub installation by booting some Linux live media and issuing following commands. </p> @@ -99,14 +99,14 @@ booting some Linux live media and issuing following commands. </pre> <note> -Replace <c>/dev/sda</c> with device node of the disk you boot from and -<c>/path/to/backup</c> with path to the place where you've stored your backup. +Replace <c>/dev/sda</c> with the device node of the disk you boot from and +<c>/path/to/backup</c> with the path to the place where you've stored your backup. </note> <warn> Writing directly to disk sectors (even those that are outside of partitions in typical setup) is risky operation and will make your data <e>inaccessible</e> -if you changed your parititon layout between backup and restore. Other slower +if you changed your partition layout between backup and restore. Other slower and safer option would be chrooting into your Gentoo installation and re-installing bootloader - you can use <uri link="/doc/en/handbook/">Gentoo Handbook</uri> for that task. @@ -129,11 +129,11 @@ should be set in /etc/make.conf. <p>Description of mostly used values for GRUB_PLATFORMS as of =sys-boot/grub-1.99:</p> <ol> -<li>pc: normal BIOS pc</li> -<li>efi-64: EFI systems, their latest 64b version</li> +<li>pc: Normal BIOS PC</li> +<li>efi-64: EFI systems, their latest 64-bit version</li> <li>coreboot: Coreboot replacement of BIOS</li> -<li>qemu: support for QEMU booting</li> -<li>yeelong: Support for MIPS loongson</li> +<li>qemu: Support for QEMU booting</li> +<li>yeeloong: Support for MIPS loongson</li> </ol> @@ -237,7 +237,7 @@ Replace <c>/dev/sda</c> with the disk you want to have the EFI System Partition <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"> +<pre caption="EFI System Partition on GPT disk as shown by gdisk"> # <i>gdisk -l <keyword>/dev/sda</keyword></i> <comment>(...)</comment> @@ -245,7 +245,7 @@ Number Start (sector) End (sector) Size Code Name <ident> 1 34 411647 201.0 MiB EF00 </ident> </pre> -<pre caption="EFI System Partion on GPT disk as shown by parted"> +<pre caption="EFI System Partition on GPT disk as shown by parted"> # <i>parted -l</i> <comment>(...)</comment> @@ -258,7 +258,7 @@ In case the disk partition scheme is MBR (MS-DOS), the EFI System Partition shou 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"> +<pre caption="EFI System Partition on MBR disk as shown by fdisk"> # <i>fdisk -l <keyword>/dev/sda</keyword></i> <comment>(...)</comment> @@ -343,7 +343,7 @@ partition where GRUB 2 EFI application is executed from</b></ti> <th>-O</th> <ti>platform to create image for</ti> <ti><c>x86_64-efi</c></ti> -<ti>replace with <c>i386-efi</c> on 32bit systems (old Intel Macs)</ti> +<ti>replace with <c>i386-efi</c> on 32-bit systems (old Intel Macs)</ti> </tr> <tr> @@ -357,14 +357,14 @@ shell available even in cases GRUB 2 cannot load other modules</ti> </tr> </table> -<p>When GRUB 2 image (EFI application) is made, you have to tell your firmware +<p>When the GRUB 2 image (EFI application) is made, you have to tell your firmware to execute it upon boot. There are two ways to achieve this. If there is already a default bootloader on your EFI System Partition that you don't want to overwrite, you have to use the second. Otherwise you can use the first and we encourage you to do so, since it is simpler. </p> -<pre caption="Subvariant 1: copying grub.efi into default location for EFI bootloader (must be done everytime GRUB 2 is updated)"> +<pre caption="Subvariant 1: Copying grub.efi into default location for EFI bootloader (must be done everytime GRUB 2 is updated)"> # <i>mkdir -p /boot/EFI/BOOT</i> # <i>cp /boot/grub2/grub.efi /boot/EFI/BOOT/BOOTX64.EFI</i> </pre> @@ -373,11 +373,11 @@ we encourage you to do so, since it is simpler. EFI 2 specification says that the default bootloader location is <c>[EFI System Partition]\EFI\BOOT\BOOTx64.EFI</c> for x86_64 hardware. (and <c>...\BOOTIA32.EFI</c> on 32bit systems) While FAT32 filesystems should be -case-insesitive, it is recommended to use ALL-CAPS filenames in default +case-insensitive, it is recommended to use ALL-CAPS filenames in default bootloader path in order to be compatible with all vfat mount options. </note> -<pre caption="Subvariant 2: use efibootmgr to tell firmware what to execute on boot"> +<pre caption="Subvariant 2: Use efibootmgr to tell firmware what to execute on boot"> # <i>efibootmgr TODO TODO TODO</i> </pre> @@ -387,8 +387,8 @@ Various sources report that the <c>bless</c> command should be used instead. </warn> <p> -Last, you should create a GRUB 2 environment file (where GRUB 2 stores -persistent variables such number of the last booted item) as it is not created +Last, you should create a GRUB 2 environment file (where GRUB 2 stores persistent +variables such as the number of the last booted item) as it is not created automatically: </p> @@ -398,7 +398,7 @@ automatically: <impo> When you update GRUB 2, be sure to execute all commands that are marked as -such. Failure to do so would result in you using the previously installed GRUB +such. Failure to do so would result in you using (parts of) the previously installed GRUB version. </impo> @@ -478,13 +478,13 @@ Remember to replace the <i><UUID></i> with your device UUID. <body> <p> -GRUB 2 itself detects the LVM correctly, with no aditional setup required. +GRUB 2 itself detects the LVM correctly, with no additional 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 GRUB 2 needs more space to store lvm loader. In other +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> |