Changeset aff91c4 for chapter02/install.xml

Timestamp:

03/16/2001 06:06:46 PM (24 years ago)

Author:

Thomas Balu Walter <tw@…>

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, 12.2, 12.2-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, v3_0, v3_1, v3_2, v3_3, 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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

7d90bd3

Parents:

1b256332

Message:

You-fix

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

File:

• chapter02/install.xml (modified) (7 diffs)

chapter02/install.xml

@@ -3 +3 @@
 
 <para>
-Before you can actually start doing something with a package, you need
-to unpack it first. Often you will find the package files being tar'ed and
-gzip'ed. (You can determine this by looking at the extension of the file.
+Before a user can actually start doing something with a package, he needs
+to unpack it first. Often the package files are tar'ed and
+gzip'ed. (that can determined by looking at the extension of the file.
 tar'ed and gzip'ed archives have a .tar.gz or .tgz extension, for
 example.) I'm not going to write down every time how to ungzip and how 
-to untar an archive. I will tell you how to do that once, in this section. 
-There is also the possibility  that you have the ability of downloading 
-a .tar.bz2 file. Such a file is tar'ed and compressed with the bzip2 program. 
+to untar an archive. I will tell how to do that once, in this section. 
+There is also the possibility  that a .tar.bz2 file can be downloaded.
+Such a file is tar'ed and compressed with the bzip2 program. 
 Bzip2 achieves a better compression than the commonly used gzip does. In 
-order to use bz2 archives you need to have the bzip2 program installed. 
+order to use bz2 archives the bzip2 program needs to be installed. 
 Most if not every distribution comes with this program so chances are 
-high it is already installed on your system. If not, install it using 
-your distribution's installation tool.
+high it is already installed on the host-system. If not, it's installed using 
+the distribution's installation tool.
 </para>
 
@@ -29 +29 @@
 
 <para>
-When you have a file that is tar'ed and gzip'ed, you unpack it by
+If a file is tar'ed and gzip'ed, it is unpacked by
 running either one of the following two commands, depending on the
 filename format:
@@ -43 +43 @@
 
 <para>
-When you have a file that is tar'ed and bzip2'ed, you unpack it by
+If a file is tar'ed and bzip2'ed, it is unpacked by
 running:
 </para>
@@ -61 +61 @@
 
 <para>
-When you have a file that is tar'ed, you unpack it by running:
+If a file is just tar'ed, it is unpacked by running:
 </para>
 
@@ -72 +72 @@
 <para>
 When the archive is unpacked a new directory will be created under the
-current directory (and this document assumes that you unpack the archives
-under the $LFS/usr/src directory). You have to enter that new directory
-before you continue with the installation instructions. So every time the
-book is going to install a program, it's up to you to unpack the source
+current directory (and this document assumes that the archives are unpacked
+under the $LFS/usr/src directory). A user has to enter that new directory
+before continuing with the installation instructions. So every time the
+book is going to install a program, it's up to the user to unpack the source
 archive.
 </para>
 
 <para>
-When you have a file that is gzip'ed, you unpack it by running:
+f a file is gzip'ed, it is unpacked by running:
 </para>
 
@@ -90 +90 @@
 
 <para>
-After you have installed a package you can do two things with it. You can
-either delete the directory that contains the sources or you can keep it.
-If you decide to keep it, that's fine with me. But, if you need the same package
-again in a later chapter, you need to delete the directory first before using
-it again. If you don't do this, you might end up in trouble because old
-settings will be used (settings that apply to your normal Linux system but
-which don't always apply to your LFS system). Doing a simple make clean
+After a package is installed two things can be done with it. 
+Either the directory that contains the sources can be deleted 
+or it can be kept.
+If it is kept, that's fine with me. But, if the same package is needed
+again in a later chapter, the directory needs to be deleted first before using
+it again. If this is not done, it might end up in trouble because old
+settings will be used (settings that apply to the normal Linux system but
+which don't always apply to the LFS system). Doing a simple make clean
 or make distclean does not always guarantee a totally clean source tree. 
 The configure script can also have files lying around in various 
@@ -105 +106 @@
 There is one exception to that rule: don't remove the linux kernel source
 tree. A lot of programs need the kernel headers, so that's the only
-directory you don't want to remove, unless you are not going to
-compile any software anymore.
+directory that should not be removed, unless no software is to be compiled
+anymore.
 </para>