Changeset a266616


Ignore:
Timestamp:
Jul 13, 2006, 10:13:15 AM (17 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:
a5b01a51
Parents:
036cbc7
Message:

r4564@server: jim | 2006-07-13 10:12:58 -0700
Text Updates

Location:
BOOK
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • BOOK/final-preps/settingenviron.xml

    r036cbc7 ra266616  
    6969  chosen mount point.</para>
    7070
    71   <para os="i">TO BE REWRITTEN - The <envar>LC_ALL</envar> variable controls
    72   the localization of
    73   certain programs, making their messages follow the conventions of a
     71  <para os="i">The <envar>LC_ALL</envar> variable controls the localization
     72  of certain programs, making their messages follow the conventions of a
    7473  specified country.  If the host system uses a version of Glibc older
    7574  than 2.2.4, having <envar>LC_ALL</envar> set to something other than
  • BOOK/introduction/common/how.xml

    r036cbc7 ra266616  
    1212
    1313  <para>The CLFS system will be built by using a previously installed
    14   Linux distribution (such as Debian, Mandrake, Red Hat, or SuSE). This
    15   existing Linux system (the host) will be used as a starting point to
     14  Linux distribution (such as Debian, Fedora, Mandriva, SuSE, or Ubuntu).
     15  This existing Linux system (the host) will be used as a starting point to
    1616  provide necessary programs, including a compiler, linker, and shell,
    1717  to build the new system. Select the <quote>development</quote> option
     
    2020
    2121  <para>As an alternative to installing an entire separate distribution
    22   onto your machine, you may wish to
    23   use the Linux From Scratch LiveCD. The CD works well as a host system,
    24   providing all the tools you need to successfully follow the instructions
    25   in this book. Additionally, it contains all the source packages, patches
    26   and a copy of this book. So once you have the CD, no network connection
    27   or additional downloads are necessary. For more information about the
    28   LFS LiveCD or to download a copy, visit <ulink url="&livecd-root;"/></para>
    29 
    30   <!-- -->
    31   <para>THE TEXT BELOW NEEDS TO BE REWRITTEN</para>
     22  onto your machine, you may wish to use the Linux From Scratch LiveCD.
     23  The CD works well as a host system, providing all the tools you need to
     24  successfully follow the instructions in this book. Additionally, it
     25  contains all the source packages, patches and a copy of this book. So
     26  once you have the CD, no network connection or additional downloads are
     27  necessary. For more information about the LFS LiveCD or to download a copy,
     28  visit <ulink url="&livecd-root;"/></para>
    3229
    3330  <para><xref linkend="chapter-partitioning"/> of this book describes how
     
    5249
    5350  <para>The process of building cross-compile tools first involves installing
    54   binutils into /cross-tools, so that the linker can be used with the building
    55   of everything else in the temp-system. GCC is then compiled statically and
    56   installed into /cross-tools, and this cross-compiler is used to build glibc
    57   into /tools for the temp-system. The GCC cross-compiler is then rebuilt
    58   dynamically - this final cross-compiler is what will be used to build the
    59   rest of the temporary system. When this is done, the CLFS installation
    60   process will no longer depend on the host distribution, with the exception
    61   of the running kernel.
    62   <!-- still needs some work - needs to provide a better technical
    63 explanation, especially the reasoning for compiling gcc statically then dynamically... --></para>
     51  building all the necessary tools to create a build system for the target
     52  machine. With the Cross-Compiled tools we just created, we elminate any
     53  dependencies on the toolchain from our host distro.</para>
    6454
    65   <para>The packages in <xref linkend="chapter-temp-system"/> are then built
    66   using the cross-compiled tools in /cross-tools, and linked against the
    67   C library that was installed during the building of the cross-tools.</para>
    68 
    69   <para>This effort to isolate the new system from the host distribution
    70   may seem excessive, but a full technical explanation is provided at the
    71   beginning of <xref linkend="chapter-temp-system"/>.</para>
     55  <para>After we build our <quote>Cross-Tools</quote>, we start building
     56  a very minimal working system in /tools. This effort to isolate the new
     57  system from the host distribution may seem excessive, but a full technical
     58  explanation is provided at the beginning of
     59  <xref linkend="chapter-temp-system"/>.</para>
    7260
    7361  <para>In <xref linkend="chapter-building-system"/>, the full CLFS system is
     
    8977  support the target machine. Booting involves installing a few
    9078  additional packages that are needed for bootup, installing
    91   bootscripts, and building a miminal kernel.</para>
     79  bootscripts, and building a miminal kernel. We also describe some
     80  alternative booting methods in <xref linkend="ch-boot-whatnext"/></para>
    9281
    9382  <para>To finish the installation, the CLFS-Bootscripts are set up in <xref
    9483  linkend="chapter-bootscripts"/>, and the kernel and boot loader are set
    95   up in <xref linkend="chapter-bootable"/>. <xref
    96   linkend="chapter-finalizing"/> contains information on furthering the
    97   CLFS experience beyond this book.  After the steps in this book have
    98   been implemented, the computer will be ready to reboot into the new
    99   CLFS system.</para>
    100   <!-- -->
     84  up in <xref linkend="chapter-bootable"/>. <xref linkend="chapter-finalizing"/>
     85  contains information on furthering the CLFS experience beyond this book.
     86  After the steps in this book have been implemented, the computer will be
     87  ready to reboot into the new CLFS system.</para>
    10188
    10289  <para>This is the process in a nutshell. Detailed information on each
  • BOOK/materials/common/introduction.xml

    r036cbc7 ra266616  
    2525  most packages. If this search is unsuccessful, try one of the
    2626  alternative means of downloading discussed at <ulink
    27   url="&clfs-root;wiki/download"/>.</para>
     27  url="http://cross-lfs.org/files/packages/&major-version;.&minor-version;.&extra-version;"/>.</para>
    2828
    2929  <para>Downloaded packages and patches will need to be stored somewhere
  • BOOK/partitioning/common/creatingpartition.xml

    r036cbc7 ra266616  
    1111  <title>Creating a New Partition</title>
    1212
    13   <para os="a">Like most other operating systems, CLFS is usually installed on
    14   a dedicated partition. The recommended approach to building a CLFS
     13  <para os="a">Like most other operating systems, CLFS is usually installed
     14  on a dedicated partition. The recommended approach to building a CLFS
    1515  system is to use an available empty partition or, if you have enough
    16   unpartitioned space, to create one. However, a CLFS system (in fact
    17   even multiple CLFS systems) may also be installed on a partition already
    18   occupied by another operating system and the different systems will
    19   co-exist peacefully. The document <ulink
    20   url="&hints-root;lfs_next_to_existing_systems.txt"/> explains how to
    21   implement this, whereas this book discusses the method of using a fresh
    22   partition for the installation.</para>
     16  unpartitioned space, to create one. However, if your building for a different
     17  architecture you can simply build everyting in <quote>/mnt/clfs</quote>
     18  and transfer it to your target machine.</para>
    2319
    24   <para os="b">A minimal system requires a partition of around 1.3 gigabytes (GB).
     20  <para os="b">A minimal system requires around 1.5 gigabytes (GB).
    2521  This is enough to store all the source tarballs and compile the packages.
    2622  However, if the CLFS system is intended to be the primary Linux system,
Note: See TracChangeset for help on using the changeset viewer.