Changeset fb40919 for BOOK/bootscripts


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/bootscripts
Files:
7 edited

Legend:

Unmodified
Added
Removed

  • BOOK/bootscripts/common/console.xml

    r0de816f8 rfb40919  
    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>

  • BOOK/bootscripts/common/introduction.xml

    r0de816f8 rfb40919  
    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

  • BOOK/bootscripts/common/network.xml

    r0de816f8 rfb40919  
    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>

  • BOOK/bootscripts/common/profile.xml

    r0de816f8 rfb40919  
    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>

  • BOOK/bootscripts/common/udev.xml

    r0de816f8 rfb40919  
    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

  • BOOK/bootscripts/common/usage.xml

    r0de816f8 rfb40919  
    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

  • BOOK/bootscripts/mips/bootscripts.xml

    r0de816f8 rfb40919  
    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
Note: See TracChangeset for help on using the changeset viewer.