aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/books/handbook/eresources/chapter.xml
diff options
context:
space:
mode:
Diffstat (limited to 'en_US.ISO8859-1/books/handbook/eresources/chapter.xml')
-rw-r--r--en_US.ISO8859-1/books/handbook/eresources/chapter.xml370
1 files changed, 183 insertions, 187 deletions
diff --git a/en_US.ISO8859-1/books/handbook/eresources/chapter.xml b/en_US.ISO8859-1/books/handbook/eresources/chapter.xml
index af585cf8b8..0ea9b6e6a0 100644
--- a/en_US.ISO8859-1/books/handbook/eresources/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/eresources/chapter.xml
@@ -8,18 +8,18 @@
<appendix id="eresources">
<title>Resources on the Internet</title>
- <para>The rapid pace of FreeBSD progress makes print media
+ <para>The rapid pace of &os; 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
+ to stay informed of the latest advances. Since &os; 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
+ <para>The most important points of contact with the &os; user
+ community are outlined below. Please send other resources
+ not mentioned here to the &a.doc; so that they
may also be included.</para>
<sect1 id="eresources-mail">
@@ -27,23 +27,23 @@
<para>The mailing lists are the most direct way of addressing
questions or opening a technical discussion to a concentrated
- FreeBSD audience. There are a wide variety of lists on a number
- of different FreeBSD topics. Addressing your questions to the
+ &os; audience. There are a wide variety of lists on a number
+ of different &os; topics. Sending questions to the
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
+ joining or sending mail to any list</emphasis>. Most
+ list subscribers receive many hundreds of &os; related
+ messages every day, and the charters and rules for
+ use are meant 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>
+ Project.</para>
<note>
- <para><emphasis>If you wish to test your ability to send to
+ <para><emphasis>To test the ability to send email to
&os; lists, send a test message to &a.test.name;.</emphasis>
Please do not send test messages to any other list.</para>
</note>
@@ -61,11 +61,11 @@
<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
+ url="&url.base;/search/index.html">&os; 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
+ this also means that messages sent to &os; 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>
@@ -89,12 +89,13 @@
<tbody>
<row>
<entry>&a.advocacy.name;</entry>
- <entry>FreeBSD Evangelism</entry>
+ <entry>&os; Evangelism</entry>
</row>
<row>
<entry>&a.announce.name;</entry>
- <entry>Important events and project milestones (moderated)</entry>
+ <entry>Important events and Project milestones
+(moderated)</entry>
</row>
<row>
@@ -105,7 +106,7 @@
<row>
<entry>&a.bugbusters.name;</entry>
<entry>Discussions pertaining to the maintenance of
- the FreeBSD problem report database and related
+ the &os; problem report database and related
tools</entry>
</row>
@@ -116,13 +117,13 @@
<row>
<entry>&a.chat.name;</entry>
- <entry>Non-technical items related to the FreeBSD
+ <entry>Non-technical items related to the &os;
community</entry>
</row>
<row>
<entry>&a.chromium.name;</entry>
- <entry>FreeBSD-specific Chromium issues</entry>
+ <entry>&os;-specific Chromium issues</entry>
</row>
<row>
@@ -134,12 +135,12 @@
<row>
<entry>&a.isp.name;</entry>
<entry>Issues for Internet Service Providers using
- FreeBSD</entry>
+ &os;</entry>
</row>
<row>
<entry>&a.jobs.name;</entry>
- <entry>FreeBSD employment and consulting
+ <entry>&os; employment and consulting
opportunities</entry>
</row>
@@ -161,7 +162,7 @@
<row>
<entry>&a.test.name;</entry>
- <entry>Where to send your test messages instead of
+ <entry>Where to send test messages instead of to
one of the actual lists</entry>
</row>
</tbody>
@@ -169,7 +170,7 @@
</informaltable>
<para><emphasis>Technical lists:</emphasis> The following
- lists are for technical discussion. You should read the
+ lists are for technical discussion. 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>
@@ -191,7 +192,7 @@
<row>
<entry>&a.afs.name;</entry>
- <entry>Porting AFS to FreeBSD</entry>
+ <entry>Porting AFS to &os;</entry>
</row>
<row>
@@ -202,7 +203,7 @@
<row>
<entry>&a.amd64.name;</entry>
- <entry>Porting FreeBSD to AMD64 systems (moderated)</entry>
+ <entry>Porting &os; to AMD64 systems (moderated)</entry>
</row>
<row>
@@ -214,22 +215,22 @@
<row>
<entry>&a.arm.name;</entry>
- <entry>Porting FreeBSD to &arm; processors</entry>
+ <entry>Porting &os; to &arm; processors</entry>
</row>
<row>
<entry>&a.atm.name;</entry>
- <entry>Using ATM networking with FreeBSD</entry>
+ <entry>Using ATM networking with &os;</entry>
</row>
<row>
<entry>&a.bluetooth.name;</entry>
- <entry>Using &bluetooth; technology in FreeBSD</entry>
+ <entry>Using &bluetooth; technology in &os;</entry>
</row>
<row>
<entry>&a.cluster.name;</entry>
- <entry>Using FreeBSD in a clustered environment</entry>
+ <entry>Using &os; in a clustered environment</entry>
</row>
<row>
@@ -240,7 +241,7 @@
<row>
<entry>&a.database.name;</entry>
<entry>Discussing database use and development under
- FreeBSD</entry>
+ &os;</entry>
</row>
<row>
@@ -250,7 +251,7 @@
<row>
<entry>&a.doc.name;</entry>
- <entry>Creating FreeBSD related documents</entry>
+ <entry>Creating &os; related documents</entry>
</row>
<row>
@@ -265,19 +266,19 @@
<row>
<entry>&a.eclipse.name;</entry>
- <entry>FreeBSD users of Eclipse IDE, tools, rich client
+ <entry>&os; users of Eclipse IDE, tools, rich client
applications and ports.</entry>
</row>
<row>
<entry>&a.embedded.name;</entry>
- <entry>Using FreeBSD in embedded applications</entry>
+ <entry>Using &os; in embedded applications</entry>
</row>
<row>
<entry>&a.eol.name;</entry>
- <entry>Peer support of FreeBSD-related software that
- is no longer supported by the FreeBSD project.</entry>
+ <entry>Peer support of &os;-related software that
+ is no longer supported by the &os; Project.</entry>
</row>
<row>
@@ -288,7 +289,7 @@
<row>
<entry>&a.firewire.name;</entry>
- <entry>FreeBSD &firewire; (iLink, IEEE 1394) technical
+ <entry>&os; &firewire; (iLink, IEEE 1394) technical
discussion</entry>
</row>
@@ -323,29 +324,29 @@
<row>
<entry>&a.hardware.name;</entry>
<entry>General discussion of hardware for running
- FreeBSD</entry>
+ &os;</entry>
</row>
<row>
<entry>&a.i18n.name;</entry>
- <entry>FreeBSD Internationalization</entry>
+ <entry>&os; Internationalization</entry>
</row>
<row>
<entry>&a.ia32.name;</entry>
- <entry>FreeBSD on the IA-32 (&intel; x86)
+ <entry>&os; on the IA-32 (&intel; x86)
platform</entry>
</row>
<row>
<entry>&a.ia64.name;</entry>
- <entry>Porting FreeBSD to &intel;'s upcoming IA64
+ <entry>Porting &os; to &intel;'s upcoming IA64
systems</entry>
</row>
<row>
<entry>&a.infiniband.name;</entry>
- <entry>Infiniband on FreeBSD</entry>
+ <entry>Infiniband on &os;</entry>
</row>
<row>
@@ -368,23 +369,17 @@
<row>
<entry>&a.java.name;</entry>
<entry>&java; developers and people porting &jdk;s to
- FreeBSD</entry>
- </row>
-
- <row>
- <entry>&a.kde.name;</entry>
- <entry>Porting <application>KDE</application> and
- <application>KDE</application> applications</entry>
+ &os;</entry>
</row>
<row>
<entry>&a.lfs.name;</entry>
- <entry>Porting LFS to FreeBSD</entry>
+ <entry>Porting LFS to &os;</entry>
</row>
<row>
<entry>&a.mips.name;</entry>
- <entry>Porting FreeBSD to &mips;</entry>
+ <entry>Porting &os; to &mips;</entry>
</row>
<row>
@@ -394,13 +389,13 @@
<row>
<entry>&a.mono.name;</entry>
- <entry>Mono and C# applications on FreeBSD</entry>
+ <entry>Mono and C# applications on &os;</entry>
</row>
<row>
<entry>&a.mozilla.name;</entry>
<entry>Porting <application>Mozilla</application> to
- FreeBSD</entry>
+ &os;</entry>
</row>
<row>
@@ -473,18 +468,18 @@
<row>
<entry>&a.ppc.name;</entry>
- <entry>Porting FreeBSD to the &powerpc;</entry>
+ <entry>Porting &os; to the &powerpc;</entry>
</row>
<row>
<entry>&a.proliant.name;</entry>
- <entry>Technical discussion of FreeBSD on HP ProLiant
+ <entry>Technical discussion of &os; on HP ProLiant
server platforms</entry>
</row>
<row>
<entry>&a.python.name;</entry>
- <entry>FreeBSD-specific Python issues</entry>
+ <entry>&os;-specific Python issues</entry>
</row>
<row>
@@ -497,12 +492,12 @@
<row>
<entry>&a.realtime.name;</entry>
<entry>Development of realtime extensions to
- FreeBSD</entry>
+ &os;</entry>
</row>
<row>
<entry>&a.ruby.name;</entry>
- <entry>FreeBSD-specific Ruby discussions</entry>
+ <entry>&os;-specific Ruby discussions</entry>
</row>
<row>
@@ -512,12 +507,12 @@
<row>
<entry>&a.security.name;</entry>
- <entry>Security issues affecting FreeBSD</entry>
+ <entry>Security issues affecting &os;</entry>
</row>
<row>
<entry>&a.small.name;</entry>
- <entry>Using FreeBSD in embedded applications
+ <entry>Using &os; in embedded applications
(obsolete; use &a.embedded.name; instead)</entry>
</row>
@@ -528,12 +523,12 @@
<row>
<entry>&a.sparc.name;</entry>
- <entry>Porting FreeBSD to &sparc; based systems</entry>
+ <entry>Porting &os; to &sparc; based systems</entry>
</row>
<row>
<entry>&a.standards.name;</entry>
- <entry>FreeBSD's conformance to the C99 and the &posix;
+ <entry>&os;'s conformance to the C99 and the &posix;
standards</entry>
</row>
@@ -544,7 +539,7 @@
<row>
<entry>&a.tcltk.name;</entry>
- <entry>FreeBSD-specific Tcl/Tk discussions</entry>
+ <entry>&os;-specific Tcl/Tk discussions</entry>
</row>
<row>
@@ -561,18 +556,18 @@
<row>
<entry>&a.threads.name;</entry>
- <entry>Threading in FreeBSD</entry>
+ <entry>Threading in &os;</entry>
</row>
<row>
<entry>&a.tilera.name;</entry>
- <entry>Porting FreeBSD to the Tilera family of
+ <entry>Porting &os; to the Tilera family of
CPUs</entry>
</row>
<row>
<entry>&a.tokenring.name;</entry>
- <entry>Support Token Ring in FreeBSD</entry>
+ <entry>Support Token Ring in &os;</entry>
</row>
<row>
@@ -599,7 +594,7 @@
<row>
<entry>&a.x11.name;</entry>
- <entry>Maintenance and support of X11 on FreeBSD</entry>
+ <entry>Maintenance and support of X11 on &os;</entry>
</row>
<row>
@@ -627,7 +622,7 @@
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
+ before joining one of these limited lists in order to
understand the communications etiquette involved.</para>
<informaltable frame="none" pgwide="1">
@@ -653,7 +648,7 @@
<row>
<entry>&a.wip-status.name;</entry>
- <entry>FreeBSD Work-In-Progress Status</entry>
+ <entry>&os; Work-In-Progress Status</entry>
</row>
<row>
@@ -667,7 +662,7 @@
<para><emphasis>Digest lists:</emphasis> 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
+ the digest options can be changed in the account options
section.</para>
<para><emphasis>SVN lists:</emphasis> The following lists
@@ -851,38 +846,38 @@
<sect2 id="eresources-subscribe">
<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>
+ <para>To subscribe to a list, click the list name at
+ &a.mailman.lists.link;.
+ The page that is displayed should contain all of the
+ necessary subscription instructions for that list.</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>
- <para>To unsubscribe yourself from a list, click on the URL
+ <para>To unsubscribe 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>
+ to unsubscribe.</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>
+ <para>It is important to keep discussion
+ in the technical mailing lists on a technical track. To
+ only receive important announcements, instead
+ join the &a.announce;, which is intended
+ for infrequent traffic.</para>
</sect2>
<sect2 id="eresources-charters">
<title>List Charters</title>
- <para><emphasis>All</emphasis> FreeBSD mailing lists have
+ <para><emphasis>All</emphasis> &os; 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
+ in two (2) written warnings from the &os; Postmaster
<email>postmaster@FreeBSD.org</email>, after which, on a
- third offense, the poster will removed from all FreeBSD
+ third offense, the poster will removed from all &os;
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
@@ -894,8 +889,8 @@
<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
+ charter of the list it is posted to. If the list
+ is about technical issues, the 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
@@ -910,11 +905,11 @@
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
+ a time. If a message is received with
+ multiple mailing lists on the <literal>Cc</literal>
+ line, trim the <literal>Cc</literal> line
+ before replying. <emphasis>The person who replies is
+ still responsible for cross-posting, no matter
who the originator might have been.</emphasis></para>
</listitem>
@@ -932,7 +927,7 @@
</listitem>
<listitem>
- <para>Advertising of non-FreeBSD related products or
+ <para>Advertising of non-&os; 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>
@@ -971,10 +966,10 @@
milestones</emphasis></para>
<para>This is the mailing list for people interested
- only in occasional announcements of significant FreeBSD
+ only in occasional announcements of significant &os;
events. This includes announcements about snapshots
and other releases. It contains announcements of new
- FreeBSD capabilities. It may contain calls for
+ &os; capabilities. It may contain calls for
volunteers etc. This is a low volume, strictly
moderated mailing list.</para>
</listitem>
@@ -987,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 &os;
architecture. Messages will mostly be kept strictly
technical in nature. Examples of suitable topics
are:</para>
@@ -1020,9 +1015,9 @@
<term>&a.bluetooth.name;</term>
<listitem>
- <para><emphasis>&bluetooth; in FreeBSD</emphasis></para>
+ <para><emphasis>&bluetooth; in &os;</emphasis></para>
- <para>This is the forum where FreeBSD's &bluetooth; users
+ <para>This is the forum where &os;'s &bluetooth; users
congregate. Design issues, implementation details,
patches, bug reports, status reports, feature requests,
and all matters related to &bluetooth; are fair
@@ -1052,7 +1047,7 @@
<para><emphasis>Bug reports</emphasis></para>
<para>This is the mailing list for reporting bugs in
- FreeBSD. Whenever possible, bugs should be submitted
+ &os;. 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>
@@ -1063,7 +1058,7 @@
<term>&a.chat.name;</term>
<listitem>
- <para><emphasis>Non technical items related to the FreeBSD
+ <para><emphasis>Non technical items related to the &os;
community</emphasis></para>
<para>This list contains the overflow from the other
@@ -1083,11 +1078,11 @@
<term>&a.chromium.name;</term>
<listitem>
- <para><emphasis>FreeBSD-specific Chromium
+ <para><emphasis>&os;-specific Chromium
issues</emphasis></para>
<para>This is a list for the discussion of Chromium
- support for FreeBSD. This is a technical list to
+ support for &os;. This is a technical list to
discuss development and installation of Chromium.</para>
</listitem>
</varlistentry>
@@ -1096,11 +1091,11 @@
<term>&a.core.name;</term>
<listitem>
- <para><emphasis>FreeBSD core team</emphasis></para>
+ <para><emphasis>&os; core team</emphasis></para>
<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
+ &os;-related matter requires arbitration or
high-level scrutiny.</para>
</listitem>
</varlistentry>
@@ -1126,10 +1121,10 @@
<term>&a.cvsweb.name;</term>
<listitem>
- <para><emphasis>FreeBSD CVSweb Project</emphasis></para>
+ <para><emphasis>&os; CVSweb Project</emphasis></para>
<para>Technical discussions about use, development and
- maintenance of FreeBSD-CVSweb.</para>
+ maintenance of &os;-CVSweb.</para>
</listitem>
</varlistentry>
@@ -1151,12 +1146,12 @@
<term>&a.doc.name;</term>
<listitem>
- <para><emphasis>Documentation project</emphasis></para>
+ <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
+ for &os;. The members of this mailing list are
+ collectively referred to as <quote>The &os;
Documentation Project</quote>. It is an open list;
feel free to join and contribute!</para>
</listitem>
@@ -1221,13 +1216,13 @@
<term>&a.embedded.name;</term>
<listitem>
- <para><emphasis>Using FreeBSD in embedded
+ <para><emphasis>Using &os; in embedded
applications</emphasis></para>
- <para>This list discusses topics related to using FreeBSD
+ <para>This list discusses topics related to using &os;
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
+ the purpose of this list, embedded systems are
those computing devices which are not desktops and which
usually serve a single purpose as opposed to being
general computing environments. Examples include, but
@@ -1255,15 +1250,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><emphasis>Peer support of &os;-related software
+ that is no longer supported by the &os;
+ 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>
+ making use of peer support of &os;-related software
+ for which the &os; Project no longer provides
+ official support in the form of security
+ advisories and patches.</para>
</listitem>
</varlistentry>
@@ -1276,7 +1271,7 @@
<para>This is a mailing list for discussion of the design
and implementation of a &firewire; (aka IEEE 1394 aka
- iLink) subsystem for FreeBSD. Relevant topics
+ iLink) subsystem for &os;. 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
@@ -1290,7 +1285,7 @@
<listitem>
<para><emphasis>File systems</emphasis></para>
- <para>Discussions concerning FreeBSD file systems.
+ <para>Discussions concerning &os; filesystems.
This is a technical mailing list for which strictly
technical content is expected.</para>
</listitem>
@@ -1332,7 +1327,7 @@
<para>Discussions concerning The
<application>GNOME</application> Desktop Environment
- for FreeBSD systems. This is a technical mailing list
+ for &os; systems. This is a technical mailing list
for which strictly technical content is expected.</para>
</listitem>
</varlistentry>
@@ -1356,7 +1351,7 @@
<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
+ &os;. This is a technical mailing list for which
strictly technical content is expected.</para>
</listitem>
</varlistentry>
@@ -1365,10 +1360,10 @@
<term>&a.ia64.name;</term>
<listitem>
- <para><emphasis>Porting FreeBSD to IA64</emphasis></para>
+ <para><emphasis>Porting &os; to IA64</emphasis></para>
<para>This is a technical mailing list for individuals
- actively working on porting FreeBSD to the IA-64
+ actively working on porting &os; to the IA-64
platform from &intel;, to bring up problems or discuss
alternative solutions. Individuals interested in
following the technical discussion are also
@@ -1383,7 +1378,7 @@
<para><emphasis>ISDN Communications</emphasis></para>
<para>This is the mailing list for people discussing the
- development of ISDN support for FreeBSD.</para>
+ development of ISDN support for &os;.</para>
</listitem>
</varlistentry>
@@ -1395,7 +1390,7 @@
<para>This is the mailing list for people discussing the
development of significant &java; applications for
- FreeBSD and the porting and maintenance of
+ &os; and the porting and maintenance of
&jdk;s.</para>
</listitem>
</varlistentry>
@@ -1407,17 +1402,17 @@
<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
+ specifically related to &os; and resumes from those
+ seeking &os;-related employment. 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
+ is distributed worldwide. Be clear
+ about the geographic location and the extent to which
+ telecommuting or
assistance with relocation is available.</para>
<para>Email should use open formats only &mdash;
@@ -1436,7 +1431,7 @@
<para><emphasis>KDE</emphasis></para>
<para>Discussions concerning
- <application>KDE</application> on FreeBSD systems.
+ <application>KDE</application> on &os; systems.
This is a technical mailing list for which strictly
technical content is expected.</para>
</listitem>
@@ -1449,8 +1444,8 @@
<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
+ to &os;. This is the primary technical mailing list.
+ It is for individuals actively working on &os;, to
bring up problems or discuss alternative solutions.
Individuals interested in following the technical
discussion are also welcome. This is a technical
@@ -1463,11 +1458,11 @@
<term>&a.hardware.name;</term>
<listitem>
- <para><emphasis>General discussion of FreeBSD
+ <para><emphasis>General discussion of &os;
hardware</emphasis></para>
<para>General discussion about the types of hardware
- that FreeBSD runs on, various problems and suggestions
+ that &os; runs on, various problems and suggestions
concerning what to buy or avoid.</para>
</listitem>
</varlistentry>
@@ -1479,7 +1474,7 @@
<para><emphasis>Mirror sites</emphasis></para>
<para>Announcements and discussion for people who run
- FreeBSD mirror sites.</para>
+ &os; mirror sites.</para>
</listitem>
</varlistentry>
@@ -1491,7 +1486,7 @@
Providers</emphasis></para>
<para>This mailing list is for discussing topics relevant
- to Internet Service Providers (ISPs) using FreeBSD.
+ to Internet Service Providers (ISPs) using &os;.
This is a technical mailing list for which strictly
technical content is expected.</para>
</listitem>
@@ -1502,7 +1497,7 @@
<listitem>
<para><emphasis>Mono and C# applications on
- FreeBSD</emphasis></para>
+ &os;</emphasis></para>
<para>This is a list for discussions related to the Mono
development framework on &os;. This is a technical
@@ -1535,7 +1530,7 @@
Announcements</emphasis></para>
<para>This is the mailing list for people interested in
- changes and issues related to the FreeBSD.org project
+ changes and issues related to the FreeBSD.org Project
infrastructure.</para>
<para>This moderated list is strictly for announcements: no replies,
@@ -1547,21 +1542,21 @@
<term>&a.performance.name;</term>
<listitem>
- <para><emphasis>Discussions about tuning or speedingup
- FreeBSD</emphasis></para>
+ <para><emphasis>Discussions about tuning or speeding up
+ &os;</emphasis></para>
<para>This mailing list exists to provide a place for
hackers, administrators, and/or concerned parties to
discuss performance related topics pertaining to
- FreeBSD. Acceptable topics includes talking about
- FreeBSD installations that are either under high load,
+ &os;. Acceptable topics includes talking about
+ &os; installations that are either under high load,
are experiencing performance problems, or are pushing
- the limits of FreeBSD. Concerned parties that are
+ the limits of &os;. Concerned parties that are
willing to work toward improving the performance of
- FreeBSD are highly encouraged to subscribe to this list.
+ &os; are highly encouraged to subscribe to this list.
This is a highly technical list ideally suited for
- experienced FreeBSD users, hackers, or administrators
- interested in keeping FreeBSD fast, robust, and
+ experienced &os; users, hackers, or administrators
+ interested in keeping &os; fast, robust, and
scalable. This list is not a question-and-answer list
that replaces reading through documentation, but it is a
place to make contributions or inquire about unanswered
@@ -1578,7 +1573,7 @@
filter firewall system</emphasis></para>
<para>Discussion concerning the packet filter (pf)
- firewall system in terms of FreeBSD. Technical
+ firewall system in terms of &os;. Technical
discussion and user questions are both welcome. This
list is also a place to discuss the ALTQ QoS
framework.</para>
@@ -1613,8 +1608,8 @@
<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
+ <para>Cross-platform &os; issues, general discussion
+ and proposals for non &intel; &os; ports. This is
a technical mailing list for which strictly technical
content is expected.</para>
</listitem>
@@ -1627,7 +1622,7 @@
<para><emphasis>Discussion of
<quote>ports</quote></emphasis></para>
- <para>Discussions concerning FreeBSD's <quote>ports
+ <para>Discussions concerning &os;'s <quote>ports
collection</quote> (<filename>/usr/ports</filename>),
ports infrastructure, and general ports coordination
efforts. This is a technical mailing list for which
@@ -1660,7 +1655,7 @@
<para><emphasis>Discussion of
<quote>ports</quote> bugs</emphasis></para>
- <para>Discussions concerning problem reports for FreeBSD's
+ <para>Discussions concerning problem reports for &os;'s
<quote>ports collection</quote>
(<filename>/usr/ports</filename>), proposed ports, or
modifications to ports. This is a technical mailing
@@ -1673,11 +1668,11 @@
<term>&a.proliant.name;</term>
<listitem>
- <para><emphasis>Technical discussion of FreeBSD on HP
+ <para><emphasis>Technical discussion of &os; on HP
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
+ discussion of the usage of &os; 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
@@ -1690,13 +1685,13 @@
<term>&a.python.name;</term>
<listitem>
- <para><emphasis>Python on FreeBSD</emphasis></para>
+ <para><emphasis>Python on &os;</emphasis></para>
<para>This is a list for discussions related to improving
- Python-support on FreeBSD. This is a technical mailing
+ Python-support on &os;. 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.
+ <application>Zope</application> stuff to &os;.
Individuals interested in following the technical
discussion are also welcome.</para>
</listitem>
@@ -1709,9 +1704,9 @@
<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>
+ &os;. Do not send <quote>how to</quote>
+ questions to the technical lists unless
+ the question is quite technical.</para>
</listitem>
</varlistentry>
@@ -1719,11 +1714,11 @@
<term>&a.ruby.name;</term>
<listitem>
- <para><emphasis>FreeBSD-specific Ruby
+ <para><emphasis>&os;-specific Ruby
discussions</emphasis></para>
<para>This is a list for discussions related to the Ruby
- support on FreeBSD. This is a technical mailing
+ support on &os;. This is a technical mailing
list. It is for individuals working on Ruby ports,
3rd party libraries and frameworks.</para>
@@ -1739,7 +1734,7 @@
<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
+ the SCSI subsystem for &os;. This is a technical
mailing list for which strictly technical content is
expected.</para>
</listitem>
@@ -1751,7 +1746,7 @@
<listitem>
<para><emphasis>Security issues</emphasis></para>
- <para>FreeBSD computer security issues (DES, Kerberos,
+ <para>&os; 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
@@ -1766,7 +1761,7 @@
<listitem>
<para><emphasis>Security Notifications</emphasis></para>
- <para>Notifications of FreeBSD security problems and
+ <para>Notifications of &os; security problems and
fixes. This is not a discussion list. The discussion
list is FreeBSD-security.</para>
</listitem>
@@ -1776,11 +1771,11 @@
<term>&a.small.name;</term>
<listitem>
- <para><emphasis>Using FreeBSD in embedded
+ <para><emphasis>Using &os; in embedded
applications</emphasis></para>
<para>This list discusses topics related to unusually
- small and embedded FreeBSD installations. This is a
+ small and embedded &os; installations. This is a
technical mailing list for which strictly technical
content is expected.</para>
@@ -1799,7 +1794,8 @@
<para><emphasis>&os; Development Snapshot
Announcements</emphasis></para>
- <para>This list will notify you about the availability
+ <para>This list provides notifications about the
+ availability
of new &os; development snapshots for the head/ and
stable/ branches.</para>
</listitem>
@@ -1830,7 +1826,7 @@
Conformance</emphasis></para>
<para>This is a forum for technical discussions related
- to FreeBSD Conformance to the C99 and the POSIX
+ to &os; Conformance to the C99 and the POSIX
standards.</para>
</listitem>
</varlistentry>
@@ -1868,7 +1864,7 @@
<term>&a.toolchain.name;</term>
<listitem>
- <para><emphasis>Maintenance of FreeBSD's integrated
+ <para><emphasis>Maintenance of &os;'s integrated
toolchain</emphasis></para>
<para>This is the mailing list for discussions related
@@ -1930,11 +1926,12 @@
<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
+ <para>This mailing list can be used by developers to
+ announce the creation
+ and progress of &os; related work. Messages
will be moderated. It is suggested to send the message
"To:" a more topical &os; list and only "BCC:"
- this list. This way your WIP can also be discussed on
+ this list. This way the WIP can also be discussed on
the topical list, as no discussion is allowed on this
list.</para>
@@ -1942,12 +1939,11 @@
messages.</para>
<para>An editorial digest of the messages to this list
- might be posted to the &os; website every few month
+ might be posted to the &os; website every few months
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>
+ Past reports are archived.</para>
</listitem>
</varlistentry>
@@ -2094,9 +2090,9 @@
<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 &os; specific newsgroups, there are
+ many others in which &os; is discussed or are otherwise
+ relevant to &os; users.</para>
<sect2>
<title>BSD Specific Newsgroups</title>
@@ -2247,14 +2243,14 @@
<itemizedlist>
<listitem><para><ulink url="http://forums.freebsd.org/">The
- FreeBSD Forums</ulink> provide a web based discussion
- forum for FreeBSD questions and technical
+ &os; Forums</ulink> provide a web based discussion
+ forum for &os; questions and technical
discussion.</para></listitem>
<listitem><para><ulink
- url="http://planet.freebsdish.org/">Planet FreeBSD</ulink>
+ url="http://planet.freebsdish.org/">Planet &os;</ulink>
offers an aggregation feed of dozens of blogs written by
- FreeBSD developers. Many developers use this to post quick
+ &os; developers. Many developers use this to post quick
notes about what they are working on, new patches, and other
works in progress.</para></listitem>
@@ -2263,7 +2259,7 @@
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
- about new work in FreeBSD.</para></listitem>
+ about new work in &os;.</para></listitem>
</itemizedlist>
</sect2>
@@ -2281,7 +2277,7 @@
<sect1 id="eresources-email">
<title>Email Addresses</title>
- <para>The following user groups provide FreeBSD related email
+ <para>The following user groups provide &os; related email
addresses for their members. The listed administrator reserves
the right to revoke the address if it is abused in any
way.</para>