From e9d65f2f4c1dbdac90a590a7368143d648fd9fed Mon Sep 17 00:00:00 2001 From: Xi Ruoyao Date: Fri, 26 Aug 2022 19:47:50 +0800 Subject: [PATCH 1/4] grub: update description for grub-glue-efi Text only change. Found out this utility also exists on ARM, so copied "grub-glue-efi --help" here, which does not mention "ia32" or "amd64". --- chapter08/grub.xml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/chapter08/grub.xml b/chapter08/grub.xml index e9008c31a..78304a3ab 100644 --- a/chapter08/grub.xml +++ b/chapter08/grub.xml @@ -167,8 +167,7 @@ mv -v /etc/bash_completion.d/grub /usr/share/bash-completion/completions grub-glue-efi - Processes ia32 and amd64 EFI images and glues them - according to Apple format. + Glue 32-bit and 64-bit binary into Apple universal one. grub-glue-efi From d84087141cc4974817183cc5dba2354e3b783e44 Mon Sep 17 00:00:00 2001 From: Xi Ruoyao Date: Fri, 26 Aug 2022 19:52:20 +0800 Subject: [PATCH 2/4] reboot: mention firmwares Text only change. I've forgotten this several times for AMDGPU... --- chapter11/reboot.xml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/chapter11/reboot.xml b/chapter11/reboot.xml index 3d7953897..b4413f1ce 100644 --- a/chapter11/reboot.xml +++ b/chapter11/reboot.xml @@ -61,6 +61,11 @@ url='&blfs-book;basicnet/wpa_supplicant.html'>wpa_supplicant. + Install firmwares if the kernel + driver for your hardware require some firmware to function properly. + + Finally, a review of the following configuration files is also appropriate at this point. From 5353a1948fa64dac71603a6477f15bfa6390411b Mon Sep 17 00:00:00 2001 From: Xi Ruoyao Date: Fri, 26 Aug 2022 20:11:57 +0800 Subject: [PATCH 3/4] grub: add a note about filesystem UUID and partition UUID usage Text only change. --- chapter10/grub.xml | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/chapter10/grub.xml b/chapter10/grub.xml index c569525c9..233902633 100644 --- a/chapter10/grub.xml +++ b/chapter10/grub.xml @@ -155,6 +155,38 @@ EOF set root line to point to the boot partition. + + The GRUB designator for a partition may change if you added or + removed some disks (including removable disks like USB thumb devices). + 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. + Run lsblk -o UUID,PARTUUID,PATH,MOUNTPOINT to show + the UUID of your filesystems (in UUID column) and + partitions (in 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 + 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 + 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 + 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 + paths to device nodes like /dev/sda1 with + PARTUUID=<partition UUID>, + in /etc/fstab, to avoid a potential boot failure + in case the device node name has changed. + + 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 From bf6f9e75ee62ff6f73805d27285800b816444fbf Mon Sep 17 00:00:00 2001 From: Xi Ruoyao Date: Fri, 26 Aug 2022 19:35:47 +0800 Subject: [PATCH 4/4] python: supress "failed to check new pip version" or "a new pip version is available" warnings The non-text change during freeze is approved by bdubbs. --- chapter08/python.xml | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/chapter08/python.xml b/chapter08/python.xml index da1f75cdc..0f50bf6ef 100644 --- a/chapter08/python.xml +++ b/chapter08/python.xml @@ -102,12 +102,24 @@ root user. The main reason of this recommendation is for avoiding a conflict with the system package manager (dpkg for example), but LFS does not - have a system-wide package manager so this is not a problem. If desired, - suppress this warning by running the following commands: + have a system-wide package manager so this is not a problem. And, + pip3 will attempt to check for a new version of + itself whenever it's run. As domain name resolving is not configured + yet in LFS chroot environment, it will fail to check for a new version + and produce a warning. Once we boot the LFS system and set up network + connection, it will then produce a warning telling the user to update it + from a pre-built wheel on PyPI if any new version is available. But LFS + consider pip3 a part of Python 3 so it should not be + updated separately, and an update from a pre-built wheel will deviate + from our purpose to build a Linux system from source code. So the + warning for a new pip3 version should be ignored as + well. If desired, suppress these warnings by running the following + commands: cat > /etc/pip.conf << EOF [global] root-user-action = ignore +disable-pip-version-check = true EOF