gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-18 19:29:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

Grammar fixes

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@473 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2001-04-12 23:28:53 +00:00
parent 280bcc86e7
commit cc107b1a51
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
chapter02/install.xml
View File

@ -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.
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.
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.
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.
@ -72,7 +72,7 @@ If a file is just tar'ed, it is unpacked by running:
<para>
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
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
@ -108,17 +108,17 @@ If a file is bzip2'ed, it is unpacked by running:
<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
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
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
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
always guarantee a totally clean source tree.
</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
directory that should not be removed, unless no software is to be compiled
anymore.