diff --git a/prologue/architecture.xml b/prologue/architecture.xml index ca240183c..d416780e4 100644 --- a/prologue/architecture.xml +++ b/prologue/architecture.xml @@ -13,15 +13,15 @@ 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 CPUs, the main prerequisite, in +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 other distribution -that targets the architecture that you have. Also note that a 32-bit +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. +computer.) -For building LFS, the gain of building on a 64-bit system -compared to a 32-bit system is minimal. +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: @@ -30,21 +30,21 @@ using 4 cores, the following statistics were measured: 64-bit 233.2 minutes 4.4 GB 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. +(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. -The default 64-bit build that results from LFS is considered a +The default 64-bit build that results from LFS is a pure 64-bit system. That is, it supports 64-bit executables only. Building a multi-lib 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 . But it -is an advanced topic. +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 . But +that's an advanced topic. diff --git a/prologue/audience.xml b/prologue/audience.xml index 03f92dce3..81a4b9112 100644 --- a/prologue/audience.xml +++ b/prologue/audience.xml @@ -18,26 +18,26 @@ an existing one? 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 that this learning experience can provide is +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. -Another key benefit of LFS is that it allows you to have more control -over the system without relying on someone else's Linux implementation. With -LFS, you are in the driver's seat and dictate every aspect of the +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. You dictate every aspect of your system. -LFS allows you to create very compact Linux systems. When installing -regular distributions, you are often forced to install a great many -programs which are probably never used or understood. These programs waste -resources. You may argue that with today's hard drive and CPUs, such +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 size considerations if nothing else. Think about bootable +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. 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 desired. It is no longer necessary to +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 @@ -48,10 +48,10 @@ 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. -There are too many other good reasons to build your own LFS system to -list them all here. In the end, education is by far the most powerful of -reasons. As you continue in your LFS experience, you will discover the power -that information and knowledge truly bring. +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. diff --git a/prologue/prerequisites.xml b/prologue/prerequisites.xml index 65042e2a5..745ed788d 100644 --- a/prologue/prerequisites.xml +++ b/prologue/prerequisites.xml @@ -13,19 +13,19 @@ Building an LFS system is not a simple task. It requires a certain level of existing knowledge of Unix system administration in order to resolve problems and correctly execute the commands listed. In particular, as an - absolute minimum, you should already have the ability to use the + absolute minimum, you should already know how to use the command line (shell) to copy or move files and directories, list directory and file contents, and change the current directory. It is also expected that - you have a reasonable knowledge of using and installing Linux + you know how to use and install Linux software. Because the LFS book assumes at least this basic - level of skill, the various LFS support forums are unlikely to be able to + level of skill, the various LFS support forums are unlikely to provide you with much assistance in these areas. You will find that your - questions regarding such basic knowledge will likely go unanswered or you - will simply be referred to the LFS essential pre-reading list. + questions regarding such basic knowledge will likely go unanswered (or you + will simply be referred to the LFS essential pre-reading list). - Before building an LFS system, we recommend reading the following: + Before building an LFS system, we urge you to read these articles: @@ -35,14 +35,14 @@ This is a comprehensive guide to building and installing generic Unix software packages under Linux. Although it was written some time ago, it still provides a good summary of the - basic techniques needed to build and install software. + basic techniques used to build and install software. Beginner's Guide to Installing from Source - This guide provides a good summary of basic skills and + This guide provides a good summary of the basic skills and techniques needed to build software from source code.