Changeset 5756284 for chapter05

Timestamp:

05/30/2002 11:43:04 PM (22 years ago)

Author:

Gerard Beekmans <gerard@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

0230a11

Parents:

f64f4b5

Message:

applied alex's ch5-intro-rewrite and chapter6-intro.patch patches

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1950 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter05/introduction.xml (modified) (1 diff)

chapter05/introduction.xml

@@ -3 +3 @@
 <?dbhtml filename="introduction.html" dir="chapter05"?>
 
-<para>In the following chapters we will install all the software that belongs 
-to a basic Linux system. After you're done with this and the next chapter,
-you'll have a fully working Linux system. The remaining chapters deal 
-with creating the boot scripts, making the LFS system bootable and
-setting up basic networking.</para>
+<para>In this chapter we will compile and install a minimal
+Linux system. This system will contain just enough tools to be able
+to start constructing the final LFS system in the next chapter.</para>
 
-<para>The software in this chapter will be linked statically and will be 
-reinstalled in the next chapter and linked dynamically. The
-reason for the static version first is that there is a chance that our
-normal Linux system and the LFS system aren't using the same C
-Library versions. If the programs in the first part are linked against
-an older C library version, those programs might not work well on the
-LFS system. Another reason is to resolve circular dependencies. An
-example of such a dependency is that you need a compiler to install a
-compiler, and you're going to need a shell to install a shell and that
-compiler.</para>
+<para>The software in this chapter will be linked statically, because
+there is a possibility that your host Linux system uses a different
+version of the C library than the version you downloaded for
+use in your LFS system. If we were to link the programs in this
+chapter against that older C library, these programs might work
+incorrectly, or not at all, when we change to the LFS system.</para>
 
-<para>All the files from this chapter will be installed under the <filename
-class="directory">$LFS/static</filename> directory. By doing it this way,
-we keep the installation from this chapter separate from the final
-installation in the next chapter. Everything done here is only temporarily
-so we don't want it to pollute the to-be LFS system.</para>
+<para>The files compiled in this chapter will be installed under the
+<filename class="directory">$LFS/static</filename> directory,
+to keep them separate from the files installed in the next chapter.
+As everything done here is only temporarily, we don't want
+these files to pollute the to-be LFS system.</para>
 
-<para>The key to learning what makes Linux tick is to know exactly what packages
-are used for and why a user or the system needs them. Descriptions
-of the package content are provided after the Installation subsection of each
-package and in Appendix A as well.</para>
+<para>The key to learning what makes a Linux system work is to know
+exactly what each package is used for, and why the user or the system
+needs it. For this purpose a short description of the content of each
+package is given right after the installation instructions.</para>
 
-<para>During the installation of various packages, you will more than likely see
-all kinds of compiler warnings scrolling by on the screen. These are 
-normal and can be safely ignored. They are just that, warnings (mostly 
-about improper use of the C or C++ syntax, but not illegal use. It's just 
-that, often, C standards changed and packages still use the old standard 
-which is not a problem).</para>
+<para>During the installation of several packages you will probably
+see all kinds of compiler warnings scroll by on your screen. These are
+normal and can be safely ignored. They are just what they say they are:
+warnings -- mostly about improper, but not illegal, use of the C or C++
+syntax. It's just that C standards have changed rather often and some
+packages still use the older standard, which is not really a problem.</para>
 
-<para>Before we start, make sure the LFS environment variable is set up
+<para>Before you start, make sure the LFS environment variable is set up
 properly if you decided to make use of it. Run the following:</para>