Changeset 1e6acd6 for chapter02/install.xml

Timestamp:

09/22/2002 03:01:40 AM (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:

b4a5535

Parents:

f8decc78

Message:

Applied Bill Maltby's grammatic-fixes patch.

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

File:

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

chapter02/install.xml

@@ -39 +39 @@
 <para>If a file is just tar'ed, it is unpacked by running:</para>
 
-<para><screen><userinput>tar xvf filename.tar</userinput></screen></para>
+<para><screen><userinput>tar -xvf filename.tar</userinput></screen></para>
 
 <para>When an archive is unpacked, a new directory will be created under the
@@ -50 +50 @@
 <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>
+can be used they need to be uncompressed.</para>
 
 <para>If a file is gzip'ed, it is unpacked by running:</para>
@@ -64 +64 @@
 can be kept. We highly recommend deleting it. If you don't do this and
 try to re-use the same source later on in the book (for example re-using
-the source trees from Chapter 5 for use in Chapter 6), it may not work
+the source trees from Chapter 5 in Chapter 6), it may not work
 as you expect it to. Source trees from Chapter 5 will have your host
 distribution's settings, which don't always apply to the LFS system
-after you enter the chroot'ed environment. Even running something like
+after you enter the chroot environment. Even running something like
 <emphasis>make clean</emphasis> doesn't always guarantee a clean source
 tree.</para>
@@ -76 +76 @@
 
 <para>There is one exception; the kernel source tree. Keep it around as you
-will need it later in this book when building a kernel. Nothing will use
-the kernel tree so the source tree won't be in your way.  If, however,
-you are short of disk space, you can remove the kernel tree and re-untar
-it later when required.</para>
+will need it later in this book when building a kernel. Nothing before then
+will use the kernel tree, so the source tree won't be in your way.  If,
+however, you are short of disk space, you can remove the kernel tree and
+re-untar it later when required.</para>
 
 </sect1>