Ignore:
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/partitioning/common
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • BOOK/partitioning/common/creatingfilesystem.xml

    r0de816f8 rfb40919  
    2020
    2121  <para os="b">To create an <systemitem class="filesystem">ext2</systemitem> file
    22   system on the LFS partition, run the following:</para>
     22  system on the CLFS partition, run the following:</para>
    2323
    2424<screen os="c"><userinput>mke2fs /dev/<replaceable>[xxx]</replaceable></userinput></screen>
    2525
    26   <para os="d">Replace <replaceable>[xxx]</replaceable> with the name of the LFS
     26  <para os="d">Replace <replaceable>[xxx]</replaceable> with the name of the CLFS
    2727  partition (<filename class="devicefile">hda5</filename> in our previous
    2828  example).</para>
     
    3131    <para>Some host distributions use custom features in their filesystem
    3232    creation tools (E2fsprogs). This can cause problems when booting into
    33     your new LFS, as those features will not be supported by the LFS-installed
    34     E2fsprogs; you will get an error similar to <computeroutput>unsupported
    35     filesystem features, upgrade your e2fsprogs</computeroutput>. To check
    36     if your host system uses custom enhancements, run the following
    37     command:</para>
     33    your new CLFS system, as those features will not be supported by the
     34    CLFS-installed E2fsprogs; you will get an error similar to
     35    <computeroutput>unsupported filesystem features, upgrade your
     36    e2fsprogs</computeroutput>. To check if your host system uses custom
     37    enhancements, run the following command:</para>
    3838
    3939<screen os="f"><userinput>debugfs -R feature /dev/<replaceable>[xxx]</replaceable></userinput></screen>
     
    4343    enhancements.  In that case, to avoid later problems, you should compile the
    4444    stock E2fsprogs package and use the resulting binaries to re-create the
    45     filesystem on your LFS partition:</para>
     45    filesystem on your CLFS partition:</para>
    4646
    4747<screen os="g"><userinput>cd /tmp
  • BOOK/partitioning/common/creatingpartition.xml

    r0de816f8 rfb40919  
    2626  However, if the CLFS system is intended to be the primary Linux system,
    2727  additional software will probably be installed which will require
    28   additional space (2-3 GB). The LFS system itself will not take up this
     28  additional space (2-3 GB). The CLFS system itself will not take up this
    2929  much room. A large portion of this requirement is to provide sufficient
    3030  free temporary storage. Compiling packages can require a lot of disk space
     
    3535  partition as swap space. This is used by the kernel to store seldom-used
    3636  data and leave more memory available for active processes. The swap
    37   partition for an LFS system can be the same as the one used by the host
     37  partition for an CLFS system can be the same as the one used by the host
    3838  system, in which case it is not necessary to create another one.</para>
    3939
  • BOOK/partitioning/common/mounting.xml

    r0de816f8 rfb40919  
    3232  the CLFS partition.</para>
    3333
    34   <para>If using multiple partitions for LFS (e.g., one for <filename
     34  <para>If using multiple partitions for CLFS (e.g., one for <filename
    3535  class="directory">/</filename> and another for <filename
    3636  class="directory">/usr</filename>), mount them using:</para>
Note: See TracChangeset for help on using the changeset viewer.