r1815 - / trunk/BOOK/appendices/dependencies trunk/BOOK/boot/common trunk/BOOK/boot/x86_64-64 trunk/BOOK/bootable trunk/BOOK/bootable/alpha trunk/BOOK/bootable/common trunk/BOOK/bootable/mips trunk/BOOK/bootable/mips64 trunk/BOOK/bootable/ppc trunk/BOOK/bootable/sparc trunk/BOOK/bootable/x86 trunk/BOOK/bootable/x86_64-64 trunk/BOOK/bootscripts/common trunk/BOOK/bootscripts/mips trunk/BOOK/chroot/common trunk/BOOK/final-preps trunk/BOOK/final-system/common trunk/BOOK/final-system/multilib trunk/BOOK/final-system/ppc64 trunk/BOOK/introduction/common trunk/BOOK/materials/common trunk/BOOK/partitioning/common trunk/BOOK/prologue/common trunk/BOOK/the-end

jim at linuxfromscratch.org jim at linuxfromscratch.org
Wed Jun 21 16:54:53 PDT 2006


Author: jim
Date: 2006-06-21 17:54:49 -0600 (Wed, 21 Jun 2006)
New Revision: 1815

Modified:
   /
   trunk/BOOK/appendices/dependencies/common.xml
   trunk/BOOK/boot/common/creatingdirs.xml
   trunk/BOOK/boot/common/introduction.xml
   trunk/BOOK/boot/x86_64-64/lilo.xml
   trunk/BOOK/bootable/alpha-chapter.xml
   trunk/BOOK/bootable/alpha/aboot.xml
   trunk/BOOK/bootable/common/introduction.xml
   trunk/BOOK/bootable/mips-chapter.xml
   trunk/BOOK/bootable/mips/arcload.xml
   trunk/BOOK/bootable/mips/colo.xml
   trunk/BOOK/bootable/mips64-chapter.xml
   trunk/BOOK/bootable/mips64/arcload.xml
   trunk/BOOK/bootable/ppc-chapter.xml
   trunk/BOOK/bootable/ppc/yaboot.xml
   trunk/BOOK/bootable/ppc64-chapter.xml
   trunk/BOOK/bootable/sparc-chapter.xml
   trunk/BOOK/bootable/sparc/silo.xml
   trunk/BOOK/bootable/x86-chapter.xml
   trunk/BOOK/bootable/x86/grub.xml
   trunk/BOOK/bootable/x86/kernel.xml
   trunk/BOOK/bootable/x86_64-64-chapter.xml
   trunk/BOOK/bootable/x86_64-64/lilo.xml
   trunk/BOOK/bootable/x86_64-chapter.xml
   trunk/BOOK/bootscripts/common/console.xml
   trunk/BOOK/bootscripts/common/introduction.xml
   trunk/BOOK/bootscripts/common/network.xml
   trunk/BOOK/bootscripts/common/profile.xml
   trunk/BOOK/bootscripts/common/udev.xml
   trunk/BOOK/bootscripts/common/usage.xml
   trunk/BOOK/bootscripts/mips/bootscripts.xml
   trunk/BOOK/chroot/common/changingowner.xml
   trunk/BOOK/chroot/common/chroot.xml
   trunk/BOOK/chroot/common/kernfs.xml
   trunk/BOOK/final-preps/creatingtoolsdir.xml
   trunk/BOOK/final-system/common/coreutils.xml
   trunk/BOOK/final-system/common/e2fsprogs.xml
   trunk/BOOK/final-system/common/glibc.xml
   trunk/BOOK/final-system/common/inetutils.xml
   trunk/BOOK/final-system/common/iproute2.xml
   trunk/BOOK/final-system/common/kbd.xml
   trunk/BOOK/final-system/common/man.xml
   trunk/BOOK/final-system/common/psmisc.xml
   trunk/BOOK/final-system/common/sysvinit.xml
   trunk/BOOK/final-system/common/udev.xml
   trunk/BOOK/final-system/common/util-linux.xml
   trunk/BOOK/final-system/common/vim.xml
   trunk/BOOK/final-system/multilib/glibc-64bit.xml
   trunk/BOOK/final-system/ppc64/glibc-64bit.xml
   trunk/BOOK/introduction/common/askforhelp.xml
   trunk/BOOK/introduction/common/changelog.xml
   trunk/BOOK/introduction/common/resources.xml
   trunk/BOOK/materials/common/patches.xml
   trunk/BOOK/partitioning/common/creatingfilesystem.xml
   trunk/BOOK/partitioning/common/creatingpartition.xml
   trunk/BOOK/partitioning/common/mounting.xml
   trunk/BOOK/prologue/common/errata.xml
   trunk/BOOK/prologue/common/prerequisites.xml
   trunk/BOOK/prologue/common/typography.xml
   trunk/BOOK/the-end/reboot.xml
   trunk/BOOK/the-end/whatnow.xml
Log:
 r4048 at server (orig r1882):  chris at beaker67.com | 2006-06-21 14:53:33 -0700
 Changed many 'LFS' references to 'CLFS'



Property changes on: 
___________________________________________________________________
Name: svk:merge
   - b6734a72-470d-0410-b049-f317dca95413:/:1881
   + b6734a72-470d-0410-b049-f317dca95413:/:1882

Modified: trunk/BOOK/appendices/dependencies/common.xml
===================================================================
--- trunk/BOOK/appendices/dependencies/common.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/appendices/dependencies/common.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -11,12 +11,12 @@
 
   <title>Dependencies</title>
 
-  <para>Every package built in LFS relies on one or more other packages
+  <para>Every package built in CLFS relies on one or more other packages
   in order to build and install properly. Some packages even participate
   in circular dependencies, that is, the first package depends on the second
   which in turn depends on the first. Because of these dependencies, the
-  order in which packages are built in LFS is very important. The purpose
-  of this page is to document the dependencies of each package built in LFS.</para>
+  order in which packages are built in CLFS is very important. The purpose
+  of this page is to document the dependencies of each package built in CLFS.</para>
 
   <para>For each package we build, we have listed three types of dependencies.
   The first lists what other packages need to be available in order to compile
@@ -75,7 +75,7 @@
         <seglistitem>
           <seg>Binutils, Bison, Bzip2, DejaGNU, Diffutils, Expect, Findutils,
           Flex, GCC, Gettext, Gzip, Libtool and Tar. Can also use several
-          other packages that are not installed in LFS.</seg>
+          other packages that are not installed in CLFS.</seg>
         </seglistitem>
       </segmentedlist>
 

