diff options
Diffstat (limited to 'chapter02/install.xml')
| -rw-r--r-- | chapter02/install.xml | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/chapter02/install.xml b/chapter02/install.xml index 1ab16935e..5d2068903 100644 --- a/chapter02/install.xml +++ b/chapter02/install.xml @@ -4,16 +4,16 @@ <para> 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 +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 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. +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. -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 +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. </para> @@ -55,7 +55,7 @@ running: <para> Some tar programs (most of them nowadays but not all of them) are 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 +the I or the y tar parameter, which works the same as the z tar parameter to handle gzip archives. </para> @@ -70,16 +70,16 @@ If a file is just tar'ed, it is unpacked by running: </literallayout></blockquote> <para> -When the archive is unpacked a new directory will be created under the +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 +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> -f a file is gzip'ed, it is unpacked by running: +If a file is gzip'ed, it is unpacked by running: </para> <blockquote><literallayout> @@ -89,10 +89,10 @@ f a file is gzip'ed, it is unpacked by running: </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 -or it can be kept. -If it is kept, that's fine with me. But, if the same package is needed +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 |