Ported from trunk some redaction changes in preface and chapter01 pages.

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/6.1.1/BOOK@7055 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

chapter01/administrativa.xml

@@ -20,9 +20,11 @@ that is located at <ulink url="&faq-root;"/>.</para>
 <sect2 id="ch-scatter-maillists" xreflabel="Chapter 1 - Mailing Lists">
 <title>Mailing Lists</title>
 
-<para>The <uri>linuxfromscratch.org</uri> server hosts a number of
+<para>The <uri>linuxfromscratch.org</uri> server hosts a number of mailing lists
-mailing lists used for the development of the LFS project. These lists
+used for the development of the LFS project. These lists include the main
-include the main development and support lists, among others.</para> 
+development and support lists, among others. If the FAQ does not solve the
+problem you are having, the next step would be to search the mailing lists at
+<ulink url="&lfs-root;search.html"/>.</para> 
 
 <para>For information on the different lists, how to subscribe, archive
 locations, and additional information, visit

chapter01/askforhelp.xml

@@ -14,11 +14,18 @@ not answered on this page, try to find the source of the problem. The
 following hint will give you some guidance for troubleshooting: <ulink
 url="&hints-root;errors.txt"/>.</para>
 
-<para>We also have a wonderful LFS community that is willing to offer
+<para>If you cannot find your problem listed in the FAQ, search the mailing
-assistance through the mailing lists and IRC (see the <xref
+lists at <ulink url="&lfs-root;search.html"/>.</para>
-linkend="ch-scatter-administrativa"/> section of this book). In order
+
-to assist with diagnosing and solving the problem, please include
+<para>We also have a wonderful LFS community that is willing to offer assistance
-all relevant information in your request for help.</para>
+through the mailing lists and IRC (see the <xref
+linkend="ch-scatter-administrativa"/> section of this book). However, we get
+several support questions everyday and many of them can be easily answered by
+going to the FAQ and by searching the mailing lists first. So for us to offer
+the best assistance possible, you need to do some research on your own first.
+That allows us to focus on the more unusual support needs. If your searches do
+not produce a solution, please include all relevant information (mentioned
+below) in your request for help.</para>
 
 <sect2>
 <title>Things to Mention</title>

chapter01/changelog.xml

@@ -43,7 +43,8 @@ First a summary, then a detailed log.</para>
 </listitem>
 
 <listitem><para>October 19, 2005 [manuel]: Updated the acknowledgements
-to current trunk version.</para></listitem>
+to current trunk version. Ported also some redaction changes in preface
+and chapter01 pages.</para></listitem>
 
 <listitem><para>October 19, 2005 [manuel]: Updated the stylesheets, Makefile
 and related files to current trunk versions.</para></listitem>

chapter01/how.xml

@@ -54,9 +54,9 @@ pass toolchain. When this is done, the LFS installation process will no longer
 depend on the host distribution, with the exception of the running kernel.
 </para>
 
-<para>While this may initially seem like a lot of work to isolate the new system
+<para>This effort to isolate the new system from the host distribution may seem
-from the host distribution, a full technical explanation is provided at the
+excessive, but a full technical explanation is provided at the beginning of
-beginning of <xref linkend="chapter-temporary-tools"/>.</para>
+<xref linkend="chapter-temporary-tools"/>.</para>
 
 <para>In <xref linkend="chapter-building-system"/>, the full LFS system is
 built. The <command>chroot</command> (change root) program is used to enter a virtual

prologue/errata.xml

@@ -10,7 +10,7 @@
 <para>The software used to create an LFS system is constantly being updated and
 enhanced. Security warnings and bug fixes may become available after the LFS
 book has been released. To check whether the package versions or instructions in
-this release of LFS need any modifications to accomodate security
+this release of LFS need any modifications to accommodate security
 vulnerabilities or other bug fixes, please visit <ulink url="&errata;"/> before
 proceeding with your build. You should note any changes shown and apply them to
 the relevant section of the book as you progress with building the LFS system.

prologue/prerequisites.xml

@@ -7,9 +7,22 @@
 <title>Prerequisites</title>
 <?dbhtml filename="prerequisites.html"?>
 
-<para>This book assumes that the reader has a reasonable knowledge of using
+<para>Building an LFS system is not a simple task. It requires a certain level
-and installing Linux software. Before building an LFS system, we
+of existing knowledge of Unix system administration in order to resolve
-recommend reading the following HOWTOs:</para>
+problems, and correctly execute the commands listed.  In particular, as an
+absolute minimum, the reader should already have the ability to use the command
+line (shell) to copy or move files and directories, list directory and file
+contents, and change the current directory.  It is also expected that the reader
+has a reasonable knowledge of using and installing Linux software.</para>
+
+<para>Because the LFS book assumes <emphasis>at least</emphasis> this basic
+level of skill, the various LFS support forums are unlikely to be able to
+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>
+
+<para>Before building an LFS system, we recommend reading the following HOWTOs:
+</para>
 
 <itemizedlist>
 <listitem><para remap="verbatim">Software-Building-HOWTO