Changeset 9f08378


Ignore:
Timestamp:
May 17, 2006, 1:20:04 PM (19 years ago)
Author:
Jim Gifford <clfs@…>
Branches:
clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
Children:
13bd751
Parents:
76246b3
Message:

r3564@server (orig r1629): chris | 2006-05-17 13:05:26 -0700
More text updates, mostly to change LFS references to CLFS

Location:
BOOK
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • BOOK/final-system/common/introduction.xml

    r76246b3 r9f08378  
    1212
    1313  <para os="a">In this chapter, we enter the building site and start
    14   constructing the LFS system in earnest. The installation of this
     14  constructing the CLFS system in earnest. The installation of this
    1515  software is straightforward. Although in many cases the installation
    1616  instructions could be made shorter and more generic, we have opted
    … …  
    3535  packages (Binutils, GCC and Glibc). The small potential gains achieved in
    3636  using compiler optimizations are often outweighed by the risks. First-time
    37   builders of LFS are encouraged to build without custom optimizations.
     37  builders of CLFS are encouraged to build without custom optimizations.
    3838  The subsequent system will still run very fast and be stable at the
    3939  same time.</para>
    … …  
    4949  removed.</para>
    5050
    51   <para os="d">Before the installation instructions, each installation page
    52   provides information about the package, including a concise
    53   description of what it contains, approximately how long it will take
    54   to build, how much disk space is required during this building
    55   process, and any other packages needed to successfully build the
    56   package. Following the installation instructions, there is a list of
    57   programs and libraries (along with brief descriptions of these) that
    58   the package installs.</para>
     51  <para os="d">Before the installation instructions, each installation
     52  page provides a concise description of what the package contains.
     53  Following the installation instructions, there is a list of programs
     54  and libraries (along with brief descriptions of these) that the
     55  package installs.</para>
    5956
    6057  <para os="e">To keep track of which package installs particular files, a

  • BOOK/final-system/common/pkgmgt.xml

    r76246b3 r9f08378  
    1111  <title>Package Management</title>
    1212
    13   <para>Package Management is an often requested addition to the LFS Book. A
     13  <para>Package Management is an often-requested addition to the CLFS Book. A
    1414  Package Manager allows tracking the installation of files making it easy to
    1515  remove and upgrade packages. Before you begin to wonder, NO&mdash;this section
    … …  
    2020  issues that may arise when upgrading packages.</para>
    2121
    22   <para>Some reasons why no specific package manager is recommended in LFS or
    23   BLFS include:</para>
     22  <para>Some reasons why no specific package manager is recommended in
     23  CLFS or BLFS include:</para>
    2424
    2525  <itemizedlist>
    … …  
    4444
    4545    <para>A Package Manager makes it easy to upgrade to newer versions when they
    46     are released. Generally the instructions in the LFS and BLFS Book can be
     46    are released. Generally the instructions in the CLFS and BLFS Book can be
    4747    used to upgrade to the newer versions. Here are some points that you should
    4848    be aware of when upgrading packages, especially on a running system.</para>
    … …  
    5151      <listitem>
    5252        <para>If one of the toolchain packages (Glibc, GCC or Binutils) needs
    53         to be upgraded to a newer minor version, it is safer to rebuild LFS.
    54         Though, you <emphasis>may</emphasis> be able to get by rebuilding all
    55         the packages in their dependency order, we do not recommend it. For
    56         example, if glibc-2.2.x needs to be updated to glibc-2.3.x, it is safer
    57         to rebuild. For micro version updates, a simple reinstallation usually
    58         works, but is not guaranteed. For example, upgrading from glibc-2.3.4
    59         to glibc-2.3.5 will not usually cause any problems.</para>
     53        to be upgraded to a newer minor version, it is safer to
     54        rebuild CLFS. Though you <emphasis>may</emphasis> be able to get by
     55        rebuilding all the packages in their dependency order, we do not
     56        recommend it. For example, if glibc-2.2.x needs to be updated to
     57        glibc-2.3.x, it is safer to rebuild. For micro version updates, a
     58        simple reinstallation usually works, but is not guaranteed. For
     59        example, upgrading from glibc-2.3.4 to glibc-2.3.5 will not
     60        usually cause any problems.</para>
    6061      </listitem>
    6162
    … …  
    229230      <title>User Based Management</title>
    230231
    231       <para>This scheme, unique to LFS, was devised by Matthias Benkmann, and is
     232      <para>This scheme, unique to the LFS project, was devised by Matthias Benkmann, and is
    232233      available from the <ulink url="&hints-root;">Hints Project</ulink>. In
    233234      this scheme, each package is installed as a separate user into the

  • BOOK/final-system/x86/linux-headers.xml

    r76246b3 r9f08378  
    2626    <title>Installation of Linux-Headers</title>
    2727
    28     <para os="a">For years it has been common practice to use <quote>raw</quote>
    29     kernel headers (straight from a kernel tarball) in <filename
    30     class="directory">/usr/include</filename>, but over the last few
     28    <para os="a">For years it has been common practice to use
     29    <quote>raw</quote> kernel headers (straight from a kernel tarball) in
     30    <filename class="directory">/usr/include</filename>, but over the last few
    3131    years, the kernel developers have taken a strong stance that this
    3232    should not be done. This gave birth to the Linux-Libc-Headers Project,
    3333    which was designed to maintain an API stable version of the Linux
    34     headers. But recently this project stopped producing updates. Cross-LFS
    35     decided to come up with our own santized headers and placed them in
    36     the book.</para>
     34    headers. Recently this project stopped producing updates, so the Cross-LFS
     35    team started development on our own project to sanitize the headers.</para>
    3736
    3837    <para os="b">Install the header files that are common to all architectures:</para>

  • BOOK/introduction/common/changelog.xml

    r76246b3 r9f08378  
    3838
    3939    <listitem>
     40      <para>May 17 2006</para>
     41      <itemizedlist>
     42        <listitem>
     43          <para>[Chris] - Made a number of text updates and grammar
     44          fixes and added more dependency info (bootscripts,
     45          udev-rules, tree) to Appendix C.</para>
     46        </listitem>
     47      </itemizedlist>
     48    </listitem>
     49
     50    <listitem>
    4051      <para>May 16, 2006</para>
    4152      <itemizedlist>
Note: See TracChangeset for help on using the changeset viewer.