aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/books/handbook/eresources
diff options
context:
space:
mode:
authorGabor Kovesdan <gabor@FreeBSD.org>2013-02-05 09:14:34 +0000
committerGabor Kovesdan <gabor@FreeBSD.org>2013-02-05 09:14:34 +0000
commita06603e1e8c43dac65e769d0577e15561dde3acb (patch)
tree56789ede4270141e038c244e602fe2503127b62f /en_US.ISO8859-1/books/handbook/eresources
parent5be98520031882d40220ca83d603138abb7ef89a (diff)
parentfbf79ce9835e43f0e5de684052af39c914b817ab (diff)
downloaddoc-a06603e1e8c43dac65e769d0577e15561dde3acb.tar.gz
doc-a06603e1e8c43dac65e769d0577e15561dde3acb.zip
- MFH
Notes
Notes: svn path=/projects/xml-tools/; revision=40889
Diffstat (limited to 'en_US.ISO8859-1/books/handbook/eresources')
-rw-r--r--en_US.ISO8859-1/books/handbook/eresources/chapter.xml1060
1 files changed, 594 insertions, 466 deletions
diff --git a/en_US.ISO8859-1/books/handbook/eresources/chapter.xml b/en_US.ISO8859-1/books/handbook/eresources/chapter.xml
index b7091fe6ae..860935c5fc 100644
--- a/en_US.ISO8859-1/books/handbook/eresources/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/eresources/chapter.xml
@@ -8,18 +8,19 @@
<appendix id="eresources">
<title>Resources on the Internet</title>
- <para>The rapid pace of FreeBSD progress makes print media impractical as a
- means of following the latest developments. Electronic resources are the
- best, if not often the only, way to stay informed of the latest advances.
- Since FreeBSD is a volunteer effort, the user community itself also
- generally serves as a <quote>technical support department</quote> of sorts,
- with electronic mail, web forums, and USENET news being the most
+ <para>The rapid pace of FreeBSD progress makes print media
+ impractical as a means of following the latest developments.
+ Electronic resources are the best, if not often the only, way
+ to stay informed of the latest advances. Since FreeBSD is a
+ volunteer effort, the user community itself also generally serves
+ as a <quote>technical support department</quote> of sorts, with
+ electronic mail, web forums, and USENET news being the most
effective way of reaching that community.</para>
- <para>The most important points of contact with the FreeBSD user community
- are outlined below. If you are aware of other resources not mentioned
- here, please send them to the &a.doc; so that they may also be
- included.</para>
+ <para>The most important points of contact with the FreeBSD user
+ community are outlined below. If you are aware of other resources
+ not mentioned here, please send them to the &a.doc; so that they
+ may also be included.</para>
<sect1 id="eresources-mail">
<title>Mailing Lists</title>
@@ -31,45 +32,50 @@
most appropriate mailing list will invariably assure a faster
and more accurate response.</para>
- <para>The charters for the various lists are given at the bottom of this
- document. <emphasis>Please read the charter before joining or sending
- mail to any list</emphasis>. Most of our list subscribers now receive
- many hundreds of FreeBSD related messages every day, and by setting down
- charters and rules for proper use we are striving to keep the
- signal-to-noise ratio of the lists high. To do less would see the
- mailing lists ultimately fail as an effective communications medium for
- the project.</para>
+ <para>The charters for the various lists are given at the bottom
+ of this document. <emphasis>Please read the charter before
+ joining or sending mail to any list</emphasis>. Most of our
+ list subscribers now receive many hundreds of FreeBSD related
+ messages every day, and by setting down charters and rules for
+ proper use we are striving to keep the signal-to-noise ratio
+ of the lists high. To do less would see the mailing lists
+ ultimately fail as an effective communications medium for the
+ project.</para>
<note>
<para><emphasis>If you wish to test your ability to send to
- &os; lists, send a test message to &a.test.name;.</emphasis>
+ &os; lists, send a test message to &a.test.name;.</emphasis>
Please do not send test messages to any other list.</para>
</note>
- <para>When in doubt about what list to post a question to, see <ulink
- url="&url.articles.freebsd-questions;">How to get best results from
- the FreeBSD-questions mailing list</ulink>.</para>
-
- <para>Before posting to any list, please learn about how to best use
- the mailing lists, such as how to help avoid frequently-repeated
- discussions, by reading the <ulink url="&url.articles.mailing-list-faq;">
- Mailing List Frequently Asked Questions</ulink> (FAQ) document.</para>
-
- <para>Archives are kept for all of the mailing lists and can be searched
- using the <ulink url="&url.base;/search/index.html">FreeBSD World
- Wide Web server</ulink>. The keyword searchable archive offers an
- excellent way of finding answers to frequently asked questions and
- should be consulted before posting a question. Note that this
- also means that messages sent to FreeBSD mailing lists are
- archived in perpetuity. When protecting privacy is a
- concern, consider using a disposable secondary email address and
- posting only public information.</para>
+ <para>When in doubt about what list to post a question to, see
+ <ulink url="&url.articles.freebsd-questions;">How to get best
+ results from the FreeBSD-questions mailing
+ list</ulink>.</para>
+
+ <para>Before posting to any list, please learn about how to
+ best use the mailing lists, such as how to help avoid
+ frequently-repeated discussions, by reading the <ulink
+ url="&url.articles.mailing-list-faq;"> Mailing List Frequently
+ Asked Questions</ulink> (FAQ) document.</para>
+
+ <para>Archives are kept for all of the mailing lists and can be
+ searched using the <ulink
+ url="&url.base;/search/index.html">FreeBSD World Wide Web
+ server</ulink>. The keyword searchable archive offers an
+ excellent way of finding answers to frequently asked questions
+ and should be consulted before posting a question. Note that
+ this also means that messages sent to FreeBSD mailing lists
+ are archived in perpetuity. When protecting privacy is a
+ concern, consider using a disposable secondary email address
+ and posting only public information.</para>
<sect2 id="eresources-summary">
<title>List Summary</title>
- <para><emphasis>General lists:</emphasis> The following are general
- lists which anyone is free (and encouraged) to join:</para>
+ <para><emphasis>General lists:</emphasis> The following are
+ general lists which anyone is free (and encouraged) to
+ join:</para>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
@@ -98,11 +104,12 @@
<row>
<entry>&a.bugbusters.name;</entry>
- <entry>Discussions pertaining to the maintenance of the FreeBSD
- problem report database and related tools</entry>
+ <entry>Discussions pertaining to the maintenance of
+ the FreeBSD problem report database and related
+ tools</entry>
</row>
- <row>
+ <row>
<entry>&a.bugs.name;</entry>
<entry>Bug reports</entry>
</row>
@@ -154,17 +161,18 @@
<row>
<entry>&a.test.name;</entry>
- <entry>Where to send your test messages instead of one of
- the actual lists</entry>
+ <entry>Where to send your test messages instead of
+ one of the actual lists</entry>
</row>
</tbody>
</tgroup>
</informaltable>
- <para><emphasis>Technical lists:</emphasis> The following lists are for
- technical discussion. You should read the charter for each list
- carefully before joining or sending mail to one as there are firm
- guidelines for their use and content.</para>
+ <para><emphasis>Technical lists:</emphasis> The following
+ lists are for technical discussion. You should read the
+ charter for each list carefully before joining or sending
+ mail to one as there are firm guidelines for their use and
+ content.</para>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
@@ -188,7 +196,8 @@
<row>
<entry>&a.aic7xxx.name;</entry>
- <entry>Developing drivers for the &adaptec; AIC 7xxx</entry>
+ <entry>Developing drivers for the &adaptec;
+ AIC 7xxx</entry>
</row>
<row>
@@ -198,7 +207,9 @@
<row>
<entry>&a.apache.name;</entry>
- <entry>Discussion about <application>Apache</application> related ports</entry>
+ <entry>Discussion about
+ <application>Apache</application> related
+ ports</entry>
</row>
<row>
@@ -212,11 +223,6 @@
</row>
<row>
- <entry>&a.binup.name;</entry>
- <entry>Design and development of the binary update system</entry>
- </row>
-
- <row>
<entry>&a.bluetooth.name;</entry>
<entry>Using &bluetooth; technology in FreeBSD</entry>
</row>
@@ -255,7 +261,7 @@
<row>
<entry>&a.eclipse.name;</entry>
<entry>FreeBSD users of Eclipse IDE, tools, rich client
- applications and ports.</entry>
+ applications and ports.</entry>
</row>
<row>
@@ -288,17 +294,20 @@
<row>
<entry>&a.gecko.name;</entry>
- <entry><application>Gecko Rendering Engine</application> issues</entry>
+ <entry><application>Gecko Rendering
+ Engine</application> issues</entry>
</row>
<row>
<entry>&a.geom.name;</entry>
- <entry>GEOM-specific discussions and implementations</entry>
+ <entry>GEOM-specific discussions and
+ implementations</entry>
</row>
<row>
<entry>&a.gnome.name;</entry>
- <entry>Porting <application>GNOME</application> and <application>GNOME</application> applications</entry>
+ <entry>Porting <application>GNOME</application> and
+ <application>GNOME</application> applications</entry>
</row>
<row>
@@ -319,18 +328,25 @@
<row>
<entry>&a.ia32.name;</entry>
- <entry>FreeBSD on the IA-32 (&intel; x86) platform</entry>
+ <entry>FreeBSD on the IA-32 (&intel; x86)
+ platform</entry>
</row>
<row>
<entry>&a.ia64.name;</entry>
- <entry>Porting FreeBSD to &intel;'s upcoming IA64 systems</entry>
+ <entry>Porting FreeBSD to &intel;'s upcoming IA64
+ systems</entry>
+ </row>
+
+ <row>
+ <entry>&a.infiniband.name;</entry>
+ <entry>Infiniband on FreeBSD</entry>
</row>
<row>
<entry>&a.ipfw.name;</entry>
- <entry>Technical discussion concerning the redesign of the IP
- firewall code</entry>
+ <entry>Technical discussion concerning the redesign
+ of the IP firewall code</entry>
</row>
<row>
@@ -340,7 +356,8 @@
<row>
<entry>&a.jail.name;</entry>
- <entry>Discussion about the &man.jail.8; facility</entry>
+ <entry>Discussion about the &man.jail.8;
+ facility</entry>
</row>
<row>
@@ -351,7 +368,8 @@
<row>
<entry>&a.kde.name;</entry>
- <entry>Porting <application>KDE</application> and <application>KDE</application> applications</entry>
+ <entry>Porting <application>KDE</application> and
+ <application>KDE</application> applications</entry>
</row>
<row>
@@ -376,7 +394,8 @@
<row>
<entry>&a.mozilla.name;</entry>
- <entry>Porting <application>Mozilla</application> to FreeBSD</entry>
+ <entry>Porting <application>Mozilla</application> to
+ FreeBSD</entry>
</row>
<row>
@@ -386,17 +405,20 @@
<row>
<entry>&a.newbus.name;</entry>
- <entry>Technical discussions about bus architecture</entry>
+ <entry>Technical discussions about bus
+ architecture</entry>
</row>
<row>
<entry>&a.net.name;</entry>
- <entry>Networking discussion and TCP/IP source code</entry>
+ <entry>Networking discussion and TCP/IP source
+ code</entry>
</row>
<row>
<entry>&a.numerics.name;</entry>
- <entry>Discussions of high quality implementation of libm functions</entry>
+ <entry>Discussions of high quality implementation of
+ libm functions</entry>
</row>
<row>
@@ -435,7 +457,8 @@
<row>
<entry>&a.ports-announce.name;</entry>
- <entry>Important news and instructions about the Ports Collection</entry>
+ <entry>Important news and instructions about the Ports
+ Collection</entry>
</row>
<row>
@@ -450,7 +473,8 @@
<row>
<entry>&a.proliant.name;</entry>
- <entry>Technical discussion of FreeBSD on HP ProLiant server platforms</entry>
+ <entry>Technical discussion of FreeBSD on HP ProLiant
+ server platforms</entry>
</row>
<row>
@@ -460,12 +484,15 @@
<row>
<entry>&a.rc.name;</entry>
- <entry>Discussion related to the <filename>rc.d</filename> system and its development</entry>
+ <entry>Discussion related to the
+ <filename>rc.d</filename> system and its
+ development</entry>
</row>
<row>
<entry>&a.realtime.name;</entry>
- <entry>Development of realtime extensions to FreeBSD</entry>
+ <entry>Development of realtime extensions to
+ FreeBSD</entry>
</row>
<row>
@@ -490,6 +517,11 @@
</row>
<row>
+ <entry>&a.snapshots.name;</entry>
+ <entry>&os; Development Snapshot Announcements</entry>
+ </row>
+
+ <row>
<entry>&a.sparc.name;</entry>
<entry>Porting FreeBSD to &sparc; based systems</entry>
</row>
@@ -506,13 +538,19 @@
</row>
<row>
+ <entry>&a.tcltk.name;</entry>
+ <entry>FreeBSD-specific Tcl/Tk discussions</entry>
+ </row>
+
+ <row>
<entry>&a.threads.name;</entry>
<entry>Threading in FreeBSD</entry>
</row>
<row>
<entry>&a.tilera.name;</entry>
- <entry>Porting FreeBSD to the Tilera family of CPUs</entry>
+ <entry>Porting FreeBSD to the Tilera family of
+ CPUs</entry>
</row>
<row>
@@ -522,7 +560,8 @@
<row>
<entry>&a.toolchain.name;</entry>
- <entry>Maintenance of &os;'s integrated toolchain</entry>
+ <entry>Maintenance of &os;'s integrated
+ toolchain</entry>
</row>
<row>
@@ -532,8 +571,8 @@
<row>
<entry>&a.virtualization.name;</entry>
- <entry>Discussion of various virtualization techniques supported
- by &os;</entry>
+ <entry>Discussion of various virtualization techniques
+ supported by &os;</entry>
</row>
<row>
@@ -548,12 +587,14 @@
<row>
<entry>&a.xen.name;</entry>
- <entry>Discussion of the &os; port to &xen; &mdash; implementation and usage</entry>
+ <entry>Discussion of the &os; port to &xen; &mdash;
+ implementation and usage</entry>
</row>
<row>
<entry>&a.xfce.name;</entry>
- <entry><application>XFCE</application> for &os; &mdash; porting and maintaining</entry>
+ <entry><application>XFCE</application> for &os; &mdash;
+ porting and maintaining</entry>
</row>
<row>
@@ -565,11 +606,12 @@
</tgroup>
</informaltable>
- <para><emphasis>Limited lists:</emphasis> 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.</para>
+ <para><emphasis>Limited lists:</emphasis> 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.</para>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
@@ -610,7 +652,9 @@
<row>
<entry>&a.www.name;</entry>
- <entry>Maintainers of <ulink url="&url.base;/index.html">www.FreeBSD.org</ulink></entry>
+ <entry>Maintainers of
+ <ulink
+ url="&url.base;/index.html">www.FreeBSD.org</ulink></entry>
</row>
</tbody>
</tgroup>
@@ -622,10 +666,10 @@
section.</para>
<para><emphasis>SVN lists:</emphasis> The following lists
- are for people interested in seeing the log messages for changes to
- various areas of the source tree. They are
- <emphasis>Read-Only</emphasis> lists and should not have mail sent to
- them.</para>
+ are for people interested in seeing the log messages for
+ changes to various areas of the source tree. They are
+ <emphasis>Read-Only</emphasis> lists and should not have
+ mail sent to them.</para>
<informaltable frame="none" pgwide="1">
<tgroup cols="3">
@@ -641,10 +685,10 @@
<row>
<entry>&a.svn-doc-all.name;</entry>
<entry><filename>/usr/doc</filename></entry>
- <entry>All changes to the doc Subversion repository (except
- for <filename>user</filename>,
- <filename>projects</filename>
- and <filename>translations</filename>)</entry>
+ <entry>All changes to the doc Subversion repository
+ (except for <filename>user</filename>,
+ <filename>projects</filename>
+ and <filename>translations</filename>)</entry>
</row>
<row>
@@ -672,14 +716,15 @@
<row>
<entry>&a.svn-ports-all.name;</entry>
<entry><filename>/usr/ports</filename></entry>
- <entry>All changes to the ports Subversion repository</entry>
+ <entry>All changes to the ports Subversion
+ repository</entry>
</row>
<row>
<entry>&a.svn-ports-head.name;</entry>
<entry><filename>/usr/ports</filename></entry>
- <entry>All changes to the <quote>head</quote> branch of
- the ports Subversion repository</entry>
+ <entry>All changes to the <quote>head</quote> branch
+ of the ports Subversion repository</entry>
</row>
<row>
@@ -693,16 +738,16 @@
<row>
<entry>&a.svn-src-all.name;</entry>
<entry><filename>/usr/src</filename></entry>
- <entry>All changes to the src Subversion repository (except
- for <filename>user</filename>
+ <entry>All changes to the src Subversion repository
+ (except for <filename>user</filename>
and <filename>projects</filename>)</entry>
</row>
<row>
<entry>&a.svn-src-head.name;</entry>
<entry><filename>/usr/src</filename></entry>
- <entry>All changes to the <quote>head</quote> branch of
- the src Subversion repository (the &os;-CURRENT
+ <entry>All changes to the <quote>head</quote> branch
+ of the src Subversion repository (the &os;-CURRENT
branch)</entry>
</row>
@@ -802,85 +847,90 @@
<title>How to Subscribe</title>
<para>To subscribe to a list, click on the list name above or
- go to &a.mailman.lists.link;
- and click on the list that you are interested in. The list
- page should contain all of the necessary subscription
- instructions.</para>
+ go to &a.mailman.lists.link; and click on the list that you
+ are interested in. The list page should contain all of the
+ necessary subscription instructions.</para>
<para>To actually post to a given list, send mail to
- <email><replaceable>listname</replaceable>@FreeBSD.org</email>. It will then
- be redistributed to mailing list members world-wide.</para>
+ <email><replaceable>listname</replaceable>@FreeBSD.org</email>.
+ It will then be redistributed to mailing list members
+ world-wide.</para>
<para>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
- <email><replaceable>listname</replaceable>-unsubscribe@FreeBSD.org</email> to unsubscribe
- yourself.</para>
-
- <para>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.announce;, which is intended only for infrequent
- traffic.</para>
+ found at the bottom of every email received from the list.
+ It is also possible to send an email to
+ <email><replaceable>listname</replaceable>-unsubscribe@FreeBSD.org</email>
+ to unsubscribe yourself.</para>
+
+ <para>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.announce;, which is intended
+ only for infrequent traffic.</para>
</sect2>
<sect2 id="eresources-charters">
<title>List Charters</title>
- <para><emphasis>All</emphasis> 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 <email>postmaster@FreeBSD.org</email>, 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.</para>
+ <para><emphasis>All</emphasis> 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
+ <email>postmaster@FreeBSD.org</email>, 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.</para>
<para>Rules of the road:</para>
<itemizedlist>
<listitem>
- <para>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.chat;
+ <para>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.chat;
is freely available and should be used instead.</para>
</listitem>
<listitem>
- <para>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
- <quote>-stable &amp; -scsi</quote>), 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
- <literal>Cc</literal> line then the <literal>Cc</literal>
- line should also be trimmed before sending it out again.
- <emphasis>You are still responsible for your
- own cross-postings, no matter who the originator might have
- been.</emphasis></para>
+ <para>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 <quote>-stable &amp; -scsi</quote>),
+ 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 <literal>Cc</literal>
+ line then the <literal>Cc</literal> line should also be
+ trimmed before sending it out again. <emphasis>You are
+ still responsible for your own cross-postings, no matter
+ who the originator might have been.</emphasis></para>
</listitem>
<listitem>
- <para>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.
- <emphasis>However</emphasis>, 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.</para>
+ <para>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.
+ <emphasis>However</emphasis>, 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.</para>
</listitem>
<listitem>
- <para>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.</para>
+ <para>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.</para>
</listitem>
</itemizedlist>
@@ -893,7 +943,7 @@
<listitem>
<para><emphasis>ACPI and power management
- development</emphasis></para>
+ development</emphasis></para>
</listitem>
</varlistentry>
@@ -903,8 +953,8 @@
<listitem>
<para><emphasis>Andrew File System</emphasis></para>
- <para>This list is for discussion on porting and using AFS from
- CMU/Transarc</para>
+ <para>This list is for discussion on porting and using
+ AFS from CMU/Transarc</para>
</listitem>
</varlistentry>
@@ -912,13 +962,15 @@
<term>&a.announce.name;</term>
<listitem>
- <para><emphasis>Important events / milestones</emphasis></para>
-
- <para>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
+ <para><emphasis>Important events /
+ milestones</emphasis></para>
+
+ <para>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.</para>
</listitem>
</varlistentry>
@@ -930,7 +982,7 @@
<para><emphasis>Architecture and design
discussions</emphasis></para>
- <para>This list is for discussion of the FreeBSD
+ <para>This list is for discussion of the FreeBSD
architecture. Messages will mostly be kept strictly
technical in nature. Examples of suitable topics
are:</para>
@@ -942,14 +994,14 @@
</listitem>
<listitem>
- <para>What needs to be fixed with VFS to make Heidemann layers
- work.</para>
- </listitem>
+ <para>What needs to be fixed with VFS to make
+ Heidemann layers work.</para>
+ </listitem>
<listitem>
- <para>How do we change the device driver interface to be able
- to use the same drivers cleanly on many buses and
- architectures.</para>
+ <para>How do we change the device driver interface
+ to be able to use the same drivers cleanly on many
+ buses and architectures.</para>
</listitem>
<listitem>
@@ -960,31 +1012,16 @@
</varlistentry>
<varlistentry>
- <term>&a.binup.name;</term>
-
- <listitem>
- <para><emphasis>FreeBSD Binary Update Project</emphasis></para>
-
- <para>This list exists to provide discussion for the binary
- update system, or <application>binup</application>.
- Design issues, implementation details,
- patches, bug reports, status reports, feature requests, commit
- logs, and all other things related to
- <application>binup</application> are fair game.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
<term>&a.bluetooth.name;</term>
<listitem>
<para><emphasis>&bluetooth; in FreeBSD</emphasis></para>
<para>This is the forum where FreeBSD's &bluetooth; users
- congregate. Design issues, implementation details,
- patches, bug reports, status reports, feature requests,
- and all matters related to &bluetooth; are fair
- game.</para>
+ congregate. Design issues, implementation details,
+ patches, bug reports, status reports, feature requests,
+ and all matters related to &bluetooth; are fair
+ game.</para>
</listitem>
</varlistentry>
@@ -992,12 +1029,14 @@
<term>&a.bugbusters.name;</term>
<listitem>
- <para><emphasis>Coordination of the Problem Report handling effort</emphasis></para>
-
- <para>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.</para>
+ <para><emphasis>Coordination of the Problem Report
+ handling effort</emphasis></para>
+
+ <para>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.</para>
</listitem>
</varlistentry>
@@ -1007,10 +1046,9 @@
<listitem>
<para><emphasis>Bug reports</emphasis></para>
- <para>This is the mailing list for reporting bugs in FreeBSD.
- Whenever possible, bugs should be submitted using the
- &man.send-pr.1;
- command or the <ulink
+ <para>This is the mailing list for reporting bugs in
+ FreeBSD. Whenever possible, bugs should be submitted
+ using the &man.send-pr.1; command or the <ulink
url="&url.base;/send-pr.html">WEB
interface</ulink> to it.</para>
</listitem>
@@ -1023,15 +1061,16 @@
<para><emphasis>Non technical items related to the FreeBSD
community</emphasis></para>
- <para>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.</para>
+ <para>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.</para>
</listitem>
</varlistentry>
@@ -1039,11 +1078,12 @@
<term>&a.chromium.name;</term>
<listitem>
- <para><emphasis>FreeBSD-specific Chromium issues</emphasis></para>
+ <para><emphasis>FreeBSD-specific Chromium
+ issues</emphasis></para>
<para>This is a list for the discussion of Chromium
- support for FreeBSD. This is a technical list to discuss
- development and installation of Chromium.</para>
+ support for FreeBSD. This is a technical list to
+ discuss development and installation of Chromium.</para>
</listitem>
</varlistentry>
@@ -1055,8 +1095,8 @@
<para>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.</para>
+ FreeBSD-related matter requires arbitration or
+ high-level scrutiny.</para>
</listitem>
</varlistentry>
@@ -1067,12 +1107,13 @@
<para><emphasis>Discussions about the use of
&os.current;</emphasis></para>
- <para>This is the mailing list for users of &os.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 <quote>CURRENT</quote>
- must subscribe to this list. This is a technical mailing list
- for which strictly technical content is expected.</para>
+ <para>This is the mailing list for users of &os.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 <quote>CURRENT</quote> must subscribe to this
+ list. This is a technical mailing list for which
+ strictly technical content is expected.</para>
</listitem>
</varlistentry>
@@ -1082,8 +1123,8 @@
<listitem>
<para><emphasis>FreeBSD CVSweb Project</emphasis></para>
- <para>Technical discussions about use, development and maintenance
- of FreeBSD-CVSweb.</para>
+ <para>Technical discussions about use, development and
+ maintenance of FreeBSD-CVSweb.</para>
</listitem>
</varlistentry>
@@ -1091,7 +1132,8 @@
<term>&a.desktop.name;</term>
<listitem>
- <para><emphasis>Using and improving &os; on the desktop</emphasis></para>
+ <para><emphasis>Using and improving &os; on the
+ desktop</emphasis></para>
<para>This is a forum for discussion of &os; on the
desktop. It is primarily a place for desktop porters
@@ -1106,11 +1148,12 @@
<listitem>
<para><emphasis>Documentation project</emphasis></para>
- <para>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
- <quote>The FreeBSD Documentation Project</quote>. It is an open
- list; feel free to join and contribute!</para>
+ <para>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 <quote>The FreeBSD
+ Documentation Project</quote>. It is an open list;
+ feel free to join and contribute!</para>
</listitem>
</varlistentry>
@@ -1118,13 +1161,14 @@
<term>&a.drivers.name;</term>
<listitem>
- <para><emphasis>Writing device drivers for &os;</emphasis></para>
-
- <para>This is a forum for technical discussions related to
- device drivers on &os;. It is primarily a place
- for device driver writers to ask questions about
- how to write device drivers using the APIs in the
- &os; kernel.</para>
+ <para><emphasis>Writing device drivers for
+ &os;</emphasis></para>
+
+ <para>This is a forum for technical discussions related
+ to device drivers on &os;. It is primarily a place
+ for device driver writers to ask questions about how
+ to write device drivers using the APIs in the &os;
+ kernel.</para>
</listitem>
</varlistentry>
@@ -1133,7 +1177,7 @@
<listitem>
<para><emphasis>&os; users of Eclipse IDE, tools, rich
- client applications and ports.</emphasis></para>
+ client applications and ports.</emphasis></para>
<para>The intention of this list is to provide mutual
support for everything to do with choosing, installing,
@@ -1149,8 +1193,7 @@
<para>Although this list is focused primarily on the needs
of Eclipse users it will also provide a forum for those
who would like to develop &os; specific applications
- using the Eclipse framework.
- </para>
+ using the Eclipse framework.</para>
</listitem>
</varlistentry>
@@ -1159,18 +1202,19 @@
<listitem>
<para><emphasis>Using FreeBSD in embedded
- applications</emphasis></para>
-
- <para>This list discusses topics related to using FreeBSD in
- embedded systems. This is a technical mailing list for which
- strictly technical content is expected. For the purpose of
- this list we define embedded systems as those computing
- devices which are not desktops and which usually serve a
- single purpose as opposed to being general computing
- environments. Examples include, but are not limited to,
- all kinds of phone handsets, network equipment such as
- routers, switches and PBXs, remote measuring equipment,
- PDAs, Point Of Sale systems, and so on.</para>
+ applications</emphasis></para>
+
+ <para>This list discusses topics related to using FreeBSD
+ in embedded systems. This is a technical mailing list
+ for which strictly technical content is expected. For
+ the purpose of this list we define embedded systems as
+ those computing devices which are not desktops and which
+ usually serve a single purpose as opposed to being
+ general computing environments. Examples include, but
+ are not limited to, all kinds of phone handsets, network
+ equipment such as routers, switches and PBXs, remote
+ measuring equipment, PDAs, Point Of Sale systems, and
+ so on.</para>
</listitem>
</varlistentry>
@@ -1181,9 +1225,9 @@
<para><emphasis>Emulation of other systems such as
Linux/&ms-dos;/&windows;</emphasis></para>
- <para>This is a forum for technical discussions related to
- running programs written for other operating systems on &os;.
- </para>
+ <para>This is a forum for technical discussions related
+ to running programs written for other operating systems
+ on &os;.</para>
</listitem>
</varlistentry>
@@ -1191,13 +1235,15 @@
<term>&a.eol.name;</term>
<listitem>
- <para><emphasis>Peer support of FreeBSD-related software that is
- no longer supported by the FreeBSD project.</emphasis></para>
-
- <para>This list is for those interested in providing or making use
- of peer support of FreeBSD-related software for which the
- FreeBSD project no longer provides official support (e.g., in
- the form of security advisories and patches).</para>
+ <para><emphasis>Peer support of FreeBSD-related software
+ that is no longer supported by the FreeBSD
+ project.</emphasis></para>
+
+ <para>This list is for those interested in providing or
+ making use of peer support of FreeBSD-related software
+ for which the FreeBSD project no longer provides
+ official support (e.g., in the form of security
+ advisories and patches).</para>
</listitem>
</varlistentry>
@@ -1205,7 +1251,8 @@
<term>&a.firewire.name;</term>
<listitem>
- <para><emphasis>&firewire; (iLink, IEEE 1394)</emphasis></para>
+ <para><emphasis>&firewire; (iLink, IEEE
+ 1394)</emphasis></para>
<para>This is a mailing list for discussion of the design
and implementation of a &firewire; (aka IEEE 1394 aka
@@ -1223,9 +1270,9 @@
<listitem>
<para><emphasis>File systems</emphasis></para>
- <para>Discussions concerning FreeBSD file systems. This is a
- technical mailing list for which strictly technical content is
- expected.</para>
+ <para>Discussions concerning FreeBSD file systems.
+ This is a technical mailing list for which strictly
+ technical content is expected.</para>
</listitem>
</varlistentry>
@@ -1235,8 +1282,9 @@
<listitem>
<para><emphasis>Gecko Rendering Engine</emphasis></para>
- <para>This is a forum about <application>Gecko</application>
- applications using &os;.</para>
+ <para>This is a forum about
+ <application>Gecko</application> applications using
+ &os;.</para>
<para>Discussion centers around Gecko Ports applications,
their installation, their development and their support
@@ -1250,9 +1298,9 @@
<listitem>
<para><emphasis>GEOM</emphasis></para>
- <para>Discussions specific to GEOM and related implementations.
- This is a technical mailing list for which strictly technical
- content is expected.</para>
+ <para>Discussions specific to GEOM and related
+ implementations. This is a technical mailing list for
+ which strictly technical content is expected.</para>
</listitem>
</varlistentry>
@@ -1262,9 +1310,21 @@
<listitem>
<para><emphasis>GNOME</emphasis></para>
- <para>Discussions concerning The <application>GNOME</application> Desktop Environment for
- FreeBSD systems. This is a technical mailing list for
- which strictly technical content is expected.</para>
+ <para>Discussions concerning The
+ <application>GNOME</application> Desktop Environment
+ for FreeBSD systems. This is a technical mailing list
+ for which strictly technical content is expected.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>&a.infiniband.name;</term>
+
+ <listitem>
+ <para><emphasis>Infiniband on &os;</emphasis></para>
+
+ <para>Technical mailing list discussing Infiniband, OFED,
+ and OpenSM on &os;.</para>
</listitem>
</varlistentry>
@@ -1274,10 +1334,10 @@
<listitem>
<para><emphasis>IP Firewall</emphasis></para>
- <para>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.</para>
+ <para>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.</para>
</listitem>
</varlistentry>
@@ -1288,10 +1348,11 @@
<para><emphasis>Porting FreeBSD to IA64</emphasis></para>
<para>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.</para>
+ 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.</para>
</listitem>
</varlistentry>
@@ -1313,8 +1374,9 @@
<para><emphasis>&java; Development</emphasis></para>
<para>This is the mailing list for people discussing the
- development of significant &java; applications for FreeBSD and the
- porting and maintenance of &jdk;s.</para>
+ development of significant &java; applications for
+ FreeBSD and the porting and maintenance of
+ &jdk;s.</para>
</listitem>
</varlistentry>
@@ -1324,19 +1386,19 @@
<listitem>
<para><emphasis>Jobs offered and sought</emphasis></para>
- <para>This is a forum for posting employment notices and
- resumes specifically related to &os;, e.g., if you are
- seeking &os;-related employment or have a job involving
- &os; to advertise then this is the right place. This is
- <emphasis>not</emphasis> a mailing list for general
- employment issues since adequate forums for that
- already exist elsewhere.</para>
+ <para>This is a forum for posting employment notices
+ and resumes specifically related to &os;, e.g., if you
+ are seeking &os;-related employment or have a job
+ involving &os; to advertise then this is the right
+ place. This is <emphasis>not</emphasis> a mailing list
+ for general employment issues since adequate forums
+ for that already exist elsewhere.</para>
- <para>Note that this list, like other <hostid role="domainname">FreeBSD.org</hostid> 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.</para>
+ <para>Note that this list, like other <hostid
+ role="domainname">FreeBSD.org</hostid> 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.</para>
<para>Email should use open formats only &mdash;
preferably plain text, but basic Portable Document
@@ -1353,9 +1415,10 @@
<listitem>
<para><emphasis>KDE</emphasis></para>
- <para>Discussions concerning <application>KDE</application> on
- FreeBSD systems. This is a technical mailing list for
- which strictly technical content is expected.</para>
+ <para>Discussions concerning
+ <application>KDE</application> on FreeBSD systems.
+ This is a technical mailing list for which strictly
+ technical content is expected.</para>
</listitem>
</varlistentry>
@@ -1365,12 +1428,13 @@
<listitem>
<para><emphasis>Technical discussions</emphasis></para>
- <para>This is a forum for technical discussions related to
- FreeBSD. This is the primary technical mailing list. It is for
- individuals actively working on FreeBSD, to bring up problems or
- discuss alternative solutions. Individuals interested in
- following the technical discussion are also welcome. This is a
- technical mailing list for which strictly technical content is
+ <para>This is a forum for technical discussions related
+ to FreeBSD. This is the primary technical mailing list.
+ It is for individuals actively working on FreeBSD, to
+ bring up problems or discuss alternative solutions.
+ Individuals interested in following the technical
+ discussion are also welcome. This is a technical
+ mailing list for which strictly technical content is
expected.</para>
</listitem>
</varlistentry>
@@ -1382,9 +1446,9 @@
<para><emphasis>General discussion of FreeBSD
hardware</emphasis></para>
- <para>General discussion about the types of hardware that FreeBSD
- runs on, various problems and suggestions concerning what to buy
- or avoid.</para>
+ <para>General discussion about the types of hardware
+ that FreeBSD runs on, various problems and suggestions
+ concerning what to buy or avoid.</para>
</listitem>
</varlistentry>
@@ -1394,8 +1458,8 @@
<listitem>
<para><emphasis>Mirror sites</emphasis></para>
- <para>Announcements and discussion for people who run FreeBSD
- mirror sites.</para>
+ <para>Announcements and discussion for people who run
+ FreeBSD mirror sites.</para>
</listitem>
</varlistentry>
@@ -1406,10 +1470,10 @@
<para><emphasis>Issues for Internet Service
Providers</emphasis></para>
- <para>This mailing list is for discussing topics relevant to
- Internet Service Providers (ISPs) using FreeBSD. This is a
- technical mailing list for which strictly technical content is
- expected.</para>
+ <para>This mailing list is for discussing topics relevant
+ to Internet Service Providers (ISPs) using FreeBSD.
+ This is a technical mailing list for which strictly
+ technical content is expected.</para>
</listitem>
</varlistentry>
@@ -1418,15 +1482,15 @@
<listitem>
<para><emphasis>Mono and C# applications on
- FreeBSD</emphasis></para>
+ FreeBSD</emphasis></para>
<para>This is a list for discussions related to the Mono
development framework on &os;. This is a technical
- mailing list. It is for individuals actively working on
- porting Mono or C# applications to &os;, to bring up
- problems or discuss alternative solutions. Individuals
- interested in following the technical discussion are also
- welcome.</para>
+ mailing list. It is for individuals actively working
+ on porting Mono or C# applications to &os;, to bring
+ up problems or discuss alternative solutions.
+ Individuals interested in following the technical
+ discussion are also welcome.</para>
</listitem>
</varlistentry>
@@ -1434,19 +1498,37 @@
<term>&a.office.name;</term>
<listitem>
- <para><emphasis>Office applications on &os;</emphasis></para>
+ <para><emphasis>Office applications on
+ &os;</emphasis></para>
<para>Discussion centers around office applications,
their installation, their development and their support
within &os;.</para>
- </listitem>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>&a.ops-announce.name;</term>
+
+ <listitem>
+ <para><emphasis>Project Infrastructure
+ Announcements</emphasis></para>
+
+ <para>This is the mailing list for people interested in
+ changes and issues related to the FreeBSD.org project
+ infrastructure.</para>
+
+ <para>This list is strictly for announcements: no replies,
+ requests, discussions, or opinions.</para>
+ </listitem>
</varlistentry>
<varlistentry>
<term>&a.performance.name;</term>
<listitem>
- <para><emphasis>Discussions about tuning or speeding up FreeBSD</emphasis></para>
+ <para><emphasis>Discussions about tuning or speedingup
+ FreeBSD</emphasis></para>
<para>This mailing list exists to provide a place for
hackers, administrators, and/or concerned parties to
@@ -1472,27 +1554,49 @@
<term>&a.pf.name;</term>
<listitem>
- <para><emphasis>Discussion and questions about the packet filter
- firewall system</emphasis></para>
+ <para><emphasis>Discussion and questions about the packet
+ filter firewall system</emphasis></para>
- <para>Discussion concerning the packet filter (pf) firewall
- system in terms of FreeBSD. Technical discussion and user
- questions are both welcome. This list is also a place to
- discuss the ALTQ QoS framework.</para>
+ <para>Discussion concerning the packet filter (pf)
+ firewall system in terms of FreeBSD. Technical
+ discussion and user questions are both welcome. This
+ list is also a place to discuss the ALTQ QoS
+ framework.</para>
</listitem>
</varlistentry>
<varlistentry>
+ <term>&a.pkg.name;</term>
+
+ <listitem>
+ <para><emphasis>Binary package management and package
+ tools discussion</emphasis></para>
+
+ <para>Discussion of all aspects of managing &os; systems
+ by using binary packages to install software, including
+ binary package toolkits and formats, their development
+ and support within &os;, package repository management,
+ and 3rd party packages.</para>
+
+ <para>Note that discussion of ports which fail to generate
+ packages correctly should generally be considered as
+ ports problems, and so inappropriate for this
+ list.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
<term>&a.platforms.name;</term>
<listitem>
- <para><emphasis>Porting to Non &intel; platforms</emphasis></para>
+ <para><emphasis>Porting to Non &intel;
+ platforms</emphasis></para>
- <para>Cross-platform FreeBSD issues, general discussion and
- proposals for non &intel; FreeBSD ports. This is a technical
- mailing list for which strictly technical content is
- expected.</para>
+ <para>Cross-platform FreeBSD issues, general discussion
+ and proposals for non &intel; FreeBSD ports. This is
+ a technical mailing list for which strictly technical
+ content is expected.</para>
</listitem>
</varlistentry>
@@ -1504,9 +1608,10 @@
<quote>ports</quote></emphasis></para>
<para>Discussions concerning FreeBSD's <quote>ports
- collection</quote> (<filename>/usr/ports</filename>), ports infrastructure, and
- general ports coordination efforts. This is a technical mailing list
- for which strictly technical content is expected.</para>
+ collection</quote> (<filename>/usr/ports</filename>),
+ ports infrastructure, and general ports coordination
+ efforts. This is a technical mailing list for which
+ strictly technical content is expected.</para>
</listitem>
</varlistentry>
@@ -1515,15 +1620,16 @@
<listitem>
<para><emphasis>Important news and instructions about the
- &os;&nbsp;<quote>Ports Collection</quote></emphasis></para>
+ &os;&nbsp;<quote>Ports
+ Collection</quote></emphasis></para>
- <para>Important news for developers, porters, and users of
- the <quote>Ports Collection</quote> (<filename
+ <para>Important news for developers, porters, and users
+ of the <quote>Ports Collection</quote> (<filename
role="directory">/usr/ports</filename>), including
architecture/infrastructure changes, new capabilities,
critical upgrade instructions, and release engineering
- information. This is a low-volume mailing list, intended
- for announcements.</para>
+ information. This is a low-volume mailing list,
+ intended for announcements.</para>
</listitem>
</varlistentry>
@@ -1534,10 +1640,12 @@
<para><emphasis>Discussion of
<quote>ports</quote> bugs</emphasis></para>
- <para>Discussions concerning problem reports for FreeBSD's <quote>ports
- collection</quote> (<filename>/usr/ports</filename>), proposed
- ports, or modifications to ports. This is a technical mailing list
- for which strictly technical content is expected.</para>
+ <para>Discussions concerning problem reports for FreeBSD's
+ <quote>ports collection</quote>
+ (<filename>/usr/ports</filename>), proposed ports, or
+ modifications to ports. This is a technical mailing
+ list for which strictly technical content is
+ expected.</para>
</listitem>
</varlistentry>
@@ -1549,11 +1657,12 @@
ProLiant server platforms</emphasis></para>
<para>This mailing list is to be used for the technical
- discussion of the usage of FreeBSD on HP ProLiant servers,
- including the discussion of ProLiant-specific drivers,
- management software, configuration tools, and BIOS
- updates. As such, this is the primary place to discuss
- the hpasmd, hpasmcli, and hpacucli modules.</para>
+ discussion of the usage of FreeBSD on HP ProLiant
+ servers, including the discussion of ProLiant-specific
+ drivers, management software, configuration tools, and
+ BIOS updates. As such, this is the primary place to
+ discuss the hpasmd, hpasmcli, and hpacucli
+ modules.</para>
</listitem>
</varlistentry>
@@ -1563,11 +1672,13 @@
<listitem>
<para><emphasis>Python on FreeBSD</emphasis></para>
- <para>This is a list for discussions related to improving Python-support
- on FreeBSD. This is a technical mailing list. It is for individuals
- working on porting Python, its 3rd party modules and <application>Zope</application> stuff to
- FreeBSD. Individuals interested in following the technical discussion
- are also welcome.</para>
+ <para>This is a list for discussions related to improving
+ Python-support on FreeBSD. This is a technical mailing
+ list. It is for individuals working on porting Python,
+ its 3rd party modules and
+ <application>Zope</application> stuff to FreeBSD.
+ Individuals interested in following the technical
+ discussion are also welcome.</para>
</listitem>
</varlistentry>
@@ -1577,10 +1688,10 @@
<listitem>
<para><emphasis>User questions</emphasis></para>
- <para>This is the mailing list for questions about FreeBSD. You
- should not send <quote>how to</quote> questions to the technical
- lists unless you consider the question to be pretty
- technical.</para>
+ <para>This is the mailing list for questions about
+ FreeBSD. You should not send <quote>how to</quote>
+ questions to the technical lists unless you consider
+ the question to be pretty technical.</para>
</listitem>
</varlistentry>
@@ -1589,7 +1700,7 @@
<listitem>
<para><emphasis>FreeBSD-specific Ruby
- discussions</emphasis></para>
+ discussions</emphasis></para>
<para>This is a list for discussions related to the Ruby
support on FreeBSD. This is a technical mailing
@@ -1607,9 +1718,10 @@
<listitem>
<para><emphasis>SCSI subsystem</emphasis></para>
- <para>This is the mailing list for people working on the SCSI
- subsystem for FreeBSD. This is a technical mailing list for
- which strictly technical content is expected.</para>
+ <para>This is the mailing list for people working on
+ the SCSI subsystem for FreeBSD. This is a technical
+ mailing list for which strictly technical content is
+ expected.</para>
</listitem>
</varlistentry>
@@ -1619,12 +1731,12 @@
<listitem>
<para><emphasis>Security issues</emphasis></para>
- <para>FreeBSD computer security issues (DES, Kerberos, known
- security holes and fixes, etc). This is a technical mailing
- list for which strictly technical discussion is expected. Note
- that this is not a question-and-answer list, but that
- contributions (BOTH question AND answer) to the FAQ are
- welcome.</para>
+ <para>FreeBSD computer security issues (DES, Kerberos,
+ known security holes and fixes, etc). This is a
+ technical mailing list for which strictly technical
+ discussion is expected. Note that this is not a
+ question-and-answer list, but that contributions (BOTH
+ question AND answer) to the FAQ are welcome.</para>
</listitem>
</varlistentry>
@@ -1635,7 +1747,7 @@
<para><emphasis>Security Notifications</emphasis></para>
<para>Notifications of FreeBSD security problems and
- fixes. This is not a discussion list. The discussion
+ fixes. This is not a discussion list. The discussion
list is FreeBSD-security.</para>
</listitem>
</varlistentry>
@@ -1645,32 +1757,48 @@
<listitem>
<para><emphasis>Using FreeBSD in embedded
- applications</emphasis></para>
+ applications</emphasis></para>
- <para>This list discusses topics related to unusually small and
- embedded FreeBSD installations. This is a technical mailing
- list for which strictly technical content is expected.</para>
+ <para>This list discusses topics related to unusually
+ small and embedded FreeBSD installations. This is a
+ technical mailing list for which strictly technical
+ content is expected.</para>
<note>
- <para>This list has been obsoleted by &a.embedded.name;.</para>
+ <para>This list has been obsoleted by
+ &a.embedded.name;.</para>
</note>
</listitem>
</varlistentry>
<varlistentry>
+ <term>&a.snapshots.name;</term>
+
+ <listitem>
+ <para><emphasis>&os; Development Snapshot
+ Announcements</emphasis></para>
+
+ <para>This list will notify you about the availability
+ of new &os; development snapshots for the head/ and
+ stable/ branches.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
<term>&a.stable.name;</term>
<listitem>
<para><emphasis>Discussions about the use of
&os.stable;</emphasis></para>
- <para>This is the mailing list for users of &os.stable;. It
- includes warnings about new features coming out in -STABLE that
- will affect the users, and instructions on steps that must be
- taken to remain -STABLE. Anyone running <quote>STABLE</quote>
- should subscribe to this list. This is a technical mailing list
- for which strictly technical content is expected.</para>
+ <para>This is the mailing list for users of &os.stable;.
+ It includes warnings about new features coming out in
+ -STABLE that will affect the users, and instructions
+ on steps that must be taken to remain -STABLE. Anyone
+ running <quote>STABLE</quote> should subscribe to this
+ list. This is a technical mailing list for which
+ strictly technical content is expected.</para>
</listitem>
</varlistentry>
@@ -1678,10 +1806,12 @@
<term>&a.standards.name;</term>
<listitem>
- <para><emphasis>C99 &amp; POSIX Conformance</emphasis></para>
+ <para><emphasis>C99 &amp; POSIX
+ Conformance</emphasis></para>
- <para>This is a forum for technical discussions related to
- FreeBSD Conformance to the C99 and the POSIX standards.</para>
+ <para>This is a forum for technical discussions related
+ to FreeBSD Conformance to the C99 and the POSIX
+ standards.</para>
</listitem>
</varlistentry>
@@ -1690,22 +1820,22 @@
<listitem>
<para><emphasis>Maintenance of FreeBSD's integrated
- toolchain</emphasis></para>
+ toolchain</emphasis></para>
- <para>This is the mailing list for discussions related to
- the maintenance of the toolchain shipped with &os;. This
- could include the state of Clang and GCC, but also pieces
- of software such as assemblers, linkers and
+ <para>This is the mailing list for discussions related
+ to the maintenance of the toolchain shipped with &os;.
+ This could include the state of Clang and GCC, but also
+ pieces of software such as assemblers, linkers and
debuggers.</para>
- </listitem>
- </varlistentry>
+ </listitem>
+ </varlistentry>
<varlistentry>
<term>&a.usb.name;</term>
<listitem>
<para><emphasis>Discussing &os; support for
- USB</emphasis></para>
+ USB</emphasis></para>
<para>This is a mailing list for technical discussions
related to &os; support for USB.</para>
@@ -1716,13 +1846,15 @@
<term>&a.usergroups.name;</term>
<listitem>
- <para><emphasis>User Group Coordination List</emphasis></para>
-
- <para>This is the mailing list for the coordinators from each of
- the local area Users Groups to discuss matters with each other
- and a designated individual from the Core Team. This mail list
- should be limited to meeting synopsis and coordination of
- projects that span User Groups.</para>
+ <para><emphasis>User Group Coordination
+ List</emphasis></para>
+
+ <para>This is the mailing list for the coordinators from
+ each of the local area Users Groups to discuss matters
+ with each other and a designated individual from the
+ Core Team. This mail list should be limited to meeting
+ synopsis and coordination of projects that span User
+ Groups.</para>
</listitem>
</varlistentry>
@@ -1732,8 +1864,9 @@
<listitem>
<para><emphasis>Vendors</emphasis></para>
- <para>Coordination discussions between The FreeBSD Project and
- Vendors of software and hardware for FreeBSD.</para>
+ <para>Coordination discussions between The FreeBSD
+ Project and Vendors of software and hardware for
+ FreeBSD.</para>
</listitem>
</varlistentry>
@@ -1742,14 +1875,14 @@
<listitem>
<para><emphasis>Discussion of various virtualization
- techniques supported by &os;</emphasis></para>
+ techniques supported by &os;</emphasis></para>
<para>A list to discuss the various virtualization
- techniques supported by &os;. On one hand the focus will
- be on the implementation of the basic functionality as
- well as adding new features. On the other hand users
- will have a forum to ask for help in case of problems
- or to discuss their use cases.</para>
+ techniques supported by &os;. On one hand the focus
+ will be on the implementation of the basic functionality
+ as well as adding new features. On the other hand users
+ will have a forum to ask for help in case of problems or
+ to discuss their use cases.</para>
</listitem>
</varlistentry>
@@ -1757,7 +1890,8 @@
<term>&a.wip-status.name;</term>
<listitem>
- <para><emphasis>&os; Work-In-Progress Status</emphasis></para>
+ <para><emphasis>&os; Work-In-Progress
+ Status</emphasis></para>
<para>This mailing list can be used to announce creation
and progress of your &os; related work. Messages
@@ -1773,9 +1907,10 @@
<para>An editorial digest of the messages to this list
might be posted to the &os; website every few month
as part of the Status Reports
- <footnote><para><ulink url="http://www.freebsd.org/news/status/"></ulink></para></footnote>.
- You can find more
- examples and past reports there, too.</para>
+ <footnote><para><ulink
+ url="http://www.freebsd.org/news/status/"></ulink></para></footnote>.
+ You can find more examples and past reports there,
+ too.</para>
</listitem>
</varlistentry>
@@ -1784,7 +1919,7 @@
<listitem>
<para><emphasis>Discussions of 802.11 stack, tools device
- driver development</emphasis></para>
+ driver development</emphasis></para>
<para>The FreeBSD-wireless list focuses on 802.11 stack
(sys/net80211), device driver and tools development.
@@ -1797,9 +1932,9 @@
<listitem>
<para><emphasis>Discussion of the &os; port to &xen;
- &mdash; implementation and usage</emphasis></para>
+ &mdash; implementation and usage</emphasis></para>
- <para>A list that focuses on the &os; &xen; port. The
+ <para>A list that focuses on the &os; &xen; port. The
anticipated traffic level is small enough that it is
intended as a forum for both technical discussions of
the implementation and design details as well as
@@ -1813,13 +1948,14 @@
<listitem>
<para><emphasis>XFCE</emphasis></para>
- <para>This is a forum for discussions related to bring the
- <application>XFCE</application> environment to &os;. This
- is a technical mailing list. It is for individuals actively
- working on porting <application>XFCE</application> to &os;,
- to bring up problems or discuss alternative solutions.
- Individuals interested in following the technical discussion
- are also welcome.</para>
+ <para>This is a forum for discussions related to bring
+ the <application>XFCE</application> environment to &os;.
+ This is a technical mailing list. It is for individuals
+ actively working on porting
+ <application>XFCE</application> to &os;, to bring up
+ problems or discuss alternative solutions. Individuals
+ interested in following the technical discussion are
+ also welcome.</para>
</listitem>
</varlistentry>
@@ -1829,13 +1965,14 @@
<listitem>
<para><emphasis>Zope</emphasis></para>
- <para>This is a forum for discussions related to bring the
- <application>Zope</application> environment to &os;. This
- is a technical mailing list. It is for individuals actively
- working on porting <application>Zope</application> to &os;,
- to bring up problems or discuss alternative solutions.
- Individuals interested in following the technical discussion
- are also welcome.</para>
+ <para>This is a forum for discussions related to bring
+ the <application>Zope</application> environment to &os;.
+ This is a technical mailing list. It is for individuals
+ actively working on porting
+ <application>Zope</application> to &os;, to bring up
+ problems or discuss alternative solutions. Individuals
+ interested in following the technical discussion are
+ also welcome.</para>
</listitem>
</varlistentry>
</variablelist>
@@ -1844,9 +1981,10 @@
<title>Filtering on the Mailing Lists</title>
<para>The &os; mailing lists are filtered in multiple ways to
- avoid the distribution of spam, viruses, and other unwanted emails.
- The filtering actions described in this section do not include all
- those used to protect the mailing lists.</para>
+ avoid the distribution of spam, viruses, and other unwanted
+ emails. The filtering actions described in this section do
+ not include all those used to protect the mailing
+ lists.</para>
<para>Only certain types of attachments are allowed on the
mailing lists. All attachments with a MIME content type not
@@ -1909,18 +2047,19 @@
applicable for most of the mailing lists.</para>
</note>
- <para>If an email contains both an HTML and a plain text version,
- the HTML version will be removed. If an email contains only an
- HTML version, it will be converted to plain text.</para>
+ <para>If an email contains both an HTML and a plain text
+ version, the HTML version will be removed. If an email
+ contains only an HTML version, it will be converted to plain
+ text.</para>
</sect2>
</sect1>
<sect1 id="eresources-news">
<title>Usenet Newsgroups</title>
- <para>In addition to two FreeBSD specific newsgroups, there are many
- others in which FreeBSD is discussed or are otherwise relevant to
- FreeBSD users.</para>
+ <para>In addition to two FreeBSD specific newsgroups, there are
+ many others in which FreeBSD is discussed or are otherwise
+ relevant to FreeBSD users.</para>
<sect2>
<title>BSD Specific Newsgroups</title>
@@ -1938,22 +2077,20 @@
<listitem>
<para><ulink
- url="news:de.comp.os.unix.bsd">de.comp.os.unix.bsd</ulink> (German)</para>
+ url="news:de.comp.os.unix.bsd">de.comp.os.unix.bsd</ulink>
+ (German)</para>
</listitem>
<listitem>
<para><ulink
- url="news:fr.comp.os.bsd">fr.comp.os.bsd</ulink> (French)</para>
+ url="news:fr.comp.os.bsd">fr.comp.os.bsd</ulink>
+ (French)</para>
</listitem>
<listitem>
<para><ulink
- url="news:it.comp.os.freebsd">it.comp.os.freebsd</ulink> (Italian)</para>
- </listitem>
-
- <listitem>
- <para><ulink
- url="news:tw.bbs.comp.386bsd">tw.bbs.comp.386bsd</ulink> (Traditional Chinese)</para>
+ url="news:it.comp.os.freebsd">it.comp.os.freebsd</ulink>
+ (Italian)</para>
</listitem>
</itemizedlist>
</sect2>
@@ -2013,16 +2150,6 @@
<listitem>
<para><ulink
- url="news:comp.bugs.4bsd">comp.bugs.4bsd</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink
- url="news:comp.bugs.4bsd.ucb-fixes">comp.bugs.4bsd.ucb-fixes</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink
url="news:comp.unix.bsd">comp.unix.bsd</ulink></para>
</listitem>
</itemizedlist>
@@ -2082,20 +2209,20 @@
<title>Forums, Blogs, and Social Networks</title>
<itemizedlist>
- <listitem><para><ulink url="http://forums.freebsd.org/">The
- FreeBSD Forums</ulink> provide a web based discussion forum
- for FreeBSD questions and technical
- discussion.</para></listitem>
+ <listitem><para><ulink url="http://forums.freebsd.org/">The
+ FreeBSD Forums</ulink> provide a web based discussion
+ forum for FreeBSD questions and technical
+ discussion.</para></listitem>
<listitem><para><ulink
- url="http://planet.freebsdish.org/">Planet FreeBSD</ulink>
+ url="http://planet.freebsdish.org/">Planet FreeBSD</ulink>
offers an aggregation feed of dozens of blogs written by
FreeBSD developers. Many developers use this to post quick
notes about what they are working on, new patches, and other
works in progress.</para></listitem>
<listitem><para>The <ulink
- url="http://www.youtube.com/bsdconferences">BSDConferences
+ url="http://www.youtube.com/bsdconferences">BSDConferences
YouTube Channel</ulink> provides a collection of high
quality videos from BSD Conferences around the world. This
is a great way to watch key developers give presentations
@@ -2117,19 +2244,20 @@
<sect1 id="eresources-email">
<title>Email Addresses</title>
- <para>The following user groups provide FreeBSD related email addresses
- for their members. The listed administrator reserves the right to
- revoke the address if it is abused in any way.</para>
+ <para>The following user groups provide FreeBSD related email
+ addresses for their members. The listed administrator reserves
+ the right to revoke the address if it is abused in any
+ way.</para>
<informaltable frame="none" pgwide="1">
<tgroup cols="4">
- <thead>
+ <thead>
<row>
<entry>Domain</entry>
<entry>Facilities</entry>
<entry>User Group</entry>
<entry>Administrator</entry>
- </row>
+ </row>
</thead>
<tbody>