About

From 818b4b1d30cee0a2a16e7262ff1342bd50e052ef Mon Sep 17 00:00:00 2001 From: Moritz Schlarb Date: Sun, 23 Oct 2011 21:48:23 +0200 Subject: GRUB 2 Guide fixes by Moritz Schlarb --- docs/grub-2-guide.xml | 58 +++++++++++++++++++++++++-------------------------- 1 file 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. 1 -2011-10-11 +2011-10-23 About @@ -62,30 +62,30 @@ Some examples of new features:

-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 (Gentoo LiveDVD or System Rescue CD 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.

-# # copy grub modules and configuration
+# # backup grub modules and configuration
 # cp -a /boot/grub /path/to/backup/
 # # backup the MBR and GRUB stage 1.5
 # dd if=/dev/sda of=/path/to/backup/first-sectors count=63

-Replace /dev/sda with device node of the disk you boot from (this is -usually and the whole disk like sda, not a partition like sda1) and -/path/to/backup with path to your favourite backup medium. +Replace /dev/sda with the device node of the disk you boot from (this is +usually the whole disk like sda, not a partition like sda1) and +/path/to/backup with the path to your favourite backup medium.

-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.

@@ -99,14 +99,14 @@ booting some Linux live media and issuing following commands. -Replace /dev/sda with device node of the disk you boot from and -/path/to/backup with path to the place where you've stored your backup. +Replace /dev/sda with the device node of the disk you boot from and +/path/to/backup with the path to the place where you've stored your backup. Writing directly to disk sectors (even those that are outside of partitions in typical setup) is risky operation and will make your data inaccessible -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 Gentoo Handbook for that task. @@ -129,11 +129,11 @@ should be set in /etc/make.conf.

Description of mostly used values for GRUB_PLATFORMS as of =sys-boot/grub-1.99:

pc: normal BIOS pc
efi-64: EFI systems, their latest 64b version
pc: Normal BIOS PC
efi-64: EFI systems, their latest 64-bit version
coreboot: Coreboot replacement of BIOS
qemu: support for QEMU booting
yeelong: Support for MIPS loongson
qemu: Support for QEMU booting
yeeloong: Support for MIPS loongson

@@ -237,7 +237,7 @@ Replace /dev/sda with the disk you want to have the EFI System Partition /dev/sda1 with the partition designated for it in all following samples. -

+ # gdisk -l /dev/sda
 (...)
 
@@ -245,7 +245,7 @@ Number  Start (sector)    End (sector)  Size       Code  Name
    1              34          411647   201.0 MiB   EF00  
 
 
-+ # parted -l
 (...)
 
@@ -258,7 +258,7 @@ In case the disk partition scheme is MBR (MS-DOS), the EFI System Partition shou
 have type EF. Create or re-type it, it should be at least 100 MiB large here, too.
 
 
-+ # fdisk -l /dev/sda
 (...)
 
@@ -343,7 +343,7 @@ partition where GRUB 2 EFI application is executed from
 -O
 platform to create image for
 x86_64-efi
-replace with i386-efi on 32bit systems (old Intel Macs)
+replace with i386-efi on 32-bit systems (old Intel Macs)
 
 
 
@@ -357,14 +357,14 @@ shell available even in cases GRUB 2 cannot load other modules
 
 
 
-When GRUB 2 image (EFI application) is made, you have to tell your firmware
+
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.
 
 
-+ # mkdir -p /boot/EFI/BOOT
 # cp /boot/grub2/grub.efi /boot/EFI/BOOT/BOOTX64.EFI
 
@@ -373,11 +373,11 @@ we encourage you to do so, since it is simpler.
 EFI 2 specification says that the default bootloader location is [EFI System
 Partition]\EFI\BOOT\BOOTx64.EFI for x86_64 hardware. (and
 ...\BOOTIA32.EFI 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.
 
 
-+ # efibootmgr TODO TODO TODO
 
 
@@ -387,8 +387,8 @@ Various sources report that the bless command should be used instead.
 
 
 
-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:
 
 
@@ -398,7 +398,7 @@ automatically:
 
 
 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.
 
 
@@ -478,13 +478,13 @@ Remember to replace the <UUID> with your device UUID.
 
 
 
-GRUB 2 itself detects the LVM correctly, with no aditional setup required.
+GRUB 2 itself detects the LVM correctly, with no additional setup required.
 
 
 
 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.
 
-- 
cgit v1.2.3