|
@@ -7,7 +7,7 @@ to unpack it first. Often the package files are tar'ed and
|
|
|
gzip'ed. (That can be 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
|
|
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
|
|
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.
|
|
|
|
|
|
|
+to untar an archive. I will explain how to do that once, in this section.
|
|
|
There is also the possibility that a .tar.bz2 file could be downloaded.
|
|
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.
|
|
Such a file would be tar'ed and compressed with the bzip2 program.
|
|
|
Bzip2 achieves a better compression than the more commonly used gzip does.
|
|
Bzip2 achieves a better compression than the more commonly used gzip does.
|
|
@@ -72,7 +72,7 @@ If a file is just tar'ed, it is unpacked by running:
|
|
|
|
|
|
|
|
<para>
|
|
<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
|
|
|
|
|
|
|
+current directory (and this book assumes that the archives are unpacked
|
|
|
under the $LFS/usr/src directory). Please enter that new directory
|
|
under the $LFS/usr/src directory). Please enter that new directory
|
|
|
before continuing with the installation instructions. Again, every time
|
|
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
|
|
this book is going to install a package, it's up to you to unpack the source
|
|
@@ -108,17 +108,17 @@ If a file is bzip2'ed, it is unpacked by running:
|
|
|
<para>
|
|
<para>
|
|
|
After a package is installed, two things can be done with it:
|
|
After a package is installed, two things can be done with it:
|
|
|
either the directory that contains the sources can be deleted,
|
|
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
|
|
|
|
|
|
|
+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
|
|
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,
|
|
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
|
|
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
|
|
|
|
|
|
|
+that apply to the host system but which don't always apply to
|
|
|
the LFS system). Doing a simple make clean or make distclean does not
|
|
the LFS system). Doing a simple make clean or make distclean does not
|
|
|
always guarantee a totally clean source tree.
|
|
always guarantee a totally clean source tree.
|
|
|
</para>
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
<para>
|
|
|
-There is one exception to that rule: don't remove the linux kernel source
|
|
|
|
|
|
|
+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
|
|
tree. A lot of programs need the kernel headers, so that's the only
|
|
|
directory that should not be removed, unless no software is to be compiled
|
|
directory that should not be removed, unless no software is to be compiled
|
|
|
anymore.
|
|
anymore.
|
Gerard Beekmans