Modified: trunk/BOOK/boot/common/creatingdirs.xml
===================================================================
--- trunk/BOOK/boot/common/creatingdirs.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/boot/common/creatingdirs.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -10,7 +10,7 @@
 
   <title>Creating Directories</title>
 
-  <para os="a">It is time to create some structure in the LFS file system. Create a
+  <para os="a">It is time to create some structure in the CLFS file system. Create a
   standard directory tree by issuing the following commands:</para>
 
 <screen><userinput>mkdir -pv ${LFS}/{bin,boot,dev,etc/opt,home,lib,mnt,opt}

Modified: trunk/BOOK/boot/common/introduction.xml
===================================================================
--- trunk/BOOK/boot/common/introduction.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/boot/common/introduction.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -16,7 +16,7 @@
 
   <para>There are a few additional packages that will need to be
   installed to allow you to boot the minimal system. Some of these
-  packages will be installed onto the root or in /usr on the LFS
+  packages will be installed onto the root or in /usr on the CLFS
   partition ($LFS/bin, $LFS/usr/lib, etc...), rather than /tools, using the
   "DESTDIR" option with make. This will require the
   <systemitem class="username">lfs</systemitem> user to have write access to

Modified: trunk/BOOK/boot/x86_64-64/lilo.xml
===================================================================
--- trunk/BOOK/boot/x86_64-64/lilo.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/boot/x86_64-64/lilo.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -8,7 +8,7 @@
 <sect1 id="ch-boot-lilo">
   <?dbhtml filename="lilo.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <indexterm zone="ch-boot-lilo">
     <primary sortas="a-Lilo">Lilo</primary>

Modified: trunk/BOOK/bootable/alpha/aboot.xml
===================================================================
--- trunk/BOOK/bootable/alpha/aboot.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/alpha/aboot.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -8,7 +8,7 @@
 <sect1 id="ch-bootable-aboot">
   <?dbhtml filename="aboot.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <indexterm zone="ch-bootable-aboot">
     <primary sortas="a-Aboot">Aboot</primary>

Modified: trunk/BOOK/bootable/alpha-chapter.xml
===================================================================
--- trunk/BOOK/bootable/alpha-chapter.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/alpha-chapter.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -5,11 +5,11 @@
   %general-entities;
 ]>
 
-<chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
+<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
   <?dbhtml dir="bootable"?>
   <?dbhtml filename="chapter.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="alpha/fstab.xml"/>

Modified: trunk/BOOK/bootable/common/introduction.xml
===================================================================
--- trunk/BOOK/bootable/common/introduction.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/common/introduction.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -10,10 +10,10 @@
 
   <title>Introduction</title>
 
-  <para>It is time to make the LFS system bootable. This chapter
+  <para>It is time to make the CLFS system bootable. This chapter
   discusses creating an <filename>fstab</filename> file, building a
-  kernel for the new LFS system, and installing the boot loader so
-  that the LFS system can be selected for booting at startup.</para>
+  kernel for the new CLFS system, and installing the boot loader so
+  that the CLFS system can be selected for booting at startup.</para>
 
 </sect1>
 

Modified: trunk/BOOK/bootable/mips/arcload.xml
===================================================================
--- trunk/BOOK/bootable/mips/arcload.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/mips/arcload.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -8,7 +8,7 @@
 <sect1 id="ch-bootable-arcload">
   <?dbhtml filename="arcload.html"?>
 
-  <title>Making the LFS System Bootable via Arcload</title>
+  <title>Making the CLFS System Bootable via Arcload</title>
 
   <indexterm zone="ch-bootable-arcload">
     <primary sortas="a-Arcload">Arcload</primary>

Modified: trunk/BOOK/bootable/mips/colo.xml
===================================================================
--- trunk/BOOK/bootable/mips/colo.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/mips/colo.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -8,7 +8,7 @@
 <sect1 id="ch-bootable-colo">
   <?dbhtml filename="colo.html"?>
 
-  <title>Making the LFS System Bootable via Colo</title>
+  <title>Making the CLFS System Bootable via Colo</title>
 
   <indexterm zone="ch-bootable-colo">
     <primary sortas="a-Colo">Colo</primary>
@@ -20,7 +20,7 @@
     RaQ2, Qube, or the Qube2.</para>
   </note>
 
-  <para os="c">Your shiny new LFS system is almost complete. One of the last
+  <para os="c">Your shiny new CLFS system is almost complete. One of the last
   things to do is ensure you can boot it. The instructions below apply
   only to Cobalt RaQ1/RaQ2/Cube2 servers. Information on <quote>boot
   loading</quote> for other architectures should be available in the

Modified: trunk/BOOK/bootable/mips-chapter.xml
===================================================================
--- trunk/BOOK/bootable/mips-chapter.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/mips-chapter.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -5,11 +5,11 @@
   %general-entities;
 ]>
 
-<chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
+<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
   <?dbhtml dir="bootable"?>
   <?dbhtml filename="chapter.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/fstab.xml"/>

Modified: trunk/BOOK/bootable/mips64/arcload.xml
===================================================================
--- trunk/BOOK/bootable/mips64/arcload.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/mips64/arcload.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -8,7 +8,7 @@
 <sect1 id="ch-bootable-arcload">
   <?dbhtml filename="arcload.html"?>
 
-  <title>Making the LFS System Bootable via Arcload</title>
+  <title>Making the CLFS System Bootable via Arcload</title>
 
   <indexterm zone="ch-bootable-arcload">
     <primary sortas="a-Arcload">Arcload</primary>

Modified: trunk/BOOK/bootable/mips64-chapter.xml
===================================================================
--- trunk/BOOK/bootable/mips64-chapter.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/mips64-chapter.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -5,11 +5,11 @@
   %general-entities;
 ]>
 
-<chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
+<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
   <?dbhtml dir="bootable"?>
   <?dbhtml filename="chapter.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/fstab.xml"/>

Modified: trunk/BOOK/bootable/ppc/yaboot.xml
===================================================================
--- trunk/BOOK/bootable/ppc/yaboot.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/ppc/yaboot.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -8,13 +8,13 @@
 <sect1 id="ch-bootable-yaboot" arch="ppc">
   <?dbhtml filename="yaboot.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <indexterm zone="ch-bootable-yaboot">
     <primary sortas="a-Yaboot">Yaboot</primary>
   <secondary>configuring</secondary></indexterm>
 
-  <para os="a">Your shiny new LFS system is almost complete. One of the last
+  <para os="a">Your shiny new CLFS system is almost complete. One of the last
   things to do is to ensure that the system can be properly booted. The
   instructions below apply only to NewWorld Macintoshes.</para>
 
