Changeset b8cf8df

Timestamp:

04/12/2001 11:41:40 PM (23 years ago)

Author:

Gerard Beekmans <gerard@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

b16c005

Parents:

dcc45c5

Message:

Update

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@476 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:

• chapter01/acknowledgements.xml (modified) (1 diff)
• chapter02/download.xml (modified) (2 diffs)
• chapter02/install.xml (modified) (4 diffs)

chapter01/acknowledgements.xml

@@ -72 +72 @@
 
 <listitem><para>
+Dag Stenstad for providing the hardware and bandwidth to run the
+Norwegian mirror and <ulink url="mailto:ian@ichilton.co.uk">
+Ian Chilton</ulink> for maintaining the mirror.
+</para></listitem>
+
+<listitem><para>
 Countless other people from the various LFS mailing lists who are making
 this book happen by making suggestions, testing, and submitting bug

chapter02/download.xml

@@ -10 +10 @@
 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 as sysvinit-2.78.tar.gz is stored under
-$LFS/usr/src/sources/s/. A package as bash-2.04.tar.gz is stored under 
+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 
@@ -23 +23 @@
 downloaded,
 but the partition that is going to contain our LFS system isn't created yet.
-Therefore, the files are temporarily stored somewhere else and later 
-copied to $LFS/usr/src/ when the chapter in which 
-the new partition is prepared has been finished.
+Therefore, the files are temporarily stored somewhere else (it's up to
+you to decide where this 'else' is) and later moved to $LFS/usr/src/ when 
+the chapter in which the new partition is prepared has been finished.
 </para>
 

chapter02/install.xml

@@ -5 +5 @@
 Before you can actually start doing something with a package, you need
 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 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. 
-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 the distribution's installation tool.
+gzip'ed or bzip2'ed. I'm not going to write down every time how to
+unpack an archive. I will explain how to do that once, in this 
+section. 
 </para>
 
@@ -72 +64 @@
 
 <para>
-When the archive is unpacked, a new directory will be created under the
+When ab archive is unpacked, a new directory will be created under the
 current directory (and this book assumes that the archives are unpacked
 under the $LFS/usr/src directory). Please enter that new directory
@@ -107 +99 @@
 
 <para>
-After a package is installed, two things can be done with it:
+After a package has been 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 
@@ -119 +111 @@
 
 <para>
+So, save yourself a lot of hassle and just remove the source directory
+immediately after you have installed it.
+</para>
+
+<para>
 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
+directory that should not be removed, unless no package is to be compiled
 anymore.
 </para>