eresources.html

FreeBSD操作系统的详细使用手册

<div class="SECT2">
<h2 class="SECT2"><a id="ERESOURCES-CHARTERS" name="ERESOURCES-CHARTERS">C.1.3 List
Charters</a></h2>

<p><span class="emphasis"><i class="EMPHASIS">All</i></span> FreeBSD mailing lists have
certain basic rules which must be adhered to by anyone using them. Failure to comply with
these guidelines will result in two (2) written warnings from the FreeBSD Postmaster
<code class="EMAIL">&#60;<a
href="mailto:[e-mail]">[e-mail]</a>&#62;</code>, after which,
on a third offense, the poster will removed from all FreeBSD mailing lists and filtered
from further posting to them. We regret that such rules and measures are necessary at
all, but today's Internet is a pretty harsh environment, it would seem, and many fail to
appreciate just how fragile some of its mechanisms are.</p>

<p>Rules of the road:</p>

<ul>
<li>
<p>The topic of any posting should adhere to the basic charter of the list it is posted
to, e.g. if the list is about technical issues then your posting should contain technical
discussion. Ongoing irrelevant chatter or flaming only detracts from the value of the
mailing list for everyone on it and will not be tolerated. For free-form discussion on no
particular topic, the <a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-chat"
target="_top">FreeBSD chat mailing list</a> is freely available and should be used
instead.</p>
</li>

<li>
<p>No posting should be made to more than 2 mailing lists, and only to 2 when a clear and
obvious need to post to both lists exists. For most lists, there is already a great deal
of subscriber overlap and except for the most esoteric mixes (say ``-stable &amp;
-scsi''), there really is no reason to post to more than one list at a time. If a message
is sent to you in such a way that multiple mailing lists appear on the <var
class="LITERAL">Cc</var> line then the <var class="LITERAL">Cc</var> line should also be
trimmed before sending it out again. <span class="emphasis"><i class="EMPHASIS">You are
still responsible for your own cross-postings, no matter who the originator might have
been.</i></span></p>
</li>

<li>
<p>Personal attacks and profanity (in the context of an argument) are not allowed, and
that includes users and developers alike. Gross breaches of netiquette, like excerpting
or reposting private mail when permission to do so was not and would not be forthcoming,
are frowned upon but not specifically enforced. <span class="emphasis"><i
class="EMPHASIS">However</i></span>, there are also very few cases where such content
would fit within the charter of a list and it would therefore probably rate a warning (or
ban) on that basis alone.</p>
</li>

<li>
<p>Advertising of non-FreeBSD related products or services is strictly prohibited and
will result in an immediate ban if it is clear that the offender is advertising by
spam.</p>
</li>
</ul>

<p><span class="emphasis"><i class="EMPHASIS">Individual list charters:</i></span></p>

<div class="VARIABLELIST">
<dl>
<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-acpi"
target="_top">freebsd-acpi</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">ACPI and power management
development</i></span></p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-afs"
target="_top">freebsd-afs</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">Andrew File System</i></span></p>

<p>This list is for discussion on porting and using AFS from CMU/Transarc</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-announce"
target="_top">freebsd-announce</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">Important events /
milestones</i></span></p>

<p>This is the mailing list for people interested only in occasional announcements of
significant FreeBSD events. This includes announcements about snapshots and other
releases. It contains announcements of new FreeBSD capabilities. It may contain calls for
volunteers etc. This is a low volume, strictly moderated mailing list.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-arch"
target="_top">freebsd-arch</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">Architecture and design
discussions</i></span></p>

<p>This list is for discussion of the FreeBSD architecture. Messages will mostly be kept
strictly technical in nature. Examples of suitable topics are:</p>

<ul>
<li>
<p>How to re-vamp the build system to have several customized builds running at the same
time.</p>
</li>

<li>
<p>What needs to be fixed with VFS to make Heidemann layers work.</p>
</li>

<li>
<p>How do we change the device driver interface to be able to use the same drivers
cleanly on many buses and architectures.</p>
</li>

<li>
<p>How to write a network driver.</p>
</li>
</ul>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-audit"
target="_top">freebsd-audit</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">Source code audit project</i></span></p>

<p>This is the mailing list for the FreeBSD source code audit project. Although this was
originally intended for security-related changes, its charter has been expanded to review
any code changes.</p>

<p>This list is very heavy on patches, and is probably of no interest to the average
FreeBSD user. Security discussions not related to a particular code change are held on
freebsd-security. Conversely, all developers are encouraged to send their patches here
for review, especially if they touch a part of the system where a bug may adversely
affect the integrity of the system.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-binup"
target="_top">freebsd-binup</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">FreeBSD Binary Update
Project</i></span></p>

<p>This list exists to provide discussion for the binary update system, or <b
class="APPLICATION">binup</b>. Design issues, implementation details, patches, bug
reports, status reports, feature requests, commit logs, and all other things related to
<b class="APPLICATION">binup</b> are fair game.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-bugbusters"
target="_top">freebsd-bugbusters</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">Coordination of the Problem Report handling
effort</i></span></p>

<p>The purpose of this list is to serve as a coordination and discussion forum for the
Bugmeister, his Bugbusters, and any other parties who have a genuine interest in the PR
database. This list is not for discussions about specific bugs, patches or PRs.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-bugs"
target="_top">freebsd-bugs</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">Bug reports</i></span></p>

