Changeset fb40919 for BOOK/chroot

Timestamp:

Jun 21, 2006, 2:53:33 PM (18 years ago)

Author:

Chris Staub <chris@…>

Branches:

clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit

Children:

a702d3f

Parents:

0de816f8

Message:

Changed many 'LFS' references to 'CLFS'

Location:

BOOK/chroot/common

Files:

• changingowner.xml (modified) (2 diffs)
• chroot.xml (modified) (2 diffs)
• kernfs.xml (modified) (2 diffs)

BOOK/chroot/common/changingowner.xml

@@ -17 +17 @@
     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
@@ -27 +27 @@
 
     <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,

BOOK/chroot/common/chroot.xml

@@ -12 +12 @@
 
   <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
@@ -37 +37 @@
   <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>

BOOK/chroot/common/kernfs.xml

@@ -30 +30 @@
 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>
@@ -44 +44 @@
   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>