Ignore:
Timestamp:
12/04/2004 11:07:21 AM (20 years ago)
Author:
Matthew Burgess <matthew@…>
Children:
522b09f
Parents:
a8f36125
Message:
  • (chapter01/*.xml) RELAX NG validation fixes

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter01/askforhelp.xml

    ra8f36125 ra0a2d970  
    11<?xml version="1.0" encoding="ISO-8859-1"?>
    2 <!DOCTYPE sect1 [
     2<!DOCTYPE section [
    33  <!ENTITY % general-entities SYSTEM "../general.ent">
    44  %general-entities;
    55]>
    6 <sect1 id="prepare-askforhelp">
    7 <title>How to ask for help</title>
     6<section xmlns="http://docbook.org/docbook-ng"
     7         xmlns:xlink="http://www.w3.org/1999/xlink"
     8         xml:id="prepare-askforhelp">
     9<info><title>How to ask for help</title></info>
    810<?dbhtml filename="askforhelp.html"?>
    911
    1012<para>If you run into a problem while working through this book, you should
    11 first check the FAQ at <ulink url="&faq-root;"/> -- often your question
     13first check the FAQ at <uri xlink:href="&faq-root;"/> -- often your question
    1214is already answered there. If it is not, you should try to find the source of
    1315the problem. The following hint might give you some ideas for your
    14 troubleshooting: <ulink url="&hints-root;errors.txt"/>.</para>
     16troubleshooting: <uri xlink:href="&hints-root;errors.txt">&hints-root;errors.txt</uri>.</para>
    1517
    1618<para>If all that fails, you will find that most people on IRC and the mailing
     
    1921all relevant information in your request for help.</para>
    2022
    21 <sect2>
    22 <title>Things to mention</title>
     23<section>
     24<info><title>Things to mention</title></info>
    2325 
    2426<para>Apart from a brief explanation of the problem you're having, the
     
    3840help us to see other possible causes of your problem.</para></note>
    3941
    40 </sect2>
     42</section>
    4143
    42 <sect2>
    43 <title>Configure problems</title>
     44<section>
     45<info><title>Configure problems</title></info>
    4446
    4547<para>When something goes wrong during the stage where the configure script
     
    4951help.</para>
    5052
    51 </sect2>
     53</section>
    5254
    53 <sect2>
    54 <title>Compile problems</title>
     55<section>
     56<info><title>Compile problems</title></info>
    5557
    5658<para>To help us find the cause of the problem, both screen output and
     
    8991<para>An excellent article on asking for help on the Internet in general
    9092has been written by Eric S. Raymond. It is available online at
    91 <ulink url="http://catb.org/~esr/faqs/smart-questions.html"/>.
     93<uri xlink:href="http://catb.org/~esr/faqs/smart-questions.html">http://catb.org/~esr/faqs/smart-questions.html"</uri>.
    9294Read and follow the hints in that document and you are much more likely
    9395to get a response to start with and also to get the help you actually
    9496need.</para>
    9597
    96 </sect2>
     98</section>
    9799
    98 <sect2>
    99 <title>Test suite problems</title>
     100<section>
     101<info><title>Test suite problems</title></info>
    100102
    101103<para>Many packages provide a test suite which, depending on the importance
    102104of the package, we may encourage you to run. Sometimes packages will
    103105generate false or expected failures. If you encounter these, you can check
    104 the LFS Wiki page at <ulink url="&wiki-root;"/> to see whether we have
    105 already noted and investigated them. If we already know
    106 about them, then usually there is no need to be concerned.</para>
     106the LFS Wiki page at <uri xlink:href="&wiki-root;">&wiki-root;</uri> to see
     107whether we have already noted and investigated them. If we already know about
     108them, then usually there is no need to be concerned.</para>
    107109
    108 </sect2>
     110</section>
    109111
    110 
    111 </sect1>
     112</section>
Note: See TracChangeset for help on using the changeset viewer.