From 8190ca0715c1b5c9048aa1277dad3e499ea8b4e4 Mon Sep 17 00:00:00 2001 From: David Bryant Date: Sun, 1 Jan 2023 17:15:09 -0600 Subject: Clarify some things, correct grammatical & idiomatic errors. --- chapter10/grub.xml | 35 +++++++++++++++++++---------------- 1 file changed, 19 insertions(+), 16 deletions(-) (limited to 'chapter10') diff --git a/chapter10/grub.xml b/chapter10/grub.xml index 233902633..ef3cc8a43 100644 --- a/chapter10/grub.xml +++ b/chapter10/grub.xml @@ -19,7 +19,7 @@ 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 the BLFS page. @@ -54,8 +54,8 @@ xorriso -as cdrecord -v dev=/dev/cdrw blank=as_needed grub-img.isoGRUB uses its own naming structure for drives and partitions in the form of (hdn,m), where n is the hard drive number and m 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. + number. The hard drive numbers start from zero, but the partition numbers + start from one for normal partitions (from five for extended partitions). Note that this is different from earlier versions where both numbers started from zero. For example, partition sda1 is (hd0,1) to @@ -83,12 +83,13 @@ xorriso -as cdrecord -v dev=/dev/cdrw blank=as_needed grub-img.iso/boot 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 /boot. If you do this, be sure to update /etc/fstab. - Using the current lfs partition will also work, but configuration + Leaving >/boot on + the current LFS partition will also work, but configuration for multiple systems is more difficult. Using the above information, determine the appropriate @@ -161,26 +162,28 @@ EOF The change may cause boot failure because grub.cfg refers to some old designators. If you wish to avoid such a problem, you may use - the UUID of partition and filesystem instead of GRUB designator to - specify a partition. + the UUID of a partition and the UUID of a filesystem instead of a GRUB designator to + specify a device. Run lsblk -o UUID,PARTUUID,PATH,MOUNTPOINT to show - the UUID of your filesystems (in UUID column) and - partitions (in PARTUUID column). Then replace + the UUIDs of your filesystems (in the UUID column) and + partitions (in the PARTUUID column). Then replace set root=(hdx,y) with - search --set=root --fs-uuid <UUID of the filesystem where the kernel is installed>, and replace + search --set=root --fs-uuid <UUID of the filesystem + where the kernel is installed>, and replace root=/dev/sda2 with - root=PARTUUID=<UUID of the partition where LFS is built>. - Note that the UUID of a partition and the UUID of the filesystem - in this partition is completely different. Some online resources may + root=PARTUUID=<UUID of the partition where LFS + is built>. + 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 root=UUID=<filesystem UUID> instead of root=PARTUUID=<partition UUID>, - 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. The name of the device node for a partition in - /dev may also change (more - unlikely than GRUB designator change though). You can also replace + /dev may also change (this is less + likely than a GRUB designator change). You can also replace paths to device nodes like /dev/sda1 with PARTUUID=<partition UUID>, in /etc/fstab, to avoid a potential boot failure -- cgit v1.2.3-54-g00ecf