Index: prologue/architecture.xml
===================================================================
--- prologue/architecture.xml	(revision 8d5a2a12e99ee86ccfe7cacf51f702226d9a8e81)
+++ prologue/architecture.xml	(revision dbb38594bc3b622e41c12696d27880dd8eb9401c)
@@ -11,34 +11,19 @@
   <title>LFS Target Architectures</title>
 
-<para>The primary target architectures of LFS are the AMD/Intel x86 (32-bit)
-and x86_64 (64-bit) CPUs.  On the other hand, the instructions in this book are
-also known to work, with some modifications, with the Power PC and ARM CPUs. To
-build a system that utilizes one of these alternative CPUs, the main prerequisite, in
+<para>The primary target architectures of this LFS edition are LoongArch
+CPUs.
+<!--On the other hand, the instructions in this book are
+also known to work, with some modifications, with the Power PC and ARM
+CPUs. -->
+To build a system that utilizes one of these CPUs, the main prerequisite, in
 addition to those on the next page, is an existing Linux system such as an
-earlier LFS installation, Ubuntu, Red Hat/Fedora, SuSE, or some other distribution
-that targets that architecture. (Note that a 32-bit
-distribution can be installed and used as a host system on a 64-bit AMD/Intel
-computer.)</para>
+earlier LFS installation, Loong Arch Linux, CLFS for LoongArch, Gentoo,
+Slackware, or other distribution that targets LoongArch.</para>
 
-<para>The gain from building on a 64-bit system, as
-compared to a 32-bit system, is minimal.
-For example, in a test build of LFS-9.1 on a Core i7-4790 CPU based system,
-using 4 cores, the following statistics were measured:</para>
-
-<screen><computeroutput>Architecture Build Time     Build Size
-32-bit       239.9 minutes  3.6 GB
-64-bit       233.2 minutes  4.4 GB</computeroutput></screen>
-
-<para>As you can see, on the same hardware, the 64-bit build is only 3% faster
-(and 22% larger) than the 32-bit build. If you plan to use LFS as a LAMP
-server, or a firewall, a 32-bit CPU may be good enough. On the other
-hand, several packages in BLFS now need more than 4 GB of RAM to be built
-and/or to run; if you plan to use LFS as a desktop, the LFS authors
-recommend building a 64-bit system.</para>
-
-<para>The default 64-bit build that results from LFS is a
-<quote>pure</quote> 64-bit system. That is, it supports 64-bit executables
+<para>The build that results from this LFS edition is a
+<quote>pure</quote> lp64d system. That is, it supports executables with
+the lp64d ABI
 only. Building a <quote>multi-lib</quote> system requires compiling many
-applications twice, once for a 32-bit system and once for a 64-bit system.
+applications multiple times, once for each ABI to be supported.
 This is not directly supported in LFS because it would interfere with the
 educational objective of providing the minimal instructions needed for a
@@ -46,5 +31,6 @@
 of LFS, accessible at <ulink
 url="https://www.linuxfromscratch.org/~thomas/multilib/index.html"/>. But
-that's an advanced topic.</para>
+the multilib edition is for x86_64, and multilib is an advanced topic
+anyway.</para>
 
 </sect1>
Index: prologue/bookinfo.xml
===================================================================
--- prologue/bookinfo.xml	(revision 8d5a2a12e99ee86ccfe7cacf51f702226d9a8e81)
+++ prologue/bookinfo.xml	(revision dbb38594bc3b622e41c12696d27880dd8eb9401c)
@@ -50,4 +50,6 @@
     Linus Torvalds.</para>
 
+    <para><trademark class='registered'>LoongArch</trademark> is a
+    registered trademark of Loongson Technology Co., Ltd.</para>
   </legalnotice>
 
Index: prologue/standards.xml
===================================================================
--- prologue/standards.xml	(revision 8d5a2a12e99ee86ccfe7cacf51f702226d9a8e81)
+++ prologue/standards.xml	(revision dbb38594bc3b622e41c12696d27880dd8eb9401c)
@@ -35,7 +35,9 @@
         Languages, and Imaging.  Some parts of Core and Desktop
         specifications are architecture specific.  There are also two trial
-        specifications: Gtk3 and Graphics.  LFS attempts to conform to the LSB
-        specifications for the IA32 (32-bit x86) or AMD64 (x86_64)
-        architectures discussed in the previous section.</para>
+        specifications: Gtk3 and Graphics.  There's no architecture specific
+        parts for LoongArch, and on LoongArch Glibc has intentionally left out
+        some symbol versions required by the architecture independant part of
+        LSB Core.  So we cannot satisfy the LSB architecture independant
+        parts, but we still use them as a reference.</para>
 
         <note><para>Many people do not agree with these requirements.
@@ -162,7 +164,13 @@
           <para>
             <command>install_initd</command>,
+            <filename class='libraryfile'>libc.so.6</filename>
+            (the file is provided by the LFS Glibc package but it lacks some
+            symbol versions required by LSB),
             <filename class='libraryfile'>libcrypt.so.1</filename>
             (can be provided with optional instructions for the LFS
             Libxcrypt package),
+            <filename class='libraryfile'>libpthread.so.2</filename>
+            (the file is provided by the LFS Glibc package but it lacks some
+            symbol versions required by LSB),
             <filename class='libraryfile'>libncurses.so.5</filename>
             (can be provided with optional instructions for the LFS
@@ -170,5 +178,11 @@
             <filename class='libraryfile'>libncursesw.so.5</filename>
             (but <filename class='libraryfile'>libncursesw.so.6</filename>
-            is provided by the LFS Ncurses package)
+            is provided by the LFS Ncurses package),
+            <filename class='libraryfile'>librt.so.1</filename>
+            (the file is provided by the LFS Glibc package but it lacks some
+            symbol versions required by LSB),
+            <filename class='libraryfile'>libutil.so.1</filename>
+            (can be provided as a symlink to
+            <filename class='libraryfile'>libc.so.6</filename>)
           </para>
         </listitem>
