Changeset 85ec218a for prologue/architecture.xml

Timestamp:

10/18/2022 08:27:54 AM (2 years ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

xry111/clfs-ng

Children:

00eeab8

Parents:

9247501d (diff), 0f9c02a (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.

Message:

Merge remote-tracking branch 'origin/trunk' into xry111/clfs-ng

File:

• prologue/architecture.xml (modified) (2 diffs)

prologue/architecture.xml

@@ -16 +16 @@
 CPUs.</para>
 
-<para>For building LFS, the gain of building on a 64-bit system
-compared to a 32-bit system is minimal.
+<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>
@@ -26 +26 @@
 
 <para>As you can see, on the same hardware, the 64-bit build is only 3% faster
-and is 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 largely sufficient. On the other
-hand, several packages in BLFS now need more than 4GB of RAM to be built
-and/or to run, so that if you plan to use LFS as a desktop, the LFS authors
-recommend building on a 64-bit system.</para>
+(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 considered a
+<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
 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.
 This is not directly supported in LFS because it would interfere with the
-educational objective of providing the instructions needed for a
-straightforward base Linux system. Some LFS/BLFS editors maintain a fork
-of LFS for multilib, which is accessible at <ulink
-url="https://www.linuxfromscratch.org/~thomas/multilib/index.html"/>. But it
-is an advanced topic.</para>
+educational objective of providing the minimal instructions needed for a
+basic Linux system. Some of the LFS/BLFS editors maintain a multilib fork
+of LFS, accessible at <ulink
+url="https://www.linuxfromscratch.org/~thomas/multilib/index.html"/>. But
+that's an advanced topic.</para>
 
 </sect1>