eresources.html

来自「FreeBSD安装说明概述 FreeBSD 提供了一个以文字为主」· HTML 代码 · 共 1,329 行 · 第 1/3 页

target="_top">freebsd-performance</a></td>
<td>Performance tuning questions for high performance/load installations</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-platforms"
target="_top">freebsd-platforms</a></td>
<td>Concerning ports to non-Intel architecture platforms</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-ports"
target="_top">freebsd-ports</a></td>
<td>Discussion of the ports collection</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-ports-bugs"
target="_top">freebsd-ports-bugs</a></td>
<td>Discussion of the ports bugs/PRs</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-ppc"
target="_top">freebsd-ppc</a></td>
<td>Porting FreeBSD to the <span class="TRADEMARK">PowerPC</span>&reg;</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-qa"
target="_top">freebsd-qa</a></td>
<td>Discussion of Quality Assurance, usually pending a release</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-realtime"
target="_top">freebsd-realtime</a></td>
<td>Development of realtime extensions to FreeBSD</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-scsi"
target="_top">freebsd-scsi</a></td>
<td>The SCSI subsystem</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-security"
target="_top">freebsd-security</a></td>
<td>Security issues affecting FreeBSD</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-small"
target="_top">freebsd-small</a></td>
<td>Using FreeBSD in embedded applications</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-smp"
target="_top">freebsd-smp</a></td>
<td>Design discussions for [A]Symmetric MultiProcessing</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-sparc64"
target="_top">freebsd-sparc64</a></td>
<td>Porting FreeBSD to <span class="TRADEMARK">Sparc</span>&reg; based systems</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-standards"
target="_top">freebsd-standards</a></td>
<td>FreeBSD's conformance to the C99 and the <span class="TRADEMARK">POSIX</span>&reg;
standards</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-threads"
target="_top">freebsd-threads</a></td>
<td>Threading in FreeBSD</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-testing"
target="_top">freebsd-testing</a></td>
<td>FreeBSD Performance and Stability Tests</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-tokenring"
target="_top">freebsd-tokenring</a></td>
<td>Support Token Ring in FreeBSD</td>
</tr>
</tbody>
</table>
</div>

<p><span class="emphasis"><i class="EMPHASIS">Limited lists:</i></span> The following
lists are for more specialized (and demanding) audiences and are probably not of interest
to the general public. It is also a good idea to establish a presence in the technical
lists before joining one of these limited lists so that you will understand the
communications etiquette involved.</p>

<div class="INFORMALTABLE"><a id="AEN37487" name="AEN37487"></a>
<table border="0" frame="void" class="CALSTABLE">
<col />
<col />
<thead>
<tr>
<th>List</th>
<th>Purpose</th>
</tr>
</thead>

<tbody>
<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-hubs"
target="_top">freebsd-hubs</a></td>
<td>People running mirror sites (infrastructural support)</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-user-groups"
target="_top">freebsd-user-groups</a></td>
<td>User group coordination</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-vendors"
target="_top">freebsd-vendors</a></td>
<td>Vendors pre-release coordination</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-www"
target="_top">freebsd-www</a></td>
<td>Maintainers of <a href="../../../../index.html"
target="_top">www.FreeBSD.org</a></td>
</tr>
</tbody>
</table>
</div>

<p><span class="emphasis"><i class="EMPHASIS">Digest lists:</i></span> All of the above
lists are available in a digest format. Once subscribed to a list, you can change your
digest options in your account options section.</p>

<p><span class="emphasis"><i class="EMPHASIS">CVS lists:</i></span> The following lists
are for people interested in seeing the log messages for changes to various areas of the
source tree. They are <span class="emphasis"><i class="EMPHASIS">Read-Only</i></span>
lists and should not have mail sent to them.</p>

<div class="INFORMALTABLE"><a id="AEN37516" name="AEN37516"></a>
<table border="0" frame="void" class="CALSTABLE">
<col />
<col />
<col />
<thead>
<tr>
<th>List</th>
<th>Source area</th>
<th>Area Description (source for)</th>
</tr>
</thead>

<tbody>
<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/cvs-all"
target="_top">cvs-all</a></td>
<td><tt class="FILENAME">/usr/(CVSROOT|doc|ports|projects|src)</tt></td>
<td>All changes to any place in the tree (superset of other cvs commit lists)</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/cvs-doc"
target="_top">cvs-doc</a></td>
<td><tt class="FILENAME">/usr/doc</tt></td>
<td>All changes to the doc tree</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/cvs-ports"
target="_top">cvs-ports</a></td>
<td><tt class="FILENAME">/usr/ports</tt></td>
<td>All changes to the ports tree</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/cvs-projects"
target="_top">cvs-projects</a></td>
<td><tt class="FILENAME">/usr/projects</tt></td>
<td>All changes to the projects tree</td>
</tr>

<tr>
<td><a href="http://lists.FreeBSD.org/mailman/listinfo/cvs-src"
target="_top">cvs-src</a></td>
<td><tt class="FILENAME">/usr/src</tt></td>
<td>All changes to the src tree</td>
</tr>
</tbody>
</table>
</div>
</div>

<div class="SECT2">
<h2 class="SECT2"><a id="ERESOURCES-SUBSCRIBE" name="ERESOURCES-SUBSCRIBE">C.1.2. How to
Subscribe</a></h2>

<p>To subscribe to a list, click on the list name above or go to <a
href="http://lists.FreeBSD.org/mailman/listinfo"
target="_top">http://lists.FreeBSD.org/mailman/listinfo</a> and click on the list that
you are interested in. The list page should contain all of the necessary subscription
instructions.</p>

<p>To actually post to a given list you simply send mail to &lt;<var
class="REPLACEABLE">listname</var>@FreeBSD.org&gt;. It will then be redistributed to
mailing list members world-wide.</p>

<p>To unsubscribe yourself from a list, click on the URL found at the bottom of every
email received from the list. It is also possible to send an email to
freebsd-[listname][e-mail] to unsubscribe yourself.</p>

<p>Again, we would like to request that you keep discussion in the technical mailing
lists on a technical track. If you are only interested in important announcements then it
is suggested that you join the <a
href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-announce" target="_top">FreeBSD
announcements 邮件列表</a>, which is intended only for infrequent traffic.</p>
</div>

<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 邮件列表</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-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 <span class="CITEREFENTRY"><span
class="REFENTRYTITLE">send-pr</span>(1)</span> 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>