Changeset b71fa50


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'

Files:
60 edited

Legend:

Unmodified
Added
Removed

  • appendices/dependencies/common.xml

    r9fcb5e4 rb71fa50  
    1212  <title>Dependencies</title>
    1313
    14   <para>Every package built in LFS relies on one or more other packages
     14  <para>Every package built in CLFS relies on one or more other packages
    1515  in order to build and install properly. Some packages even participate
    1616  in circular dependencies, that is, the first package depends on the second
    1717  which in turn depends on the first. Because of these dependencies, the
    18   order in which packages are built in LFS is very important. The purpose
    19   of this page is to document the dependencies of each package built in LFS.</para>
     18  order in which packages are built in CLFS is very important. The purpose
     19  of this page is to document the dependencies of each package built in CLFS.</para>
    2020
    2121  <para>For each package we build, we have listed three types of dependencies.
    … …  
    7676          <seg>Binutils, Bison, Bzip2, DejaGNU, Diffutils, Expect, Findutils,
    7777          Flex, GCC, Gettext, Gzip, Libtool and Tar. Can also use several
    78           other packages that are not installed in LFS.</seg>
     78          other packages that are not installed in CLFS.</seg>
    7979        </seglistitem>
    8080      </segmentedlist>

  • boot/common/creatingdirs.xml

    r9fcb5e4 rb71fa50  
    1111  <title>Creating Directories</title>
    1212
    13   <para os="a">It is time to create some structure in the LFS file system. Create a
     13  <para os="a">It is time to create some structure in the CLFS file system. Create a
    1414  standard directory tree by issuing the following commands:</para>
    1515

  • boot/common/introduction.xml

    r9fcb5e4 rb71fa50  
    1717  <para>There are a few additional packages that will need to be
    1818  installed to allow you to boot the minimal system. Some of these
    19   packages will be installed onto the root or in /usr on the LFS
     19  packages will be installed onto the root or in /usr on the CLFS
    2020  partition ($LFS/bin, $LFS/usr/lib, etc...), rather than /tools, using the
    2121  "DESTDIR" option with make. This will require the

  • boot/x86_64-64/lilo.xml

    r9fcb5e4 rb71fa50  
    99  <?dbhtml filename="lilo.html"?>
    1010
    11   <title>Making the LFS System Bootable</title>
     11  <title>Making the CLFS System Bootable</title>
    1212
    1313  <indexterm zone="ch-boot-lilo">

  • bootable/alpha-chapter.xml

    r9fcb5e4 rb71fa50  
    66]>
    77
    8 <chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
     8<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
    99  <?dbhtml dir="bootable"?>
    1010  <?dbhtml filename="chapter.html"?>
    1111
    12   <title>Making the LFS System Bootable</title>
     12  <title>Making the CLFS System Bootable</title>
    1313
    1414  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>

  • bootable/alpha/aboot.xml

    r9fcb5e4 rb71fa50  
    99  <?dbhtml filename="aboot.html"?>
    1010
    11   <title>Making the LFS System Bootable</title>
     11  <title>Making the CLFS System Bootable</title>
    1212
    1313  <indexterm zone="ch-bootable-aboot">

  • bootable/common/introduction.xml

    r9fcb5e4 rb71fa50  
    1111  <title>Introduction</title>
    1212
    13   <para>It is time to make the LFS system bootable. This chapter
     13  <para>It is time to make the CLFS system bootable. This chapter
    1414  discusses creating an <filename>fstab</filename> file, building a
    15   kernel for the new LFS system, and installing the boot loader so
    16   that the LFS system can be selected for booting at startup.</para>
     15  kernel for the new CLFS system, and installing the boot loader so
     16  that the CLFS system can be selected for booting at startup.</para>
    1717
    1818</sect1>

  • bootable/mips-chapter.xml

    r9fcb5e4 rb71fa50  
    66]>
    77
    8 <chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
     8<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
    99  <?dbhtml dir="bootable"?>
    1010  <?dbhtml filename="chapter.html"?>
    1111
    12   <title>Making the LFS System Bootable</title>
     12  <title>Making the CLFS System Bootable</title>
    1313
    1414  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>

  • bootable/mips/arcload.xml

    r9fcb5e4 rb71fa50  
    99  <?dbhtml filename="arcload.html"?>
    1010
    11   <title>Making the LFS System Bootable via Arcload</title>
     11  <title>Making the CLFS System Bootable via Arcload</title>
    1212
    1313  <indexterm zone="ch-bootable-arcload">

  • bootable/mips/colo.xml

    r9fcb5e4 rb71fa50  
    99  <?dbhtml filename="colo.html"?>
    1010
    11   <title>Making the LFS System Bootable via Colo</title>
     11  <title>Making the CLFS System Bootable via Colo</title>
    1212
    1313  <indexterm zone="ch-bootable-colo">
    … …  
    2121  </note>
    2222
    23   <para os="c">Your shiny new LFS system is almost complete. One of the last
     23  <para os="c">Your shiny new CLFS system is almost complete. One of the last
    2424  things to do is ensure you can boot it. The instructions below apply
    2525  only to Cobalt RaQ1/RaQ2/Cube2 servers. Information on <quote>boot

  • bootable/mips64-chapter.xml

    r9fcb5e4 rb71fa50  
    66]>
    77
    8 <chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
     8<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
    99  <?dbhtml dir="bootable"?>
    1010  <?dbhtml filename="chapter.html"?>
    1111
    12   <title>Making the LFS System Bootable</title>
     12  <title>Making the CLFS System Bootable</title>
    1313
    1414  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>

  • bootable/mips64/arcload.xml

    r9fcb5e4 rb71fa50  
    99  <?dbhtml filename="arcload.html"?>
    1010
    11   <title>Making the LFS System Bootable via Arcload</title>
     11  <title>Making the CLFS System Bootable via Arcload</title>
    1212
    1313  <indexterm zone="ch-bootable-arcload">

  • bootable/ppc-chapter.xml

    r9fcb5e4 rb71fa50  
    66]>
    77
    8 <chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
     8<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
    99  <?dbhtml dir="bootable"?>
    1010  <?dbhtml filename="chapter.html"?>
    1111
    12   <title>Making the LFS System Bootable</title>
     12  <title>Making the CLFS System Bootable</title>
    1313
    1414  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>

  • bootable/ppc/yaboot.xml

    r9fcb5e4 rb71fa50  
    99  <?dbhtml filename="yaboot.html"?>
    1010
    11   <title>Making the LFS System Bootable</title>
     11  <title>Making the CLFS System Bootable</title>
    1212
    1313  <indexterm zone="ch-bootable-yaboot">
    … …  
    1515  <secondary>configuring</secondary></indexterm>
    1616
    17   <para os="a">Your shiny new LFS system is almost complete. One of the last
     17  <para os="a">Your shiny new CLFS system is almost complete. One of the last
    1818  things to do is to ensure that the system can be properly booted. The
    1919  instructions below apply only to NewWorld Macintoshes.</para>
    … …  
    107107fgcolor=light-green
    108108
    109 # The first entry is for LFS.
     109# The first entry is for CLFS.
    110110# For all images, the pathname is relative to the filesystem
    111111# on which they are situated and can include at most one

  • bootable/ppc64-chapter.xml

    r9fcb5e4 rb71fa50  
    66]>
    77
    8 <chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
     8<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
    99  <?dbhtml dir="bootable"?>
    1010  <?dbhtml filename="chapter.html"?>
    1111
    12   <title>Making the LFS System Bootable</title>
     12  <title>Making the CLFS System Bootable</title>
    1313
    1414  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>

  • bootable/sparc-chapter.xml

    r9fcb5e4 rb71fa50  
    66]>
    77
    8 <chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
     8<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
    99  <?dbhtml dir="bootable"?>
    1010  <?dbhtml filename="chapter.html"?>
    1111
    12   <title>Making the LFS System Bootable</title>
     12  <title>Making the CLFS System Bootable</title>
    1313
    1414  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>

  • bootable/sparc/silo.xml

    r9fcb5e4 rb71fa50  
    99  <?dbhtml filename="silo.html"?>
    1010
    11   <title>Making the LFS System Bootable</title>
     11  <title>Making the CLFS System Bootable</title>
    1212
    1313  <indexterm zone="ch-bootable-silo">

  • bootable/x86-chapter.xml

    r9fcb5e4 rb71fa50  
    66]>
    77
    8 <chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
     8<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
    99  <?dbhtml dir="bootable"?>
    1010  <?dbhtml filename="chapter.html"?>
    1111
    12   <title>Making the LFS System Bootable</title>
     12  <title>Making the CLFS System Bootable</title>
    1313
    1414  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>

  • bootable/x86/grub.xml

    r9fcb5e4 rb71fa50  
    99  <?dbhtml filename="grub.html"?>
    1010
    11   <title>Making the LFS System Bootable</title>
     11  <title>Making the CLFS System Bootable</title>
    1212
    1313  <indexterm zone="ch-bootable-grub">
    … …  
    1616  </indexterm>
    1717
    18   <para os="a">Your shiny new LFS system is almost complete. One of the last
     18  <para os="a">Your shiny new CLFS system is almost complete. One of the last
    1919  things to do is to ensure that the system can be properly booted. The
    2020  instructions below apply only to computers of IA-32 architecture,
    … …  
    7171    a third party boot manager to manage the Master Boot Record (MBR).
    7272    In this scenario, it would make more sense to install GRUB into the
    73     <quote>boot sector</quote> of the LFS partition. In this case, this
     73    <quote>boot sector</quote> of the CLFS partition. In this case, this
    7474    next command would become <userinput>setup (hd0,3)</userinput>.</para>
    7575  </warning>
    … …  
    101101color green/black light-green/black
    102102
    103 # The first entry is for LFS.
    104 title LFS &version;
     103# The first entry is for CLFS.
     104title CLFS &version;
    105105root (hd0,3)
    106106kernel /boot/lfskernel-&linux-version; root=/dev/hda4</literal>

  • bootable/x86/kernel.xml

    r9fcb5e4 rb71fa50  
    5151    enabled and built into the kernel, not as modules. BLFS has
    5252    some information regarding particular kernel configuration requirements of
    53     packages outside of LFS at <ulink
     53    packages outside of CLFS at <ulink
    5454    url="&blfs-root;view/svn/longindex.html#kernel-config-index"/>:</para>
    5555
    … …  
    144144      <filename class="symlink">/usr/src/linux</filename> pointing to the
    145145      kernel source directory. This is specific to kernels prior to the
    146       2.6 series and <emphasis>must not</emphasis> be created on an LFS
     146      2.6 series and <emphasis>must not</emphasis> be created on a CLFS
    147147      system as it can cause problems for packages you may wish to build
    148       once your base LFS system is complete.</para>
     148      once your base CLFS system is complete.</para>
    149149
    150150      <para>Also, the headers in the system's <filename

  • bootable/x86_64-64-chapter.xml

    r9fcb5e4 rb71fa50  
    66]>
    77
    8 <chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
     8<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
    99  <?dbhtml dir="bootable"?>
    1010  <?dbhtml filename="chapter.html"?>
    1111
    12   <title>Making the LFS System Bootable</title>
     12  <title>Making the CLFS System Bootable</title>
    1313
    1414  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>

  • bootable/x86_64-64/lilo.xml

    r9fcb5e4 rb71fa50  
    99  <?dbhtml filename="lilo.html"?>
    1010
    11   <title>Making the LFS System Bootable</title>
     11  <title>Making the CLFS System Bootable</title>
    1212
    1313  <indexterm zone="ch-bootable-lilo">
    … …  
    1616  </indexterm>
    1717
    18     <para os="a">Your shiny new LFS system is almost complete. One of the
     18    <para os="a">Your shiny new CLFS system is almost complete. One of the
    1919      last things to do is to ensure that the system can be properly
    2020      booted. The instructions below apply only to computers using lilo,

  • bootable/x86_64-chapter.xml

    r9fcb5e4 rb71fa50  
    66]>
    77
    8 <chapter id="chapter-bootable" xreflabel="Making the LFS System Bootable">
     8<chapter id="chapter-bootable" xreflabel="Making the CLFS System Bootable">
    99  <?dbhtml dir="bootable"?>
    1010  <?dbhtml filename="chapter.html"?>
    1111
    12   <title>Making the LFS System Bootable</title>
     12  <title>Making the CLFS System Bootable</title>
    1313
    1414  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="common/introduction.xml"/>

  • bootscripts/common/console.xml

    r9fcb5e4 rb71fa50  
    2727  url="http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>. A pre-made
    2828  <filename>/etc/sysconfig/console</filename> file with known settings for
    29   several countries was installed with the LFS-Bootscripts package, so the
     29  several countries was installed with the CLFS-Bootscripts package, so the
    3030  relevant section can be uncommented if the country is supported. If still
    3131  in doubt, look in the <filename class="directory">/usr/share/kbd</filename>

  • bootscripts/common/introduction.xml

    r9fcb5e4 rb71fa50  
    1111  <title>Introduction</title>
    1212
    13   <para>This chapter details how to install and configure the LFS-Bootscripts
     13  <para>This chapter details how to install and configure the CLFS-Bootscripts
    1414  package. Most of these scripts will work without modification, but a few
    1515  require additional configuration files because they deal with

  • bootscripts/common/network.xml

    r9fcb5e4 rb71fa50  
    5858
    5959    <para>The <envar>SERVICE</envar> variable defines the method used for
    60     obtaining the IP address. The LFS-Bootscripts package has a modular IP
     60    obtaining the IP address. The CLFS-Bootscripts package has a modular IP
    6161    assignment format, and creating additional files in the <filename
    6262    class="directory">/etc/sysconfig/network-devices/services</filename>

  • bootscripts/common/profile.xml

    r9fcb5e4 rb71fa50  
    119119  from Glibc.</para>
    120120
    121   <para>Some packages beyond LFS may also lack support for your chosen locale.
     121  <para>Some packages beyond CLFS may also lack support for your chosen locale.
    122122  One example is the X library (part of the X Window System), which outputs
    123123  the following error message:</para>
    … …  
    161161  require additional steps and additional patches because many applications
    162162  tend to not work properly under such conditions. These steps and patches
    163   are not included in the LFS book and such locales are not yet supported
    164   by LFS.</para>
     163  are not included in the CLFS book and such locales are not yet supported
     164  by CLFS.</para>
    165165
    166166</sect1>

  • bootscripts/common/udev.xml

    r9fcb5e4 rb71fa50  
    99  <?dbhtml filename="udev.html"?>
    1010
    11   <title>Device and Module Handling on an LFS System</title>
     11  <title>Device and Module Handling on a CLFS System</title>
    1212
    1313  <indexterm zone="ch-scripts-udev">
    … …  
    9999    the rules specified in the files within the <filename
    100100    class="directory">/etc/udev/rules.d/</filename> directory. These are
    101     numbered in a similar fashion to the LFS-Bootscripts package. If
     101    numbered in a similar fashion to the CLFS-Bootscripts package. If
    102102    <command>udev</command> can't find a rule for the device it is creating,
    103103    it will default permissions to <emphasis>660</emphasis> and ownership to
    … …  
    129129    this method will not work because the device node does not exist until
    130130    the module is loaded. To solve this, the <command>S05modules</command>
    131     bootscript was added to the LFS-Bootscripts package, along with the
     131    bootscript was added to the CLFS-Bootscripts package, along with the
    132132    <filename>/etc/sysconfig/modules</filename> file. By adding module
    133133    names to the <filename>modules</filename> file, these modules will be

  • bootscripts/common/usage.xml

    r9fcb5e4 rb71fa50  
    1919  different from one system to another, so it cannot be assumed that
    2020  because things worked in one particular Linux distribution, they should work
    21   the same in LFS too. LFS has its own way of doing things, but it
     21  the same in CLFS too. CLFS has its own way of doing things, but it
    2222  respects generally accepted standards.</para>
    2323
    … …  
    124124
    125125  <para>Feel free to modify the way the boot process works (after all,
    126   it is your own LFS system). The files given here are an example of how
     126  it is your own CLFS system). The files given here are an example of how
    127127  it can be done.</para>
    128128

  • bootscripts/mips/bootscripts.xml

    r9fcb5e4 rb71fa50  
    99  <?dbhtml filename="bootscripts.html"?>
    1010
    11   <title>LFS-Bootscripts-&lfs-bootscripts-version;</title>
     11  <title>CLFS-Bootscripts-&lfs-bootscripts-version;</title>
    1212
    1313  <indexterm zone="ch-scripts-bootscripts">
    … …  
    2020
    2121  <sect2 role="installation">
    22     <title>Installation of LFS-Bootscripts</title>
     22    <title>Installation of CLFS-Bootscripts</title>
    2323
    2424    <para>Need to update the current bootscripts to handle LCD

  • 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>

  • final-preps/creatingtoolsdir.xml

    r9fcb5e4 rb71fa50  
    2828  <para>The next step is to create a <filename class="symlink">/tools</filename>
    2929  symlink on the host system. This will point to the newly-created directory
    30   on the LFS partition. Run this command as <systemitem
     30  on the CLFS partition. Run this command as <systemitem
    3131  class="username">root</systemitem> as well:</para>
    3232

  • 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>

  • final-system/multilib/glibc-64bit.xml

    r9fcb5e4 rb71fa50  
    124124      </listitem>
    125125      <listitem>
    126         <para>If you have mounted the LFS partition with the
     126        <para>If you have mounted the CLFS partition with the
    127127        <parameter>noatime</parameter> option, the <emphasis>atime</emphasis> test
    128128        will fail. As mentioned in <xref linkend="ch-partitioning-mounting"/>,
    129129        do not use the <parameter>noatime</parameter> option while building
    130         LFS.</para>
     130        CLFS.</para>
    131131      </listitem>
    132132      <listitem>

  • final-system/ppc64/glibc-64bit.xml

    r9fcb5e4 rb71fa50  
    135135      </listitem>
    136136      <listitem>
    137         <para>If you have mounted the LFS partition with the
     137        <para>If you have mounted the CLFS partition with the
    138138        <parameter>noatime</parameter> option, the <emphasis>atime</emphasis> test
    139139        will fail. As mentioned in <xref linkend="ch-partitioning-mounting"/>,
    140140        do not use the <parameter>noatime</parameter> option while building
    141         LFS.</para>
     141        CLFS.</para>
    142142      </listitem>
    143143      <listitem>

  • introduction/common/askforhelp.xml

    r9fcb5e4 rb71fa50  
    4444      <listitem>
    4545        <para>The host distribution and version being used to
    46         create LFS</para>
     46        create CLFS</para>
    4747      </listitem>
    4848      <listitem>

  • introduction/common/changelog.xml

    r9fcb5e4 rb71fa50  
    3737-->
    3838
     39    <listitem>
     40      <para>June 21, 2006</para>
     41      <itemizedlist>
     42        <listitem>
     43          <para>[Chris] - Text updates to the book, including replacing
     44          "LFS" with "CLFS".</para>
     45        </listitem>
     46      </itemizedlist>
     47    </listitem>
    3948
    4049    <listitem>

  • introduction/common/resources.xml

    r9fcb5e4 rb71fa50  
    1414    <title>FAQ</title>
    1515
    16     <para>If during the building of the LFS system you encounter any
     16    <para>If during the building of the CLFS system you encounter any
    1717    errors, have any questions, or think there is a typo in the book,
    1818    please start by consulting the Frequently Asked Questions (FAQ)

  • materials/common/patches.xml

    r9fcb5e4 rb71fa50  
    1515  fixed by the maintainer. The patches also make small modifications to
    1616  make the packages easier to work with. The following patches will be
    17   needed to build an LFS system:</para>
     17  needed to build an CLFS system:</para>
    1818
    1919  <variablelist role="materials">
    … …  
    299299
    300300  <para>In addition to the above required patches, there exist a number of
    301   optional patches created by the LFS community. These optional patches
     301  optional patches created by the CLFS community. These optional patches
    302302  solve minor problems or enable functionality that is not enabled by
    303303  default. Feel free to peruse the patches database located at

  • partitioning/common/creatingfilesystem.xml

    r9fcb5e4 rb71fa50  
    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

  • partitioning/common/creatingpartition.xml

    r9fcb5e4 rb71fa50  
    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

  • partitioning/common/mounting.xml

    r9fcb5e4 rb71fa50  
    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>

  • prologue/common/errata.xml

    r9fcb5e4 rb71fa50  
    1313  <para>The software used to create a CLFS system is constantly being
    1414  updated and enhanced. Security warnings and bug fixes may become
    15   available after the LFS book has been released. To check whether the
    16   package versions or instructions in this release of CLFS need any
    17   modifications to accommodate security vulnerabilities or other bug fixes,
    18   please visit <ulink url="&errata;"/> before proceeding with your build.
    19   You should note any changes shown and apply them to the relevant section
    20   of the book as you progress with building the LFS system.</para>
     15  available after the CLFS book has been released. Some host systems may
     16  also have problems building CLFS. To check whether the package versions
     17  or instructions in this release of CLFS need any modifications to
     18  accommodate security vulnerabilities, other bug fixes, or host-specific
     19  issues, please visit <ulink url="&errata;"/> before proceeding with your
     20  build. You should note any changes shown and apply them to the relevant
     21  section of the book as you progress with building the CLFS system.</para>
    2122
    2223</sect1>

  • prologue/common/prerequisites.xml

    r9fcb5e4 rb71fa50  
    2323
    2424  <para>Because the CLFS book assumes <emphasis>at least</emphasis> this basic
    25   level of skill, the various LFS support forums are unlikely to be able to
     25  level of skill, the various CLFS support forums are unlikely to be able to
    2626  provide you with much assistance; you will find that your questions regarding
    2727  such basic knowledge will likely go unanswered, or you will simply be referred

  • prologue/common/typography.xml

    r9fcb5e4 rb71fa50  
    1313  <para>To make things easier to follow, there are a few typographical
    1414  conventions used throughout this book. This section contains some
    15   examples of the typographical format found throughout Linux From
    16   Scratch.</para>
     15  examples of the typographical format found throughout Cross-Compiled
     16  Linux From Scratch.</para>
    1717
    1818<screen role="nodump"><userinput>./configure --prefix=/usr</userinput></screen>
    … …  
    3636  <para><ulink url="&lfs-root;"/></para>
    3737
    38   <para>This format is used for hyperlinks, both within the LFS
     38  <para>This format is used for hyperlinks, both within the CLFS
    3939  community and to external pages. It includes HOWTOs, download locations,
    4040  and websites.</para>
    … …  
    6262  referred to simply as a <quote>man</quote> page). The number inside
    6363  parentheses indicates a specific section inside of <command>man</command>.
    64   For example, <command>passwd</command> has two man pages. Per LFS
     64  For example, <command>passwd</command> has two man pages. Per CLFS
    6565  installation instructions, those two man pages will be located at
    6666  <filename>/usr/share/man/man1/passwd.1</filename> and

  • the-end/reboot.xml

    r9fcb5e4 rb71fa50  
    2121  book while still in our current chroot environment, you can leave
    2222  yourself in a much better position to continue on once you reboot
    23   into your new LFS installation. Installing a text mode web browser,
     23  into your new CLFS installation. Installing a text mode web browser,
    2424  such as Lynx, you can easily view the BLFS book in one virtual terminal,
    2525  while building packages in another. The GPM package will also allow you
    … …  
    3030
    3131  <para>Now that we have said that, lets move on to booting our shiny
    32   new LFS installation for the first time! First exit from the chroot
     32  new CLFS installation for the first time! First exit from the chroot
    3333  environment:</para>
    3434
    … …  
    4343umount $LFS/sys</userinput></screen>
    4444
    45   <para>Unmount the LFS file system itself:</para>
     45  <para>Unmount the CLFS file system itself:</para>
    4646
    4747<screen><userinput>umount $LFS</userinput></screen>
    … …  
    6161  <emphasis>CLFS &version;</emphasis> will boot automatically.</para>
    6262
    63   <para>When the reboot is complete, the LFS system is ready for use and
     63  <para>When the reboot is complete, the CLFS system is ready for use and
    6464  more software may be added to suit your needs.</para>
    6565

  • the-end/whatnow.xml

    r9fcb5e4 rb71fa50  
    1111  <title>What Now?</title>
    1212
    13   <para>Thank you for reading this LFS book. We hope that you have
     13  <para>Thank you for reading this CLFS book. We hope that you have
    1414  found this book helpful and have learned more about the system
    1515  creation process.</para>
    1616
    17   <para>Now that the LFS system is installed, you may be wondering
     17  <para>Now that the CLFS system is installed, you may be wondering
    1818  <quote>What next?</quote> To answer that question, we have compiled
    1919  a list of resources for you.</para>
    … …  
    2525
    2626      <para>Bugs and security notices are reported regularly for all software.
    27       Since an LFS system is compiled from source, it is up to you to keep
     27      Since a CLFS system is compiled from source, it is up to you to keep
    2828      abreast of such reports.  There are several online resources that track
    2929      such reports, some of which are shown below:</para>
    … …  
    6565
    6666      <para>The Beyond Linux From Scratch book covers installation
    67       procedures for a wide range of software beyond the scope of the LFS
     67      procedures for a wide range of software beyond the scope of the CLFS
    6868      Book. The BLFS project is located at <ulink url="&blfs-root;"/>.</para>
    6969    </listitem>
Note: See TracChangeset for help on using the changeset viewer.