| Newsgroups |
gmane.linux.lfs.book |
| Message-ID |
<176991664124.19716.4206509634769705267@rivendell.linuxfromscratch.org> |
This is an automated email from the git hooks/post-receive script.
git pushed a commit to branch multilib
in repository lfs.
The following commit(s) were added to refs/heads/multilib by this push:
new 892241025 prologue/*: Rewrite some things.
892241025 is described below
commit 892241025fbd6921071e997bc0cbf4492b91f968
Author: Zeckmathederg <[email protected]>
AuthorDate: Sat Jan 31 20:31:40 2026 -0700
prologue/*: Rewrite some things.
---
prologue/architecture.xml | 43 +++++-------------------------------
prologue/audience.xml | 56 ++++++++++++-----------------------------------
prologue/multilib.xml | 2 +-
3 files changed, 21 insertions(+), 80 deletions(-)
diff --git a/prologue/architecture.xml b/prologue/architecture.xml
index 189857760..d859f1f51 100644
--- a/prologue/architecture.xml
+++ b/prologue/architecture.xml
@@ -8,43 +8,12 @@
<sect1 id="pre-architecture">
<?dbhtml filename="architecture.html"?>
- <title>LFS Target Architectures</title>
+ <title>MLFS Target Architecture</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
-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>
-
-<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
-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 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>
+ <para>
+ Due to the nature of multilib, the only supported CPU architecture is
+ 64-bit x86 (x86_64) or AMD64. 32-bit and 16-bit x86 CPUs aren't capable of
+ the multilib system this book employs.
+ </para>
</sect1>
diff --git a/prologue/audience.xml b/prologue/audience.xml
index b0c8f6276..79accb24c 100644
--- a/prologue/audience.xml
+++ b/prologue/audience.xml
@@ -10,48 +10,20 @@
<title>Audience</title>
-<para>There are many reasons why you would want to read this book. One of the
-questions many people raise is, <quote>why go through all the hassle of manually
-building a Linux system from scratch when you can just download and install
-an existing one?</quote></para>
-
-<para>One important reason for this project's existence is to help you learn
-how a Linux system works from the inside out. Building an LFS system helps
-demonstrate what makes Linux tick, and how things work together and depend on
-each other. One of the best things this learning experience can provide is
-the ability to customize a Linux system to suit your own unique needs.</para>
-
-<para>Another key benefit of LFS is that it gives you control
-of the system without relying on someone else's Linux implementation. With
-LFS, you are in the driver's seat. <emphasis>You</emphasis> dictate every aspect of your
-system.</para>
-
-<para>LFS allows you to create very compact Linux systems. With
-other distributions you are often forced to install a great many
-programs you neither use nor understand. These programs waste
-resources. You may argue that with today's hard drives and CPUs, wasted
-resources are no longer a consideration. Sometimes, however, you are still
-constrained by the system's size, if nothing else. Think about bootable
-CDs, USB sticks, and embedded systems. Those are areas where LFS can be
-beneficial.</para>
-
-<para>Another advantage of a custom built Linux system is security. By compiling
-the entire system from source code, you are empowered to audit everything
-and apply all the security patches you want. You don't have to
-wait for somebody else to compile binary packages that fix a security hole.
-Unless you examine the patch and implement it yourself, you have no
-guarantee that the new binary package was built correctly and adequately
-fixes the problem.</para>
-
-<para>The goal of Linux From Scratch is to build a complete and usable
-foundation-level system. If you do not wish to build your own Linux system
-from scratch, you may nevertheless benefit from the information in this
-book.</para>
-
-<para>There are too many good reasons to build your own LFS system to
-list them all here. In the end, education is by far the most important
-reason. As you continue your LFS experience, you will discover the power
-that information and knowledge can bring.</para>
+ <para>
+ Installing vanilla LFS has all its perks and upsides, alongside an
+ educational benefit. This book aims to solve another problem, where users
+ may need to build or run something for 32-bit on a 64-bit machine, where
+ 64-bit is the architecture they built LFS for. <phrase
+ arch="ml_32,ml_x32,ml_all"><xref linkend="pre-multilib"/> covers why this
+ may be the case and how multilib works.</phrase>
+ </para>
+
+ <para>
+ MLFS is recommended to be installed after having installed LFS at least
+ once beforehand to be better equipped with the knowledge of how LFS is
+ supposed to work.
+ </para>
</sect1>
diff --git a/prologue/multilib.xml b/prologue/multilib.xml
index 10cfe4e28..368c5ba4e 100644
--- a/prologue/multilib.xml
+++ b/prologue/multilib.xml
@@ -31,7 +31,7 @@
the software's bit size while still offering a mainly 64-bit
experience.</para>
- <para>This book provides 32-bit (i386/i486/i586/i686) and x32-bit
+ <para>This book provides 32-bit (i?86) and x32-bit
dependencies and toolchains intended for 64-bit x86 (x86_64)
systems.</para>
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
--
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page