About

From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RI42u-00089F-Fu for garchives@archives.gentoo.org; Sun, 23 Oct 2011 19:49:24 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A184F21C119; Sun, 23 Oct 2011 19:49:12 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 5C34B21C119 for ; Sun, 23 Oct 2011 19:49:12 +0000 (UTC) Received: from pelican.gentoo.org (unknown [66.219.59.40]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 84E531B401D for ; Sun, 23 Oct 2011 19:49:11 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by pelican.gentoo.org (Postfix) with ESMTP id EF4DB80042 for ; Sun, 23 Oct 2011 19:49:10 +0000 (UTC) From: "Matěj Laitl" To: gentoo-commits@lists.gentoo.org Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Matěj Laitl" Message-ID: <818b4b1d30cee0a2a16e7262ff1342bd50e052ef.matej@gentoo> Subject: [gentoo-commits] dev/scarabeus:master commit in: docs/ X-VCS-Repository: dev/scarabeus X-VCS-Files: docs/grub-2-guide.xml X-VCS-Directories: docs/ X-VCS-Committer: matej X-VCS-Committer-Name: Matěj Laitl X-VCS-Revision: 818b4b1d30cee0a2a16e7262ff1342bd50e052ef Date: Sun, 23 Oct 2011 19:49:10 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: ea3deed6e07fe5ef2a7872c9c64e944d commit: 818b4b1d30cee0a2a16e7262ff1342bd50e052ef Author: Moritz Schlarb moritz-schlarb de> AuthorDate: Sun Oct 23 19:48:23 2011 +0000 Commit: Mat=C4=9Bj Laitl laitl cz> CommitDate: Sun Oct 23 19:48:23 2011 +0000 URL: http://git.overlays.gentoo.org/gitweb/?p=3Ddev/scarabeus.git;= a=3Dcommit;h=3D818b4b1d GRUB 2 Guide fixes by Moritz Schlarb --- 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 G= RUB 2 bootloader. =20 1 -2011-10-11 +2011-10-23 =20 About @@ -62,30 +62,30 @@ Some examples of new features: =20

-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 sy= stem in an +unbootable state. Fortunately, no data is lost in most cases and recover= y is not hard, but we recommend you to have a bootable CD, DVD or a USB flash dis= k with Linux around (Gent= oo LiveDVD or System Rescue C= D 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 backi= ng it up.

=20

-# # 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=3D/dev/sda of=3D/path/to/backup/first-sectors count=3D63

=20 -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) a= nd -/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. =20

-When something goes wrong, you can restore previous grub installation by +When something goes wrong, you can restore the previous grub installatio= n by booting some Linux live media and issuing following commands.

=20 @@ -99,14 +99,14 @@ booting some Linux live media and issuing following c= ommands. =20 -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 b= ackup. +Replace /dev/sda with the device node of the disk you boot from a= nd +/path/to/backup with the path to the place where you've stored yo= ur backup. =20 Writing directly to disk sectors (even those that are outside of partiti= ons in typical setup) is risky operation and will make your data inaccess= ible -if you changed your parititon layout between backup and restore. Other s= lower +if you changed your partition layout between backup and restore. Other s= lower and safer option would be chrooting into your Gentoo installation and re-installing bootloader - you can use G= entoo 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 =3Dsys-boo= t/grub-1.99:

=20

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

=20 @@ -237,7 +237,7 @@ Replace /dev/sda with the disk you want to hav= e the EFI System Partition /dev/sda1 with the partition designated for it in all following s= amples. =20 -

+ # gdisk -l /dev/sda
 (...)
=20
@@ -245,7 +245,7 @@ Number  Start (sector)    End (sector)  Size       Co=
de  Name
    1              34          411647   201.0 MiB   EF00  
 
=20
-+ # parted -l
 (...)
=20
@@ -258,7 +258,7 @@ In case the disk partition scheme is MBR (MS-DOS), th=
e EFI System Partition shou
 have type EF. Create or re-type it, it should be at least 100 MiB=
 large here, too.
 
=20
-+ # fdisk -l /dev/sda
 (...)
=20
@@ -343,7 +343,7 @@ partition where GRUB 2 EFI application is executed fr=
om
 -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)
 
=20
 
@@ -357,14 +357,14 @@ shell available even in cases GRUB 2 cannot load ot=
her modules
 
 
=20
-When GRUB 2 image (EFI application) is made, you have to tell your fi=
rmware
+
When the GRUB 2 image (EFI application) is made, you have to tell you=
r 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 firs=
t and
 we encourage you to do so, since it is simpler.
 
=20
-+ # 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.
 
=20
-+ # efibootmgr TODO TODO TODO
 
=20
@@ -387,8 +387,8 @@ Various sources report that the bless command =
should be used instead.
 
=20
 
-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 c=
reated
+Last, you should create a GRUB 2 environment file (where GRUB 2 stores p=
ersistent
+variables such as the number of the last booted item) as it is not creat=
ed
 automatically:
 
=20
@@ -398,7 +398,7 @@ automatically:
=20
 
 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 installe=
d GRUB
+such. Failure to do so would result in you using (parts of) the previous=
ly installed GRUB
 version.
 
=20
@@ -478,13 +478,13 @@ Remember to replace the <UUID> with yo=
ur device UUID.
 
=20
 
-GRUB 2 itself detects the LVM correctly, with no aditional setup require=
d.
+GRUB 2 itself detects the LVM correctly, with no additional setup requir=
ed.
 
=20
 
 If you placed your root and boot partitions inside LVM make sure that di=
sk
 you plan to use as booting one has at least few MBs of space before firs=
t
-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.