diff options
| -rw-r--r-- | chapter01/changelog.xml | 12 | ||||
| -rw-r--r-- | general.ent | 4 | ||||
| -rw-r--r-- | prologue/architecture.xml | 34 | ||||
| -rw-r--r-- | prologue/standards.xml | 4 | ||||
| -rw-r--r-- | prologue/why.xml | 16 |
5 files changed, 41 insertions, 29 deletions
diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index c523c160a..409959c70 100644 --- a/chapter01/changelog.xml +++ b/chapter01/changelog.xml @@ -38,6 +38,18 @@ --> <listitem> + <para>2009-12-10</para> + <itemizedlist> + <listitem> + <para>[bdubbs] Grammar and spelling updates from + Chris Staub. Fixes + <ulink url="&lfs-ticket-root;2548">#2548</ulink>.</para> + </listitem> + </itemizedlist> + </listitem> + + + <listitem> <para>2010-01-03</para> <itemizedlist> <listitem> diff --git a/general.ent b/general.ent index f091044fe..589d67a8f 100644 --- a/general.ent +++ b/general.ent @@ -1,5 +1,5 @@ -<!ENTITY version "SVN-20100103"> -<!ENTITY releasedate "January 3, 2010"> +<!ENTITY version "SVN-20100110"> +<!ENTITY releasedate "January 10, 2010"> <!ENTITY copyrightdate "1999-2010"><!-- jhalfs needs a literal dash, not – --> <!ENTITY milestone "7.0"> <!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" --> diff --git a/prologue/architecture.xml b/prologue/architecture.xml index f4b1a2744..aa8cb2399 100644 --- a/prologue/architecture.xml +++ b/prologue/architecture.xml @@ -10,22 +10,22 @@ <title>LFS Target Architectures</title> -<para>The primary target architecture of LFS is the 32-bit Intel CPU. If you +<para>The primary target architecture of LFS is the 32-bit Intel CPU. If you have not built an LFS system before, you should probably start with that -target. The 32-bit architecture is the most widely supported Linux system and +target. The 32-bit architecture is the most widely supported Linux system and is most compatible with both open source and proprietary software.</para> <para>On the other hand, the instructions in this book are known to work, with -some modifications, with both Power PC and 64-bit AMD/Intel CPUs. To build a -system that utilizes these CPUs, the main prerequisite in addition to those on -the next few pages, is an existing system such as an earlier LFS system, -Ubuntu, Red Hat/Fedora, SuSE, or other distribution that targets the system -that you have. Also note that a 32-bit system can be installed and used as a -host system on a 64-bit AMD/Intel system.</para> - -<para>Some other facts about a 64-bit systems need to be added here. When +some modifications, with both Power PC and 64-bit AMD/Intel CPUs. To build a +system that utilizes one of these CPUs, the main prerequisite, in addition to +those on the next few pages, is an existing Linux system such as an earlier LFS +installation, Ubuntu, Red Hat/Fedora, SuSE, or other distribution that targets +the architecture that you have. Also note that a 32-bit distribution can be +installed and used as a host system on a 64-bit AMD/Intel computer.</para> + +<para>Some other facts about a 64-bit systems need to be added here. When compared to a 32-bit system, the sizes of executable programs are slightly -larger and the execution speeds are only slightly faster. For example, in a +larger and the execution speeds are only slightly faster. For example, in a test build of LFS-6.5 on a Core2Duo CPU based system, the following statistics were measured:</para> @@ -39,16 +39,16 @@ minimal. Of course, if you have more than 4GB of RAM or want to manipulate data that exceeds 4GB, the advantages of a 64-bit system are substantial.</para> <para>The default 64-bit build that results from LFS is considered a "pure" -64-bit system. That is, it supports 64-bit executables only. Building a -"multi-lib" system requires building many applications twice, once for a 32-bit -system and once for a 64-bit system. Currently this is not directly supported -in the book, but is under consideration for a future release. In the meantime, +64-bit system. That is, it supports 64-bit executables only. Building a +"multi-lib" system requires compiling many applications twice, once for a 32-bit +system and once for a 64-bit system. Currently this is not directly supported +in the book, but is under consideration for a future release. In the meantime, you can refer to the <ulink url="http://trac.cross-lfs.org/">Cross Linux From Scratch</ulink> project for this advanced topic.</para> -<para>There is one last comment about 64-bit systems. There are some packages +<para>There is one last comment about 64-bit systems. There are some packages that cannot currently be built in a "pure" 64-bit system or require specialized -build instructions. Generally, these packages have some embedded 32-bit +build instructions. Generally, these packages have some embedded 32-bit specific assembly language instructions that fail when building on a 64-bit system. Examples include the <ulink url="http://www.linuxfromscratch.org/blfs/view/svn/">Beyond Linux From Scratch diff --git a/prologue/standards.xml b/prologue/standards.xml index 85c252947..da56719fd 100644 --- a/prologue/standards.xml +++ b/prologue/standards.xml @@ -20,7 +20,7 @@ <listitem> <para><ulink url="http://www.unix.org/single_unix_specification">The Single UNIX Specification Version 3 (POSIX)</ulink>. Note: - Free registratration is required.</para> + Free registration is required.</para> </listitem> <listitem> <para><ulink url="http://www.pathname.com/fhs/pub/fhs-2.3.html">Filesystem @@ -49,7 +49,7 @@ <para>Creating a complete LFS system capable of passing the LSB certifications tests is possible, but not without many additional packages that are beyond the scope of LFS. Most of these additional packages have - intallation instructions in BLFS. </para> + installation instructions in BLFS. </para> <variablelist> <bridgehead renderas="sect3">Packages supplied by LFS needed to diff --git a/prologue/why.xml b/prologue/why.xml index e21ab16c2..99cca1ce9 100644 --- a/prologue/why.xml +++ b/prologue/why.xml @@ -12,7 +12,7 @@ <para>As stated earlier, the goal of LFS is to build a complete and usable foundation-level system. This includes all packages needed to replicate - itself while providing a relativly minimal base from which to customize + itself while providing a relatively minimal base from which to customize a more complete system based on the choices of the user. This does not mean that LFS is the smallest system possible. Several important packages are included that are not strictly required. The lists below document the @@ -50,14 +50,14 @@ <para>Binutils</para> <para>This package package contains a linker, an assembler, and other - tools for handling object files. </para> + tools for handling object files.</para> </listitem> <listitem> <para>Bison</para> <para>This package contains the GNU version of yacc (Yet Another - Compiler Compiler) needed to build several other LFS programs. + Compiler Compiler) needed to build several other LFS programs. </para> </listitem> @@ -102,7 +102,7 @@ <para>E2fsprogs</para> <para>This package contains the utilities for handling the ext2, ext3 - and ext4 file systems. These are the most common and thouroughly + and ext4 file systems. These are the most common and thoroughly tested file systems that Linux supports.</para> </listitem> @@ -239,7 +239,7 @@ <para>Less</para> <para>This package contains a very nice text file viewer that - allows scolling up or down when viewing a file. + allows scrolling up or down when viewing a file. </para> </listitem> @@ -329,7 +329,7 @@ <para>Perl</para> <para>This package is an interpreter for the runtime language - PERL. </para> + PERL.</para> </listitem> <listitem> @@ -436,8 +436,8 @@ <listitem> <para>Vim</para> - <para>This package an editor. It was chosen because its compatibility - with the classic vi editor and its huge number of powerful + <para>This package contains an editor. It was chosen because of its + compatibility with the classic vi editor and its huge number of powerful capabilities. An editor is a very personal choice for many users and any other editor could be substituted if desired. </para> |