diff options
| author | Mark Hymers <markh@linuxfromscratch.org> | 2001-08-18 09:48:20 +0000 |
|---|---|---|
| committer | Mark Hymers <markh@linuxfromscratch.org> | 2001-08-18 09:48:20 +0000 |
| commit | c092a4a32d2e288b92a6a5d2e76bbcbb12cb5076 (patch) | |
| tree | 8271dced5558d3c445cf239a204f6f5c314d5cf2 /chapter02 | |
| parent | 9aecc7d3d23d0623fb0799bb9bd1cd0715ffa8fe (diff) | |
minor textual changes
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@995 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter02')
| -rw-r--r-- | chapter02/download.xml | 8 | ||||
| -rw-r--r-- | chapter02/install.xml | 4 |
2 files changed, 6 insertions, 6 deletions
diff --git a/chapter02/download.xml b/chapter02/download.xml index c5c3840b3..b8e76fa41 100644 --- a/chapter02/download.xml +++ b/chapter02/download.xml @@ -6,10 +6,10 @@ packages that were downloaded are placed somewhere in $LFS/usr/src.</para> <para>I use the convention of having a $LFS/usr/src/sources directory. Under sources, I have the directory 0-9 and the directories a -through z. A package like sysvinit-2.78.tar.gz is stored under -$LFS/usr/src/sources/s/. A package like bash-2.04.tar.gz is stored under -$LFS/usr/src/sources/b/, and so forth. This convention does not have to be -followed, of course; I was just giving an example. It's better to keep +through z. A package like sysvinit-&sysvinit-version;.tar.bz2 is stored under +$LFS/usr/src/sources/s/. A package like bash-&bash-version;.tar.bz2 is stored +under $LFS/usr/src/sources/b/, and so forth. This convention does not have to +be followed, of course; I was just giving an example. It's better to keep the packages out of $LFS/usr/src and move them to a subdirectory, so we'll have a clean $LFS/usr/src directory in which we will unpack the packages and work with them.</para> diff --git a/chapter02/install.xml b/chapter02/install.xml index 5be2aee29..ca6374a92 100644 --- a/chapter02/install.xml +++ b/chapter02/install.xml @@ -31,8 +31,8 @@ running:</para> <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 -to handle gzip archives. The above construction works no matter how +the I, the y or the j tar parameter, which works the same as the z tar +parameter to handle gzip archives. The above construction works no matter how your host system decided to patch bzip2.</para> <para>If a file is just tar'ed, it is unpacked by running:</para> |