@@ -106,7 +106,7 @@
 # in this context, light means 'without high intensity'
 fgcolor=light-green
 
-# The first entry is for LFS.
+# The first entry is for CLFS.
 # For all images, the pathname is relative to the filesystem
 # on which they are situated and can include at most one
 # directory

Modified: trunk/BOOK/bootable/ppc-chapter.xml
===================================================================
--- trunk/BOOK/bootable/ppc-chapter.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/ppc-chapter.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -5,11 +5,11 @@
   %general-entities;
 ]>
 
-<chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
+<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
   <?dbhtml dir="bootable"?>
   <?dbhtml filename="chapter.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/fstab.xml"/>

Modified: trunk/BOOK/bootable/ppc64-chapter.xml
===================================================================
--- trunk/BOOK/bootable/ppc64-chapter.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/ppc64-chapter.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -5,11 +5,11 @@
   %general-entities;
 ]>
 
-<chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
+<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
   <?dbhtml dir="bootable"?>
   <?dbhtml filename="chapter.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/fstab.xml"/>

Modified: trunk/BOOK/bootable/sparc/silo.xml
===================================================================
--- trunk/BOOK/bootable/sparc/silo.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/sparc/silo.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -8,7 +8,7 @@
 <sect1 id="ch-bootable-silo">
   <?dbhtml filename="silo.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <indexterm zone="ch-bootable-silo">
     <primary sortas="a-silo">Silo</primary>

Modified: trunk/BOOK/bootable/sparc-chapter.xml
===================================================================
--- trunk/BOOK/bootable/sparc-chapter.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/sparc-chapter.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -5,11 +5,11 @@
   %general-entities;
 ]>
 
-<chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
+<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
   <?dbhtml dir="bootable"?>
   <?dbhtml filename="chapter.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="sparc/fstab.xml"/>

Modified: trunk/BOOK/bootable/x86/grub.xml
===================================================================
--- trunk/BOOK/bootable/x86/grub.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/x86/grub.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -8,14 +8,14 @@
 <sect1 id="ch-bootable-grub">
   <?dbhtml filename="grub.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <indexterm zone="ch-bootable-grub">
     <primary sortas="a-GRUB">GRUB</primary>
     <secondary>configuring</secondary>
   </indexterm>
 
-  <para os="a">Your shiny new LFS system is almost complete. One of the last
+  <para os="a">Your shiny new CLFS system is almost complete. One of the last
   things to do is to ensure that the system can be properly booted. The
   instructions below apply only to computers of IA-32 architecture,
   meaning mainstream PCs. Information on <quote>boot loading</quote> for
@@ -70,7 +70,7 @@
     Do not run the command if this is not desired, for example, if using
     a third party boot manager to manage the Master Boot Record (MBR).
     In this scenario, it would make more sense to install GRUB into the
-    <quote>boot sector</quote> of the LFS partition. In this case, this
+    <quote>boot sector</quote> of the CLFS partition. In this case, this
     next command would become <userinput>setup (hd0,3)</userinput>.</para>
   </warning>
 
@@ -100,8 +100,8 @@
 # Use prettier colors.
 color green/black light-green/black
 
-# The first entry is for LFS.
-title LFS &version;
+# The first entry is for CLFS.
+title CLFS &version;
 root (hd0,3)
 kernel /boot/lfskernel-&linux-version; root=/dev/hda4</literal>
 EOF</userinput></screen>

Modified: trunk/BOOK/bootable/x86/kernel.xml
===================================================================
--- trunk/BOOK/bootable/x86/kernel.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/x86/kernel.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -50,7 +50,7 @@
     Please note that the udev bootscript requires "rtc" and "tmpfs" to be
     enabled and built into the kernel, not as modules. BLFS has
     some information regarding particular kernel configuration requirements of
-    packages outside of LFS at <ulink
+    packages outside of CLFS at <ulink
     url="&blfs-root;view/svn/longindex.html#kernel-config-index"/>:</para>
 
 <screen os="i"><userinput>make menuconfig</userinput></screen>
@@ -143,9 +143,9 @@
       <para>Some kernel documentation recommends creating a symlink from
       <filename class="symlink">/usr/src/linux</filename> pointing to the
       kernel source directory. This is specific to kernels prior to the
-      2.6 series and <emphasis>must not</emphasis> be created on an LFS
+      2.6 series and <emphasis>must not</emphasis> be created on a CLFS
       system as it can cause problems for packages you may wish to build
-      once your base LFS system is complete.</para>
+      once your base CLFS system is complete.</para>
 
       <para>Also, the headers in the system's <filename
       class="directory">include</filename> directory should

Modified: trunk/BOOK/bootable/x86-chapter.xml
===================================================================
--- trunk/BOOK/bootable/x86-chapter.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/x86-chapter.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -5,11 +5,11 @@
   %general-entities;
 ]>
 
-<chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
+<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
   <?dbhtml dir="bootable"?>
   <?dbhtml filename="chapter.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/fstab.xml"/>

Modified: trunk/BOOK/bootable/x86_64-64/lilo.xml
===================================================================
--- trunk/BOOK/bootable/x86_64-64/lilo.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/x86_64-64/lilo.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -8,14 +8,14 @@
 <sect1 id="ch-bootable-lilo">
   <?dbhtml filename="lilo.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <indexterm zone="ch-bootable-lilo">
     <primary sortas="a-Lilo">Lilo</primary>
     <secondary>configuring</secondary>
   </indexterm>
 
-    <para os="a">Your shiny new LFS system is almost complete. One of the
+    <para os="a">Your shiny new CLFS system is almost complete. One of the
       last things to do is to ensure that the system can be properly
       booted. The instructions below apply only to computers using lilo,
       which in the context of this book means x86_64 Pure64 systems.

Modified: trunk/BOOK/bootable/x86_64-64-chapter.xml
===================================================================
--- trunk/BOOK/bootable/x86_64-64-chapter.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/x86_64-64-chapter.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -5,11 +5,11 @@
   %general-entities;
 ]>
 
-<chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
+<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
   <?dbhtml dir="bootable"?>
   <?dbhtml filename="chapter.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/fstab.xml"/>

Modified: trunk/BOOK/bootable/x86_64-chapter.xml
===================================================================
--- trunk/BOOK/bootable/x86_64-chapter.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootable/x86_64-chapter.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -5,11 +5,11 @@
   %general-entities;
 ]>
 
-<chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
+<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
   <?dbhtml dir="bootable"?>
   <?dbhtml filename="chapter.html"?>
 
-  <title>Making the LFS System Bootable</title>
+  <title>Making the CLFS System Bootable</title>
 
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/fstab.xml"/>

