gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-19 11:49:20 +01:00
Code Issues Packages Projects Releases Wiki Activity

Clarify some things, correct grammatical & idiomatic errors.

Browse Source
This commit is contained in:
David Bryant 2023-01-01 17:15:09 -06:00
parent f0cb1e415f
commit 8190ca0715
1 changed files with 19 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
chapter10/grub.xml
View File

@ -19,7 +19,7 @@
<note> <note>
<para> <para>
If your system has UEFI support and you wish to boot LFS with UEFI, If your system has UEFI support and you wish to boot LFS with UEFI,
you should skip this page, and config GRUB with UEFI support you should skip this page, and configure GRUB with UEFI support
using the instructions provided in using the instructions provided in
<ulink url="&blfs-book;postlfs/grub-setup.html">the BLFS page</ulink>. <ulink url="&blfs-book;postlfs/grub-setup.html">the BLFS page</ulink>.
</para> </para>
@ -54,8 +54,8 @@ xorriso -as cdrecord -v dev=/dev/cdrw blank=as_needed grub-img.iso</userinput></
<para>GRUB uses its own naming structure for drives and partitions in <para>GRUB uses its own naming structure for drives and partitions in
the form of <emphasis>(hdn,m)</emphasis>, where <emphasis>n</emphasis> the form of <emphasis>(hdn,m)</emphasis>, where <emphasis>n</emphasis>
is the hard drive number and <emphasis>m</emphasis> is the partition is the hard drive number and <emphasis>m</emphasis> is the partition
number. The hard drive number starts from zero, but the partition number number. The hard drive numbers start from zero, but the partition numbers
starts from one for normal partitions and five for extended partitions. start from one for normal partitions (from five for extended partitions).
Note that this is different from earlier versions where Note that this is different from earlier versions where
both numbers started from zero. For example, partition <filename both numbers started from zero. For example, partition <filename
class="partition">sda1</filename> is <emphasis>(hd0,1)</emphasis> to class="partition">sda1</filename> is <emphasis>(hd0,1)</emphasis> to
@ -83,12 +83,13 @@ xorriso -as cdrecord -v dev=/dev/cdrw blank=as_needed grub-img.iso</userinput></
files and access can be made from any booted system. If you choose to do files and access can be made from any booted system. If you choose to do
this, you will need to mount the separate partition, move all files in the this, you will need to mount the separate partition, move all files in the
current <filename class="directory">/boot</filename> directory (e.g. the current <filename class="directory">/boot</filename> directory (e.g. the
linux kernel you just built in the previous section) to the new partition. Linux kernel you just built in the previous section) to the new partition.
You will then need to unmount the partition and remount it as <filename You will then need to unmount the partition and remount it as <filename
class="directory">/boot</filename>. If you do this, be sure to update class="directory">/boot</filename>. If you do this, be sure to update
<filename>/etc/fstab</filename>.</para> <filename>/etc/fstab</filename>.</para>
<para>Using the current lfs partition will also work, but configuration <para>Leaving <filename class="directory">>/boot</filename> on
the current LFS partition will also work, but configuration
for multiple systems is more difficult.</para> for multiple systems is more difficult.</para>
<para>Using the above information, determine the appropriate <para>Using the above information, determine the appropriate
@ -161,26 +162,28 @@ EOF</userinput></screen>
The change may cause boot failure because The change may cause boot failure because
<filename>grub.cfg</filename> refers to some <quote>old</quote> <filename>grub.cfg</filename> refers to some <quote>old</quote>
designators. If you wish to avoid such a problem, you may use designators. If you wish to avoid such a problem, you may use
the UUID of partition and filesystem instead of GRUB designator to the UUID of a partition and the UUID of a filesystem instead of a GRUB designator to
specify a partition. specify a device.
Run <command>lsblk -o UUID,PARTUUID,PATH,MOUNTPOINT</command> to show Run <command>lsblk -o UUID,PARTUUID,PATH,MOUNTPOINT</command> to show
the UUID of your filesystems (in <literal>UUID</literal> column) and the UUIDs of your filesystems (in the <literal>UUID</literal> column) and
partitions (in <literal>PARTUUID</literal> column). Then replace partitions (in the <literal>PARTUUID</literal> column). Then replace
<literal>set root=(hdx,y)</literal> with <literal>set root=(hdx,y)</literal> with
<literal>search --set=root --fs-uuid <replaceable>&lt;UUID of the filesystem where the kernel is installed&gt;</replaceable></literal>, and replace <literal>search --set=root --fs-uuid <replaceable>&lt;UUID of the filesystem
where the kernel is installed&gt;</replaceable></literal>, and replace
<literal>root=/dev/sda2</literal> with <literal>root=/dev/sda2</literal> with
<literal>root=PARTUUID=<replaceable>&lt;UUID of the partition where LFS is built&gt;</replaceable></literal>.</para> <literal>root=PARTUUID=<replaceable>&lt;UUID of the partition where LFS
<para>Note that the UUID of a partition and the UUID of the filesystem is built&gt;</replaceable></literal>.</para>
in this partition is completely different. Some online resources may <para>Note that the UUID of a partition is completely different from the
UUID of the filesystem in this partition. Some online resources may
instruct you to use instruct you to use
<literal>root=UUID=<replaceable>&lt;filesystem UUID&gt;</replaceable></literal> <literal>root=UUID=<replaceable>&lt;filesystem UUID&gt;</replaceable></literal>
instead of instead of
<literal>root=PARTUUID=<replaceable>&lt;partition UUID&gt;</replaceable></literal>, <literal>root=PARTUUID=<replaceable>&lt;partition UUID&gt;</replaceable></literal>,
but doing so will require an initramfs which is beyond the scope of but doing so will require an initramfs, which is beyond the scope of
LFS.</para> LFS.</para>
<para>The name of the device node for a partition in <para>The name of the device node for a partition in
<filename class='directory'>/dev</filename> may also change (more <filename class='directory'>/dev</filename> may also change (this is less
unlikely than GRUB designator change though). You can also replace likely than a GRUB designator change). You can also replace
paths to device nodes like <literal>/dev/sda1</literal> with paths to device nodes like <literal>/dev/sda1</literal> with
<literal>PARTUUID=<replaceable>&lt;partition UUID&gt;</replaceable></literal>, <literal>PARTUUID=<replaceable>&lt;partition UUID&gt;</replaceable></literal>,
in <filename>/etc/fstab</filename>, to avoid a potential boot failure in <filename>/etc/fstab</filename>, to avoid a potential boot failure