Changeset 26e62aa for chapter01/how.xml

Timestamp:

09/20/2002 09:11:28 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:

88abb11

Parents:

eb7df24

Message:

Removed --enable-threads=posix from static gcc compilation. Fixed changelog and a number of typos.

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

File:

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

chapter01/how.xml

@@ -6 +6 @@
 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
-development tools to build our system. Ordinarily, the required tools are
-available by default if we selected "development" as one of our installation
-options when we installed the distributed Linux.</para>
+we need tools like a compiler, linker, text editor, and other development
+tools to build our system. Ordinarily, the required tools are available by
+default if we selected "development" as one of our installation options
+when we installed a Linux distribution.</para>
 
-<para>After you have downloaded the necessary packages that make up an LFS
-system we will create a new Linux native partition and filesystem. Here
-is where the LFS system will be compiled and installed.</para>
+<para>After you have downloaded the packages that make up an LFS system,
+we will create a new Linux native partition and filesystem. Here is where
+the LFS system will be compiled and installed.</para>
 
-<para>The next step, chapter 5, will discuss the installation of a number of
+<para>The next step, Chapter 5, will discuss the installation of a number of
 packages that will form the basic development suite which is used to
 build the actual system, or needed to resolve circular dependencies. For
@@ -29 +29 @@
 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
+our software in Chapter 5 because we will, in theory, be moving our
 development system to a virtual environment where the already mentioned
 libraries will be absent. If the software is built dynamically, our
 development suite will not function. Since the libraries we are talking
-about are provided by our distribution Linux, the goal of chapter 5 is to
+about are provided by our distribution Linux, the goal of Chapter 5 is to
 build a development environment where those libraries are not required
 and is therefore independent of the distribution.</para>
 
-<para>In chapter 6 we will build and install our final system. We will use
+<para>In Chapter 6 we will build and install our final system. We will use
 the chroot program to enter a virtual environment and start a new shell
 whose root directory will be set to the partition where we built all the
-chapter 5 software. This is very similar to rebooting and instructing the
+Chapter 5 software. This is very similar to rebooting and instructing the
 kernel to mount our LFS partition as the root partition. The reason that
-we don't actually reboot, but instead chroot, is that creating a static
-system that we can boot into requires more work that simply isn't necessary.
-As well, we can continue to use our platform system while we are building
-LFS. While software is being compiled and installed you can simply switch
-to a different VC (Virtual Console) or X desktop and continue using your
+we don't actually reboot, but instead chroot, is that creating a bootable
+static system requires additional work which simply isn't necessary. As
+well, we can continue to use our platform system while we are building LFS.
+While software is being compiled and installed you can simply switch to a
+different VC (Virtual Console) or X desktop and continue using your
 computer normally.</para>
 
-<para>When all the software from chapter 6 is installed, chapters 7, 8 and 9
+<para>When all the software from Chapter 6 is installed, Chapters 7, 8 and 9
 will help us finalize our installation. We will set up our boot
-scripts in chapter 7. In chapter 8 we will build our final linux kernel and
+scripts in Chapter 7. In Chapter 8 we will build our final linux kernel and
 set up the Linux boot loader. Chapter 9 has some pointers to help you after
 you finish the book. Then finally, you reboot your system and boot into your
@@ -61 +61 @@
 It should become very clear shortly.</para>
 
-<para>Please read chapter 2 carefully as it explains a few important things
-you should be aware of before you begin to work through chapters 5 and
+<para>Please read Chapter 2 carefully as it explains a few important things
+you should be aware of before you begin to work through Chapters 5 and
 later.</para>