r1078 - trunk/BOOK/chapter01
manuel at linuxfromscratch.org
manuel at linuxfromscratch.org
Mon Apr 30 02:04:21 MDT 2007
Author: manuel
Date: 2007-04-30 02:04:21 -0600 (Mon, 30 Apr 2007)
New Revision: 1078
Added:
trunk/BOOK/chapter01/resources.xml
Removed:
trunk/BOOK/chapter01/administrativa.xml
Modified:
trunk/BOOK/chapter01/askforhelp.xml
trunk/BOOK/chapter01/chapter01.xml
trunk/BOOK/chapter01/how.xml
Log:
Indented chapter01, except changelog.
Updated wording to match LFS book.
Deleted: trunk/BOOK/chapter01/administrativa.xml
===================================================================
--- trunk/BOOK/chapter01/administrativa.xml 2007-04-30 08:02:56 UTC (rev 1077)
+++ trunk/BOOK/chapter01/administrativa.xml 2007-04-30 08:04:21 UTC (rev 1078)
@@ -1,73 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
- <!ENTITY % general-entities SYSTEM "../general.ent">
- %general-entities;
-]>
-<sect1 id="ch-scatter-administrativa">
-<title>Resources</title>
-<?dbhtml filename="resources.html"?>
-
-<sect2 id="ch-scatter-faq">
-<title>FAQ</title>
-
-<para>If during the building of your HLFS system you encounter any errors, or
-have any questions, or think you found a typo in the book, then please first
-consult the FAQ (Frequently Asked Questions) at
-<ulink url="&faq-root;"/>.</para>
-
-</sect2>
-
-<sect2 id="ch-scatter-maillists" xreflabel="Chapter 1 - Mailing lists">
-<title>Mailing lists</title>
-
-<para>The <uri>linuxfromscratch.org</uri> server is hosting a number
-of mailing lists used for the development of the LFS projects. These lists
-include, among others, the main development and support lists.</para>
-
-<para>For information on which lists are available, how to subscribe to them,
-their archive locations, and so on, visit <ulink url="&lfs-root;mail.html"/>.</para>
-
-</sect2>
-
-<sect2 id="ch-scatter-newsserver">
-<title>News server</title>
-
-<para>All the mailing lists hosted at <uri>linuxfromscratch.org</uri>
-are also accessible via the NNTP server. All messages posted to a mailing list
-are copied to the corresponding newsgroup, and vice versa.</para>
-
-<para>The news server can be reached at
-<uri>news.linuxfromscratch.org</uri>.</para>
-
-</sect2>
-
-<sect2 id="ch-scatter-irc">
-<title>IRC</title>
-
-<para>Several members of the LFS community offer assistance on our community
-Internet Relay Chat (IRC) network. Before using this support, please make sure
-that your question is not already answered in the LFS FAQ or the mailing list
-archives. You can find the IRC network at <uri>irc.linuxfromscratch.org</uri>,
-<uri>irc.linux-phreak.net</uri> or <uri>irc.lfs-matrix.de</uri>. The channel is
-named #HLFS.</para>
-</sect2>
-
-<sect2 id="ch-scatter-mirrors" xreflabel="Chapter 1 - Mirror sites">
-<title>Mirror sites</title>
-
-<para>The LFS project has a number of mirrors set up world-wide to make
-accessing the website and downloading the required packages more convenient.
-Please visit the website at <ulink url="&lfs-root;hlfs"/> for a list of current
-mirrors.</para>
-
-</sect2>
-
-<sect2 id="ch-scatter-contactinfo">
-<title>Contact information</title>
-
-<para>Please direct all your questions and comments to the appropriate mailing
-list (see above).</para>
-
-</sect2>
-
-</sect1>
Modified: trunk/BOOK/chapter01/askforhelp.xml
===================================================================
--- trunk/BOOK/chapter01/askforhelp.xml 2007-04-30 08:02:56 UTC (rev 1077)
+++ trunk/BOOK/chapter01/askforhelp.xml 2007-04-30 08:04:21 UTC (rev 1078)
@@ -1,98 +1,126 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+ "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % general-entities SYSTEM "../general.ent">
%general-entities;
]>
-<sect1 id="prepare-askforhelp">
-<title>How to ask for help</title>
-<?dbhtml filename="askforhelp.html"?>
-<para>If you run into a problem while working through this book, you should
-first check the FAQ at <ulink url="&faq-root;"/>—often your question
-is already answered there. If it is not, you should try to find the source of
-the problem. The following hint might give you some ideas for your
-troubleshooting: <ulink url="&hints-root;errors.txt"/>.</para>
+<sect1 id="ch-intro-askforhelp">
+ <?dbhtml filename="askforhelp.html"?>
-<para>If all that fails, you will find that most people on IRC and the mailing
-lists (see <xref linkend="ch-scatter-administrativa"/>) are willing to help
-you. But to assist them in diagnosing and solving your problem, please include
-all relevant information in your request for help.</para>
+ <title>Help</title>
-<sect2>
-<title>Things to mention</title>
-
-<para>Apart from a brief explanation of the problem you're having, the
-essential things to include in your request are:</para>
+ <para>If an issue or a question is encountered while working through
+ this book, check the FAQ page at <ulink url="&faq-root;#generalfaq"/>.
+ Questions are often already answered there. If your question is 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>
-<itemizedlist>
-<listitem><para>the version of the book you are using (being &version;),</para></listitem>
-<listitem><para>the host distribution and version you are using to create
-HLFS,</para></listitem>
-<listitem><para>the package or section giving you problems,</para></listitem>
-<listitem><para>the exact error message or symptom you are receiving,</para></listitem>
-<listitem><para>whether you have deviated from the book at all.</para></listitem>
-</itemizedlist>
+ <para>If you cannot find your problem listed in the FAQ, search the mailing
+ lists at <ulink url="&lfs-root;search.html"/>.</para>
-<note><para>Saying that you've deviated from the book doesn't mean
-that we won't help you. After all, LFS is about choice. It'll just
-help us to see other possible causes of your problem.</para></note>
+ <para>We also have a wonderful LFS community that is willing to offer
+ assistance through the mailing lists and IRC (see the <xref
+ linkend="ch-intro-resources"/> section of this book). However,
+ we get several support questions every day 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>
+ <sect2>
+ <title>Things to Mention</title>
-<sect2>
-<title>Configure problems</title>
+ <para>Apart from a brief explanation of the problem being experienced,
+ the essential things to include in any request for help are:</para>
-<para>When something goes wrong during the stage where the configure script
-is run, look through the <filename>config.log</filename> file. This file
-may contain errors encountered during configure which weren't printed to
-the screen. Include those relevant lines if you decide to ask for
-help.</para>
+ <itemizedlist>
+ <listitem>
+ <para>The version of the book being used (in this case &version;)</para>
+ </listitem>
+ <listitem>
+ <para>The host distribution and version being used to create LFS</para>
+ </listitem>
+ <listitem>
+ <para>The package or section the problem was encountered in</para>
+ </listitem>
+ <listitem>
+ <para>The exact error message or symptom being received</para>
+ </listitem>
+ <listitem>
+ <para>Note whether you have deviated from the book at all </para>
+ </listitem>
+ </itemizedlist>
-</sect2>
+ <note>
+ <para>Deviating from this book does <emphasis>not</emphasis> mean that
+ we will not help you. After all, LFS is about personal preference.
+ Being upfront about any changes to the established procedure helps us
+ evaluate and determine possible causes of your problem.</para>
+ </note>
-<sect2>
-<title>Compile problems</title>
+ </sect2>
-<para>To help us find the cause of the problem, both screen output and
-the contents of various files are useful. The screen output from both
-the ./configure script and the make run can be useful. Don't blindly
-include the whole thing but, on the other hand, don't include too little.
-As an example, here is some screen output from make:</para>
+ <sect2>
+ <title>Configure Script Problems</title>
-<screen><computeroutput>gcc -DALIASPATH=\"/mnt/hlfs/usr/share/locale:.\"
--DLOCALEDIR=\"/mnt/hlfs/usr/share/locale\" -DLIBDIR=\"/mnt/hlfs/usr/lib\"
--DINCLUDEDIR=\"/mnt/hlfs/usr/include\" -DHAVE_CONFIG_H -I. -I.
+ <para>If something goes wrong while running the <command>configure</command>
+ script, review the <filename>config.log</filename> file. This file may
+ contain errors encountered during <command>configure</command> which were
+ not printed to the screen. Include the <emphasis>relevant</emphasis> lines
+ if you need to ask for help.</para>
+
+ </sect2>
+
+ <sect2>
+ <title>Compilation Problems</title>
+
+ <para>Both the screen output and the contents of various files are useful
+ in determining the cause of compilation problems. The screen output from
+ the <command>configure</command> script and the <command>make</command>
+ run can be helpful. It is not necessary to include the entire output, but
+ do include enough of the relevant information. Below is an example of the
+ type of information to include from the screen output from
+ <command>make</command>:</para>
+
+<screen><computeroutput>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
+-DLOCALEDIR=\"/mnt/lfs/usr/share/locale\"
+-DLIBDIR=\"/mnt/lfs/usr/lib\"
+-DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I.
-g -O2 -c getopt1.c
-gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o expand.o file.o
-function.o getopt.o implicit.o job.o main.o misc.o read.o remake.o rule.o
-signame.o variable.o vpath.o default.o remote-stub.o version.o opt1.o
+gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o
+expand.o file.o function.o getopt.o implicit.o job.o main.o
+misc.o read.o remake.o rule.o signame.o variable.o vpath.o
+default.o remote-stub.o version.o opt1.o
-lutil job.o: In function `load_too_high':
-/hlfs/tmp/make-3.79.1/job.c:1565: undefined reference to `getloadavg'
+/lfs/tmp/make-3.79.1/job.c:1565: undefined reference
+to `getloadavg'
collect2: ld returned 1 exit status
make[2]: *** [make] Error 1
-make[2]: Leaving directory `/hlfs/tmp/make-3.79.1'
+make[2]: Leaving directory `/lfs/tmp/make-3.79.1'
make[1]: *** [all-recursive] Error 1
-make[1]: Leaving directory `/hlfs/tmp/make-3.79.1'
+make[1]: Leaving directory `/lfs/tmp/make-3.79.1'
make: *** [all-recursive-am] Error 2</computeroutput></screen>
-<para>In this case, many people just include the bottom section where it
-says:</para>
+ <para>In this case, many people would just include the bottom
+ section:</para>
<screen><computeroutput>make [2]: *** [make] Error 1</computeroutput></screen>
-<para>and onwards. This isn't enough for us to diagnose the problem because it
-only tells us that <emphasis>something</emphasis> went wrong, not
-<emphasis>what</emphasis> went wrong. The whole section, as in the example
-above, is what should be included to be helpful, because it includes the
-command that was executed and the command's error message(s).</para>
+ <para>This is not enough information to properly diagnose the problem
+ because it only notes that something went wrong, not
+ <emphasis>what</emphasis> went wrong. The entire section, as in the
+ example above, is what should be saved because it includes the command
+ that was executed and the associated error message(s).</para>
-<para>An excellent article on asking for help on the Internet in general
-has been written by Eric S. Raymond. It is available online at
-<ulink url="http://catb.org/~esr/faqs/smart-questions.html"/>.
-Read and follow the hints in that document and you are much more likely
-to get a response to start with and also to get the help you actually
-need.</para>
+ <para>An excellent article about asking for help on the Internet is
+ available online at <ulink
+ url="http://catb.org/~esr/faqs/smart-questions.html"/>. Read and
+ follow the hints in this document to increase the likelihood of getting
+ the help you need.</para>
-</sect2>
+ </sect2>
</sect1>
Modified: trunk/BOOK/chapter01/chapter01.xml
===================================================================
--- trunk/BOOK/chapter01/chapter01.xml 2007-04-30 08:02:56 UTC (rev 1077)
+++ trunk/BOOK/chapter01/chapter01.xml 2007-04-30 08:04:21 UTC (rev 1078)
@@ -6,13 +6,14 @@
]>
<chapter id="chapter-intro" xreflabel="Chapter 1">
-<?dbhtml dir="chapter01"?>
-<title>Introduction</title>
-<?dbhtml filename="chapter01.html"?>
+ <?dbhtml dir="chapter01"?>
+ <?dbhtml filename="chapter01.html"?>
-<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="how.xml"/>
-<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="changelog.xml"/>
-<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="administrativa.xml"/>
-<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="askforhelp.xml"/>
+ <title>Introduction</title>
+ <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="how.xml"/>
+ <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="changelog.xml"/>
+ <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="resources.xml"/>
+ <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="askforhelp.xml"/>
+
</chapter>
Modified: trunk/BOOK/chapter01/how.xml
===================================================================
--- trunk/BOOK/chapter01/how.xml 2007-04-30 08:02:56 UTC (rev 1077)
+++ trunk/BOOK/chapter01/how.xml 2007-04-30 08:04:21 UTC (rev 1078)
@@ -1,10 +1,11 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+ "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % general-entities SYSTEM "../general.ent">
%general-entities;
]>
-<sect1 id="ch-scatter-how">
+<sect1 id="ch-intro-how">
<?dbhtml filename="how.html"?>
<title>How to Build an HLFS System</title>
@@ -49,19 +50,14 @@
compiles, are completely independent of the previous toolchains and host
system.</para>
-<!--
-<para>FIX ME some code is commented until later sections are written</para>
-<para>To finish the installation, the 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 HLFS experience beyond this book. After
-the steps in this book have been implemented, the computer will be ready to
-reboot into the new HLFS system.</para>
--->
+ <para>To finish the installation, the bootscripts, kernel and boot loader are
+ set up in <xref linkend="chapter-bootable"/>. After the steps in this book
+ have been implemented, the computer will be ready to reboot into the new HLFS
+ system.</para>
+
<para>This is the process in a nutshell. Detailed information on each step is
discussed in the following chapters and package descriptions. Items that may
seem complicated will be clarified, and everything will fall into place as the
developer embarks on the HLFS adventure.</para>
</sect1>
-
Copied: trunk/BOOK/chapter01/resources.xml (from rev 1076, trunk/BOOK/chapter01/administrativa.xml)
===================================================================
--- trunk/BOOK/chapter01/resources.xml (rev 0)
+++ trunk/BOOK/chapter01/resources.xml 2007-04-30 08:04:21 UTC (rev 1078)
@@ -0,0 +1,92 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+ "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+ <!ENTITY % general-entities SYSTEM "../general.ent">
+ %general-entities;
+]>
+
+<sect1 id="ch-intro-resources">
+ <?dbhtml filename="resources.html"?>
+
+ <title>Resources</title>
+
+ <sect2 id="ch-intro-faq">
+ <title>FAQ</title>
+
+ <para>If during the building of the HLFS system you encounter any
+ errors, have any questions, or think there is a typo in the book,
+ please start by consulting the Frequently Asked Questions (FAQ)
+ that is located at <ulink url="&faq-root;"/>.</para>
+
+ </sect2>
+
+ <sect2 id="ch-intro-maillists" xreflabel="Chapter 1 - Mailing Lists">
+ <title>Mailing Lists</title>
+
+ <para>The <uri>linuxfromscratch.org</uri> server hosts a number of mailing
+ lists used for the development of the LFS project. These lists include the
+ main 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
+ <ulink url="&lfs-root;mail.html"/>.</para>
+
+ </sect2>
+
+ <!-- FIXME: Remove until such time as we have our own News Server, JH 20060105
+
+ <sect2 id="ch-intro-newsserver">
+ <title>News Server</title>
+
+ <para>The mailing lists hosted at <uri>linuxfromscratch.org</uri> are
+ also accessible via the Network News Transfer Protocol (NNTP) server.
+ All messages posted to a mailing list are copied to the corresponding
+ newsgroup, and vice versa.</para>
+
+ <para>The news server is located at
+ <uri>news.linuxfromscratch.org</uri>.</para>
+
+ </sect2> -->
+
+ <sect2 id="ch-intro-irc">
+ <title>IRC</title>
+
+ <para>Several members of the LFS community offer assistance on our
+ community Internet Relay Chat (IRC) network. Before using this support,
+ please make sure that your question is not already answered in the LFS
+ FAQ or the mailing list archives. You can find the IRC network at
+ <uri>irc.linuxfromscratch.org</uri>. The support channel is named
+ #LFS-support.</para>
+
+ </sect2>
+
+ <sect2 id="ch-intro-references">
+ <title>References</title>
+
+ <para>For additional information on the packages, useful tips are
+ available in the LFS Package Reference page located at <ulink
+ url="http://www.linuxfromscratch.org/~matthew/LFS-references.html"/>.</para>
+
+ </sect2>
+
+ <sect2 id="ch-intro-mirrors" xreflabel="Chapter 1 - Mirror sites">
+ <title>Mirror Sites</title>
+
+ <para>The LFS project has a number of world-wide mirrors to make accessing
+ the website and downloading the required packages more convenient. Please
+ visit the LFS website at <ulink url="&lfs-root;mirrors.html"/> for a list
+ of current mirrors.</para>
+
+ </sect2>
+
+ <sect2 id="ch-intro-contactinfo">
+ <title>Contact Information</title>
+
+ <para>Please direct all your questions and comments to one of the LFS
+ mailing lists (see above).</para>
+
+ </sect2>
+
+</sect1>
More information about the hlfs-book
mailing list