<p>This is the mailing list for reporting bugs in FreeBSD. Whenever possible, bugs should
be submitted using the <a
href="http://www.FreeBSD.org/cgi/man.cgi?query=send-pr&sektion=1"><span
class="CITEREFENTRY"><span class="REFENTRYTITLE">send-pr</span>(1)</span></a> command or
the <a href="../../../../send-pr.html" target="_top">WEB interface</a> to it.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-chat"
target="_top">freebsd-chat</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">Non technical items related to the FreeBSD
community</i></span></p>

<p>This list contains the overflow from the other lists about non-technical, social
information. It includes discussion about whether Jordan looks like a toon ferret or not,
whether or not to type in capitals, who is drinking too much coffee, where the best beer
is brewed, who is brewing beer in their basement, and so on. Occasional announcements of
important events (such as upcoming parties, weddings, births, new jobs, etc) can be made
to the technical lists, but the follow ups should be directed to this -chat list.</p>
</dd>

<dt>freebsd-core</dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">FreeBSD core team</i></span></p>

<p>This is an internal mailing list for use by the core members. Messages can be sent to
it when a serious FreeBSD-related matter requires arbitration or high-level scrutiny.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-current"
target="_top">freebsd-current</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">Discussions about the use of
FreeBSD-CURRENT</i></span></p>

<p>This is the mailing list for users of FreeBSD-CURRENT. It includes warnings about new
features coming out in -CURRENT that will affect the users, and instructions on steps
that must be taken to remain -CURRENT. Anyone running ``CURRENT'' must subscribe to this
list. This is a technical mailing list for which strictly technical content is
expected.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-cvsweb"
target="_top">freebsd-cvsweb</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">FreeBSD CVSweb Project</i></span></p>

<p>Technical discussions about use, development and maintenance of FreeBSD-CVSweb.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-doc"
target="_top">freebsd-doc</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">Documentation project</i></span></p>

<p>This mailing list is for the discussion of issues and projects related to the creation
of documentation for FreeBSD. The members of this mailing list are collectively referred
to as ``The FreeBSD Documentation Project''. It is an open list; feel free to join and
contribute!</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-firewire"
target="_top">freebsd-firewire</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS"><span class="TRADEMARK">FireWire</span>
(iLink, IEEE 1394)</i></span></p>

<p>This is a mailing list for discussion of the design and implementation of a <span
class="TRADEMARK">FireWire</span> (aka IEEE 1394 aka iLink) subsystem for FreeBSD.
Relevant topics specifically include the standards, bus devices and their protocols,
adapter boards/cards/chips sets, and the architecture and implementation of code for
their proper support.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-fs"
target="_top">freebsd-fs</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">File systems</i></span></p>

<p>Discussions concerning FreeBSD file systems. This is a technical mailing list for
which strictly technical content is expected.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-geom"
target="_top">freebsd-geom</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">GEOM</i></span></p>

<p>Discussions specific to GEOM and related implementations. This is a technical mailing
list for which strictly technical content is expected.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-gnome"
target="_top">freebsd-gnome</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">GNOME</i></span></p>

<p>Discussions concerning The <b class="APPLICATION">GNOME</b> Desktop Environment for
FreeBSD systems. This is a technical mailing list for which strictly technical content is
expected.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-ipfw"
target="_top">freebsd-ipfw</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">IP Firewall</i></span></p>

<p>This is the forum for technical discussions concerning the redesign of the IP firewall
code in FreeBSD. This is a technical mailing list for which strictly technical content is
expected.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-ia64"
target="_top">freebsd-ia64</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">Porting FreeBSD to IA64</i></span></p>

<p>This is a technical mailing list for individuals actively working on porting FreeBSD
to the IA-64 platform from Intel, to bring up problems or discuss alternative solutions.
Individuals interested in following the technical discussion are also welcome.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-isdn"
target="_top">freebsd-isdn</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">ISDN Communications</i></span></p>

<p>This is the mailing list for people discussing the development of ISDN support for
FreeBSD.</p>
</dd>

<dt><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-java"
target="_top">freebsd-java</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS"><span class="TRADEMARK">Java</span>
Development</i></span></p>

<p>This is the mailing list for people discussing the development of significant <span
class="TRADEMARK">Java</span> applications for FreeBSD and the porting and maintenance of
<span class="TRADEMARK">JDK</span>s.</p>
</dd>

<dt><a id="ERESOURCES-CHARTERS-JOBS" name="ERESOURCES-CHARTERS-JOBS"></a><a
href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-jobs"
target="_top">freebsd-jobs</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">Jobs offered and sought</i></span></p>

<p>This is a forum for posting employment notices and resumes specifically related to
FreeBSD, e.g. if you're seeking FreeBSD-related employment or have a job involving
FreeBSD to advertise then this is the right place. This is <span class="emphasis"><i
class="EMPHASIS">not</i></span> a mailing list for general employment issues since
adequate forums for that already exist elsewhere.</p>

<p>Note that this list, like other FreeBSD.org mailing lists, is distributed worldwide.
Thus, you need to be clear about location and the extent to which telecommuting or
assistance with relocation is available.</p>

<p>Email should use open formats only -- preferably plain text, but basic Portable
Document Format (<acronym class="ACRONYM">PDF</acronym>), HTML, and a few others are
acceptable to many readers. Closed formats such as <span
class="TRADEMARK">Microsoft</span>&reg; Word (<tt class="FILENAME">.doc</tt>) will be
rejected by the mailing list server.</p>
</dd>

<dt><a href="http://freebsd.kde.org/mailman/listinfo/kde-freebsd"
target="_top">freebsd-kde</a></dt>

<dd>
<p><span class="emphasis"><i class="EMPHASIS">KDE</i></span></p>