Modified: trunk/BOOK/bootscripts/common/console.xml
===================================================================
--- trunk/BOOK/bootscripts/common/console.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootscripts/common/console.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -26,7 +26,7 @@
   language-specific HOWTO's can also help with this (see <ulink
   url="http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>. A pre-made
   <filename>/etc/sysconfig/console</filename> file with known settings for
-  several countries was installed with the LFS-Bootscripts package, so the
+  several countries was installed with the CLFS-Bootscripts package, so the
   relevant section can be uncommented if the country is supported. If still
   in doubt, look in the <filename class="directory">/usr/share/kbd</filename>
   directory for valid keymaps and screen fonts. Read

Modified: trunk/BOOK/bootscripts/common/introduction.xml
===================================================================
--- trunk/BOOK/bootscripts/common/introduction.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootscripts/common/introduction.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -10,7 +10,7 @@
 
   <title>Introduction</title>
 
-  <para>This chapter details how to install and configure the LFS-Bootscripts
+  <para>This chapter details how to install and configure the CLFS-Bootscripts
   package. Most of these scripts will work without modification, but a few
   require additional configuration files because they deal with
   hardware-dependent information.</para>

Modified: trunk/BOOK/bootscripts/common/network.xml
===================================================================
--- trunk/BOOK/bootscripts/common/network.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootscripts/common/network.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -57,7 +57,7 @@
     network script and not brought up.</para>
 
     <para>The <envar>SERVICE</envar> variable defines the method used for
-    obtaining the IP address. The LFS-Bootscripts package has a modular IP
+    obtaining the IP address. The CLFS-Bootscripts package has a modular IP
     assignment format, and creating additional files in the <filename
     class="directory">/etc/sysconfig/network-devices/services</filename>
     directory allows other IP assignment methods. This is commonly used

Modified: trunk/BOOK/bootscripts/common/profile.xml
===================================================================
--- trunk/BOOK/bootscripts/common/profile.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootscripts/common/profile.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -118,7 +118,7 @@
   locale. Further instructions assume that there are no such error messages
   from Glibc.</para>
 
-  <para>Some packages beyond LFS may also lack support for your chosen locale.
+  <para>Some packages beyond CLFS may also lack support for your chosen locale.
   One example is the X library (part of the X Window System), which outputs
   the following error message:</para>
 
@@ -160,7 +160,7 @@
   writing direction. More complex cases (including UTF-8 based locales)
   require additional steps and additional patches because many applications
   tend to not work properly under such conditions. These steps and patches
-  are not included in the LFS book and such locales are not yet supported
-  by LFS.</para>
+  are not included in the CLFS book and such locales are not yet supported
+  by CLFS.</para>
 
 </sect1>

Modified: trunk/BOOK/bootscripts/common/udev.xml
===================================================================
--- trunk/BOOK/bootscripts/common/udev.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootscripts/common/udev.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -8,7 +8,7 @@
 <sect1 id="ch-scripts-udev">
   <?dbhtml filename="udev.html"?>
 
-  <title>Device and Module Handling on an LFS System</title>
+  <title>Device and Module Handling on a CLFS System</title>
 
   <indexterm zone="ch-scripts-udev">
     <primary sortas="a-Udev">Udev</primary>
@@ -98,7 +98,7 @@
     class="directory">/dev</filename> directory are configured according to
     the rules specified in the files within the <filename
     class="directory">/etc/udev/rules.d/</filename> directory. These are
-    numbered in a similar fashion to the LFS-Bootscripts package. If
+    numbered in a similar fashion to the CLFS-Bootscripts package. If
     <command>udev</command> can't find a rule for the device it is creating,
     it will default permissions to <emphasis>660</emphasis> and ownership to
     <emphasis>root:root</emphasis>.</para>
@@ -128,7 +128,7 @@
     the appropriate kernel module to load. With <command>udev</command>,
     this method will not work because the device node does not exist until
     the module is loaded. To solve this, the <command>S05modules</command>
-    bootscript was added to the LFS-Bootscripts package, along with the
+    bootscript was added to the CLFS-Bootscripts package, along with the
     <filename>/etc/sysconfig/modules</filename> file. By adding module
     names to the <filename>modules</filename> file, these modules will be
     loaded when the computer starts up. This allows <command>udev</command>

Modified: trunk/BOOK/bootscripts/common/usage.xml
===================================================================
--- trunk/BOOK/bootscripts/common/usage.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootscripts/common/usage.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -18,7 +18,7 @@
   based on a concept of <emphasis>run-levels</emphasis>. It can be quite
   different from one system to another, so it cannot be assumed that
   because things worked in one particular Linux distribution, they should work
-  the same in LFS too. LFS has its own way of doing things, but it
+  the same in CLFS too. CLFS has its own way of doing things, but it
   respects generally accepted standards.</para>
 
   <para>SysVinit (which will be referred to as <quote>init</quote> from
@@ -123,7 +123,7 @@
   </variablelist>
 
   <para>Feel free to modify the way the boot process works (after all,
-  it is your own LFS system). The files given here are an example of how
+  it is your own CLFS system). The files given here are an example of how
   it can be done.</para>
 
 </sect1>

Modified: trunk/BOOK/bootscripts/mips/bootscripts.xml
===================================================================
--- trunk/BOOK/bootscripts/mips/bootscripts.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/bootscripts/mips/bootscripts.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -8,7 +8,7 @@
 <sect1 id="ch-scripts-bootscripts" role="wrap">
   <?dbhtml filename="bootscripts.html"?>
 
-  <title>LFS-Bootscripts-&lfs-bootscripts-version;</title>
+  <title>CLFS-Bootscripts-&lfs-bootscripts-version;</title>
 
   <indexterm zone="ch-scripts-bootscripts">
     <primary sortas="a-Bootscripts">Bootscripts</primary>
@@ -19,7 +19,7 @@
   xpointer="xpointer(//*[@role='package'])"/>
 
   <sect2 role="installation">
-    <title>Installation of LFS-Bootscripts</title>
+    <title>Installation of CLFS-Bootscripts</title>
 
     <para>Need to update the current bootscripts to handle LCD
     screens keeping this file for reference:</para>

Modified: trunk/BOOK/chroot/common/changingowner.xml
===================================================================
--- trunk/BOOK/chroot/common/changingowner.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/chroot/common/changingowner.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -16,8 +16,8 @@
     exists only on the host system. Although the <filename
     class="directory">/tools</filename> and <filename
     class="directory">/cross-tools</filename> directories can be deleted
