Changeset ff9fe017

Timestamp:

03/23/2001 02:56:31 AM (23 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, 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/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

6dc64f6

Parents:

97f1db3

Message:

Text update

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

Files:

• chapter02/aboutlfs.xml (modified) (3 diffs)
• chapter02/install.xml (modified) (6 diffs)
• chapter03/introduction.xml (modified) (1 diff)

chapter02/aboutlfs.xml

@@ -7 +7 @@
 replaced by the directory where the partition that contains the LFS system 
 is mounted. How to create and where to mount the partition will be
-explaind in full detail in chapter 4. In my case, the LFS 
+explained in full detail in chapter 4. In my case, the LFS 
 partition is mounted  on /mnt/lfs.
 </para>
@@ -13 +13 @@
 <para>
 For example when you are told to run a command like
-<userinput>./configure --prefix=$LFS</userinput> you will actually run
-<userinput>./configure --prefix=/mnt/lfs</userinput>
+<userinput>./configure --prefix=$LFS</userinput> you actually have to
+run <userinput>./configure --prefix=/mnt/lfs</userinput>
 </para>
 
@@ -33 +33 @@
 --prefix=$LFS</userinput> you can type that literally. Your shell will
 replace $LFS with /mnt/lfs when it processes the command line (meaning
-when you hit enter).
+when you hit enter after having typed the command).
 </para>
 

chapter02/install.xml

@@ -3 +3 @@
 
 <para>
-Before a user can actually start doing something with a package, he needs
+Before you can actually start doing something with a package, you need
 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.
+gzip'ed. (That can be 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 
@@ -11 +11 @@
 There is also the possibility that a .tar.bz2 file could be downloaded.
 Such a file would be 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, the bzip2 program needs to be installed. 
+Bzip2 achieves a better compression than the more commonly used gzip does. 
+In 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 the host system. If not, it's installed using 
-the 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>
 
@@ -31 +31 @@
 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:
+filename:
 </para>
 
@@ -57 +57 @@
 slightly modified to be able to use bzip2 files directly using either
 the I or the y tar parameter, which works the same as the z tar parameter
-to handle gzip archives.
+to handle gzip archives. The above construction works no matter how
+your host system decided to patch bzip2.
 </para>
 
@@ -73 +74 @@
 When the archive is unpacked, a new directory will be created under the
 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.
+under the $LFS/usr/src directory). Please enter that new directory
+before continuing with the installation instructions. Again, every time
+this book is going to install a package, it's up to you to unpack the source
+archive and cd into the newly created directory.
+</para>
+
+<para>
+From time to time you will be dealing with single files such as patch
+files. These files are generally gzip'ed or bzip2'ed. Before such files
+can be used they need to be uncompressed first.
 </para>
 
@@ -90 +97 @@
 
 <para>
+If a file is bzip2'ed, it is unpacked by running:
+</para.
+
+<blockquote><literallayout>
+
+        <userinput>bunzip2 filename.bz2</userinput>
+
+</literallayout></blockquote>
+
+<para>
 After a package is installed, two things can be done with it:
 either the directory that contains the sources can be deleted,
-either 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 
-subdirectories which aren't always removed by a make clean process.
+either 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, 
+you 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.
 </para>
 

chapter03/introduction.xml

@@ -4 +4 @@
 <para>
 In this chapter the partition that is going to host the LFS system is
-going to be prepared. A new partition will be created, an ext2 file
+going to be prepared. A new partition will be created, a file
 system will be created on it and the directory structure will be
 created. When this is done, we can move on to the next chapter and start