diff options
Diffstat (limited to 'chapter02/install.xml')
| -rw-r--r-- | chapter02/install.xml | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/chapter02/install.xml b/chapter02/install.xml index 70f85bbba..b7a050ee6 100644 --- a/chapter02/install.xml +++ b/chapter02/install.xml @@ -38,7 +38,7 @@ works no matter how your host system decided to patch tar.</para> <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 current directory (and this book assumes that the archives are unpacked @@ -49,7 +49,7 @@ 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> +can be used they need to be uncompressed.</para> <para>If a file is gzip'ed, it is unpacked by running:</para> @@ -63,10 +63,10 @@ can be used they need to be uncompressed first.</para> it: either the directory that contains the sources can be deleted, or it 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> @@ -75,10 +75,10 @@ immediately after you have installed it, but keep the downloaded tarball available for when you need it again.</para> <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> |