-    once the LFS system has been finished, they can be retained to build
-    additional LFS systems. If the <filename class="directory">/tools</filename>
+    once the CLFS system has been finished, they can be retained to build
+    additional CLFS systems. If the <filename class="directory">/tools</filename>
     and <filename class="directory">/cross-tools</filename> directories are
     kept as is, the files are owned by a user ID without a corresponding
     account. This is dangerous because a user account created later could
@@ -26,7 +26,7 @@
     thus exposing these files to possible malicious manipulation.</para>
 
     <para os="b">To avoid this issue, add the <systemitem
-    class="username">lfs</systemitem> user to the new LFS system later when
+    class="username">lfs</systemitem> user to the new CLFS system later when
     creating the <filename>/etc/passwd</filename> file, taking care to assign
     it the same user and group IDs as on the host system. Alternatively,
     assign the contents of the <filename class="directory">/tools</filename>

Modified: trunk/BOOK/chroot/common/chroot.xml
===================================================================
--- trunk/BOOK/chroot/common/chroot.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/chroot/common/chroot.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -11,7 +11,7 @@
   <title>Entering the Chroot Environment</title>
 
   <para>It is time to enter the chroot environment to begin building
-  and installing the final LFS system. As user <systemitem
+  and installing the final CLFS system. As user <systemitem
   class="username">root</systemitem>, run the following command to
   enter the realm that is, at the moment, populated with only the
   temporary tools:</para>
@@ -36,7 +36,7 @@
 
   <para>From this point on, there is no need to use the
   <envar>LFS</envar> variable anymore, because all work will be
-  restricted to the LFS file system.  This is because the Bash shell is
+  restricted to the CLFS file system.  This is because the Bash shell is
   told that <filename class="directory">$LFS</filename> is now the root
   (<filename class="directory">/</filename>) directory.</para>
 

Modified: trunk/BOOK/chroot/common/kernfs.xml
===================================================================
--- trunk/BOOK/chroot/common/kernfs.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/chroot/common/kernfs.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -29,7 +29,7 @@
 <screen><userinput>mount -vt proc proc $LFS/proc
 mount -vt sysfs sysfs $LFS/sys</userinput></screen>
 
-  <para>Remember that if for any reason you stop working on the LFS system
+  <para>Remember that if for any reason you stop working on the CLFS system
   and start again later, it is important to check that these file systems
   are mounted again before entering the chroot environment.</para>
 
@@ -43,9 +43,9 @@
   <para>Once the system is complete and booting, the rest of our device
   nodes are created by the Udev package.  Since this package is not
   available to us right now, we must take other steps to provide device
-  nodes under on the LFS filesystem.  We will use the <quote>bind</quote>
+  nodes under on the CLFS filesystem.  We will use the <quote>bind</quote>
   option in the mount command to make our host system's /dev structure
-  appear in the new LFS filesystem:</para>
+  appear in the new CLFS filesystem:</para>
 
 <screen><userinput>/tools/bin/mount -o bind /dev $LFS/dev</userinput></screen>
 

Modified: trunk/BOOK/final-preps/creatingtoolsdir.xml
===================================================================
--- trunk/BOOK/final-preps/creatingtoolsdir.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-preps/creatingtoolsdir.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -27,7 +27,7 @@
 
   <para>The next step is to create a <filename class="symlink">/tools</filename>
   symlink on the host system. This will point to the newly-created directory
-  on the LFS partition. Run this command as <systemitem
+  on the CLFS partition. Run this command as <systemitem
   class="username">root</systemitem> as well:</para>
 
 <screen><userinput>ln -sv $LFS/tools /</userinput></screen>

Modified: trunk/BOOK/final-system/common/coreutils.xml
===================================================================
--- trunk/BOOK/final-system/common/coreutils.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-system/common/coreutils.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -80,7 +80,7 @@
 mv -v /usr/bin/chroot /usr/sbin
 ln -svf ../../bin/install /usr/bin</userinput></screen>
 
-    <para os="t">Some of the scripts in the LFS-Bootscripts package depend on
+    <para os="t">Some of the scripts in the CLFS-Bootscripts package depend on
     <command>head</command> and <command>sleep</command>. As <filename
     class="directory">/usr</filename> may not be available during the early
     stages of booting, those binaries need to be on the root partition:</para>

Modified: trunk/BOOK/final-system/common/e2fsprogs.xml
===================================================================
--- trunk/BOOK/final-system/common/e2fsprogs.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-system/common/e2fsprogs.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -69,7 +69,7 @@
           <para>This disables the building of the Enterprise Volume
           Management System (EVMS) plugin. This plugin is not up-to-date with
           the latest EVMS internal interfaces and EVMS is not installed as part
-          of a base LFS system, so the plugin is not required. See the EVMS
+          of a base CLFS system, so the plugin is not required. See the EVMS
           website at <ulink url="http://evms.sourceforge.net/"/> for more
           information regarding EVMS.</para>
         </listitem>

Modified: trunk/BOOK/final-system/common/glibc.xml
===================================================================
--- trunk/BOOK/final-system/common/glibc.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-system/common/glibc.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -124,11 +124,11 @@
         host system issues. The exact reasons are not yet clear.</para>
       </listitem>
       <listitem>
-        <para>If you have mounted the LFS partition with the
+        <para>If you have mounted the CLFS partition with the
         <parameter>noatime</parameter> option, the <emphasis>atime</emphasis> test
         will fail. As mentioned in <xref linkend="ch-partitioning-mounting"/>,
         do not use the <parameter>noatime</parameter> option while building
-        LFS.</para>
+        CLFS.</para>
       </listitem>
       <listitem>
         <para>When running on older and slower hardware, some tests
@@ -185,12 +185,12 @@
 
     <para>Some locales installed by the <command>make
     localedata/install-locales</command> command above are not properly
-    supported by some applications that are in the LFS and BLFS books. Because
+    supported by some applications that are in the CLFS and BLFS books. Because
     of the various problems that arise due to application programmers making
-    assumptions that break in such locales, LFS should not be used in locales
+    assumptions that break in such locales, CLFS should not be used in locales
     that utilize multibyte character sets (including UTF-8) or right-to-left
     writing order.  Numerous unofficial and unstable patches are required to
