r1993 - / trunk/BOOK trunk/BOOK/final-preps trunk/BOOK/introduction/common trunk/BOOK/materials/common trunk/BOOK/partitioning/common

jim at linuxfromscratch.org jim at linuxfromscratch.org
Thu Jul 13 12:46:48 PDT 2006


Author: jim
Date: 2006-07-13 13:46:25 -0600 (Thu, 13 Jul 2006)
New Revision: 1993

Modified:
   /
   trunk/BOOK/
   trunk/BOOK/final-preps/settingenviron.xml
   trunk/BOOK/introduction/common/how.xml
   trunk/BOOK/materials/common/introduction.xml
   trunk/BOOK/partitioning/common/creatingpartition.xml
Log:
 r4565 at server (orig r2104):  jim | 2006-07-13 10:13:15 -0700
  r4564 at server:  jim | 2006-07-13 10:12:58 -0700
  Text Updates
 



Property changes on: 
___________________________________________________________________
Name: svk:merge
   - b6734a72-470d-0410-b049-f317dca95413:/:2102
   + b6734a72-470d-0410-b049-f317dca95413:/:2104


Property changes on: trunk/BOOK
___________________________________________________________________
Name: svk:merge
   - 38c7b366-470d-0410-a457-935707c16d9b:/cross-lfs:4560
3949c430-d905-0410-97b6-f115d20341b5:/cross-lfs:1422
3b7552df-c20a-0410-b7e1-d7eaf1be8828:/cross-lfs:1269
b6734a72-470d-0410-b049-f317dca95413:/trunk/BOOK:1406
f6929928-7304-0410-9559-ff6106abff4d:/cross-lfs:790
   + 38c7b366-470d-0410-a457-935707c16d9b:/cross-lfs:4564
3949c430-d905-0410-97b6-f115d20341b5:/cross-lfs:1422
3b7552df-c20a-0410-b7e1-d7eaf1be8828:/cross-lfs:1269
b6734a72-470d-0410-b049-f317dca95413:/trunk/BOOK:1406
f6929928-7304-0410-9559-ff6106abff4d:/cross-lfs:790

Modified: trunk/BOOK/final-preps/settingenviron.xml
===================================================================
--- trunk/BOOK/final-preps/settingenviron.xml	2006-07-13 15:45:04 UTC (rev 1992)
+++ trunk/BOOK/final-preps/settingenviron.xml	2006-07-13 19:46:25 UTC (rev 1993)
@@ -68,9 +68,8 @@
   <para os="h">The <envar>CLFS</envar> variable should be set to the
   chosen mount point.</para>
 
-  <para os="i">TO BE REWRITTEN - The <envar>LC_ALL</envar> variable controls
-  the localization of
-  certain programs, making their messages follow the conventions of a
+  <para os="i">The <envar>LC_ALL</envar> variable controls the localization
+  of certain programs, making their messages follow the conventions of a
   specified country.  If the host system uses a version of Glibc older
   than 2.2.4, having <envar>LC_ALL</envar> set to something other than
   <quote>POSIX</quote> or <quote>C</quote> (during this chapter) may cause

Modified: trunk/BOOK/introduction/common/how.xml
===================================================================
--- trunk/BOOK/introduction/common/how.xml	2006-07-13 15:45:04 UTC (rev 1992)
+++ trunk/BOOK/introduction/common/how.xml	2006-07-13 19:46:25 UTC (rev 1993)
@@ -11,25 +11,22 @@
   <title>How to Build a CLFS System</title>
 
   <para>The CLFS system will be built by using a previously installed
-  Linux distribution (such as Debian, Mandrake, Red Hat, or SuSE). This
-  existing Linux system (the host) will be used as a starting point to
+  Linux distribution (such as Debian, Fedora, Mandriva, SuSE, or Ubuntu).
+  This existing Linux system (the host) will be used as a starting point to
   provide necessary programs, including a compiler, linker, and shell,
   to build the new system. Select the <quote>development</quote> option
   during the distribution installation to be able to access these
   tools.</para>
 
   <para>As an alternative to installing an entire separate distribution
-  onto your machine, you may wish to
-  use the Linux From Scratch LiveCD. The CD works well as a host system,
-  providing all the tools you need to successfully follow the instructions
-  in this book. Additionally, it contains all the source packages, patches
-  and a copy of this book. So once you have the CD, no network connection
-  or additional downloads are necessary. For more information about the
-  LFS LiveCD or to download a copy, visit <ulink url="&livecd-root;"/></para>
+  onto your machine, you may wish to use the Linux From Scratch LiveCD.
+  The CD works well as a host system, providing all the tools you need to
+  successfully follow the instructions in this book. Additionally, it
+  contains all the source packages, patches and a copy of this book. So
+  once you have the CD, no network connection or additional downloads are
+  necessary. For more information about the LFS LiveCD or to download a copy,
+  visit <ulink url="&livecd-root;"/></para>
 
-  <!-- -->
-  <para>THE TEXT BELOW NEEDS TO BE REWRITTEN</para>
-
   <para><xref linkend="chapter-partitioning"/> of this book describes how
   to create a new Linux native partition and file system, the place
   where the new CLFS system will be compiled and installed. <xref
