cvs commit: BLFS/BOOK/preface foreword.xml organization.xml

igor at linuxfromscratch.org igor at linuxfromscratch.org
Sat May 29 01:25:12 PDT 2004


igor        04/05/29 02:25:12

  Modified:    BOOK/introduction/important bootscripts.xml patches.xml
                        pkgmgt.xml unpacking.xml
               BOOK/introduction/welcome askhelp.xml changelog.xml
                        conventions.xml version.xml
               BOOK/preface foreword.xml organization.xml
  Log:
  applied Randy's grammar and spelling fixes
  
  Revision  Changes    Path
  1.16      +1 -1      BLFS/BOOK/introduction/important/bootscripts.xml
  
  Index: bootscripts.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/introduction/important/bootscripts.xml,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- bootscripts.xml	29 May 2004 00:43:21 -0000	1.15
  +++ bootscripts.xml	29 May 2004 08:25:10 -0000	1.16
  @@ -16,7 +16,7 @@
   
   <para>The blfs-bootscripts package will be used throughout the <acronym>BLFS</acronym>
   book for startup scripts.  Unlike <acronym>LFS</acronym>, each init script
  -has a seperate install target in the blfs-bootscripts package. 
  +has a separate install target in the blfs-bootscripts package. 
   It is recomended you keep the package
   source directory around until completion of your
   <acronym>BLFS</acronym> system.  When a script is requested from
  
  
  
  1.5       +3 -3      BLFS/BOOK/introduction/important/patches.xml
  
  Index: patches.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/introduction/important/patches.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- patches.xml	29 May 2004 00:43:21 -0000	1.4
  +++ patches.xml	29 May 2004 08:25:10 -0000	1.5
  @@ -13,9 +13,9 @@
   <listitem><para>Fixes a broken functionality.</para></listitem>
   </itemizedlist>
   
  -<para>In short, the book only includes patches that are either Required or
  -Recommended. There is a <ulink url="http://www.linuxfromscratch.org/patches">Patches subproject</ulink>
  -which hosts various patches (including the patches included in the books)
  +<para>In short, the book only includes patches that are either required or
  +recommended. There is a <ulink url="http://www.linuxfromscratch.org/patches">Patches subproject</ulink>
  +which hosts various patches (including the patches referenced in the books)
   to enable you to configure your <acronym>LFS</acronym> the way you like it.</para>
   
   </sect1>
  
  
  
  1.6       +4 -4      BLFS/BOOK/introduction/important/pkgmgt.xml
  
  Index: pkgmgt.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/introduction/important/pkgmgt.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- pkgmgt.xml	6 May 2004 19:04:28 -0000	1.5
  +++ pkgmgt.xml	29 May 2004 08:25:10 -0000	1.6
  @@ -98,7 +98,7 @@
   <para>The environment variables such as those
   mentioned in <xref linkend="intro-important-beyond"/> need to be expanded to
   include <filename>/usr/pkg/foo</filename>. For more than a few packages,
  -this scheme becomes unmanagable.</para>
  +this scheme becomes unmanageable.</para>
   
   </sect3>
   
  @@ -110,11 +110,11 @@
   each file is symlinked into <filename>/usr</filename> hierarchy. This removes the need
   to expand the environment variables. Though the symlinks can be created by the user,
   to automate the creation, many package managers have been written on this approach.
  -Few of the popular ones are Stow, Epkg, Graft, and Depot.</para>
  +A few of the popular ones are Stow, Epkg, Graft, and Depot.</para>
   
   <para>The installation needs to be faked, so that the package thinks that it is
  -installed in <filename>/usr</filename> though in reality it is installed in
  -<filename>/ust/pkg</filename> hierarchy. Installing in this manner is not usually a trivial
  +installed in <filename class="directory">/usr</filename> though in reality it is installed in
  +<filename class="directory">/usr/pkg</filename> hierarchy. Installing in this manner is not usually a trivial
   task. For example, consider that you are installing a package libfoo-1.1. The following
   instructions may not install the package properly:</para>
   
  
  
  
  1.10      +2 -2      BLFS/BOOK/introduction/important/unpacking.xml
  
  Index: unpacking.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/introduction/important/unpacking.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- unpacking.xml	6 May 2004 19:04:28 -0000	1.9
  +++ unpacking.xml	29 May 2004 08:25:10 -0000	1.10
  @@ -74,13 +74,13 @@
   <para>For larger packages, it is convenient to create log files instead of
   staring at the screen hoping to catch a particular error or warning. Log files
   are also useful for debugging and keeping records. The following command
  -allows you to create a installation log. Replace <command> with the
  +allows you to create an installation log. Replace <command> with the
   command you intend to execute.</para>
   
   <screen><command>( <command> 2>&1 | tee compile.log && exit $PIPESTATUS )</command></screen>
   
   <para><parameter>2>&1</parameter> redirects error messages
  -to the same location as normal output. The <command>tee</command> command
  +to the same location as standard output. The <command>tee</command> command
   allows viewing of the output while logging the results to a file. The parentheses
   around the command run the entire command in a subshell and finally the
   <command>exit $PIPESTATUS</command> ensures the result of the <command>
  
  
  
  1.10      +7 -8      BLFS/BOOK/introduction/welcome/askhelp.xml
  
  Index: askhelp.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/introduction/welcome/askhelp.xml,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- askhelp.xml	6 May 2004 19:04:28 -0000	1.9
  +++ askhelp.xml	29 May 2004 08:25:11 -0000	1.10
  @@ -19,28 +19,27 @@
   
   <itemizedlist>
   <listitem><para>Is the hardware support compiled into the kernel or
  -available as a module to the kernel.  If it is a module, is it configured
  -properly in <filename>modules.conf</filename> and has it been loaded.  You
  +available as a module to the kernel?  If it is a module, is it configured
  +properly in <filename>modules.conf</filename> and has it been loaded?  You
   should use <command>lsmod</command> as root to see if it's loaded. Check the
   <filename>sys.log</filename> or run <command>modprobe <driver>
   </command> to review any error message.  If it loads properly, you may need 
   to add the <command>modprobe</command> to your boot scripts.</para></listitem>
   
   <listitem><para>Are your permissions properly set, especially for
  -devices. <acronym>LFS</acronym> uses groups to make these settings easier, but 
  +devices? <acronym>LFS</acronym> uses groups to make these settings easier, but 
   it also adds the step of adding users to groups to allow access. A simple
   <command>moduser -G audio <user></command> may be all that's necessary 
   for that user to have access to the sound system.  Any question that starts 
  -out with "It works as root, but not as ..." should review permissions
  -thoroughly
  -prior to asking.</para></listitem>
  +out with "It works as root, but not as ..." requires a thorough review
  +of permissions prior to asking.</para></listitem>
   
   <listitem><para><acronym>BLFS</acronym> liberally uses <filename>
   /opt/<package></filename>. The main objection to this centers around the 
   need to expand your environment variables for each package placed there (e.g.
   PATH=$PATH:/opt/kde/bin).  In some cases, the package will walk you
  -through the changes, but some will not.  <xref linkend="intro-important-beyond"/> 
  -is available to help you check.</para></listitem>
  +through the changes, but some will not.  The section called "<ulink
  +url="beyond.html">Going Beyond BLFS</ulink>" is available to help you check.</para></listitem>
   </itemizedlist></sect2>
   
   <sect2>
  
  
  
  1.1169    +4 -0      BLFS/BOOK/introduction/welcome/changelog.xml
  
  Index: changelog.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/introduction/welcome/changelog.xml,v
  retrieving revision 1.1168
  retrieving revision 1.1169
  diff -u -r1.1168 -r1.1169
  --- changelog.xml	29 May 2004 07:46:09 -0000	1.1168
  +++ changelog.xml	29 May 2004 08:25:11 -0000	1.1169
  @@ -11,6 +11,10 @@
   
   <itemizedlist>
   
  +<listitem><para>May 29th, 2004 [igor]: Applied fixes for various
  +grammar and spelling errors, suggested by Randy
  +McMurchy.</para></listitem>
  +
   <listitem><para>May 29th, 2004 [igor]: Moved the samba maintainer
   patch to samba3 page, reported by Manuel Canales
   Esparcia.</para></listitem>
  
  
  
  1.8       +5 -1      BLFS/BOOK/introduction/welcome/conventions.xml
  
  Index: conventions.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/introduction/welcome/conventions.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- conventions.xml	6 May 2004 19:04:28 -0000	1.7
  +++ conventions.xml	29 May 2004 08:25:11 -0000	1.8
  @@ -43,5 +43,9 @@
   following lines until the sequence <acronym>EOF</acronym> is encountered. 
   Therefore, this whole section is generally typed as seen.</para></blockquote>
   
  -</sect1>
  +<para><replaceable>[REPLACED TEXT]</replaceable></para>
  +
  +<blockquote><para>This form of text is used to encapsulate text that is
  +not to be typed as seen or copy and pasted.</para></blockquote>
   
  +</sect1>
  
  
  
  1.9       +1 -1      BLFS/BOOK/introduction/welcome/version.xml
  
  Index: version.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/introduction/welcome/version.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- version.xml	6 May 2004 19:04:28 -0000	1.8
  +++ version.xml	29 May 2004 08:25:11 -0000	1.9
  @@ -3,7 +3,7 @@
   <title>Book version</title>
   
   <para>This is <acronym>BLFS</acronym>-BOOK version &version; dated &releasedate;. 
  -If this version is older than a month a newer version is probably already 
  +If this version is older than a month, a newer version is probably already 
   available for download. Check one of the mirror sites below for updated
   versions.</para>
   
  
  
  
  1.7       +1 -1      BLFS/BOOK/preface/foreword.xml
  
  Index: foreword.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/preface/foreword.xml,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- foreword.xml	19 May 2004 13:30:19 -0000	1.6
  +++ foreword.xml	29 May 2004 08:25:12 -0000	1.7
  @@ -21,7 +21,7 @@
   you go.</para>
   
   <para>Thanks as ever go to everyone in the <acronym>LFS</acronym>/<acronym>BLFS</acronym> 
  -community especially those who have contributed instructions, written text, 
  +community; especially those who have contributed instructions, written text, 
   answered questions and generally shouted when things were wrong!</para>
   
   <para>Finally, we encourage you to become involved in the community; ask 
  
  
  
  1.15      +2 -3      BLFS/BOOK/preface/organization.xml
  
  Index: organization.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/BOOK/preface/organization.xml,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- organization.xml	13 Apr 2004 01:59:17 -0000	1.14
  +++ organization.xml	29 May 2004 08:25:12 -0000	1.15
  @@ -35,12 +35,11 @@
   </acronym></application>, etc.).</para></sect2>
   
   <sect2><title>Part VII - Content Serving</title>
  -<para>In this part we deal with databases and web server software
  -<!--(including php)-->.</para></sect2>
  +<para>In this part we deal with databases and web server software.</para></sect2>
   
   <sect2><title>Part VIII - X + Window Managers</title>
   <para>This part explains how to set up a basic
  -<application>XFree86</application> installation along
  +X Window System installation along
   with some generic <application>X</application> libraries and Window managers.</para></sect2>
   
   <sect2><title>Part IX - KDE</title>
  
  
  



More information about the blfs-book mailing list