-    fix these problems, and it has been decided by the LFS developers not to
+    fix these problems, and it has been decided by the CLFS developers not to
     support such complex locales at this time. This applies to the ja_JP and
     fa_IR locales as well—they have been installed only for GCC and
     Gettext tests to pass, and the <command>watch</command> program (part of

Modified: trunk/BOOK/final-system/common/inetutils.xml
===================================================================
--- trunk/BOOK/final-system/common/inetutils.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-system/common/inetutils.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -78,7 +78,7 @@
         <listitem>
           <para>This disables the installation of the various network
           servers included as part of the Inetutils package. These servers are
-          deemed not appropriate in a basic LFS system. Some are insecure by
+          deemed not appropriate in a basic CLFS system. Some are insecure by
           nature and are only considered safe on trusted networks. More
           information can be found at <ulink
           url="&blfs-root;view/svn/basicnet/inetutils.html"/>. Note that

Modified: trunk/BOOK/final-system/common/iproute2.xml
===================================================================
--- trunk/BOOK/final-system/common/iproute2.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-system/common/iproute2.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -48,7 +48,7 @@
           <para>This ensures that the IPRoute2 binaries will install into
           <filename class="directory">/sbin</filename>. This is the correct
           location according to the FHS, because some of the IPRoute2 binaries
-          are used by the LFS-Bootscripts package.</para>
+          are used by the CLFS-Bootscripts package.</para>
         </listitem>
       </varlistentry>
     </variablelist>

Modified: trunk/BOOK/final-system/common/kbd.xml
===================================================================
--- trunk/BOOK/final-system/common/kbd.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-system/common/kbd.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -295,7 +295,7 @@
         <term><command>unicode_start</command></term>
         <listitem>
           <para>Puts the keyboard and console in UNICODE mode. Never use it on
-          LFS, because applications are not configured to support UNICODE.</para>
+          CLFS, because applications are not configured to support UNICODE.</para>
           <indexterm zone="ch-system-kbd unicode_start">
             <primary sortas="b-unicode_start">unicode_start</primary>
           </indexterm>

Modified: trunk/BOOK/final-system/common/man.xml
===================================================================
--- trunk/BOOK/final-system/common/man.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-system/common/man.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -102,7 +102,7 @@
     <command>man2dvi</command> program for localized man pages in
     non-ISO 8859-1 locales. Also, it does not work with multibyte
     character sets. The first problem does not currently have a solution.
-    The second issue is not of concern because the LFS installation does
+    The second issue is not of concern because the CLFS installation does
     not support multibyte character sets.</para>
 
     <para os="u">Additional information with regards to the compression of

Modified: trunk/BOOK/final-system/common/psmisc.xml
===================================================================
--- trunk/BOOK/final-system/common/psmisc.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-system/common/psmisc.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -39,7 +39,7 @@
           <filename class="directory">/bin</filename> instead of
           <filename class="directory">/usr/bin</filename>. This is the
           correct location according to the FHS, because some of the Psmisc
-          binaries are used by the LFS-Bootscripts package.</para>
+          binaries are used by the CLFS-Bootscripts package.</para>
         </listitem>
       </varlistentry>
     </variablelist>

Modified: trunk/BOOK/final-system/common/sysvinit.xml
===================================================================
--- trunk/BOOK/final-system/common/sysvinit.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-system/common/sysvinit.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -97,7 +97,7 @@
     before doing anything else. This escape sequence switches the console
     character set to a user-defined one, which can be modified by running
     the <command>setfont</command> program. The <command>console</command>
-    initscript from the LFS-Bootscripts package calls the
+    initscript from the CLFS-Bootscripts package calls the
     <command>setfont</command> program during system startup. Sending this
     escape sequence is necessary for people who use non-ISO 8859-1 screen
     fonts, but it does not affect native English speakers.</para>

Modified: trunk/BOOK/final-system/common/udev.xml
===================================================================
--- trunk/BOOK/final-system/common/udev.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-system/common/udev.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -176,7 +176,7 @@
         <listitem>
           <para>Simulates a <command>udev</command> run for the given device,
           and prints out the name of the node the real <command>udev</command>
-          would have created or (not in LFS) the name of the renamed network
+          would have created or (not in CLFS) the name of the renamed network
           interface</para>
           <indexterm zone="ch-system-udev udevtest">
             <primary sortas="b-udevtest">udevtest</primary>

Modified: trunk/BOOK/final-system/common/util-linux.xml
===================================================================
--- trunk/BOOK/final-system/common/util-linux.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-system/common/util-linux.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -90,7 +90,7 @@
 
     <para os="g">Install the package and move the <command>logger</command> binary
     to <filename class="directory">/bin</filename> as it is needed by the
-    LFS-Bootscripts package:</para>
+    CLFS-Bootscripts package:</para>
 
 <screen os="h"><userinput>make HAVE_KILL=yes HAVE_SLN=yes install
 mv -v /usr/bin/logger /bin</userinput></screen>

Modified: trunk/BOOK/final-system/common/vim.xml
===================================================================
--- trunk/BOOK/final-system/common/vim.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-system/common/vim.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -99,7 +99,7 @@
 
 <screen os="o"><userinput>ln -sv ../vim/vim&vim-version2;/doc /usr/share/doc/vim-&vim-version;</userinput></screen>
 
-    <para os="p">If an X Window System is going to be installed on the LFS
+    <para os="p">If an X Window System is going to be installed on the CLFS
     system, you may want to recompile Vim after installing X. Vim
     comes with a GUI version of the editor that requires X and some
     additional libraries to be installed. For more information, refer to the
@@ -375,7 +375,7 @@
           <para>Spell checks a file and generates the syntax statements
           necessary to highlight in <command>vim</command>. This script
           requires the old Unix <command>spell</command> command, which
-          is provided neither in LFS nor in BLFS</para>
+          is provided neither in CLFS nor in BLFS</para>
           <indexterm zone="ch-system-vim vimspell.sh">
             <primary sortas="b-vimspell.sh">vimspell.sh</primary>
           </indexterm>

Modified: trunk/BOOK/final-system/multilib/glibc-64bit.xml
===================================================================
--- trunk/BOOK/final-system/multilib/glibc-64bit.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-system/multilib/glibc-64bit.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -123,11 +123,11 @@
         host system issues. The exact reasons are not yet clear.</para>
       </listitem>
       <listitem>
-        <para>If you have mounted the LFS partition with the
+        <para>If you have mounted the CLFS partition with the
         <parameter>noatime</parameter> option, the <emphasis>atime</emphasis> test
         will fail. As mentioned in <xref linkend="ch-partitioning-mounting"/>,
         do not use the <parameter>noatime</parameter> option while building
-        LFS.</para>
+        CLFS.</para>
       </listitem>
       <listitem>
         <para>When running on older and slower hardware, some tests

Modified: trunk/BOOK/final-system/ppc64/glibc-64bit.xml
===================================================================
--- trunk/BOOK/final-system/ppc64/glibc-64bit.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/final-system/ppc64/glibc-64bit.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -134,11 +134,11 @@
         host system issues. The exact reasons are not yet clear.</para>
       </listitem>
       <listitem>
-        <para>If you have mounted the LFS partition with the
+        <para>If you have mounted the CLFS partition with the
         <parameter>noatime</parameter> option, the <emphasis>atime</emphasis> test
         will fail. As mentioned in <xref linkend="ch-partitioning-mounting"/>,
         do not use the <parameter>noatime</parameter> option while building
-        LFS.</para>
+        CLFS.</para>
       </listitem>
       <listitem>
         <para>When running on older and slower hardware, some tests

Modified: trunk/BOOK/introduction/common/askforhelp.xml
===================================================================
--- trunk/BOOK/introduction/common/askforhelp.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/introduction/common/askforhelp.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -43,7 +43,7 @@
       </listitem>
       <listitem>
         <para>The host distribution and version being used to
-        create LFS</para>
+        create CLFS</para>
       </listitem>
       <listitem>
         <para>The package or section the problem was encountered in</para>

Modified: trunk/BOOK/introduction/common/changelog.xml
===================================================================
--- trunk/BOOK/introduction/common/changelog.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/introduction/common/changelog.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -36,6 +36,15 @@
     </listitem>
 -->
 
+    <listitem>
+      <para>June 21, 2006</para>
+      <itemizedlist>
+        <listitem>
+          <para>[Chris] - Text updates to the book, including replacing
+          "LFS" with "CLFS".</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
 
     <listitem>
       <para>June 20, 2006</para>

Modified: trunk/BOOK/introduction/common/resources.xml
===================================================================
--- trunk/BOOK/introduction/common/resources.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/introduction/common/resources.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -13,7 +13,7 @@
   <sect2 id="ch-intro-faq">
     <title>FAQ</title>
 
-    <para>If during the building of the LFS system you encounter any
+    <para>If during the building of the CLFS system you encounter any
     errors, have any questions, or think there is a typo in the book,
     please start by consulting the Frequently Asked Questions (FAQ)
     that is located at <ulink url="&faq-root;"/>.</para>

Modified: trunk/BOOK/materials/common/patches.xml
===================================================================
--- trunk/BOOK/materials/common/patches.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/materials/common/patches.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -14,7 +14,7 @@
   These patches correct any mistakes in the packages that should be
   fixed by the maintainer. The patches also make small modifications to
   make the packages easier to work with. The following patches will be
-  needed to build an LFS system:</para>
+  needed to build an CLFS system:</para>
 
   <variablelist role="materials">
 
@@ -298,7 +298,7 @@
   <para os="a">Total size of these patches: about <returnvalue/></para>
 
   <para>In addition to the above required patches, there exist a number of
-  optional patches created by the LFS community. These optional patches
+  optional patches created by the CLFS community. These optional patches
   solve minor problems or enable functionality that is not enabled by
   default. Feel free to peruse the patches database located at
   <ulink url="&lfs-root;patches/"/> and acquire any additional

Modified: trunk/BOOK/partitioning/common/creatingfilesystem.xml
===================================================================
--- trunk/BOOK/partitioning/common/creatingfilesystem.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/partitioning/common/creatingfilesystem.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -19,22 +19,22 @@
   <ulink url="&blfs-root;view/svn/postlfs/filesystems.html"/>.</para>
 
   <para os="b">To create an <systemitem class="filesystem">ext2</systemitem> file
-  system on the LFS partition, run the following:</para>
+  system on the CLFS partition, run the following:</para>
 
 <screen os="c"><userinput>mke2fs /dev/<replaceable>[xxx]</replaceable></userinput></screen>
 
-  <para os="d">Replace <replaceable>[xxx]</replaceable> with the name of the LFS
+  <para os="d">Replace <replaceable>[xxx]</replaceable> with the name of the CLFS
   partition (<filename class="devicefile">hda5</filename> in our previous
   example).</para>
 
   <note os="e">
     <para>Some host distributions use custom features in their filesystem
     creation tools (E2fsprogs). This can cause problems when booting into
-    your new LFS, as those features will not be supported by the LFS-installed
-    E2fsprogs; you will get an error similar to <computeroutput>unsupported
-    filesystem features, upgrade your e2fsprogs</computeroutput>. To check
-    if your host system uses custom enhancements, run the following
-    command:</para>
+    your new CLFS system, as those features will not be supported by the
+    CLFS-installed E2fsprogs; you will get an error similar to
+    <computeroutput>unsupported filesystem features, upgrade your
+    e2fsprogs</computeroutput>. To check if your host system uses custom
+    enhancements, run the following command:</para>
 
 <screen os="f"><userinput>debugfs -R feature /dev/<replaceable>[xxx]</replaceable></userinput></screen>
 
@@ -42,7 +42,7 @@
     large_file; resize_inode or sparse_super then your host system may have custom
     enhancements.  In that case, to avoid later problems, you should compile the
     stock E2fsprogs package and use the resulting binaries to re-create the
-    filesystem on your LFS partition:</para>
+    filesystem on your CLFS partition:</para>
 
 <screen os="g"><userinput>cd /tmp
 tar xjf /path/to/sources/e2fsprogs-&e2fsprogs-version;.tar.bz2

Modified: trunk/BOOK/partitioning/common/creatingpartition.xml
===================================================================
--- trunk/BOOK/partitioning/common/creatingpartition.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/partitioning/common/creatingpartition.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -25,7 +25,7 @@
   This is enough to store all the source tarballs and compile the packages.
   However, if the CLFS system is intended to be the primary Linux system,
   additional software will probably be installed which will require
-  additional space (2-3 GB). The LFS system itself will not take up this
+  additional space (2-3 GB). The CLFS system itself will not take up this
   much room. A large portion of this requirement is to provide sufficient
   free temporary storage. Compiling packages can require a lot of disk space
   which will be reclaimed after the package is installed.</para>
@@ -34,7 +34,7 @@
   available for compilation processes, it is a good idea to use a small disk
   partition as swap space. This is used by the kernel to store seldom-used
   data and leave more memory available for active processes. The swap
-  partition for an LFS system can be the same as the one used by the host
+  partition for an CLFS system can be the same as the one used by the host
   system, in which case it is not necessary to create another one.</para>
 
   <para os="d">Start a disk partitioning program such as <command>cfdisk</command>

Modified: trunk/BOOK/partitioning/common/mounting.xml
===================================================================
--- trunk/BOOK/partitioning/common/mounting.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/partitioning/common/mounting.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -31,7 +31,7 @@
   <para>Replace <replaceable>[xxx]</replaceable> with the designation of
   the CLFS partition.</para>
 
-  <para>If using multiple partitions for LFS (e.g., one for <filename
+  <para>If using multiple partitions for CLFS (e.g., one for <filename
   class="directory">/</filename> and another for <filename
   class="directory">/usr</filename>), mount them using:</para>
 

Modified: trunk/BOOK/prologue/common/errata.xml
===================================================================
--- trunk/BOOK/prologue/common/errata.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/prologue/common/errata.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -12,11 +12,12 @@
 
   <para>The software used to create a CLFS system is constantly being
   updated and enhanced. Security warnings and bug fixes may become
-  available after the LFS book has been released. To check whether the
-  package versions or instructions in this release of CLFS need any
-  modifications to accommodate security vulnerabilities or other bug fixes,
-  please visit <ulink url="&errata;"/> before proceeding with your build.
-  You should note any changes shown and apply them to the relevant section
-  of the book as you progress with building the LFS system.</para>
+  available after the CLFS book has been released. Some host systems may
+  also have problems building CLFS. To check whether the package versions
+  or instructions in this release of CLFS need any modifications to
+  accommodate security vulnerabilities, other bug fixes, or host-specific
+  issues, please visit <ulink url="&errata;"/> before proceeding with your
+  build. You should note any changes shown and apply them to the relevant
+  section of the book as you progress with building the CLFS system.</para>
 
 </sect1>

Modified: trunk/BOOK/prologue/common/prerequisites.xml
===================================================================
--- trunk/BOOK/prologue/common/prerequisites.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/prologue/common/prerequisites.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -22,7 +22,7 @@
   required</para>
 
   <para>Because the CLFS book assumes <emphasis>at least</emphasis> this basic
-  level of skill, the various LFS support forums are unlikely to be able to
+  level of skill, the various CLFS support forums are unlikely to be able to
   provide you with much assistance; you will find that your questions regarding
   such basic knowledge will likely go unanswered, or you will simply be referred
   to the LFS essential pre-reading list.</para>

Modified: trunk/BOOK/prologue/common/typography.xml
===================================================================
--- trunk/BOOK/prologue/common/typography.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/prologue/common/typography.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -12,8 +12,8 @@
 
   <para>To make things easier to follow, there are a few typographical
   conventions used throughout this book. This section contains some
-  examples of the typographical format found throughout Linux From
-  Scratch.</para>
+  examples of the typographical format found throughout Cross-Compiled
+  Linux From Scratch.</para>
 
 <screen role="nodump"><userinput>./configure --prefix=/usr</userinput></screen>
 
@@ -35,7 +35,7 @@
 
   <para><ulink url="&lfs-root;"/></para>
 
-  <para>This format is used for hyperlinks, both within the LFS
+  <para>This format is used for hyperlinks, both within the CLFS
   community and to external pages. It includes HOWTOs, download locations,
   and websites.</para>
 
@@ -61,7 +61,7 @@
   <para>This format is used to refer to a specific manual page (hereinafter
   referred to simply as a <quote>man</quote> page). The number inside
   parentheses indicates a specific section inside of <command>man</command>.
-  For example, <command>passwd</command> has two man pages. Per LFS
+  For example, <command>passwd</command> has two man pages. Per CLFS
   installation instructions, those two man pages will be located at
   <filename>/usr/share/man/man1/passwd.1</filename> and
   <filename>/usr/share/man/man5/passwd.5</filename>. Both man pages have

Modified: trunk/BOOK/the-end/reboot.xml
===================================================================
--- trunk/BOOK/the-end/reboot.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/the-end/reboot.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -20,7 +20,7 @@
   continue forward. By installing a few extra packages from the BLFS
   book while still in our current chroot environment, you can leave
   yourself in a much better position to continue on once you reboot
-  into your new LFS installation. Installing a text mode web browser,
+  into your new CLFS installation. Installing a text mode web browser,
   such as Lynx, you can easily view the BLFS book in one virtual terminal,
   while building packages in another. The GPM package will also allow you
   to perform copy/paste actions in your virtual terminals. Lastly, if you
@@ -29,7 +29,7 @@
   this point might also be useful.</para>
 
   <para>Now that we have said that, lets move on to booting our shiny
-  new LFS installation for the first time! First exit from the chroot
+  new CLFS installation for the first time! First exit from the chroot
   environment:</para>
 
 <screen><userinput>logout</userinput></screen>
@@ -42,7 +42,7 @@
 umount $LFS/proc
 umount $LFS/sys</userinput></screen>
 
-  <para>Unmount the LFS file system itself:</para>
+  <para>Unmount the CLFS file system itself:</para>
 
 <screen><userinput>umount $LFS</userinput></screen>
 
@@ -60,7 +60,7 @@
   <para>Assuming the boot loader was set up as outlined earlier,
   <emphasis>CLFS &version;</emphasis> will boot automatically.</para>
 
-  <para>When the reboot is complete, the LFS system is ready for use and
+  <para>When the reboot is complete, the CLFS system is ready for use and
   more software may be added to suit your needs.</para>
 
 </sect1>

Modified: trunk/BOOK/the-end/whatnow.xml
===================================================================
--- trunk/BOOK/the-end/whatnow.xml	2006-06-21 19:56:22 UTC (rev 1814)
+++ trunk/BOOK/the-end/whatnow.xml	2006-06-21 23:54:49 UTC (rev 1815)
@@ -10,11 +10,11 @@
 
   <title>What Now?</title>
 
-  <para>Thank you for reading this LFS book. We hope that you have
+  <para>Thank you for reading this CLFS book. We hope that you have
   found this book helpful and have learned more about the system
   creation process.</para>
 
-  <para>Now that the LFS system is installed, you may be wondering
+  <para>Now that the CLFS system is installed, you may be wondering
   <quote>What next?</quote> To answer that question, we have compiled
   a list of resources for you.</para>
 
@@ -24,7 +24,7 @@
       <para>Maintenance</para>
 
       <para>Bugs and security notices are reported regularly for all software.
-      Since an LFS system is compiled from source, it is up to you to keep
+      Since a CLFS system is compiled from source, it is up to you to keep
       abreast of such reports.  There are several online resources that track
       such reports, some of which are shown below:</para>
 
@@ -64,7 +64,7 @@
       <para>Beyond Linux From Scratch</para>
 
       <para>The Beyond Linux From Scratch book covers installation
-      procedures for a wide range of software beyond the scope of the LFS
+      procedures for a wide range of software beyond the scope of the CLFS
       Book. The BLFS project is located at <ulink url="&blfs-root;"/>.</para>
     </listitem>
 




More information about the cross-lfs mailing list