@@ -51,25 +48,16 @@
   compiler.</para>
 
   <para>The process of building cross-compile tools first involves installing
-  binutils into /cross-tools, so that the linker can be used with the building
-  of everything else in the temp-system. GCC is then compiled statically and
-  installed into /cross-tools, and this cross-compiler is used to build glibc
-  into /tools for the temp-system. The GCC cross-compiler is then rebuilt
-  dynamically - this final cross-compiler is what will be used to build the
-  rest of the temporary system. When this is done, the CLFS installation
-  process will no longer depend on the host distribution, with the exception
-  of the running kernel.
-  <!-- still needs some work - needs to provide a better technical
-explanation, especially the reasoning for compiling gcc statically then dynamically... --></para>
+  building all the necessary tools to create a build system for the target 
+  machine. With the Cross-Compiled tools we just created, we elminate any
+  dependencies on the toolchain from our host distro.</para>
 
-  <para>The packages in <xref linkend="chapter-temp-system"/> are then built
-  using the cross-compiled tools in /cross-tools, and linked against the
-  C library that was installed during the building of the cross-tools.</para>
+  <para>After we build our <quote>Cross-Tools</quote>, we start building
+  a very minimal working system in /tools. This effort to isolate the new
+  system from the host distribution may seem excessive, but a full technical
+  explanation is provided at the beginning of
+  <xref linkend="chapter-temp-system"/>.</para>
 
-  <para>This effort to isolate the new system from the host distribution
-  may seem excessive, but a full technical explanation is provided at the
-  beginning of <xref linkend="chapter-temp-system"/>.</para>
-
   <para>In <xref linkend="chapter-building-system"/>, the full CLFS system is
   built. Depending on the system you are cross-compiling for, either you will
   boot the minimal temp-system on the target machine, or chroot into it.</para>
@@ -88,16 +76,15 @@
   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>
+  bootscripts, and building a miminal kernel. We also describe some
+  alternative booting methods in <xref linkend="ch-boot-whatnext"/></para>
 
   <para>To finish the installation, the CLFS-Bootscripts are set up in <xref
   linkend="chapter-bootscripts"/>, and the kernel and boot loader are set
-  up in <xref linkend="chapter-bootable"/>. <xref
-  linkend="chapter-finalizing"/> contains information on furthering the
-  CLFS experience beyond this book.  After the steps in this book have
-  been implemented, the computer will be ready to reboot into the new
-  CLFS system.</para>
-  <!-- -->
+  up in <xref linkend="chapter-bootable"/>. <xref linkend="chapter-finalizing"/>
+  contains information on furthering the CLFS experience beyond this book.
+  After the steps in this book have been implemented, the computer will be
+  ready to reboot into the new CLFS system.</para>
 
   <para>This is the process in a nutshell. Detailed information on each
   step is discussed in the following chapters and package descriptions.

Modified: trunk/BOOK/materials/common/introduction.xml
===================================================================
--- trunk/BOOK/materials/common/introduction.xml	2006-07-13 15:45:04 UTC (rev 1992)
+++ trunk/BOOK/materials/common/introduction.xml	2006-07-13 19:46:25 UTC (rev 1993)
@@ -24,7 +24,7 @@
   url="http://www.google.com/"/>) provides a useful search engine for
   most packages. If this search is unsuccessful, try one of the
   alternative means of downloading discussed at <ulink
-  url="&clfs-root;wiki/download"/>.</para>
+  url="http://cross-lfs.org/files/packages/&major-version;.&minor-version;.&extra-version;"/>.</para>
 
   <para>Downloaded packages and patches will need to be stored somewhere
   that is conveniently available throughout the entire build. A working

Modified: trunk/BOOK/partitioning/common/creatingpartition.xml
===================================================================
--- trunk/BOOK/partitioning/common/creatingpartition.xml	2006-07-13 15:45:04 UTC (rev 1992)
+++ trunk/BOOK/partitioning/common/creatingpartition.xml	2006-07-13 19:46:25 UTC (rev 1993)
@@ -10,18 +10,14 @@
 
   <title>Creating a New Partition</title>
 
-  <para os="a">Like most other operating systems, CLFS is usually installed on
-  a dedicated partition. The recommended approach to building a CLFS
+  <para os="a">Like most other operating systems, CLFS is usually installed
+  on a dedicated partition. The recommended approach to building a CLFS
   system is to use an available empty partition or, if you have enough
-  unpartitioned space, to create one. However, a CLFS system (in fact
-  even multiple CLFS systems) may also be installed on a partition already
-  occupied by another operating system and the different systems will
-  co-exist peacefully. The document <ulink
-  url="&hints-root;lfs_next_to_existing_systems.txt"/> explains how to
-  implement this, whereas this book discusses the method of using a fresh
-  partition for the installation.</para>
+  unpartitioned space, to create one. However, if your building for a different
+  architecture you can simply build everyting in <quote>/mnt/clfs</quote>
+  and transfer it to your target machine.</para>
 
-  <para os="b">A minimal system requires a partition of around 1.3 gigabytes (GB).
+  <para os="b">A minimal system requires around 1.5 gigabytes (GB).
   This is enough to store all the source tarballs and compile the packages.
   However, if the CLFS system is intended to be the primary Linux system,
   additional software will probably be installed which will require




More information about the cross-lfs mailing list