os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Change occurences of FreeBSD to &os; since I brought in those entities

Browse source 
with my most recent changes.

Suggested by:	keramida
Approved by:	ceri (mentor) (implicitly)
This commit is contained in:
Mark Linimon 2004-05-24 04:02:46 +00:00
parent 3cb0ed22ac
commit 8b1f3f8e28
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=20986
1 changed files with 22 additions and 22 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

44
en_US.ISO8859-1/articles/problem-reports/article.sgml
View file

@ -11,7 +11,7 @@
<article>
<articleinfo>
<title>Writing FreeBSD Problem Reports</title>
<title>Writing &os; Problem Reports</title>
<pubdate>$FreeBSD$</pubdate>
@ -27,7 +27,7 @@
<abstract>
<para>This article describes how to best formulate and submit a
problem report to the FreeBSD Project.</para>
problem report to the &os; Project.</para>
</abstract>
<authorgroup>
@ -60,7 +60,7 @@
can be analyzed and dealt with swiftly, to the mutual
satisfaction of both user and developer.</para>
<para>Although the primary focus of this article is on FreeBSD
<para>Although the primary focus of this article is on &os;
problem reports, most of it should apply quite well to other
software projects.</para>
@ -142,11 +142,11 @@
mailing lists, or recently was; it may even already be fixed in
a newer version than what you are running. You should therefore
check all the obvious places before submitting your problem
report. For FreeBSD, this means:</para>
report. For &os;, this means:</para>
<itemizedlist>
<listitem>
<para>The FreeBSD
<para>The &os;
<ulink URL="../../books/faq/index.html">Frequently Asked
Questions</ulink> (FAQ) list.
The FAQ attempts to provide answers for a wide range of questions,
@ -166,7 +166,7 @@
lists</ulink>&mdash;if you are not subscribed, use
<ulink
URL="http://www.FreeBSD.org/search/search.html#mailinglists">the
searchable archives</ulink> on the FreeBSD web site. If your
searchable archives</ulink> 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>
@ -183,7 +183,7 @@
<listitem>
<para>Next, the searchable
<ulink URL="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query">
FreeBSD PR database</ulink> (GNATS). Unless your problem
&os; PR database</ulink> (GNATS). Unless your problem
is recent or obscure, there is a fair chance it has already
been reported.</para>
</listitem>
@ -217,15 +217,15 @@
<para>The first catch here is that if the problem is a bug in
third-party software (a port or a package you have installed), you
should report the bug to the original author, not to the FreeBSD
should report the bug to the original author, not to the &os;
Project. There are two exceptions to this rule: the first is if
the bug does not occur on other platforms, in which case the
problem may lie in how the software was ported to FreeBSD; the
problem may lie in how the software was ported to &os;; the
second is if the original author has already fixed the bug and
released a patch or a new version of his software, and the
FreeBSD port has not been updated yet.</para>
&os; port has not been updated yet.</para>
<para>The second catch is that FreeBSD's bug tracking system sorts
<para>The second catch is that &os;'s bug tracking system sorts
problem reports according to the category the originator
selected. Therefore, if you select the wrong category when you
submit your problem report, there is a good chance that it will
@ -237,7 +237,7 @@
<title>Writing the problem report</title>
<para>Now that you have decided that your issue merits a problem
report, and that it is a FreeBSD problem, it is time to write
report, and that it is a &os; problem, it is time to write
the actual problem report. Before we get into the mechanics
of the program used to generate and submit PRs, here are some
tips and tricks to help make sure that your PR will be most
@ -445,8 +445,8 @@
tracking of problem reports. If you cannot post mail messages
from the machine you're running &man.send-pr.1; on, your
problem report will not reach the GNATS database. For details
on the setup of mail on FreeBSD, see the <quote>Electronic
Mail</quote> chapter of the FreeBSD Handbook at
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>
</section>
@ -475,7 +475,7 @@
base utilities, a patch against &os.current; (the HEAD
CVS branch) is preferred since all new code should be applied
and tested there first. After appropriate or substantial testing
has been done, the code will be merged/migrated to the STABLE
has been done, the code will be merged/migrated to the &os.stable;
branch.</para>
<para>If you attach a patch inline, instead of as an attachment,
@ -528,7 +528,7 @@
<listitem>
<para><emphasis>Submitter-Id:</emphasis> Do not change this.
The default value of <literal>current-users</literal> is
correct, even if you run FreeBSD-STABLE.</para>
correct, even if you run &os.stable;.</para>
</listitem>
<listitem>
@ -548,7 +548,7 @@
<listitem>
<para><emphasis>Confidential:</emphasis> This is prefilled
to <literal>no</literal>. Changing it makes no sense as
there is no such thing as a confidential FreeBSD problem
there is no such thing as a confidential &os; problem
report&mdash;the PR database is distributed worldwide by
<application>CVSup</application>.</para>
</listitem>
@ -602,7 +602,7 @@
<itemizedlist>
<listitem>
<para><literal>advocacy:</literal> problems relating to
FreeBSD's public image. Rarely used.</para>
&os;'s public image. Rarely used.</para>
</listitem>
<listitem>
@ -688,7 +688,7 @@
<listitem>
<para><literal>www:</literal> Changes or enhancements to
the FreeBSD website.</para>
the &os; website.</para>
</listitem>
</itemizedlist>
</listitem>
@ -726,7 +726,7 @@
</listitem>
<listitem>
<para><emphasis>Release:</emphasis> The version of FreeBSD
<para><emphasis>Release:</emphasis> The version of &os;
that you are running. This is filled out automatically by
&man.send-pr.1; and need only be changed if you are
sending a problem report from a different system than the
@ -865,14 +865,14 @@
<para><ulink
url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">
How to Report Bugs Effectively</ulink>&mdash;an excellent
essay by Simon G. Tatham on composing useful (non-FreeBSD-specific)
essay by Simon G. Tatham on composing useful (non-&os;-specific)
problem reports.</para>
</listitem>
<listitem>
<para><ulink
url="../../articles/pr-guidelines/article.html">Problem
Report Handling Guidelines</ulink>&mdash;valuable insight
into how problem reports are handled by the FreeBSD
into how problem reports are handled by the &os;
developers.</para>
</listitem>
</itemizedlist>