Changeset 755f44a in clfs-sysroot


Ignore:
Timestamp:
Jul 9, 2006, 12:29:55 PM (13 years ago)
Author:
Joe Ciccone <jciccone@…>
Branches:
master
Children:
47c828c
Parents:
83be687
Message:

LFS to CLFS changes.

Location:
BOOK
Files:
25 edited

Legend:

Unmodified
Added
Removed
  • BOOK/appendices/dependencies/common.xml

    r83be687 r755f44a  
    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
     18  order in which packages are built in CLFS is very important. The purpose
    1919  of this page is to document the dependencies of each package built in LFS.</para>
    2020
  • BOOK/bootable/arm-chapter.xml

    r83be687 r755f44a  
    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"/>
  • BOOK/bootable/arm/kernel.xml

    r83be687 r755f44a  
    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
     
    128128      2.6 series and <emphasis>must not</emphasis> be created on an LFS
    129129      system as it can cause problems for packages you may wish to build
    130       once your base LFS system is complete.</para>
     130      once your base CLFS system is complete.</para>
    131131
    132132      <para>Also, the headers in the system's <filename
  • BOOK/bootable/common/introduction.xml

    r83be687 r755f44a  
    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>
  • BOOK/bootscripts/common/introduction.xml

    r83be687 r755f44a  
    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/profile.xml

    r83be687 r755f44a  
    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/setclock.xml

    r83be687 r755f44a  
    5050EOF</userinput></screen>
    5151
    52   <para os="e">A good hint explaining how to deal with time on LFS is available
     52  <para os="e">A good hint explaining how to deal with time on CLFS is available
    5353  at <ulink url="&hints-root;time.txt"/>. It explains issues such as
    5454  time zones, UTC, and the <envar>TZ</envar> environment variable.</para>
  • BOOK/bootscripts/common/udev.xml

    r83be687 r755f44a  
    99  <?dbhtml filename="udev.html"?>
    1010
    11   <title>Device and Module Handling on an LFS System</title>
     11  <title>Device and Module Handling on an CLFS System</title>
    1212
    1313  <indexterm zone="ch-scripts-udev">
  • BOOK/bootscripts/common/usage.xml

    r83be687 r755f44a  
    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/cross-tools/common/glibc.xml

    r83be687 r755f44a  
    231231    supported by some applications that are in the LFS and BLFS books. Because
    232232    of the various problems that arise due to application programmers making
    233     assumptions that break in such locales, LFS should not be used in locales
     233    assumptions that break in such locales, CLFS should not be used in locales
    234234    that utilize multibyte character sets (including UTF-8) or right-to-left
    235235    writing order.  Numerous unofficial and unstable patches are required to
    236     fix these problems, and it has been decided by the LFS developers not to
     236    fix these problems, and it has been decided by the CLFS developers not to
    237237    support such complex locales at this time. This applies to the ja_JP and
    238238    fa_IR locales as well&mdash;they have been installed only for GCC and
  • BOOK/final-preps/creatingdirs.xml

    r83be687 r755f44a  
    1111  <title>Creating Directories</title>
    1212
    13   <para>It is time to create some structure in the LFS file system. Create a
     13  <para>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
  • BOOK/final-preps/settingenviron.xml

    r83be687 r755f44a  
    4545LC_ALL=POSIX
    4646PATH=${CLFS}/cross-tools/bin:/bin:/usr/bin
    47 export LFS LC_ALL PATH</literal>
     47export CLFS LC_ALL PATH</literal>
    4848EOF</userinput></screen>
    4949
  • BOOK/final-system/common/e2fsprogs.xml

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

    r83be687 r755f44a  
    8686          <para>This disables the installation of the various network
    8787          servers included as part of the Inetutils package. These servers are
    88           deemed not appropriate in a basic LFS system. Some are insecure by
     88          deemed not appropriate in a basic CLFS system. Some are insecure by
    8989          nature and are only considered safe on trusted networks. More
    9090          information can be found at <ulink
  • BOOK/final-system/common/man.xml

    r83be687 r755f44a  
    113113    non-ISO 8859-1 locales. Also, it does not work with multibyte
    114114    character sets. The first problem does not currently have a solution.
    115     The second issue is not of concern because the LFS installation does
     115    The second issue is not of concern because the CLFS installation does
    116116    not support multibyte character sets.</para>
    117117
  • BOOK/final-system/common/pkgmgt.xml

    r83be687 r755f44a  
    222222      Standard Base Specification</ulink>), pkg-utils, Debian's apt, and
    223223      Gentoo's Portage system.  A hint describing how to adopt this style of
    224       package management for LFS systems is located at <ulink
     224      package management for CLFS systems is located at <ulink
    225225      url="&hints-root;/fakeroot.txt"/>.</para>
    226226
  • BOOK/final-system/common/vim.xml

    r83be687 r755f44a  
    381381          necessary to highlight in <command>vim</command>. This script
    382382          requires the old Unix <command>spell</command> command, which
    383           is provided neither in LFS nor in BLFS</para>
     383          is provided neither in CLFS nor in BLFS</para>
    384384          <indexterm zone="ch-system-vim vimspell.sh">
    385385            <primary sortas="b-vimspell.sh">vimspell.sh</primary>
  • BOOK/introduction/common/askforhelp.xml

    r83be687 r755f44a  
    2121  lists at <ulink url="&lfs-root;search.html"/>.</para>
    2222
    23   <para>We also have a wonderful LFS community that is willing to offer
     23  <para>We also have a wonderful CLFS community that is willing to offer
    2424  assistance through the mailing lists and IRC (see the <xref
    2525  linkend="ch-intro-resources"/> section of this book). However, we
     
    5959    <note>
    6060      <para>Deviating from this book does <emphasis>not</emphasis>
    61       mean that we will not help you. After all, the LFS project is
     61      mean that we will not help you. After all, the CLFS project is
    6262      about personal preference. Being upfront about any changes to
    6363      the established procedure helps us evaluate and determine
  • BOOK/introduction/common/resources.xml

    r83be687 r755f44a  
    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)
     
    2525
    2626    <para>The <uri>linuxfromscratch.org</uri> server hosts a number of
    27     mailing lists used for the development of the LFS project. These lists
     27    mailing lists used for the development of the CLFS project. These lists
    2828    include the main development and support lists, among others. If the
    2929    FAQ does not solve the problem you are having, the next step would be to
     
    4949    <title>IRC</title>
    5050
    51     <para>Several members of the LFS community offer assistance on our
     51    <para>Several members of the CLFS community offer assistance on our
    5252    community Internet Relay Chat (IRC) network. Before using this support,
    53     please make sure that your question is not already answered in the LFS
     53    please make sure that your question is not already answered in the CLFS
    5454    FAQ or the mailing list archives. You can find the IRC network at
    5555    <uri>chat.freenode.net</uri>. The support channel for cross-lfs
  • BOOK/materials/common/patches.xml

    r83be687 r755f44a  
    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">
  • BOOK/partitioning/common/creatingfilesystem.xml

    r83be687 r755f44a  
    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>
     
    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

    r83be687 r755f44a  
    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

    r83be687 r755f44a  
    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>
  • BOOK/the-end/reboot.xml

    r83be687 r755f44a  
    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 $CLFS/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 $CLFS</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
  • BOOK/the-end/whatnow.xml

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