Changeset d5d4d82 in clfs-sysroot

Timestamp:

Jul 19, 2006, 7:24:03 PM (18 years ago)

Author:

Joe Ciccone <jciccone@…>

Branches:

master

Children:

6e439f9

Parents:

c3b61cb

Message:

Text and entity updates.

Location:

BOOK

Files:

• cross-tools/common/binutils.xml (modified) (1 diff)
• final-system/common/bzip2.xml (modified) (1 diff)
• final-system/common/gzip.xml (modified) (1 diff)
• final-system/common/man.xml (modified) (1 diff)
• final-system/common/sysklogd.xml (modified) (1 diff)
• general.ent (modified) (2 diffs)
• introduction/common/askforhelp.xml (modified) (1 diff)
• introduction/common/changelog.xml (modified) (1 diff)
• introduction/common/resources.xml (modified) (2 diffs)
• materials/common/introduction.xml (modified) (2 diffs)
• materials/common/patches.xml (modified) (1 diff)
• packages.ent (modified) (1 diff)
• patches.ent (modified) (1 diff)
• prologue/common/audience.xml (modified) (1 diff)
• prologue/common/foreword.xml (modified) (3 diffs)
• prologue/common/prerequisites.xml (modified) (3 diffs)

BOOK/cross-tools/common/binutils.xml

@@ -126 +126 @@
         <listitem>
           <para>This checks the host environment and makes sure all the
-          necessary tools are available to compile binutils.</para>
+          necessary tools are available to compile Binutils.</para>
         </listitem>
       </varlistentry>

BOOK/final-system/common/bzip2.xml

@@ -45 +45 @@
 <screen os="p6"><userinput>patch -Np1 -i ../&bzip2-remove_tempfile-patch;</userinput></screen>
 
-    <para os="s1">Disable running of the testsuite after a successful build:</para>
+    <para os="s1">Bzip2's default Makefile target automatically runs
+     the testsuite as well. Disable the tests since they won't work on a
+     multi-architecture build:</para>
 
 <screen os="s2"><userinput>cp Makefile{,.orig}

BOOK/final-system/common/gzip.xml

@@ -26 +26 @@
     <title>Installation of Gzip</title>
 
-    <para os="p1">The following patch fixes two security vulnerabilities in Gzip.
-    First, a path traversal bug when using the <option>-N</option> option
-    (CAN-2005-1228) Second, a race condition in the file permission restore
-    code (CAN-2005-0998)</para>
+    <para os="p1">The following patch fixes two security vulnerabilities in Gzip:
+    a path traversal bug when using the <option>-N</option> option
+    (CAN-2005-1228), and a race condition in the file permission restore
+    code (CAN-2005-0998):</para>
 
 <screen os="p2"><userinput>patch -Np1 -i ../&gzip-security_fix-patch;</userinput></screen>

BOOK/final-system/common/man.xml

@@ -118 +118 @@
     <para os="v">Additional information with regards to the compression of
     man and info pages can be found in the BLFS book at
-    <ulink url="&blfs-root;view/cvs/postlfs/compressdoc.html"/>.</para>
+    <ulink url="&blfs-root;view/svn/postlfs/compressdoc.html"/>.</para>
 
   </sect2>

BOOK/final-system/common/sysklogd.xml

@@ -27 +27 @@
 
     <para os="a">The following patch fixes various issues, including a
-    problem building Sysklogd with Linux 2.6 series kernels</para>
+    problem building Sysklogd with Linux 2.6 series kernels:</para>
 
 <screen os="b"><userinput>patch -Np1 -i ../&sysklogd-fixes-patch;</userinput></screen>

BOOK/general.ent

@@ -3 +3 @@
 <!ENTITY month "07"> <!-- Use two digits -->
 <!ENTITY month_name "July">
-<!ENTITY day "16"> <!-- Use two digits -->
+<!ENTITY day "19"> <!-- Use two digits -->
 <!ENTITY year "2006"> <!-- Use four digits -->
 
@@ -19 +19 @@
 
 <!ENTITY lfs-root "http://www.linuxfromscratch.org/">
-<!ENTITY clfs-root "http://trac.cross-lfs.org/">
+<!ENTITY clfs-root "http://cross-lfs.org/">
+<!ENTITY clfs-wiki "http://trac.cross-lfs.org/">
 <!ENTITY blfs-root "&lfs-root;blfs/">
-<!ENTITY faq-root "&lfs-root;faq/">
+<!ENTITY faq-root "&clfs-wiki;wiki/faq">
 <!ENTITY hints-root "&lfs-root;hints/downloads/files/">
 <!ENTITY hints-index "&lfs-root;hints/list.html">
 <!ENTITY livecd-root "&lfs-root;livecd/">
-<!ENTITY test-results "&clfs-root;clfs/build-logs/&generic-version;/">
-<!ENTITY errata "&clfs-root;clfs/errata/&generic-version;/">
+<!ENTITY test-results "&clfs-wiki;clfs/build-logs/&generic-version;/">
+<!ENTITY errata "&clfs-wiki;clfs/errata/&generic-version;/">
 
 <!ENTITY gnu "http://ftp.gnu.org/gnu/">

BOOK/introduction/common/askforhelp.xml

@@ -69 +69 @@
       mean that we will not help you. After all, the CLFS project is
       about personal preference. Be upfront about any changes to
-      the established procedure, this helps us evaluate and determine
+      the established procedure—this helps us evaluate and determine
       possible causes of your problem.</para>
     </note>

