|
|
@@ -85,7 +85,7 @@ cat device.map</userinput></screen>
|
|
|
|
|
|
<screen role="nodump"><userinput>grub-install --grub-setup=/bin/true /dev/sda</userinput></screen>
|
|
|
|
|
|
- <para>We use --grub-setup=/bin/true for now to prevent update the
|
|
|
+ <para>We use --grub-setup=/bin/true for now to prevent updating
|
|
|
Master Boot Record (MBR). In this way, we can test our installation
|
|
|
before committing to a change that is hard to revert.</para>
|
|
|
|
|
|
@@ -148,7 +148,7 @@ menuentry "GNU/Linux, Linux 2.6.28-11-server (recovery mode)" {
|
|
|
</computeroutput></screen>
|
|
|
|
|
|
<para>Note that even though there is a warning not to edit the file, you can
|
|
|
- do so as long as you do not re-reun <command>grub-mkconfig</command>. The
|
|
|
+ do so as long as you do not re-run <command>grub-mkconfig</command>. The
|
|
|
<emphasis>search</emphasis> lines are not meaningful for LFS systems as that
|
|
|
command needs an initrd image for processing. If installing on a separate
|
|
|
partition the linux and initrd lines will not have the /boot on the file
|
|
|
@@ -214,7 +214,7 @@ grub> boot</userinput></screen>
|
|
|
instruction is not found in grub.cfg. This is the partition that is
|
|
|
searched for the kernel and other supporting files. It is different from
|
|
|
the 'root=' parameter on the 'linux' line in the configuration line. The
|
|
|
- later is the partition the kernel mounts as '/'. In the example grub.cfg
|
|
|
+ latter is the partition the kernel mounts as '/'. In the example grub.cfg
|
|
|
above, both values point to /dev/sda2, but if there is a separate boot
|
|
|
partition, they will be different.</para></note>
|
|
|
|
Bruce Dubbs