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

Changed many 'LFS' references to 'CLFS'

Location:
final-system/common
Files:
12 edited

Legend:

Unmodified
Added
Removed
  • final-system/common/coreutils.xml

    r9fcb5e4 rb71fa50  
    8181ln -svf ../../bin/install /usr/bin</userinput></screen>
    8282
    83     <para os="t">Some of the scripts in the LFS-Bootscripts package depend on
     83    <para os="t">Some of the scripts in the CLFS-Bootscripts package depend on
    8484    <command>head</command> and <command>sleep</command>. As <filename
    8585    class="directory">/usr</filename> may not be available during the early
  • final-system/common/e2fsprogs.xml

    r9fcb5e4 rb71fa50  
    7070          Management System (EVMS) plugin. This plugin is not up-to-date with
    7171          the latest EVMS internal interfaces and EVMS is not installed as part
    72           of a base LFS system, so the plugin is not required. See the EVMS
     72          of a base CLFS system, so the plugin is not required. See the EVMS
    7373          website at <ulink url="http://evms.sourceforge.net/"/> for more
    7474          information regarding EVMS.</para>
  • final-system/common/glibc.xml

    r9fcb5e4 rb71fa50  
    125125      </listitem>
    126126      <listitem>
    127         <para>If you have mounted the LFS partition with the
     127        <para>If you have mounted the CLFS partition with the
    128128        <parameter>noatime</parameter> option, the <emphasis>atime</emphasis> test
    129129        will fail. As mentioned in <xref linkend="ch-partitioning-mounting"/>,
    130130        do not use the <parameter>noatime</parameter> option while building
    131         LFS.</para>
     131        CLFS.</para>
    132132      </listitem>
    133133      <listitem>
     
    186186    <para>Some locales installed by the <command>make
    187187    localedata/install-locales</command> command above are not properly
    188     supported by some applications that are in the LFS and BLFS books. Because
     188    supported by some applications that are in the CLFS and BLFS books. Because
    189189    of the various problems that arise due to application programmers making
    190     assumptions that break in such locales, LFS should not be used in locales
     190    assumptions that break in such locales, CLFS should not be used in locales
    191191    that utilize multibyte character sets (including UTF-8) or right-to-left
    192192    writing order.  Numerous unofficial and unstable patches are required to
    193     fix these problems, and it has been decided by the LFS developers not to
     193    fix these problems, and it has been decided by the CLFS developers not to
    194194    support such complex locales at this time. This applies to the ja_JP and
    195195    fa_IR locales as well&mdash;they have been installed only for GCC and
  • final-system/common/inetutils.xml

    r9fcb5e4 rb71fa50  
    7979          <para>This disables the installation of the various network
    8080          servers included as part of the Inetutils package. These servers are
    81           deemed not appropriate in a basic LFS system. Some are insecure by
     81          deemed not appropriate in a basic CLFS system. Some are insecure by
    8282          nature and are only considered safe on trusted networks. More
    8383          information can be found at <ulink
  • final-system/common/iproute2.xml

    r9fcb5e4 rb71fa50  
    4949          <filename class="directory">/sbin</filename>. This is the correct
    5050          location according to the FHS, because some of the IPRoute2 binaries
    51           are used by the LFS-Bootscripts package.</para>
     51          are used by the CLFS-Bootscripts package.</para>
    5252        </listitem>
    5353      </varlistentry>
  • final-system/common/kbd.xml

    r9fcb5e4 rb71fa50  
    296296        <listitem>
    297297          <para>Puts the keyboard and console in UNICODE mode. Never use it on
    298           LFS, because applications are not configured to support UNICODE.</para>
     298          CLFS, because applications are not configured to support UNICODE.</para>
    299299          <indexterm zone="ch-system-kbd unicode_start">
    300300            <primary sortas="b-unicode_start">unicode_start</primary>
  • final-system/common/man.xml

    r9fcb5e4 rb71fa50  
    103103    non-ISO 8859-1 locales. Also, it does not work with multibyte
    104104    character sets. The first problem does not currently have a solution.
    105     The second issue is not of concern because the LFS installation does
     105    The second issue is not of concern because the CLFS installation does
    106106    not support multibyte character sets.</para>
    107107
  • final-system/common/psmisc.xml

    r9fcb5e4 rb71fa50  
    4040          <filename class="directory">/usr/bin</filename>. This is the
    4141          correct location according to the FHS, because some of the Psmisc
    42           binaries are used by the LFS-Bootscripts package.</para>
     42          binaries are used by the CLFS-Bootscripts package.</para>
    4343        </listitem>
    4444      </varlistentry>
  • final-system/common/sysvinit.xml

    r9fcb5e4 rb71fa50  
    9898    character set to a user-defined one, which can be modified by running
    9999    the <command>setfont</command> program. The <command>console</command>
    100     initscript from the LFS-Bootscripts package calls the
     100    initscript from the CLFS-Bootscripts package calls the
    101101    <command>setfont</command> program during system startup. Sending this
    102102    escape sequence is necessary for people who use non-ISO 8859-1 screen
  • final-system/common/udev.xml

    r9fcb5e4 rb71fa50  
    177177          <para>Simulates a <command>udev</command> run for the given device,
    178178          and prints out the name of the node the real <command>udev</command>
    179           would have created or (not in LFS) the name of the renamed network
     179          would have created or (not in CLFS) the name of the renamed network
    180180          interface</para>
    181181          <indexterm zone="ch-system-udev udevtest">
  • final-system/common/util-linux.xml

    r9fcb5e4 rb71fa50  
    9191    <para os="g">Install the package and move the <command>logger</command> binary
    9292    to <filename class="directory">/bin</filename> as it is needed by the
    93     LFS-Bootscripts package:</para>
     93    CLFS-Bootscripts package:</para>
    9494
    9595<screen os="h"><userinput>make HAVE_KILL=yes HAVE_SLN=yes install
  • final-system/common/vim.xml

    r9fcb5e4 rb71fa50  
    100100<screen os="o"><userinput>ln -sv ../vim/vim&vim-version2;/doc /usr/share/doc/vim-&vim-version;</userinput></screen>
    101101
    102     <para os="p">If an X Window System is going to be installed on the LFS
     102    <para os="p">If an X Window System is going to be installed on the CLFS
    103103    system, you may want to recompile Vim after installing X. Vim
    104104    comes with a GUI version of the editor that requires X and some
     
    376376          necessary to highlight in <command>vim</command>. This script
    377377          requires the old Unix <command>spell</command> command, which
    378           is provided neither in LFS nor in BLFS</para>
     378          is provided neither in CLFS nor in BLFS</para>
    379379          <indexterm zone="ch-system-vim vimspell.sh">
    380380            <primary sortas="b-vimspell.sh">vimspell.sh</primary>
Note: See TracChangeset for help on using the changeset viewer.