BOOK/introduction/common/changelog.xml

@@ -14 +14 @@
   &releasedate;. If this book is more than six months old, a newer and better
   version is probably already available. To find out, please check one of the
-  mirrors via <ulink url="&clfs-root;"/>.</para>
+  mirrors via <ulink url="&clfs-wiki;"/>.</para>
 
   <para>Below is a list of detailed changes made since the previous release of

BOOK/introduction/common/resources.xml

@@ -33 +33 @@
     locations, and additional information, visit
     <ulink url="&lfs-root;mail.html"/>. For mailing lists specifically
-    for CLFS, visit <ulink url="&clfs-root;wiki/lists"/>.</para>
+    for CLFS, visit <ulink url="&clfs-wiki;wiki/lists"/>.</para>
 
   </sect2>
@@ -76 +76 @@
     convenient. Please visit the LFS website at <ulink
     url="&lfs-root;mirrors.html"/> for a list of current mirrors of
-    the LFS website, or <ulink url="&clfs-root;wiki/mirrors"/> for
+    the LFS website, or <ulink url="&clfs-wiki;wiki/mirrors"/> for
     mirrors of CLFS.</para>
 

BOOK/materials/common/introduction.xml

@@ -25 +25 @@
   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="&packages-root;"/>.</para>
 
   <para>Downloaded packages and patches will need to be stored somewhere
@@ -42 +42 @@
 <screen><userinput>mkdir -v $CLFS/sources</userinput></screen>
 
-  <para>Make this directory writable and sticky. <quote>Sticky</quote>
-  means that even if multiple users have write permission on a
-  directory, only the owner of a file can delete the file within a
-  sticky directory. The following command will enable the write and
-  sticky modes:</para>
+  <para>Make this directory writable and sticky. When a directory is
+  marked <quote>sticky</quote>, that means that even if multiple users have
+  write permission on that directory, any file within that directory can only be
+  deleted or modified by its owner. The following command will enable the
+  write and sticky modes:</para>
 
 <screen><userinput>chmod -v a+wt $CLFS/sources</userinput></screen>

BOOK/materials/common/patches.xml

@@ -15 +15 @@
   fixed by the maintainer. The patches also make small modifications to
   make the packages easier to work with. The following patches will be
-  needed to build an CLFS system:</para>
+  needed to build a CLFS system:</para>
 
   <variablelist role="materials">

BOOK/packages.ent

@@ -1 +1 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
 
-<!ENTITY packages-root "http://cross-lfs.org/files/packages/&generic-version;/">
+<!ENTITY packages-root "&clfs-root;files/packages/&generic-version;/">
 
 <!-- Note: For empty *-home entities use " " not "" -->

BOOK/patches.ent

@@ -1 +1 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
 
-<!ENTITY patches-root "http://cross-lfs.org/files/patches/&generic-version;/">
+<!ENTITY patches-root "&clfs-root;files/patches/&generic-version;/">
 
 <!-- Start of Common Patches -->

BOOK/prologue/common/audience.xml

@@ -68 +68 @@
   correctly and adequately fixes the problem.</para>
 
-  <para>The goal of Linux From Scratch is to build a complete and usable
+  <para>The goal of Cross Linux From Scratch is to build a complete and usable
   foundation-level system. Readers who do not wish to build their own
   Linux system from scratch may not benefit from the information in this

BOOK/prologue/common/foreword.xml

@@ -25 +25 @@
   improvements to the Linux From Scratch system.</para>
 
-  <para>The one "flaw" in LFS is that it has always been based on a x86
+  <para>The one "flaw" in LFS is that it has always been based on an x86
   class processor.  With the advent of the Athlon 64 and Intel EM64T
   processors, the x86-only LFS is no longer ideal. Throughout this time,
@@ -40 +40 @@
 
   <para>We hope you enjoy building your own CLFS system, and the benefits
-  that come from a system tailored to your needs!</para>
+  that come from a system tailored to your needs.</para>
 
 <literallayout>--
@@ -46 +46 @@
 Jim Gifford, CLFS Project Co-leader
 Ryan Oliver, CLFS Project Co-leader
-Joe Ciccone, Justin Knierin, Chris Staub, Matt Darcy, Ken Moffat,
+Joe Ciccone, Justin Knierim, Chris Staub, Matt Darcy, Ken Moffat,
 Manuel Canales Esparcia, and Nathan Coulson - CLFS Developers</literallayout>
 

BOOK/prologue/common/prerequisites.xml

@@ -20 +20 @@
   Linux software. A basic knowledge of the architectures being used in 
   the Cross LFS process and the host operating systems in use is also
-  required</para>
+  required.</para>
 
   <para>Because the CLFS book assumes <emphasis>at least</emphasis> this basic
@@ -26 +26 @@
   provide you with much assistance; you will find that your questions regarding
   such basic knowledge will likely go unanswered, or you will simply be referred
-  to the LFS essential pre-reading list.</para>
+  to the CLFS essential pre-reading list.</para>
 
   <para>Before building a CLFS system, we recommend reading the following
@@ -49 +49 @@
       <ulink url="&hints-root;essential_prereading.txt"/></para>
 
-      <para>This is an LFS Hint written specifically for users new to Linux.
+      <para>This is an Hint written specifically for users new to Linux.
       It includes a list of links to excellent sources of information on a
       wide range of topics. Anyone attempting to install CLFS should have an