Changeset 2e9d6f5


Ignore:
Timestamp:
May 16, 2006, 1:14:42 PM (13 years ago)
Author:
Jim Gifford <clfs@…>
Children:
8ca6da6
Parents:
627926a
Message:

r3547@server (orig r1619): chris | 2006-05-16 11:37:05 -0700
Changed a number of occurences of LFS to CLFS

Files:
5 edited

Legend:

Unmodified
Added
Removed
  • general.ent

    r627926a r2e9d6f5  
    11<?xml version="1.0" encoding="ISO-8859-1"?>
    22
    3 <!ENTITY version "CLFS-SVN-20060516">
     3<!ENTITY version "SVN-20060516">
    44<!ENTITY version-x86 "&version;-x86">
    55<!ENTITY version-x86_64 "&version;-x86_64-Multilib">
     
    2121
    2222<!ENTITY lfs-root "http://www.linuxfromscratch.org/">
     23<!ENTITY clfs-root "http:/trac.cross-lfs.org/">
    2324<!ENTITY blfs-root "&lfs-root;blfs/">
    2425<!ENTITY faq-root "&lfs-root;faq/">
     
    2627<!ENTITY hints-index "&lfs-root;hints/list.html">
    2728<!ENTITY livecd-root "&lfs-root;livecd/">
    28 <!ENTITY test-results "&lfs-root;clfs/build-logs/&generic-version;/">
    29 <!ENTITY errata "&lfs-root;clfs/errata/&generic-version;/">
     29<!ENTITY test-results "&clfs-root;clfs/build-logs/&generic-version;/">
     30<!ENTITY errata "&clfs-root;clfs/errata/&generic-version;/">
    3031
    3132<!ENTITY gnu "http://ftp.gnu.org/gnu/">
  • introduction/common/how.xml

    r627926a r2e9d6f5  
    99  <?dbhtml filename="how.html"?>
    1010
    11   <title>How to Build an LFS System</title>
     11  <title>How to Build a CLFS System</title>
    1212
    13   <para>The LFS system will be built by using a previously installed
     13  <para>The CLFS system will be built by using a previously installed
    1414  Linux distribution (such as Debian, Mandrake, Red Hat, or SuSE). This
    1515  existing Linux system (the host) will be used as a starting point to
     
    3333  <para><xref linkend="chapter-partitioning"/> of this book describes how
    3434  to create a new Linux native partition and file system, the place
    35   where the new LFS system will be compiled and installed. <xref
     35  where the new CLFS system will be compiled and installed. <xref
    3636  linkend="chapter-getting-materials"/> explains which packages and
    37   patches need to be downloaded to build an LFS system and how to store
     37  patches need to be downloaded to build a CLFS system and how to store
    3838  them on the new file system. <xref linkend="chapter-final-preps"/>
    3939  discusses the setup for an appropriate working environment. Please read
     
    4747  programs that run on the target machine. These cross-compile tools will
    4848  be used to create a temporary, minimal system that will be the basis for
    49   building the final LFS system. Some of these packages are needed to resolve
     49  building the final CLFS system. Some of these packages are needed to resolve
    5050  circular dependencies&mdash;for example, to compile a compiler, you need a
    5151  compiler.</para>
     
    7171  beginning of <xref linkend="chapter-temp-system"/>.</para>
    7272
    73   <para>In <xref linkend="chapter-building-system"/>, the full LFS system is
     73  <para>In <xref linkend="chapter-building-system"/>, the full CLFS system is
    7474  built. Depending on the system you are cross-compiling for, either you will
    7575  boot the minimal temp-system on the target machine, or chroot into it.</para>
     
    7777  <para>The <command>chroot</command> (change root) program is used to enter
    7878  a virtual environment and start a new shell whose root directory will be set
    79   to the LFS partition. This is very similar to rebooting and instructing the
    80   kernel to mount the LFS partition as the root partition.
     79  to the CLFS partition. This is very similar to rebooting and instructing the
     80  kernel to mount the CLFS partition as the root partition.
    8181  The major advantage is that <quote>chrooting</quote> allows the builder to
    82   continue using the host while LFS is being built. While waiting for package
     82  continue using the host while CLFS is being built. While waiting for package
    8383  compilation to complete, a user can switch to a different virtual console
    8484  (VC) or X desktop and continue using the computer as normal.</para>
    8585
    86   <para>Some systems cannot be built by chrooting so they must be booted instead. Generally, if you building for a different arch than the host system, you must reboot because the kernel will likely not support the target machine. Booting involves installing a few additional packages that are needed for bootup, installing bootscripts, and building a miminal kernel.</para>
     86  <para>Some systems cannot be built by chrooting so they must be
     87  booted instead. Generally, if you building for a different arch than
     88  the host system, you must reboot because the kernel will likely not
     89  support the target machine. Booting involves installing a few
     90  additional packages that are needed for bootup, installing
     91  bootscripts, and building a miminal kernel.</para>
    8792
    88   <para>To finish the installation, the LFS-Bootscripts are set up in <xref
     93  <para>To finish the installation, the CLFS-Bootscripts are set up in <xref
    8994  linkend="chapter-bootscripts"/>, and the kernel and boot loader are set
    9095  up in <xref linkend="chapter-bootable"/>. <xref
    9196  linkend="chapter-finalizing"/> contains information on furthering the
    92   LFS experience beyond this book.  After the steps in this book have
     97  CLFS experience beyond this book.  After the steps in this book have
    9398  been implemented, the computer will be ready to reboot into the new
    94   LFS system.</para>
     99  CLFS system.</para>
    95100  <!-- -->
    96101
     
    98103  step is discussed in the following chapters and package descriptions.
    99104  Items that may seem complicated will be clarified, and everything will
    100   fall into place as the reader embarks on the LFS adventure.</para>
     105  fall into place as the reader embarks on the CLFS adventure.</para>
    101106
    102107</sect1>
  • introduction/common/resources.xml

    r627926a r2e9d6f5  
    3232    <para>For information on the different lists, how to subscribe, archive
    3333    locations, and additional information, visit
    34     <ulink url="&lfs-root;mail.html"/>.</para>
     34    <ulink url="&lfs-root;mail.html"/>. For mailing lists specifically
     35    for CLFS, visit <ulink url="&clfs-root;wiki/lists"/>.</para>
    3536
    3637  </sect2>
  • prologue/common/errata.xml

    r627926a r2e9d6f5  
    1111  <title>Errata</title>
    1212
    13   <para>The software used to create an LFS system is constantly being
     13  <para>The software used to create a CLFS system is constantly being
    1414  updated and enhanced. Security warnings and bug fixes may become
    1515  available after the LFS book has been released. To check whether the
    16   package versions or instructions in this release of LFS need any
     16  package versions or instructions in this release of CLFS need any
    1717  modifications to accommodate security vulnerabilities or other bug fixes,
    1818  please visit <ulink url="&errata;"/> before proceeding with your build.
  • prologue/common/organization.xml

    r627926a r2e9d6f5  
    4949
    5050  <sect2>
    51     <title>Part V - Building the LFS System</title>
     51    <title>Part V - Building the CLFS System</title>
    5252
    53     <para>Part V guides the reader through the building of the LFS
     53    <para>Part V guides the reader through the building of the CLFS
    5454    system&mdash;compiling and installing all the packages one by one,
    5555    setting up the boot scripts, and installing the kernel. The resulting
     
    6767    anywhere else in the book. Appendix A contains definitions of acronyms and
    6868    terms used in the book, Appendix B has Acknowledgments of people who
    69     have helped work on the LFS project and website, and Appendices C
     69    have helped work on the CLFS project and website, and Appendices C
    7070    and D have information about package dependencies and the the
    7171    build order.</para>
Note: See TracChangeset for help on using the changeset viewer.