aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'en_US.ISO8859-1/books/handbook/eresources/chapter.sgml')
-rw-r--r--en_US.ISO8859-1/books/handbook/eresources/chapter.sgml1289
1 files changed, 0 insertions, 1289 deletions
diff --git a/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml b/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
deleted file mode 100644
index 93d21fbb15..0000000000
--- a/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
+++ /dev/null
@@ -1,1289 +0,0 @@
- <chapter id="eresources">
- <title>Resources on the Internet</title>
-
- <para><emphasis>Contributed by &a.jkh;.</emphasis></para>
-
- <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 &ldquo;technical support department&rdquo; 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="http://www.FreeBSD.ORG/search.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>freebsd-advocacy</entry>
- <entry>FreeBSD Evangelism</entry>
- </row>
-
- <row>
- <entry>freebsd-announce</entry>
- <entry>Important events and project milestones</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-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-questions</entry>
- <entry>User questions and technical support</entry>
- </row>
-
- <row>
- <entry>freebsd-stable</entry>
- <entry>Discussion concerning the use of
- FreeBSD-stable</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-alpha</entry>
- <entry>Porting FreeBSD to the Alpha</entry>
- </row>
-
- <row>
- <entry>freebsd-doc</entry>
- <entry>Creating FreeBSD related documents</entry>
- </row>
-
- <row>
- <entry>freebsd-database</entry>
- <entry>Discussing database use and development under
- FreeBSD</entry>
- </row>
-
- <row>
- <entry>freebsd-emulation</entry>
- <entry>Emulation of other systems such as
- Linux/DOS/Windows</entry>
- </row>
-
- <row>
- <entry>freebsd-fs</entry>
- <entry>Filesystems</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-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-mobile</entry>
- <entry>Discussions about mobile computing</entry>
- </row>
-
- <row>
- <entry>freebsd-mozilla</entry>
- <entry>Porting mozilla to FreeBSD</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-scsi</entry>
- <entry>The SCSI subsystem</entry>
- </row>
-
- <row>
- <entry>freebsd-security</entry>
- <entry>Security issues</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 systems</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 require approval from <email>core@FreeBSD.ORG</email> to join,
- though anyone is free to send messages to them which fall within
- the scope of their charters. It is also a good idea establish a
- presence in the technical lists before asking to join one of these
- limited lists.</para>
-
- <informaltable frame="none">
- <tgroup cols="2">
- <thead>
- <row>
- <entry>List</entry>
- <entry>Purpose</entry>
- </row>
- </thead>
-
- <tbody>
- <row>
- <entry>freebsd-admin</entry>
- <entry>Administrative issues</entry>
- </row>
-
- <row>
- <entry>freebsd-arch</entry>
- <entry>Architecture and design discussions</entry>
- </row>
-
- <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-security-notifications</entry>
- <entry>Security notifications</entry>
- </row>
-
- <row>
- <entry>freebsd-user-groups</entry>
- <entry>User group coordination</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
- <email><replaceable>listname</replaceable>@FreeBSD.ORG</email>. 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'd 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@somesite.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 the &ldquo;high points&rdquo; 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 freebsd-chat <email>freebsd-chat@freebsd.org</email>
- mailing list 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 Cc line then the cc 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-ADMIN</term>
-
- <listitem>
- <para><emphasis>Administrative issues</emphasis></para>
-
- <para>This list is purely for discussion of <hostid role="domainname">freebsd.org</hostid>
- related issues and to report problems or abuse of project
- resources. It is a closed list, though anyone may report
- a problem (with our systems!) to it.</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 is a moderated list for discussion of FreeBSD
- architecture. Messages will mostly be kept technical in
- nature, with (rare) exceptions for other messages the
- moderator deems need to reach all the subscribers of the
- list. Examples of suitable topics;</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 ame drivers cleanly on many buses and
- architectures?</para>
- </listitem>
-
- <listitem>
- <para>How do I write a network driver?</para>
- </listitem>
- </itemizedlist>
-
- <para>The moderator reserves the right to do minor editing
- (spell-checking, grammar correction, trimming) of messages
- that are posted to the list. The volume of the list will be
- kept low, which may involve having to delay topics until an
- active discussion has been resolved.</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 <citerefentry><refentrytitle>send-pr</refentrytitle><manvolnum>1</manvolnum></citerefentry>
- command or the <ulink
- URL="http://www.freebsd.org/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 &ldquo;current&rdquo; 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. The
- average digest size is about 40kB. 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 documenation for
- FreeBSD. The members of this mailing list are collectively
- referred to as &ldquo;The FreeBSD Documentation
- Project&rdquo;. It is an open list; feel free to join and
- contribute!</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-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. The average digest size is about 40kB.
- 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-INSTALL</term>
-
- <listitem>
- <para><emphasis>Installation discussion</emphasis></para>
-
- <para>This mailing list is for discussing FreeBSD
- installation development for the future releases and is
- closed.</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-PORTS</term>
-
- <listitem>
- <para><emphasis>Discussion of
- &ldquo;ports&rdquo;</emphasis></para>
-
- <para>Discussions concerning FreeBSD's &ldquo;ports collection&rdquo;
- (<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 &ldquo;how to&rdquo; 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. The average digest size is about
- 40kB.</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><!-- <br>
- --> 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>This list discusses topics related to unsually 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 &ldquo;stable&rdquo;
- should subscribe to this list. This is a technical mailing
- list for which strictly technical content is
- expected.</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. It is a closed list.</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.cs.adfa.oz.au/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.oz.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="http://www.FreeBSD.ORG/">http://www.FreeBSD.ORG/</ulink> &mdash; Central Server.</para>
- </listitem>
-
- <listitem>
- <para><ulink
- URL="http://www.au.freebsd.org/FreeBSD/">http://www.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia/1.</para>
- </listitem>
-
- <listitem>
- <para><ulink
- URL="http://www2.au.freebsd.org/FreeBSD/">http://www2.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia/2.</para>
- </listitem>
-
- <listitem>
- <para><ulink
- URL="http://www3.au.freebsd.org/FreeBSD/">http://www3.au.freebsd.org/FreeBSD/</ulink> &mdash; Australia/3.</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://www.br2.freebsd.org/www.freebsd.org/">http://www.br2.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://freebsd.kawartha.com/">http://freebsd.kawartha.com/</ulink> &mdash; Canada/2.</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://www.de.freebsd.org/</ulink> &mdash; Germany/3.</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.</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.</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.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://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/www.freebsd.org/">http://www.se.freebsd.org/www.freebsd.org/</ulink> &mdash; Sweden.</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/">http://www.ua.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://www.uk.freebsd.org/">http://www.uk.freebsd.org/</ulink> &mdash; United Kingdom.</para>
- </listitem>
-
- <listitem>
- <para><ulink
- URL="http://freebsd.advansys.net/">http://freebsd.advansys.net/</ulink> &mdash; USA/Indiana.</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://www2freebsd.org/">http://www2.freebsd.org/</ulink> &mdash; USA/Texas.</para>
- </listitem>
- </itemizedlist>
-
-
- </sect1>
- </chapter>
-
-
-<!--
- Local Variables:
- mode: sgml
- sgml-declaration: "../chapter.decl"
- sgml-indent-data: t
- sgml-omittag: nil
- sgml-always-quote-attributes: t
- sgml-parent-document: ("../handbook.sgml" "part" "chapter")
- End:
--->
-