diff options
Diffstat (limited to 'zh_TW.Big5/articles/problem-reports/article.xml')
| -rw-r--r-- | zh_TW.Big5/articles/problem-reports/article.xml | 123 |
1 files changed, 56 insertions, 67 deletions
diff --git a/zh_TW.Big5/articles/problem-reports/article.xml b/zh_TW.Big5/articles/problem-reports/article.xml index bdb7d37812..9839393ffc 100644 --- a/zh_TW.Big5/articles/problem-reports/article.xml +++ b/zh_TW.Big5/articles/problem-reports/article.xml @@ -1,14 +1,13 @@ <?xml version="1.0" encoding="big5"?> -<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN" - "../../../share/xml/freebsd45.dtd"> - -<article lang='zh_tw'> - <articleinfo> - <title>Writing &os; Problem Reports</title> +<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN" + "../../../share/xml/freebsd50.dtd"> +<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="zh_tw"> + <info><title>Writing &os; Problem Reports</title> + <pubdate>$FreeBSD$</pubdate> - <legalnotice id="trademarks" role="trademarks"> + <legalnotice xml:id="trademarks" role="trademarks"> &tm-attrib.freebsd; &tm-attrib.cvsup; &tm-attrib.ibm; @@ -24,24 +23,17 @@ </abstract> <authorgroup> - <author> - <firstname>Dag-Erling</firstname> - <surname>Smørgrav</surname> - <contrib>Contributed by </contrib> - </author> - - <author> - <firstname>Mark</firstname> - <surname>Linimon</surname> - </author> + <author><personname><firstname>Dag-Erling</firstname><surname>Smørgrav</surname></personname><contrib>Contributed by </contrib></author> + + <author><personname><firstname>Mark</firstname><surname>Linimon</surname></personname></author> </authorgroup> <releaseinfo>$FreeBSD$</releaseinfo> - </articleinfo> + </info> <indexterm><primary>problem reports</primary></indexterm> - <section id="pr-intro"> + <section xml:id="pr-intro"> <title>Introduction</title> <para>One of the most frustrating experiences one can have as a @@ -70,7 +62,7 @@ step-by-step tutorial.</para> </section> - <section id="pr-when"> + <section xml:id="pr-when"> <title>When to submit a problem report</title> <para>There are many types of problems, and not all of them should @@ -114,7 +106,7 @@ system components such as BIND or various GNU utilities).</para> - <para>For unmaintained ports (<makevar>MAINTAINER</makevar> contains + <para>For unmaintained ports (<varname>MAINTAINER</varname> contains <literal>ports@FreeBSD.org</literal>), such update notifications might get picked up by an interested committer, or you might be asked to provide a patch to update @@ -127,9 +119,8 @@ a new version, they have probably worked with the developers on it, they are probably testing to see there is no regression, etc.</para> - <para>In either case, following the process described in <ulink - url="&url.books.porters-handbook;/port-upgrading.html">Porter's - Handbook</ulink> will yield the best results.</para> + <para>In either case, following the process described in <link xlink:href="&url.books.porters-handbook;/port-upgrading.html">Porter's + Handbook</link> will yield the best results.</para> </listitem> </itemizedlist> @@ -191,16 +182,16 @@ <para>If the problem is in the base system, you should first read the FAQ section on - <ulink url="&url.books.faq;/introduction.html#LATEST-VERSION"> - &os; versions</ulink>, if you are not already familiar with + <link xlink:href="&url.books.faq;/introduction.html#LATEST-VERSION"> + &os; versions</link>, if you are not already familiar with the topic. It is not possible for &os; to fix problems in anything other than certain recent branches of the base system, so filing a bug report about an older version will probably only result in a developer advising you to upgrade to a supported version to see if the problem still recurs. The Security Officer team maintains the - <ulink url="http://www.freebsd.org/security/">list of supported - versions</ulink>.</para> + <link xlink:href="http://www.freebsd.org/security/">list of supported + versions</link>.</para> <para>If the problem is in a port, note that you must first upgrade to the latest version of the Ports Collection and see @@ -210,7 +201,7 @@ with older version of applications simply cannot be fixed.</para> </section> - <section id="pr-prep"> + <section xml:id="pr-prep"> <title>Preparations</title> <para>A good rule to follow is to always do a background search @@ -224,26 +215,24 @@ <itemizedlist> <listitem> <para>The &os; - <ulink url="&url.books.faq;/index.html">Frequently Asked - Questions</ulink> (FAQ) list. + <link xlink:href="&url.books.faq;/index.html">Frequently Asked + Questions</link> (FAQ) list. The FAQ attempts to provide answers for a wide range of questions, such as those concerning - <ulink url="&url.books.faq;/hardware.html">hardware - compatibility</ulink>, - <ulink url="&url.books.faq;/applications.html">user - applications</ulink>, - and <ulink url="&url.books.faq;/kernelconfig.html">kernel - configuration</ulink>.</para> + <link xlink:href="&url.books.faq;/hardware.html">hardware + compatibility</link>, + <link xlink:href="&url.books.faq;/applications.html">user + applications</link>, + and <link xlink:href="&url.books.faq;/kernelconfig.html">kernel + configuration</link>.</para> </listitem> <listitem> <para>The - <ulink - url="&url.books.handbook;/eresources.html#ERESOURCES-MAIL">mailing - lists</ulink>—if you are not subscribed, use - <ulink - url="http://www.FreeBSD.org/search/search.html#mailinglists">the - searchable archives</ulink> on the &os; web site. If your + <link xlink:href="&url.books.handbook;/eresources.html#ERESOURCES-MAIL">mailing + lists</link>—if you are not subscribed, use + <link xlink:href="http://www.FreeBSD.org/search/search.html#mailinglists">the + searchable archives</link> on the &os; web site. If your problem has not been discussed on the lists, you might try posting a message about it and waiting a few days to see if someone can spot something you have overlooked.</para> @@ -259,8 +248,8 @@ <listitem> <para>Next, the searchable - <ulink url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query"> - &os; PR database</ulink> (GNATS). Unless your problem + <link xlink:href="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query"> + &os; PR database</link> (GNATS). Unless your problem is recent or obscure, there is a fair chance it has already been reported.</para> </listitem> @@ -273,7 +262,7 @@ carefully study the contents of the <filename>/usr/src/UPDATING</filename> file on your system or its latest version at - <ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi/src/UPDATING"></ulink>. + <uri xlink:href="http://www.FreeBSD.org/cgi/cvsweb.cgi/src/UPDATING">http://www.FreeBSD.org/cgi/cvsweb.cgi/src/UPDATING</uri>. (This is vital information if you are upgrading from one version to another—especially if you are upgrading to the @@ -284,15 +273,15 @@ <filename>/usr/ports/UPDATING</filename> (for individual ports) or <filename>/usr/ports/CHANGES</filename> (for changes that affect the entire Ports Collection). - <ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/UPDATING"></ulink> + <uri xlink:href="http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/UPDATING">http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/UPDATING</uri> and - <ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/CHANGES"></ulink> + <uri xlink:href="http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/CHANGES">http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/CHANGES</uri> are also available via CVSweb.</para> </listitem> </itemizedlist> </section> - <section id="pr-writing"> + <section xml:id="pr-writing"> <title>Writing the problem report</title> <para>Now that you have decided that your issue merits a problem @@ -435,7 +424,7 @@ <listitem> <para>any environment variables that override the defaults in <filename>bsd.port.mk</filename>, such - as <makevar>PORTSDIR</makevar></para> + as <varname>PORTSDIR</varname></para> </listitem> <listitem> <para>the fact that you have read @@ -466,7 +455,7 @@ a similar PR.</emphasis> Although this has already been mentioned above, it bears repeating here. It only take a minute or two to use the web-based search engine at - <ulink url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query"></ulink>. + <uri xlink:href="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query">http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query</uri>. (Of course, everyone is guilty of forgetting to do this now and then.)</para> </listitem> @@ -477,7 +466,7 @@ offer patches, but also justification for why the patches are <quote>The Right Thing To Do</quote>. As noted above, a careful search of the mailing lists using the archives - at <ulink url="http://www.FreeBSD.org/search/search.html#mailinglists"></ulink> + at <uri xlink:href="http://www.FreeBSD.org/search/search.html#mailinglists">http://www.FreeBSD.org/search/search.html#mailinglists</uri> is always good preparation.</para> </listitem> @@ -508,7 +497,7 @@ problem report will not reach the GNATS database. For details on the setup of mail on &os;, see the <quote>Electronic Mail</quote> chapter of the &os; Handbook at - <ulink url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mail.html"></ulink>.</para> + <uri xlink:href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mail.html">http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mail.html</uri>.</para> <para>Make sure that your mailer will not mangle the message on its way to GNATS. In particular, if your mailer automatically @@ -747,7 +736,7 @@ </note> <para>Here is the current list of categories (taken from - <ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi/src/gnu/usr.bin/send-pr/categories"></ulink>):</para> + <uri xlink:href="http://www.FreeBSD.org/cgi/cvsweb.cgi/src/gnu/usr.bin/send-pr/categories">http://www.FreeBSD.org/cgi/cvsweb.cgi/src/gnu/usr.bin/send-pr/categories</uri>):</para> <itemizedlist> <listitem> @@ -994,7 +983,7 @@ </section> - <section id="pr-followup"> + <section xml:id="pr-followup"> <title>Follow-up</title> <para>Once your problem report has been filed, you will receive a @@ -1016,8 +1005,8 @@ <listitem> <para>The easiest way is to use the followup link on the individual PR's web page, which you can reach from the - <ulink url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query"> - PR search page</ulink>. Clicking on this link will bring up an + <link xlink:href="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query"> + PR search page</link>. Clicking on this link will bring up an an email window with the correct To: and Subject: lines filled in (if your browser is configured to do this).</para> </listitem> @@ -1049,7 +1038,7 @@ possible, explaining how or when the problem was fixed.</para> </section> - <section id="pr-problems"> + <section xml:id="pr-problems"> <title>If you are having problems</title> <para>Most PRs go through the system and are accepted quickly; @@ -1080,15 +1069,15 @@ may have happened is that the database index has gotten out of synchronization with the database itself. The way that you can test whether this has happened is to pull up the - <ulink url="http://www.FreeBSD.org/cgi/query-pr.cgi"> - view a single PR</ulink> page and see whether the PR shows up. + <link xlink:href="http://www.FreeBSD.org/cgi/query-pr.cgi"> + view a single PR</link> page and see whether the PR shows up. If it does, please notify the GNATS administrators at <email>bugmeister@FreeBSD.org</email>. Note that there is a <literal>cron</literal> job that periodically rebuilds the database, so unless you are in a hurry, no action needs to be taken.</para> </section> - <section id="pr-further"> + <section xml:id="pr-further"> <title>Further Reading</title> <para>This is a list of resources relevant to the proper writing @@ -1096,19 +1085,19 @@ <itemizedlist> <listitem> - <para><ulink - url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"> - How to Report Bugs Effectively</ulink>—an excellent + <para><link xlink:href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"> + How to Report Bugs Effectively</link>—an excellent essay by Simon G. Tatham on composing useful (non-&os;-specific) problem reports.</para> </listitem> <listitem> - <para><ulink - url="&url.articles.pr-guidelines;/article.html">Problem - Report Handling Guidelines</ulink>—valuable insight + <para><link xlink:href="&url.articles.pr-guidelines;/article.html">Problem + Report Handling Guidelines</link>—valuable insight into how problem reports are handled by the &os; developers.</para> </listitem> </itemizedlist> </section> + + <index/> </article> |