Changeset db9d773c

Timestamp:

02/28/2004 11:26:41 AM (20 years ago)

Author:

Alex Gronenwoud <alex@…>

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, 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:

46c039e

Parents:

687ef73

Message:

Forgetfulness makes the most traffic...

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

Files:

• chapter01/changelog.xml (modified) (1 diff)
• chapter06/chapter06.xml (modified) (2 diffs)
• chapter06/ncurses.xml (modified) (1 diff)
• chapter06/vim.xml (modified) (2 diffs)
• chapter06/zlib.xml (modified) (4 diffs)
• chapter07/loadkeys.xml (modified) (1 diff)
• chapter09/reboot.xml (modified) (1 diff)

chapter01/changelog.xml

@@ -46 +46 @@
 
 <listitem><para>February 26th, 2004 [jeremy]: Removed the creation of the
-/usr/etc directory to conform with FHS - closes bug 775</para></listitem>
+/usr/etc directory to conform with FHS - closes bug 775.</para></listitem>
 
-<listitem><para>February 26th, 2004 [jeremy]: Upgraded to Kernel 2.4.25</para></listitem>
+<listitem><para>February 26th, 2004 [jeremy]: Upgraded to
+Kernel 2.4.25</para></listitem>
 
 <listitem><para>February 23rd, 2004 [alex]: Chapters 6 + 9 : Cleaned up the

chapter06/chapter06.xml

@@ -574 +574 @@
 ensure you're not running any of the binaries that are about to be stripped.
 If you're not sure whether you entered chroot with the command given in
-<xref linkend="ch-system-chroot"/>, then now exit from chroot and reenter it
-with the following commands:</para>
-
-<screen><userinput>logout; chroot $LFS /tools/bin/env -i \
+<xref linkend="ch-system-chroot"/>, then first exit from chroot:</para>
+
+<screen><userinput>logout</userinput></screen>
+
+<para>Then reenter it with:</para>
+
+<screen><userinput>chroot $LFS /tools/bin/env -i \
 &nbsp;&nbsp;&nbsp;&nbsp;HOME=/root TERM=$TERM PS1='\u:\w\$ ' \
 &nbsp;&nbsp;&nbsp;&nbsp;PATH=/bin:/usr/bin:/sbin:/usr/sbin \
@@ -617 +620 @@
 directory, exit from chroot and reenter it with the above command. Also, before
 removing <filename class="directory">/tools</filename>, you may want to tar it
-up and store it in a safe place, in case you want build another LFS system
+up and store it in a safe place, in case you want to build another LFS system
 soon.</para>
 

chapter06/ncurses.xml

@@ -42 +42 @@
 <screen><userinput>mv /usr/lib/libncurses.so.5* /lib</userinput></screen>
 
-<para>Since the libraries have been moved to
-<filename>/lib</filename>, a few symlinks are currently pointing
-towards non-existing files. Recreate those symlinks:</para>
+<para>Now the libraries have been moved, a few symlinks are pointing to
+non-existent files. Recreate those symlinks:</para>
 
 <screen><userinput>ln -sf ../../lib/libncurses.so.5 /usr/lib/libncurses.so

chapter06/vim.xml

@@ -26 +26 @@
 
 <para>First change the default locations of the <filename>vimrc</filename> and
-<filename>gvimrc</filename> files to <filename
+<filename>gvimrc</filename> configuration files to <filename
 class="directory">/etc</filename>.</para>
 
@@ -43 +43 @@
 <userinput>make check</userinput>. However, this test suite outputs a lot of
 seemingly garbage characters to the screen, and this can wreak havoc with the
-settings of the current terminal. Accordingly, the running of the test suite
-here is strictly optional.</para>
+settings of the current terminal. Therefore the running of the test suite here
+is strictly optional.</para>
 
 <para>And install the package:</para>

chapter06/zlib.xml

@@ -34 +34 @@
 <userinput>make check</userinput>.</para>
 
-<screen><userinput>make check</userinput></screen>
-
 <para>Install the shared library:</para>
 
@@ -45 +43 @@
 make</userinput></screen>
 
-<para>To have the results tested, issue:
+<para>To have the results tested again, issue:
 <userinput>make check</userinput>.</para>
 
@@ -59 +57 @@
 the <filename class="directory">/lib</filename> directory. This matters most
 in scenarios where <filename class="directory">/usr</filename> is on a
-separate partition. Essentially, the run-time components of any libraries
-depended upon by programs in <filename class="directory">/bin</filename> or
+separate partition. Essentially, the run-time components of any libraries that
+are used by programs in <filename class="directory">/bin</filename> or
 <filename class="directory">/sbin</filename> should reside in
 <filename class="directory">/lib</filename> so that they are on the root
@@ -66 +64 @@
 <filename class="directory">/usr</filename> being inaccessible.</para>
 
-<para>Therefore we move the run-time components of the shared Zlib into
-<filename class="directory">/lib</filename> by issuing the following
-command:</para>
+<para>For the above reason we move the run-time components of the shared Zlib
+into <filename class="directory">/lib</filename>:</para>
 
 <screen><userinput>mv /usr/lib/libz.so.* /lib</userinput></screen>
 
-<para>Now we need to fix up the <filename>/usr/lib/libz.so</filename> symlink
-because we just moved the location of the file it points to:</para>
+<para>Now we need to fix the <filename>/usr/lib/libz.so</filename> symlink
+because we just moved the file it points to:</para>
 
 <screen><userinput>ln -sf ../../lib/libz.so.1 /usr/lib/libz.so</userinput></screen>

chapter07/loadkeys.xml

@@ -3 +3 @@
 <?dbhtml filename="loadkeys.html" dir="chapter07"?>
 
-<para>If you decided to compile your keymap file directly into the kernel back
-at the end of <xref linkend="chapter-building-system"/>, then you strictly speaking don't
-need to run this loadkeys script, since the kernel has already set up the
-keymap for you. You can still run it if you want, it isn't going to hurt you.
-It could even be beneficial to keep it in case you run a lot of different
-kernels and don't remember or want to compile the keymap into every kernel you
-lay your hands on.</para>
+<para>If back in <xref linkend="chapter-building-system"/> you decided to go
+compile your keymap directly into the kernel (later on in <xref
+linkend="chapter-mixture"/>), then strictly speaking you don't need to run this
+loadkeys script, since the kernel will set up the keymap for you. If you wish,
+you can still run the script, it isn't going to hurt you. Keeping it could even
+be beneficial, in case you run a lot of different kernels and can't be sure
+that the keymap is compiled into every one of them.</para>
 
-<para>If you decided you don't need to, or don't want to use the loadkeys
-script, remove the
-<filename class="symlink">/etc/rc.d/rcsysinit.d/S70loadkeys</filename>
-symlink.</para>
+<para>If you decided you don't need or don't want to use the loadkeys script,
+remove the <filename
+class="symlink">/etc/rc.d/rcsysinit.d/S70loadkeys</filename> symlink.</para>
 
 </sect1>

chapter09/reboot.xml

@@ -10 +10 @@
 <para>Then unmount the virtual files systems:</para>
 
-<screen><userinput>umount /dev/pts
-umount /proc</userinput></screen>    
+<screen><userinput>umount $LFS/dev/pts
+umount $LFS/proc</userinput></screen>    
 
 <para>And unmount the LFS file system:</para>