From 312d536a3582b1ee629687b44948874c98b14874 Mon Sep 17 00:00:00 2001
From: Bruce Dubbs <bdubbs@linuxfromscratch.org>
Date: Sun, 9 Oct 2022 10:55:14 -0500
Subject: [PATCH 1/2] Fix systemd currency

---
 lfs-latest-git.php | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lfs-latest-git.php b/lfs-latest-git.php
index 32c8150ca..d4f331697 100644
--- a/lfs-latest-git.php
+++ b/lfs-latest-git.php
@@ -17,7 +17,7 @@ $regex[ 'intltool' ] = "/^.*Latest version is (\d[\d\.]+\d).*$/";
 $regex[ 'less'     ] = "/^.*current released version is less-(\d+).*$/";
 $regex[ 'mpfr'     ] = "/^mpfr-([\d\.]+)\.tar.*$/";
 $regex[ 'Python'   ] = "/^.*Latest Python 3.*Python (3[\d\.]+\d).*$/";
-$regex[ 'systemd'  ] = "/^.*v([\d]+)$/";
+$regex[ 'systemd'  ] = "/^.*systemd v([\d]+)$/";
 //$regex[ 'sysvinit' ] = "/^.*sysvinit-([\d\.]+)dsf\.tar.*$/";
 $regex[ 'tzdata'   ] = "/^.*tzdata([\d]+[a-z]).*$/";
 $regex[ 'xz'       ] = "/^.*xz-([\d\.]*\d).*$/";

From 8b539af84d3ea5784a000eec414591e600172495 Mon Sep 17 00:00:00 2001
From: Pierre Labastie <pierre.labastie@neuf.fr>
Date: Sun, 9 Oct 2022 18:46:28 +0200
Subject: [PATCH 2/2] First attempt at clarifying "Important Preliminary
 Material"

---
 part3intro/toolchaintechnotes.xml | 23 +++++++++++++----------
 1 file changed, 13 insertions(+), 10 deletions(-)

diff --git a/part3intro/toolchaintechnotes.xml b/part3intro/toolchaintechnotes.xml
index aae3d7f3a..53c1f4a23 100644
--- a/part3intro/toolchaintechnotes.xml
+++ b/part3intro/toolchaintechnotes.xml
@@ -300,12 +300,11 @@
     its library search order. Detailed information can be obtained from
     <command>ld</command> by passing it the <parameter>--verbose</parameter>
     flag. For example, <command>$LFS_TGT-ld --verbose | grep SEARCH</command>
-    will illustrate the current search paths and their order. It shows which
-    files are linked by <command>ld</command> by compiling a dummy program and
-    passing the <parameter>--verbose</parameter> switch to the linker. For
-    example,
-    <command>$LFS_TGT-gcc dummy.c -Wl,--verbose 2&gt;&amp;1 | grep succeeded</command>
-    will show all the files successfully opened during the linking.</para>
+    will illustrate the current search paths and their order. Note that this
+    example can be run as shown only while being user
+    <systemitem class="username">lfs</systemitem>. If you come back to this
+    page later, replace <command>$LFS_TGT-ld</command> with just
+    <command>ld</command>.</para>
 
     <para>The next package installed is gcc. An example of what can be
     seen during its run of <command>configure</command> is:</para>
@@ -318,14 +317,18 @@ checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</compute
     directories to find which tools to use. However, during the actual
     operation of <command>gcc</command> itself, the same search paths are not
     necessarily used. To find out which standard linker <command>gcc</command>
-    will use, run: <command>$LFS_TGT-gcc -print-prog-name=ld</command>.</para>
+    will use, run: <command>$LFS_TGT-gcc -print-prog-name=ld</command>. Again,
+    remove the <command>$LFS_TGT-</command> part if coming back to this
+    later.</para>
 
     <para>Detailed information can be obtained from <command>gcc</command> by
     passing it the <parameter>-v</parameter> command line option while compiling
-    a dummy program. For example, <command>gcc -v dummy.c</command> will show
+    a program. For example, <command>$LFS_TGT-gcc -v
+    <replaceable>example.c</replaceable></command> (or without <command>
+    $LFS_TGT-</command> if coming back later to this) will show
     detailed information about the preprocessor, compilation, and assembly
-    stages, including <command>gcc</command>'s included search paths and their
-    order.</para>
+    stages, including <command>gcc</command>'s search paths for included
+    headers and their order.</para>
 
     <para>Next installed are sanitized Linux API headers. These allow the
     standard C library (glibc) to interface with features that the Linux