aboutsummaryrefslogtreecommitdiffstats
path: root/chapter08/grub.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter08/grub.xml')
-rw-r--r--chapter08/grub.xml24
1 files changed, 12 insertions, 12 deletions
diff --git a/chapter08/grub.xml b/chapter08/grub.xml
index 8d92d5ea7..1ff73d777 100644
--- a/chapter08/grub.xml
+++ b/chapter08/grub.xml
@@ -47,8 +47,8 @@ xorriso -as cdrecord -v dev=/dev/cdrw blank=as_needed grub-img.iso</userinput></
the form of <emphasis>(hdn,m)</emphasis>, where <emphasis>n</emphasis>
is the hard drive number and <emphasis>m</emphasis> is the partition
number. The hard drive number starts from zero, but the partition number
- starts from one for normal partitions and five for extended partitions.
- Note that this is different from earlier versions where
+ starts from one for normal partitions and five for extended partitions.
+ Note that this is different from earlier versions where
both numbers started from zero. For example, partition <filename
class="partition">sda1</filename> is <emphasis>(hd0,1)</emphasis> to
GRUB and <filename class="partition">sdb3</filename> is
@@ -63,7 +63,7 @@ xorriso -as cdrecord -v dev=/dev/cdrw blank=as_needed grub-img.iso</userinput></
<sect2>
<title>Setting Up the Configuration</title>
- <para>GRUB works by writing data to the first physical track of the
+ <para>GRUB works by writing data to the first physical track of the
hard disk. This area is not part of any file system. The programs
there access GRUB modules in the boot partition. The default location
is /boot/grub/.</para>
@@ -90,19 +90,19 @@ xorriso -as cdrecord -v dev=/dev/cdrw blank=as_needed grub-img.iso</userinput></
class="partition">sda2</filename>.</para>
<para>Install the GRUB files into <filename
- class="directory">/boot/grub</filename> and set up the boot track:</para>
+ class="directory">/boot/grub</filename> and set up the boot track:</para>
<warning>
<para>The following command will overwrite the current boot loader. Do not
run the command if this is not desired, for example, if using a third party
- boot manager to manage the Master Boot Record (MBR).</para>
+ boot manager to manage the Master Boot Record (MBR).</para>
</warning>
<screen role="nodump"><userinput>grub-install /dev/sda</userinput></screen>
<!-- This does not seem to be true any more
- <note><para><application>grub-install</application> is a script and calls another
- program, grub-probe, that may fail with a message "cannot stat `/dev/root'".
+ <note><para><application>grub-install</application> is a script and calls another
+ program, grub-probe, that may fail with a message "cannot stat `/dev/root'".
If so, create a temporary symbolic link from your root partition to /dev/root:</para>
<screen role="nodump"><userinput>ln -sv /dev/sda2 /dev/root</userinput></screen>
@@ -136,20 +136,20 @@ EOF</userinput></screen>
used a separate /boot partition, remove /boot from the above
<emphasis>linux</emphasis> line. You will also need to change the
<emphasis>set root</emphasis> line to point to the boot partition.
- </para></note>
+ </para></note>
<para>GRUB is an extremely powerful program and it provides a tremendous
number of options for booting from a wide variety of devices, operating
- systems, and partition types. There are also many options for customization
+ systems, and partition types. There are also many options for customization
such as graphical splash screens, playing sounds, mouse input, etc. The
details of these options are beyond the scope of this introduction.</para>
<caution><para>There is a command, <application>grub-mkconfig</application>, that
can write a configuration file automatically. It uses a set of scripts in
/etc/grub.d/ and will destroy any customizations that you make. These scripts
- are designed primarily for non-source distributions and are not recommended for
- LFS. If you install a commercial Linux distribution, there is a good chance
- that this program will be run. Be sure to back up your grub.cfg file.</para></caution>
+ are designed primarily for non-source distributions and are not recommended for
+ LFS. If you install a commercial Linux distribution, there is a good chance
+ that this program will be run. Be sure to back up your grub.cfg file.</para></caution>
</sect2>