Changeset 60ed866 for chapter01/how.xml

Timestamp:

09/18/2002 06:31:39 PM (22 years ago)

Author:

Timothy Bauscher <timothy@…>

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:

bee1e69

Parents:

8d8ab63

Message:

Fixed typos, removed old command explanation.

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

File:

• chapter01/how.xml (modified) (2 diffs)

chapter01/how.xml

@@ -4 +4 @@
 
 <para>We are going to build the LFS system by using a previously installed
-Linux distribution such as Debian, SuSe, Slackware, Mandrake, RedHat, etc.
+Linux distribution such as Debian, SuSE, Slackware, Mandrake, RedHat, etc.
 We will use the existing Linux system as the development platform, because
 we need tools like a compiler, linker, text editor, and other necessary
@@ -20 +20 @@
 example, you need a compiler to build a new compiler, and you need a shell
 in order to install a new shell. The packages in this chapter will be linked
-statically. Static linking describes a method of compiling software so that
+statically.</para>
+
+<para>Static linking describes a method of compiling software so that
 it does not require the presence of libraries when building is complete.
 The resulting program is able to function on its own. The program is able to
 do so because the pieces of the program that would normally remain in the
 libraries are copied from the libraries and built right into the program.
-Ordinarily software is built with dynamic linking. This conserves storage
+Ordinarily, software is built with dynamic linking. This conserves storage
 space and increases the efficiency of many programs. We statically link
 our software in chapter 5 because we will in theory be moving our