Begin of update. A lot of work still needs to be done. Document updated

to XML Docbook.
This commit is contained in:
fevrier 2005-08-07 22:27:54 +00:00
parent d97dbdd433
commit cd485528ad
1 changed files with 453 additions and 111 deletions

View File

@ -1,10 +1,15 @@
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V3.1//EN">
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
<!ENTITY email "jean DASH philippe DOT guerard AT tigreraye DOT org">
<!ENTITY tldpurl "http://www.tldp.org/HOWTO/Online-Troubleshooting-HOWTO/">
]>
<!-- $Id$ -->
<article>
<artheader>
<articleinfo>
<title>Online Troubleshooting Resources : HOWTO</title>
@ -13,18 +18,30 @@
<surname>Guérard</surname>
<affiliation>
<address>
<email>jean-philippe.guerard@laposte.net</email>
<email>&email;</email>
</address>
</affiliation>
</author>
<pubdate>2005-08-06</pubdate>
<releaseinfo>Version 1.6</releaseinfo>
<revhistory>
<revision>
<revnumber>1.6</revnumber>
<date>2005-08-06</date>
<authorinitials>JPG</authorinitials>
<revremark>
Added FOLDOC (thanks to Howard Mann for suggesting this).
</revremark>
</revision>
<revision>
<revnumber>1.5</revnumber>
<date>2002-10-20</date>
<authorinitials>jpg</authorinitials>
<authorinitials>JPG</authorinitials>
<revremark>
More dead links removal & URL updates.
More dead links removal &amp; URL updates.
Author and copyright updated as per Horward Mann request.
</revremark>
</revision>
@ -32,7 +49,7 @@
<revision>
<revnumber>1.4</revnumber>
<date>2002-03-04</date>
<authorinitials>jpg</authorinitials>
<authorinitials>JPG</authorinitials>
<revremark>
Dead links removal. Outdated links update. Revision of the
HOWTOs and FAQs sections.
@ -42,7 +59,7 @@
<revision>
<revnumber>1.3</revnumber>
<date>2000-07-24</date>
<authorinitials>hm</authorinitials>
<authorinitials>HM</authorinitials>
<revremark>
Update.
</revremark>
@ -51,7 +68,7 @@
<revision>
<revnumber>1.2</revnumber>
<date>1999-11-20</date>
<authorinitials>hm</authorinitials>
<authorinitials>HM</authorinitials>
<revremark>
Added "Introduction to Unix" to Unix section.
</revremark>
@ -60,7 +77,7 @@
<revision>
<revnumber>1.1</revnumber>
<date>1999-11-08</date>
<authorinitials>hm</authorinitials>
<authorinitials>HM</authorinitials>
<revremark>
Added Geocrawler.com to Mailing List Section. Convert to
DocBook.
@ -70,7 +87,7 @@
<revision>
<revnumber>0.5</revnumber>
<date>1999-09-18</date>
<authorinitials>hm</authorinitials>
<authorinitials>HM</authorinitials>
<revremark>
Initial release.
</revremark>
@ -78,153 +95,221 @@
</revhistory>
<abstract>
<para>
This document will direct Linux users to resources available on the Internet
that provide access to a vast amount of Linux-related information useful in
troubleshooting problems
<abstract><para>
Troubleshooting a Linux-related issue is often perceived as a difficult
task. But, often, the solution is just a few clicks away on the
internet.
</para>
</abstract>
</artheader>
<para>
This document will direct Linux users to resources available on the
Internet that provide access to a vast amount of Linux-related
information useful in the troubleshooting problems.
</para></abstract>
</articleinfo>
<sect1 id="intro">
<title>Introduction</title>
<para>The traditional means of troubleshooting computer-related problems
involves consulting user's manuals, books, friends - probably enticed with
goodies - and, when all the former do not yield a solution, calling the
technical support service of the vendor of the product in question. And, we all
know pleasant and reliably efficacious the latter stratagem is. Unfortunately,
this is the norm in the sphere of commercial proprietary products. </para>
<para>In contradistinction, Linux, and related distributions, utilities and
applications software, has largely been developed according to the <ulink
url="http://www.opensource.org" >Open Source</ulink> model, wherein developers
have used electronic communication over the Internet - typically in the form of
publically-accessible Mailing Lists - to collaborate with their peers in
the refinement of the associated source code. Such collaboration has
also traditionally involved the online publication of user's manuals,
lists of Frequently-Asked-Questions (FAQ's), knowledge bases, release
notes, formal guides such as this document (HOWTO's) and tutorials. In
addition, users often assist others through the forum of Usenet and
other newsgroups and the posted messages are readily accessible in the
form of searchable archives. These linux-related newsgroups are renowned
for their high level of user participation. In significant measure,
Linux may be considered a product of the Internet.</para>
<para>
<para>Considered together, these resources enable access to a large,
ever-expanding factual database, and my intent is to encourage and direct the
reader to utilize these repositories when faced with an issue not addressed in
the documentation that is included with each distribution of Linux. Linux
veterans who assist newcomers through the forum of Usenet soon become aware of
the frequency with which certain technical questions are repeatedly posted -
questions the answers to which are readily available in one or more of the
existent online repositories. So, to diminish the likelihood of being "flamed"
in response to your posted question on Usenet or irc , read further!</para>
The traditional means of troubleshooting computer-related problems
involves consulting user's manuals, books, friends - probably enticed
with goodies - and, when all the former do not yield a solution, calling
the technical support service of the vendor of the product in question.
And, we all know pleasant and reliably efficacious the latter stratagem
is. Unfortunately, this is the norm in the sphere of commercial
proprietary products.
<para>Armed with a browser, Linux users may rapidly become adept at
troubleshooting their systems. The key is knowing how and where to look. My
objective is to guide the user - particularly the Linux newbie - in this
quest.</para>
</para>
<para>
In contradistinction, Linux, and related distributions, utilities and
applications software, have largely been developed according to the
<ulink url="http://www.opensource.org" >Open Source</ulink> model,
wherein developers have used electronic communication over the Internet
- typically in the form of publically-accessible Mailing Lists - to
collaborate with their peers in the refinement of the associated source
code. Such collaboration has also traditionally involved the online
publication of user's manuals, lists of Frequently-Asked-Questions
(FAQ's), knowledge bases, release notes, formal guides such as this
document (HOWTO's) and tutorials. In addition, users often assist others
through the forum of Usenet and other newsgroups and the posted messages
are readily accessible in the form of searchable archives. These
linux-related newsgroups are renowned for their high level of user
participation. In significant measure, Linux may be considered a product
of the Internet.
</para>
<para>
Considered together, these resources enable access to a large,
ever-expanding factual database, and my intent is to encourage and
direct the reader to utilize these repositories when faced with an issue
not addressed in the documentation that is included with each
distribution of Linux. Linux veterans who assist newcomers through the
forum of Usenet soon become aware of the frequency with which certain
technical questions are repeatedly posted - questions the answers to
which are readily available in one or more of the existent online
repositories. So, to diminish the likelihood of being "flamed" in
response to your posted question on Usenet or irc, read further!
</para>
<para>
Armed with a browser, Linux users may rapidly become adept at
troubleshooting their systems. The key is knowing how and where to look.
My objective is to guide the user - particularly the Linux newbie - in
this quest.
</para>
</sect1>
<sect1 id="docupdates">
<title>Document Updates</title>
<para>The latest version of this document will always be available via the
<emphasis>HOWTO index</emphasis> at the <ulink
url="http://www.tldp.org">Linux Documentation Project</ulink>
The document will also be available in SGML, PS, PDF, and other
formats at that website.
</para>
<para>
The <ulink url="&tldpurl;">latest version</ulink> of this document
will always be available at the <ulink url="http://www.tldp.org">Linux
Documentation Project</ulink>. The document will also be available in
SGML, PS, PDF, and other formats at that website.
</para>
<sect2>
<title>Copyright and License</title>
<para>Copyright (c) 1999-2002 , by Jean-Philippe Guérard. This material
may be distributed only subject to the terms and conditions
set forth in the Open Publication Licence, v1.0 or later (the latest
version is presently available at <ulink url="http://www.opencontent.org/openpub/">
http://www.opencontent.org/openpub/</ulink>).
<para>
Copyright &copy; 1999-2005, by Jean-Philippe Guérard. This material may
be distributed only subject to the terms and conditions set forth in the
Open Publication Licence, v1.0 or later (see <xref linkend="openpub"/>).
</para>
</sect2>
<sect2>
<title>Feedback and Corrections</title>
<para>I always welcome feedback and constructive criticism. You can
reach me at <ulink url="mailto:jean-philippe.guerard@laposte.net">
jean-philippe.guerard@laposte.net</ulink>. In particular, I wish to be
notified about any errors in this document and resources you believe
deserving of inclusion, but not presently covered herein. Because the
assessment of the value of a particular resource is inherently
subjective, I do not guarantee that I will include it, but I will
certainly give any suggestion thoughtful consideration. In anticipation,
Thanks.
<para>
I always welcome feedback and constructive criticism. You can reach me
at <email>&email;</email>. In particular, I wish to be notified about
any errors in this document and resources you believe deserving of
inclusion, but not presently covered herein. Because the assessment of
the value of a particular resource is inherently subjective, I do not
guarantee that I will include it, but I will certainly give any
suggestion thoughtful consideration. In anticipation, Thanks.
</para>
</sect2>
<sect2>
<title>Document history</title>
<para>Howard Mann conceived and formulated the first version of this
HOWTO. He kept managing and updating it until version 1.3.
Maintainership was then taken over by Jean-Philippe Guérard, who is now
in charge of this document.
<para>
Howard Mann conceived and formulated the first version of this HOWTO. He
kept managing and updating it until version 1.3. Maintainership was then
taken over by Jean-Philippe Guérard, who is now in charge of this
document.
</para>
</sect2>
</sect1>
<sect1 id="howtos">
<title>HOWTOs and mini-HOWTOs</title>
<title>HOWTOs</title>
<para>HOWTOs are detailed reference documents on a specific subject,
usually following a step-by-step approach. A HOWTO is a good document to
help you discover a task or a topic you don't know. It will provide you
with the basic steps and the major references.</para>
<para>
<para>These documents are particularly useful when you decide to provide or
access a new service with your Linux system, or when you embark on a technically
complex project. For example, you may have the option of accessing the 'net with
a DSL or Cable Modem service - excellent guides are available in the form of
HOWTOs.</para>
HOWTOs are detailed reference documents on a specific subject, usually
following a step-by-step approach. A HOWTO is a good document to help
you discover a task or a topic you don't know. It will provide you with
the basic steps and the major references.
<para>Authors of these documents often include references and links to
sites that they have found useful. You may find the information you need
at one of these hyperlinked sites rather than in the HOWTO itself. For
example, I found <ulink url="http://www.scyld.com/network/">Linux
Network Drivers</ulink>, an interesting site for information about
Network
Interface Card drivers, in the Ethernet HOWTO.</para>
</para>
<para>To find HOWTOs, the first place to go is the <ulink
url="http://www.tldp.org">Linux Documentation Project (LDP)</ulink>.
The LDP includes a <ulink
url="http://www.tldp.org/HOWTO/HOWTO-INDEX/howtos.html">HOWTO
Index Page</ulink> that I suggest you bookmark in your browser.</para>
<para>
<para>These HOWTOs are written by Linux users and are periodically
updated by the authors. Many authors provide the latest version at a
personal website and a hyperlink to the latter is typically provided in
the document. This version may be newer than the one available at the
LDP website.</para>
These documents are particularly useful when you decide to provide or
access a new service with your Linux system, or when you embark on a
technically complex project. For example, you may have the option of
accessing the 'net with a DSL or Cable Modem service - excellent guides
are available in the form of HOWTOs.
<para>Note also that other HOWTOs are available, the authors of which
have not submitted them to the LDP. It is definitely worthwhile trying
to find these using an Internet search engine as I describe in a
subsequent section.</para>
</para>
<para>
Authors of these documents often include references and links to sites
that they have found useful. You may find the information you need at
one of these hyperlinked sites rather than in the HOWTO itself.
</para>
<!-- It would be nice to find a new relevant example to put here. -->
<para>
To find HOWTOs, the first place to go is the <ulink
url="http://www.tldp.org">Linux Documentation Project (LDP)</ulink>. The
LDP includes a <ulink
url="http://www.tldp.org/HOWTO/HOWTO-INDEX/howtos.html">HOWTO Index
Page</ulink> that I suggest you bookmark in your browser.
</para>
<para>
These HOWTOs are written by Linux users and are periodically updated by
the authors. Many authors provide the latest version at a personal
website and a hyperlink to the latter is typically provided in the
document. This version may be newer than the one available at the LDP
website.
</para>
<para>
Note also that other HOWTOs are available, the authors of which have not
submitted them to the LDP. It is definitely worthwhile trying to find
these using an Internet search engine as I describe in a subsequent
section.
</para>
<!-- Should I suggest here to use the "HOWTO" keyword in a google
search?
-->
</sect1>
<!-- Add a section about LDP guides? -->
<sect1 id="faqs">
<title>Frequently-Asked-Questions (FAQs)</title>
<para>Users of Internet Newsgroups and Mailing lists soon discovered
that some basic questions were being asked over and over again.
To provide an answer to these questions, and to avoid them
being repeated continually, FAQs were developed, listing the most
classical questions and their agreed answers.</para>
<para>
Users of Internet Newsgroups and Mailing lists soon discovered that some
basic questions were being asked over and over again. To provide an
answer to these questions, and to avoid them being repeated continually,
FAQs were developed, listing the most classical questions and their
agreed answers.
</para>
<para>A list of FAQs is also a traditional accompaniment to
Linux-related software. The FAQ is the first document to peruse when
@ -582,5 +667,262 @@ online.</para>
<para>Cheers and happy searching !</para>
</sect1>
</article>
<appendix id="openpub">
<title>Open Publication License</title>
<subtitle>v1.0, 8 June 1999</subtitle>
<sect1>
<title>REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED VERSIONS</title>
<para>
The Open Publication works may be reproduced and distributed in whole or
in part, in any medium physical or electronic, provided that the terms
of this license are adhered to, and that this license or an
incorporation of it by reference (with any options elected by the
author(s) and/or publisher) is displayed in the reproduction.
</para>
<para>
Proper form for an incorporation by reference is as follows:
</para>
<blockquote><para>
Copyright (c) &lt;year&gt; by &lt;author's name or designee&gt;. This
material may be distributed only subject to the terms and conditions set
forth in the Open Publication License, vX.Y or later (the latest version
is presently available at <ulink
url="http://www.opencontent.org/openpub/"></ulink>).
</para></blockquote>
<para>
The reference must be immediately followed with any options elected by
the author(s) and/or publisher of the document (see section VI).
</para>
<para>
Commercial redistribution of Open Publication-licensed material is
permitted.
</para>
<para>
Any publication in standard (paper) book form shall require the citation
of the original publisher and author. The publisher and author's names
shall appear on all outer surfaces of the book. On all outer surfaces of
the book the original publisher's name shall be as large as the title of
the work and cited as possessive with respect to the title.
</para>
</sect1>
<sect1>
<title>COPYRIGHT</title>
<para>
The copyright to each Open Publication is owned by its author(s) or
designee.
</para>
</sect1>
<sect1>
<title>SCOPE OF LICENSE</title>
<para>
The following license terms apply to all Open Publication works, unless
otherwise explicitly stated in the document.
</para>
<para>
Mere aggregation of Open Publication works or a portion of an Open
Publication work with other works or programs on the same media shall
not cause this license to apply to those other works. The aggregate work
shall contain a notice specifying the inclusion of the Open Publication
material and appropriate copyright notice.
</para>
<para>
SEVERABILITY. If any part of this license is found to be unenforceable
in any jurisdiction, the remaining portions of the license remain in
force.
</para>
<para>
NO WARRANTY. Open Publication works are licensed and provided "as is"
without warranty of any kind, express or implied, including, but not
limited to, the implied warranties of merchantability and fitness for a
particular purpose or a warranty of non-infringement.
</para>
</sect1>
<sect1>
<title>REQUIREMENTS ON MODIFIED WORKS</title>
<para>
All modified versions of documents covered by this license, including
translations, anthologies, compilations and partial documents, must meet
the following requirements:
</para>
<orderedlist>
<listitem><para>
The modified version must be labeled as such.
</para></listitem>
<listitem><para>
The person making the modifications must be identified and the
modifications dated.
</para></listitem>
<listitem><para>
Acknowledgement of the original author and publisher if applicable must
be retained according to normal academic citation practices.
</para></listitem>
<listitem><para>
The location of the original unmodified document must be identified.
</para></listitem>
<listitem><para>
The original author's (or authors') name(s) may not be used to assert or
imply endorsement of the resulting document without the original
author's (or authors') permission.
</para></listitem>
</orderedlist>
</sect1>
<sect1>
<title>GOOD-PRACTICE RECOMMENDATIONS</title>
<para>
In addition to the requirements of this license, it is requested from
and strongly recommended of redistributors that:
</para>
<orderedlist>
<listitem><para>
If you are distributing Open Publication works on hardcopy or CD-ROM,
you provide email notification to the authors of your intent to
redistribute at least thirty days before your manuscript or media
freeze, to give the authors time to provide updated documents. This
notification should describe modifications, if any, made to the
document.
</para></listitem>
<listitem><para>
All substantive modifications (including deletions) be either clearly
marked up in the document or else described in an attacHMent to the
document.
</para></listitem>
<listitem><para>
Finally, while it is not mandatory under this license, it is considered
good form to offer a free copy of any hardcopy and CD-ROM expression of
an Open Publication-licensed work to its author(s).
</para></listitem>
</orderedlist>
</sect1>
<sect1>
<title>LICENSE OPTIONS</title>
<para>
The author(s) and/or publisher of an Open Publication-licensed document
may elect certain options by appending language to the reference to or
copy of the license. These options are considered part of the license
instance and must be included with the license (or its incorporation by
reference) in derived works.
</para>
<orderedlist numeration="upperalpha">
<listitem><para>
To prohibit distribution of substantively modified versions without the
explicit permission of the author(s). "Substantive modification" is
defined as a change to the semantic content of the document, and
excludes mere changes in format or typographical corrections.
</para>
<para>
To accomplish this, add the phrase `Distribution of substantively
modified versions of this document is prohibited without the explicit
permission of the copyright holder.' to the license reference or copy.
</para></listitem>
<listitem><para>
To prohibit any publication of this work or derivative works in whole or
in part in standard (paper) book form for commercial purposes is
prohibited unless prior permission is obtained from the copyright
holder.
</para>
<para>
To accomplish this, add the phrase 'Distribution of the work or
derivative of the work in any standard (paper) book form is prohibited
unless prior permission is obtained from the copyright holder.' to the
license reference or copy.
</para></listitem>
</orderedlist>
</sect1>
</appendix>
</article>