diff options
Diffstat (limited to 'chapter02/askforhelp.xml')
| -rw-r--r-- | chapter02/askforhelp.xml | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/chapter02/askforhelp.xml b/chapter02/askforhelp.xml index e36f36b15..6fb4becec 100644 --- a/chapter02/askforhelp.xml +++ b/chapter02/askforhelp.xml @@ -4,9 +4,9 @@ <para>If you encounter a problem while using this book, and your problem is not listed in the FAQ, you will find that most of the people on Internet -Relay Chat (IRC) and on the mailing lists are willing to help you. (An +Relay Chat (IRC) and on the mailing lists are willing to help you. An overview of the LFS mailing lists can be found in -<xref linkend="ch01-maillists"/>.) To assist us in diagnosing and solving +<xref linkend="ch01-maillists"/>. To assist us in diagnosing and solving your problem, include as much relevant information as possible in your request for help.</para> @@ -18,7 +18,7 @@ essential things to include in your request are:</para> <itemizedlist> <listitem><para>the version of the book you are using (being &version;),</para></listitem> -<listitem><para>the package or section you are having problems with,</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> @@ -34,8 +34,8 @@ help us to see other possible causes of your problem.)</para> <para>When something goes wrong during the stage where the configure script is run, look at the last lines of the -<filename>config.log</filename>. This file contains possible errors -encountered during configure which aren't always printed to the screen. +<filename>config.log</filename>. 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> </sect2> @@ -45,9 +45,9 @@ Include those relevant lines if you decide to ask for help.</para> <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 when make is 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> +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> <para><screen>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\" -DLOCALEDIR=\"/mnt/lfs/usr/share/locale\" -DLIBDIR=\"/mnt/lfs/usr/lib\" @@ -69,15 +69,15 @@ make: *** [all-recursive-am] Error 2</screen></para> says <screen>make [2]: *** [make] Error 1</screen> 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 -quoted above is what should be included to be helpful, because it +<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>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://www.tuxedo.org/~esr/faqs/smart-questions.html"/>. -Read and follow the hints in this document and you are much more likely +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> |