Changeset b71fa50 for chroot


Ignore:
Timestamp:
Jun 21, 2006, 2:53:33 PM (19 years ago)
Author:
Chris Staub <chris@…>
Children:
73c89fd
Parents:
9fcb5e4
Message:

Changed many 'LFS' references to 'CLFS'

Location:
chroot/common
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • chroot/common/changingowner.xml

    r9fcb5e4 rb71fa50  
    1717    class="directory">/tools</filename> and <filename
    1818    class="directory">/cross-tools</filename> directories can be deleted
    19     once the LFS system has been finished, they can be retained to build
    20     additional LFS systems. If the <filename class="directory">/tools</filename>
     19    once the CLFS system has been finished, they can be retained to build
     20    additional CLFS systems. If the <filename class="directory">/tools</filename>
    2121    and <filename class="directory">/cross-tools</filename> directories are
    2222    kept as is, the files are owned by a user ID without a corresponding
     
    2727
    2828    <para os="b">To avoid this issue, add the <systemitem
    29     class="username">lfs</systemitem> user to the new LFS system later when
     29    class="username">lfs</systemitem> user to the new CLFS system later when
    3030    creating the <filename>/etc/passwd</filename> file, taking care to assign
    3131    it the same user and group IDs as on the host system. Alternatively,
  • chroot/common/chroot.xml

    r9fcb5e4 rb71fa50  
    1212
    1313  <para>It is time to enter the chroot environment to begin building
    14   and installing the final LFS system. As user <systemitem
     14  and installing the final CLFS system. As user <systemitem
    1515  class="username">root</systemitem>, run the following command to
    1616  enter the realm that is, at the moment, populated with only the
     
    3737  <para>From this point on, there is no need to use the
    3838  <envar>LFS</envar> variable anymore, because all work will be
    39   restricted to the LFS file system.  This is because the Bash shell is
     39  restricted to the CLFS file system.  This is because the Bash shell is
    4040  told that <filename class="directory">$LFS</filename> is now the root
    4141  (<filename class="directory">/</filename>) directory.</para>
  • chroot/common/kernfs.xml

    r9fcb5e4 rb71fa50  
    3030mount -vt sysfs sysfs $LFS/sys</userinput></screen>
    3131
    32   <para>Remember that if for any reason you stop working on the LFS system
     32  <para>Remember that if for any reason you stop working on the CLFS system
    3333  and start again later, it is important to check that these file systems
    3434  are mounted again before entering the chroot environment.</para>
     
    4444  nodes are created by the Udev package.  Since this package is not
    4545  available to us right now, we must take other steps to provide device
    46   nodes under on the LFS filesystem.  We will use the <quote>bind</quote>
     46  nodes under on the CLFS filesystem.  We will use the <quote>bind</quote>
    4747  option in the mount command to make our host system's /dev structure
    48   appear in the new LFS filesystem:</para>
     48  appear in the new CLFS filesystem:</para>
    4949
    5050<screen><userinput>/tools/bin/mount -o bind /dev $LFS/dev</userinput></screen>
Note: See TracChangeset for help on using the changeset viewer.