os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
doc/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
Tom Rhodes 4f253fdb9b Put in alphabetical order that which is not. 
Whitespace only, no real content changes.

PR:		37807
Submitted by:	Johan Karlsson <k@numeri.campus.luth.se>
2002-05-10 15:24:14 +00:00

1760 lines
51 KiB
Text
Raw Blame History

<!--
The FreeBSD Documentation Project
$FreeBSD$
-->
<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 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 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>
<sect1 id="eresources-mail">
<title>Mailing Lists</title>
<para>Though many of the FreeBSD development members read USENET, we
cannot always guarantee that we will get to your questions in a timely
fashion (or at all) if you post them only to one of the
<literal>comp.unix.bsd.freebsd.*</literal> groups. By addressing your
questions to the appropriate mailing list you will reach both us and a
concentrated FreeBSD audience, invariably assuring a better (or at least
faster) 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>Archives are kept for all of the mailing lists and can be searched
using the <ulink url="../../../../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.</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>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>List</entry>
<entry>Purpose</entry>
</row>
</thead>
<tbody>
<row>
<entry>cvs-all</entry>
<entry>Changes made to the FreeBSD source tree</entry>
</row>
<row>
<entry>freebsd-advocacy</entry>
<entry>FreeBSD Evangelism</entry>
</row>
<row>
<entry>freebsd-announce</entry>
<entry>Important events and project milestones</entry>
</row>
<row>
<entry>freebsd-arch</entry>
<entry>Architecture and design discussions</entry>
</row>
<row>
<entry>freebsd-bugbusters</entry>
<entry>Discussions pertaining to the maintenance of the FreeBSD
problem report database and related tools</entry>
</row>
<row>
<entry>freebsd-bugs</entry>
<entry>Bug reports</entry>
</row>
<row>
<entry>freebsd-chat</entry>
<entry>Non-technical items related to the FreeBSD
community</entry>
</row>
<row>
<entry>freebsd-config</entry>
<entry>Development of FreeBSD installation and configuration tools</entry>
</row>
<row>
<entry>freebsd-current</entry>
<entry>Discussion concerning the use of
FreeBSD-current</entry>
</row>
<row>
<entry>freebsd-isp</entry>
<entry>Issues for Internet Service Providers using
FreeBSD</entry>
</row>
<row>
<entry>freebsd-jobs</entry>
<entry>FreeBSD employment and consulting
opportunities</entry>
</row>
<row>
<entry>freebsd-newbies</entry>
<entry>New FreeBSD users activities and discussions</entry>
</row>
<row>
<entry>freebsd-policy</entry>
<entry>FreeBSD Core team policy decisions. Low volume, and
read-only</entry>
</row>
<row>
<entry>freebsd-questions</entry>
<entry>User questions and technical support</entry>
</row>
<row>
<entry>freebsd-security</entry>
<entry>Security issues</entry>
</row>
<row>
<entry>freebsd-security-notifications</entry>
<entry>Security notifications</entry>
</row>
<row>
<entry>freebsd-stable</entry>
<entry>Discussion concerning the use of
FreeBSD-stable</entry>
</row>
<row>
<entry>freebsd-test</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>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>List</entry>
<entry>Purpose</entry>
</row>
</thead>
<tbody>
<row>
<entry>freebsd-afs</entry>
<entry>Porting AFS to FreeBSD</entry>
</row>
<row>
<entry>freebsd-aic7xxx</entry>
<entry>Developing drivers for the Adaptec AIC 7xxx</entry>
</row>
<row>
<entry>freebsd-alpha</entry>
<entry>Porting FreeBSD to the Alpha</entry>
</row>
<row>
<entry>freebsd-arm</entry>
<entry>Porting FreeBSD to ARM processors</entry>
</row>
<row>
<entry>freebsd-atm</entry>
<entry>Using ATM networking with FreeBSD</entry>
</row>
<row>
<entry>freebsd-audit</entry>
<entry>Source code audit project</entry>
</row>
<row>
<entry>freebsd-binup</entry>
<entry>Design and development of the binary update system</entry>
</row>
<row>
<entry>freebsd-cluster</entry>
<entry>Using FreeBSD in a clustered environment</entry>
</row>
<row>
<entry>freebsd-database</entry>
<entry>Discussing database use and development under
FreeBSD</entry>
</row>
<row>
<entry>freebsd-doc</entry>
<entry>Creating FreeBSD related documents</entry>
</row>
<row>
<entry>freebsd-emulation</entry>
<entry>Emulation of other systems such as
Linux/DOS/Windows</entry>
</row>
<row>
<entry>freebsd-firewire</entry>
<entry>FreeBSD Firewire (iLink, IEEE 1394) technical
discussion</entry>
</row>
<row>
<entry>freebsd-fs</entry>
<entry>Filesystems</entry>
</row>
<row>
<entry>freebsd-gnome</entry>
<entry>Porting GNOME and GNOME applications</entry>
</row>
<row>
<entry>freebsd-hackers</entry>
<entry>General technical discussion</entry>
</row>
<row>
<entry>freebsd-hardware</entry>
<entry>General discussion of hardware for running
FreeBSD</entry>
</row>
<row>
<entry>freebsd-i18n</entry>
<entry>FreeBSD Internationalization</entry>
</row>
<row>
<entry>freebsd-ia64</entry>
<entry>Porting FreeBSD to Intel's upcoming IA64 systems</entry>
</row>
<row>
<entry>freebsd-ipfw</entry>
<entry>Technical discussion concerning the redesign of the IP
firewall code</entry>
</row>
<row>
<entry>freebsd-isdn</entry>
<entry>ISDN developers</entry>
</row>
<row>
<entry>freebsd-java</entry>
<entry>Java developers and people porting JDKs to
FreeBSD</entry>
</row>
<row>
<entry>freebsd-lfs</entry>
<entry>Porting LFS to FreeBSD</entry>
</row>
<row>
<entry>freebsd-libh</entry>
<entry>The second generation installation and package
system</entry>
</row>
<row>
<entry>freebsd-mobile</entry>
<entry>Discussions about mobile computing</entry>
</row>
<row>
<entry>freebsd-mozilla</entry>
<entry>Porting mozilla to FreeBSD</entry>
</row>
<row>
<entry>freebsd-multimedia</entry>
<entry>Multimedia applications</entry>
</row>
<row>
<entry>freebsd-new-bus</entry>
<entry>Technical discussions about bus architecture</entry>
</row>
<row>
<entry>freebsd-net</entry>
<entry>Networking discussion and TCP/IP source code</entry>
</row>
<row>
<entry>freebsd-platforms</entry>
<entry>Concerning ports to non-Intel architecture
platforms</entry>
</row>
<row>
<entry>freebsd-ports</entry>
<entry>Discussion of the ports collection</entry>
</row>
<row>
<entry>freebsd-ppc</entry>
<entry>Porting FreeBSD to the PowerPC</entry>
</row>
<row>
<entry>freebsd-qa</entry>
<entry>Discussion of Quality Assurance, usually pending a release</entry>
</row>
<row>
<entry>freebsd-realtime</entry>
<entry>Development of realtime extensions to FreeBSD</entry>
</row>
<row>
<entry>freebsd-scsi</entry>
<entry>The SCSI subsystem</entry>
</row>
<row>
<entry>freebsd-small</entry>
<entry>Using FreeBSD in embedded applications</entry>
</row>
<row>
<entry>freebsd-smp</entry>
<entry>Design discussions for [A]Symmetric
MultiProcessing</entry>
</row>
<row>
<entry>freebsd-sparc</entry>
<entry>Porting FreeBSD to SPARC based systems</entry>
</row>
<row>
<entry>freebsd-standards</entry>
<entry>FreeBSD's conformance to the C99 and the POSIX
standards</entry>
</row>
<row>
<entry>freebsd-tokenring</entry>
<entry>Support Token Ring in FreeBSD</entry>
</row>
</tbody>
</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>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>List</entry>
<entry>Purpose</entry>
</row>
</thead>
<tbody>
<row>
<entry>freebsd-core</entry>
<entry>FreeBSD core team</entry>
</row>
<row>
<entry>freebsd-hubs</entry>
<entry>People running mirror sites (infrastructural
support)</entry>
</row>
<row>
<entry>freebsd-install</entry>
<entry>Installation development</entry>
</row>
<row>
<entry>freebsd-user-groups</entry>
<entry>User group coordination</entry>
</row>
<row>
<entry>freebsd-vendors</entry>
<entry>Vendors pre-release coordination</entry>
</row>
<row>
<entry>freebsd-www</entry>
<entry>Maintainers of <ulink url="../../../../index.html">www.FreeBSD.org</ulink></entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para><emphasis>Digest lists:</emphasis> Many of the above lists are
also available as digests. New messages posted to the list are
collected and sent out as a single email when the sizes goes
over 100KB. The lists available in digest form are:</para>
<informaltable frame="none">
<tgroup cols="1">
<thead>
<row>
<entry>List</entry>
</row>
</thead>
<tbody>
<row>
<entry>freebsd-afs-digest</entry>
</row>
<row>
<entry>freebsd-alpha-digest</entry>
</row>
<row>
<entry>freebsd-chat-digest</entry>
</row>
<row>
<entry>freebsd-current-digest</entry>
</row>
<row>
<entry>freebsd-cvs-all-digest</entry>
</row>
<row>
<entry>freebsd-database-digest</entry>
</row>
<row>
<entry>freebsd-hackers-digest</entry>
</row>
<row>
<entry>freebsd-ia64-digest</entry>
</row>
<row>
<entry>freebsd-isdn-digest</entry>
</row>
<row>
<entry>freebsd-java-digest</entry>
</row>
<row>
<entry>freebsd-questions-digest</entry>
</row>
<row>
<entry>freebsd-security-digest</entry>
</row>
<row>
<entry>freebsd-sparc-digest</entry>
</row>
<row>
<entry>freebsd-stable-digest</entry>
</row>
<row>
<entry>freebsd-test-digest</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para><emphasis>CVS 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>
<informaltable frame="none">
<tgroup cols="3">
<thead>
<row>
<entry>List</entry>
<entry>Source area</entry>
<entry>Area Description (source for)</entry>
</row>
</thead>
<tbody>
<row>
<entry>cvs-all</entry>
<entry>/usr/src</entry>
<entry>All changes to the tree (superset)</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</sect2>
<sect2 id="eresources-subscribe">
<title>How to Subscribe</title>
<para>All mailing lists live on <hostid
role="fqdn">FreeBSD.org</hostid>, so to post to a given list you
simply mail to
&lt;<replaceable>listname</replaceable>@FreeBSD.org&gt;. It will then
be redistributed to mailing list members world-wide.</para>
<para>To subscribe to a list, send mail to &a.majordomo; and include
<programlisting>subscribe &lt;listname&gt; [&lt;optional address&gt;]</programlisting>
in the body of your message. For example, to subscribe yourself to
<literal>freebsd-announce</literal>, you would do:</para>
<screen>&prompt.user; <userinput>mail majordomo@FreeBSD.org</userinput>
subscribe freebsd-announce
^D</screen>
<para>If you want to subscribe yourself under a different name, or
submit a subscription request for a local mailing list (this is more
efficient if you have several interested parties at one site, and
highly appreciated by us!), you would do something like:</para>
<screen>&prompt.user; <userinput>mail majordomo@FreeBSD.org</userinput>
subscribe freebsd-announce local-announce@example.com
^D</screen>
<para>Finally, it is also possible to unsubscribe yourself from a list,
get a list of other list members or see the list of mailing lists
again by sending other types of control messages to majordomo. For a
complete list of available commands, do this:</para>
<screen>&prompt.user; <userinput>mail majordomo@FreeBSD.org</userinput>
help
^D</screen>
<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 freebsd-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>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;
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
"-stable &amp; -scsi"), there really is no reason to post to more
than one list at a time. If a message is sent to you in such a
way that multiple mailing lists appear on the
<literal>Cc</literal> line then the <literal>Cc</literal>
line should also be trimmed before sending it out again.
<emphasis>You are <emphasis>still</emphasis> 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>
</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>
</listitem>
</itemizedlist>
<para><emphasis>Individual list charters:</emphasis></para>
<variablelist>
<varlistentry>
<term>FREEBSD-AFS</term>
<listitem>
<para><emphasis>Andrew File System</emphasis></para>
<para>This list is for discussion on porting and using AFS from
CMU/Transarc</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-ANNOUNCE</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
moderated mailing list.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-ARCH</term>
<listitem>
<para><emphasis>Architecture and design
discussions</emphasis></para>
<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>
<itemizedlist>
<listitem>
<para>How to re-vamp the build system to have several
customized builds running at the same time.</para>
</listitem>
<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>
</listitem>
<listitem>
<para>How to write a network driver.</para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-AUDIT</term>
<listitem>
<para><emphasis>Source code audit project</emphasis></para>
<para>This is the mailing list for the FreeBSD source code
audit project. Although this was originally intended for
security-related changes, its charter has been expanded to
review any code changes.</para>
<para>This list is very heavy on patches, and is probably of no
interest to the average FreeBSD user. Security discussions
not related to a particular code change are held on
freebsd-security. Conversely, all developers are encouraged
to send their patches here for review, especially if they
touch a part of the system where a bug may adversely affect
the integrity of the system.</para>
<!-- I can't actually find a charter for this, but there's this email: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=223347+225804+/usr/local/www/db/text/2000/cvs-all/20001210.cvs-all -->
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-BINUP</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>FREEBSD-BUGBUSTERS</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>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-BUGS</term>
<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
url="../../../../send-pr.html">WEB
interface</ulink> to it.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-CHAT</term>
<listitem>
<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>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-CORE</term>
<listitem>
<para><emphasis>FreeBSD 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 high-level
scrutiny.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-CURRENT</term>
<listitem>
<para><emphasis>Discussions about the use of
FreeBSD-current</emphasis></para>
<para>This is the mailing list for users of freebsd-current. It
includes warnings about new features coming out in -current that
will affect the users, and instructions on steps that must be
taken to remain -current. Anyone running <quote>current</quote>
must subscribe to this list. This is a technical mailing list
for which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-CURRENT-DIGEST</term>
<listitem>
<para><emphasis>Discussions about the use of
FreeBSD-current</emphasis></para>
<para>This is the digest version of the freebsd-current mailing
list. The digest consists of all messages sent to
freebsd-current bundled together and mailed out as a single
message. This list is <emphasis>Read-Only</emphasis> and
should not be posted to.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-DOC</term>
<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>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-FIREWIRE</term>
<listitem>
<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
iLink) subsystem for FreeBSD. Relevant topics
specifically include the standards, bus devices and
their protocols, adapter boards/cards/chips sets, and
the architecture and implementation of code for their
proper support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-FS</term>
<listitem>
<para><emphasis>Filesystems</emphasis></para>
<para>Discussions concerning FreeBSD filesystems. This is a
technical mailing list for which strictly technical content is
expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-GNOME</term>
<listitem>
<para><emphasis>GNOME</emphasis></para>
<para>Discussions concerning The GNOME Desktop Environment for
FreeBSD filesystems. This is a technical mailing list for
which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-IPFW</term>
<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>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-IA64</term>
<listitem>
<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>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-ISDN</term>
<listitem>
<para><emphasis>ISDN Communications</emphasis></para>
<para>This is the mailing list for people discussing the
development of ISDN support for FreeBSD.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-JAVA</term>
<listitem>
<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 JDKs.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-HACKERS</term>
<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
expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-HACKERS-DIGEST</term>
<listitem>
<para><emphasis>Technical discussions</emphasis></para>
<para>This is the digest version of the freebsd-hackers mailing
list. The digest consists of all messages sent to
freebsd-hackers bundled together and mailed out as a single
message. This list is <emphasis>Read-Only</emphasis>
and should not be posted to.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-HARDWARE</term>
<listitem>
<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>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-HUBS</term>
<listitem>
<para><emphasis>Mirror sites</emphasis></para>
<para>Announcements and discussion for people who run FreeBSD
mirror sites.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-INSTALL</term>
<listitem>
<para><emphasis>Installation discussion</emphasis></para>
<para>This mailing list is for discussing FreeBSD installation
development for the future releases.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-ISP</term>
<listitem>
<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>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-NEWBIES</term>
<listitem>
<para><emphasis>Newbies activities discussion</emphasis></para>
<para>We cover any of the activities of newbies that are not
already dealt with elsewhere, including: independent learning
and problem solving techniques, finding and using resources and
asking for help elsewhere, how to use mailing lists and which
lists to use, general chat, making mistakes, boasting, sharing
ideas, stories, moral (but not technical) support, and taking an
active part in the FreeBSD community. We take our problems and
support questions to freebsd-questions, and use freebsd-newbies
to meet others who are doing the same things that we do as
newbies.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-PLATFORMS</term>
<listitem>
<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>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-POLICY</term>
<listitem>
<para><emphasis>Core team policy decisions</emphasis></para>
<para>This is a low volume, read-only mailing list for FreeBSD
Core Team Policy decisions.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-PORTS</term>
<listitem>
<para><emphasis>Discussion of
<quote>ports</quote></emphasis></para>
<para>Discussions concerning FreeBSD's <quote>ports
collection</quote> (<filename>/usr/ports</filename>), proposed
ports, modifications to ports collection infrastructure and
general coordination efforts. This is a technical mailing list
for which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-QUESTIONS</term>
<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>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-QUESTIONS-DIGEST</term>
<listitem>
<para><emphasis>User questions</emphasis></para>
<para>This is the digest version of the freebsd-questions mailing
list. The digest consists of all messages sent to
freebsd-questions bundled together and mailed out as a single
message.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-SCSI</term>
<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>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-SECURITY</term>
<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 content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-SECURITY-NOTIFICATIONS</term>
<listitem>
<para><emphasis>Security Notifications</emphasis></para>
<para>Notifications of FreeBSD security problems and
fixes. This is not a discussion list. The discussion
list is FreeBSD-security.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-SMALL</term>
<listitem>
<para><emphasis>Using FreeBSD in embedded
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>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-STABLE</term>
<listitem>
<para><emphasis>Discussions about the use of
FreeBSD-stable</emphasis></para>
<para>This is the mailing list for users of freebsd-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>
<varlistentry>
<term>FREEBSD-STANDARDS</term>
<listitem>
<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>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-USER-GROUPS</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>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-VENDORS</term>
<listitem>
<para><emphasis>VENDORS</emphasis></para>
<para>Coordination discussions between The FreeBSD Project and
Vendors of software and hardware for FreeBSD.</para>
</listitem>
</varlistentry>
</variablelist>
</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. <ulink
url="http://minnie.tuhs.org/BSD-info/bsdnews_search.html">Keyword
searchable archives</ulink> are available for some of these newsgroups
from courtesy of Warren Toomey <email>wkt@cs.adfa.edu.au</email>.</para>
<sect2>
<title>BSD Specific Newsgroups</title>
<itemizedlist>
<listitem>
<para><ulink
url="news:comp.unix.bsd.freebsd.announce">comp.unix.bsd.freebsd.announce</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.bsd.freebsd.misc">comp.unix.bsd.freebsd.misc</ulink></para>
</listitem>
</itemizedlist>
</sect2>
<sect2>
<title>Other Unix Newsgroups of Interest</title>
<itemizedlist>
<listitem>
<para><ulink url="news:comp.unix">comp.unix</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.questions">comp.unix.questions</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.admin">comp.unix.admin</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.programmer">comp.unix.programmer</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.shell">comp.unix.shell</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.user-friendly">comp.unix.user-friendly</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.security.unix">comp.security.unix</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.sources.unix">comp.sources.unix</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.advocacy">comp.unix.advocacy</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.misc">comp.unix.misc</ulink></para>
</listitem>
<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>
</sect2>
<sect2>
<title>X Window System</title>
<itemizedlist>
<listitem>
<para><ulink
url="news:comp.windows.x.i386unix">comp.windows.x.i386unix</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x">comp.windows.x</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.apps">comp.windows.x.apps</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.announce">comp.windows.x.announce</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.intrinsics">comp.windows.x.intrinsics</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.motif">comp.windows.x.motif</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.pex">comp.windows.x.pex</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.emulators.ms-windows.wine">comp.emulators.ms-windows.wine</ulink></para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="eresources-web">
<title>World Wide Web Servers</title>
<itemizedlist>
<listitem>
<para><ulink
url="../../../../index.html">http://www.FreeBSD.org/</ulink>
&mdash; Central Server.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.au.FreeBSD.org/">http://www.au.FreeBSD.org/</ulink> &mdash; Australia/1.</para>
</listitem>
<listitem>
<para><ulink
url="http://www2.au.FreeBSD.org/">http://www2.au.FreeBSD.org/</ulink> &mdash; Australia/2.</para>
</listitem>
<listitem>
<para><ulink
url="http://www3.au.FreeBSD.org/">http://www3.au.FreeBSD.org/</ulink> &mdash; Australia/3.</para>
</listitem>
<listitem>
<para><ulink
url="http://freebsd.itworks.com.au/">http://freebsd.itworks.com.au/</ulink> &mdash; Australia/4.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.br.FreeBSD.org/www.freebsd.org/">http://www.br.FreeBSD.org/www.freebsd.org/</ulink> &mdash; Brazil/1.</para>
</listitem>
<listitem>
<para><ulink
url="http://www2.br.FreeBSD.org/www.freebsd.org/">http://www2.br.FreeBSD.org/www.freebsd.org/</ulink> &mdash; Brazil/2.</para>
</listitem>
<listitem>
<para><ulink
url="http://www3.br.FreeBSD.org/">http://www3.br.FreeBSD.org/</ulink> &mdash; Brazil/3.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.bg.FreeBSD.org/">http://www.bg.FreeBSD.org/</ulink> &mdash; Bulgaria.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.ca.FreeBSD.org/">http://www.ca.FreeBSD.org/</ulink> &mdash; Canada/1.</para>
</listitem>
<listitem>
<para><ulink
url="http://www2.ca.FreeBSD.org/">http://www2.ca.FreeBSD.org/</ulink> &mdash; Canada/2.</para>
</listitem>
<listitem>
<para><ulink
url="http://www3.ca.FreeBSD.org/">http://www3.ca.FreeBSD.org/</ulink> &mdash; Canada/3.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.cn.FreeBSD.org/">http://www.cn.FreeBSD.org/</ulink> &mdash; China.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.cz.FreeBSD.org/">http://www.cz.FreeBSD.org/</ulink> &mdash; Czech Republic.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.dk.FreeBSD.org/">http://www.dk.FreeBSD.org/</ulink> &mdash; Denmark.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.ee.FreeBSD.org/">http://www.ee.FreeBSD.org/</ulink> &mdash; Estonia.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.fi.FreeBSD.org/">http://www.fi.FreeBSD.org/</ulink> &mdash; Finland.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.fr.FreeBSD.org/">http://www.fr.FreeBSD.org/</ulink> &mdash; France.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.de.FreeBSD.org/">http://www.de.FreeBSD.org/</ulink> &mdash; Germany/1.</para>
</listitem>
<listitem>
<para><ulink
url="http://www1.de.FreeBSD.org/">http://www1.de.FreeBSD.org/</ulink> &mdash; Germany/2.</para>
</listitem>
<listitem>
<para><ulink
url="http://www2.de.FreeBSD.org/">http://www2.de.FreeBSD.org/</ulink> &mdash; Germany/3.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.gr.FreeBSD.org/">http://www.gr.FreeBSD.org/</ulink> &mdash; Greece.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.hu.FreeBSD.org/">http://www.hu.FreeBSD.org/</ulink> &mdash; Hungary.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.is.FreeBSD.org/">http://www.is.FreeBSD.org/</ulink> &mdash; Iceland.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.ie.FreeBSD.org/">http://www.ie.FreeBSD.org/</ulink> &mdash; Ireland.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.jp.FreeBSD.org/www.FreeBSD.org/">http://www.jp.FreeBSD.org/www.FreeBSD.org/</ulink> &mdash; Japan.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.kr.FreeBSD.org/">http://www.kr.FreeBSD.org/</ulink> &mdash; Korea/1.</para>
</listitem>
<listitem>
<para><ulink
url="http://www2.kr.FreeBSD.org/">http://www2.kr.FreeBSD.org/</ulink> &mdash; Korea/2.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.lv.FreeBSD.org/">http://www.lv.FreeBSD.org/</ulink> &mdash; Latvia.</para>
</listitem>
<listitem>
<para><ulink
url="http://rama.asiapac.net/freebsd/">http://rama.asiapac.net/freebsd/</ulink> &mdash; Malaysia.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.nl.FreeBSD.org/">http://www.nl.FreeBSD.org/</ulink> &mdash; Netherlands/1.</para>
</listitem>
<listitem>
<para><ulink
url="http://www2.nl.FreeBSD.org/">http://www2.nl.FreeBSD.org/</ulink> &mdash; Netherlands/2.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.no.FreeBSD.org/">http://www.no.FreeBSD.org/</ulink> &mdash; Norway.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.nz.FreeBSD.org/">http://www.nz.FreeBSD.org/</ulink> &mdash; New Zealand.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.pl.FreeBSD.org/">http://www.pl.FreeBSD.org/</ulink> &mdash; Poland/1.</para>
</listitem>
<listitem>
<para><ulink
url="http://www2.pl.FreeBSD.org/">http://www2.pl.FreeBSD.org/</ulink> &mdash; Poland/2.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.pt.FreeBSD.org/">http://www.pt.FreeBSD.org/</ulink> &mdash; Portugal/1.</para>
</listitem>
<listitem>
<para><ulink
url="http://www2.pt.FreeBSD.org/">http://www2.pt.FreeBSD.org/</ulink> &mdash; Portugal/2.</para>
</listitem>
<listitem>
<para><ulink
url="http://www3.pt.FreeBSD.org/">http://www3.pt.FreeBSD.org/</ulink> &mdash; Portugal/3.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.ro.FreeBSD.org/">http://www.ro.FreeBSD.org/</ulink> &mdash; Romania.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.ru.FreeBSD.org/">http://www.ru.FreeBSD.org/</ulink> &mdash; Russia/1.</para>
</listitem>
<listitem>
<para><ulink
url="http://www2.ru.FreeBSD.org/">http://www2.ru.FreeBSD.org/</ulink> &mdash; Russia/2.</para>
</listitem>
<listitem>
<para><ulink
url="http://www3.ru.FreeBSD.org/">http://www3.ru.FreeBSD.org/</ulink> &mdash; Russia/3.</para>
</listitem>
<listitem>
<para><ulink
url="http://www4.ru.FreeBSD.org/">http://www4.ru.FreeBSD.org/</ulink> &mdash; Russia/4.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.sm.FreeBSD.org/">http://www.sm.FreeBSD.org/</ulink> &mdash; San Marino.</para>
</listitem>
<listitem>
<para><ulink
url="http://freebsd.s1web.com/">http://freebsd.s1web.com/</ulink> &mdash; Singapore.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.sk.FreeBSD.org/">http://www.sk.FreeBSD.org/</ulink> &mdash; Slovak Republic.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.si.FreeBSD.org/">http://www.si.FreeBSD.org/</ulink> &mdash; Slovenia.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.es.FreeBSD.org/">http://www.es.FreeBSD.org/</ulink> &mdash; Spain.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.za.FreeBSD.org/">http://www.za.FreeBSD.org/</ulink> &mdash; South Africa/1.</para>
</listitem>
<listitem>
<para><ulink
url="http://www2.za.FreeBSD.org/">http://www2.za.FreeBSD.org/</ulink> &mdash; South Africa/2.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.se.FreeBSD.org/">http://www.se.FreeBSD.org/</ulink> &mdash; Sweden.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.ch.FreeBSD.org/">http://www.ch.FreeBSD.org/</ulink> &mdash; Switzerland.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.tw.FreeBSD.org/www.freebsd.org/data/">http://www.tw.FreeBSD.org/www.freebsd.org/data/</ulink> &mdash; Taiwan.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.tr.FreeBSD.org/">http://www.tr.FreeBSD.org/</ulink> &mdash; Turkey.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.ua.FreeBSD.org/www.freebsd.org/">http://www.ua.FreeBSD.org/www.freebsd.org/</ulink> &mdash; Ukraine/1.</para>
</listitem>
<listitem>
<para><ulink
url="http://www2.ua.FreeBSD.org/">http://www2.ua.FreeBSD.org/</ulink> &mdash; Ukraine/2.</para>
</listitem>
<listitem>
<para><ulink
url="http://www4.ua.FreeBSD.org/">http://www4.ua.FreeBSD.org/</ulink> &mdash; Ukraine/Crimea.</para>
</listitem>
<listitem>
<para><ulink
url="http://www.uk.FreeBSD.org/">http://www.uk.FreeBSD.org/</ulink> &mdash; United Kingdom/1.</para>
</listitem>
<listitem>
<para><ulink
url="http://www2.uk.FreeBSD.org/">http://www2.uk.FreeBSD.org/</ulink> &mdash; United Kingdom/2.</para>
</listitem>
<listitem>
<para><ulink
url="http://www3.uk.FreeBSD.org/">http://www3.uk.FreeBSD.org/</ulink> &mdash; United Kingdom/3.</para>
</listitem>
<listitem>
<para><ulink
url="http://www6.FreeBSD.org/">http://www6.FreeBSD.org/</ulink> &mdash; USA/Oregon.</para>
</listitem>
<listitem>
<para><ulink
url="http://www2.FreeBSD.org/">http://www2.FreeBSD.org/</ulink> &mdash; USA/Texas.</para>
</listitem>
</itemizedlist>
</sect1>
<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>
<informaltable>
<tgroup cols="4">
<thead>
<row>
<entry>Domain</entry>
<entry>Facilities</entry>
<entry>User Group</entry>
<entry>Administrator</entry>
</row>
</thead>
<tbody>
<row>
<entry>ukug.uk.FreeBSD.org</entry>
<entry>Forwarding only</entry>
<entry><email>freebsd-users@uk.FreeBSD.org</email></entry>
<entry>Lee Johnston
<email>lee@uk.FreeBSD.org</email></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</sect1>
<sect1 id="eresources-shell">
<title>Shell Accounts</title>
<para>The following user groups provide shell accounts for people who are
actively supporting the FreeBSD project. The listed administrator
reserves the right to cancel the account if it is abused in any
way.</para>
<informaltable>
<tgroup cols="4">
<thead>
<row>
<entry>Host</entry>
<entry>Access</entry>
<entry>Facilities</entry>
<entry>Administrator</entry>
</row>
</thead>
<tbody>
<row>
<entry>storm.uk.FreeBSD.org</entry>
<entry>SSH only</entry>
<entry>Read-only cvs, personal web space, email</entry>
<entry>&a.brian;</entry>
</row>
<row>
<entry>dogma.freebsd-uk.eu.org</entry>
<entry>Telnet/FTP/SSH</entry>
<entry>Email, Web space, Anonymous FTP</entry>
<entry>Lee Johnston
<email>lee@uk.FreeBSD.org</email></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</sect1>
</appendix>
<!--
Local Variables:
mode: sgml
sgml-declaration: "../appendix.decl"
sgml-indent-data: t
sgml-omittag: nil
sgml-always-quote-attributes: t
sgml-parent-document: ("../book.sgml" "part" "appendix")
End:
-->
Reference in a new issue View git blame Copy permalink