diff --git a/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml b/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
index 77be454b7a..b54e781098 100644
--- a/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
@@ -1,1951 +1,1971 @@
Resources on the Internet
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 technical support department
of sorts,
with electronic mail and USENET news being the most effective way of
reaching that community.
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.
Mailing Lists
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
comp.unix.bsd.freebsd.* 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.
The charters for the various lists are given at the bottom of this
document. Please read the charter before joining or sending
mail to any list. 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.
If you wish to test your ability to send to
&os; lists, send a test message to &a.test.name;.
Please do not send test messages to any other list.
When in doubt about what list to post a question to, see How to get best results from
the FreeBSD-questions mailing list.
Before posting to any list, please learn about how to best use
the mailing lists, such as how to help avoid frequently-repeated
discussions, by reading the
Mailing List Frequently Asked Questions (FAQ) document.
Archives are kept for all of the mailing lists and can be searched
using the FreeBSD World
Wide Web server. The keyword searchable archive offers an
excellent way of finding answers to frequently asked questions and
should be consulted before posting a question.
List Summary
General lists: The following are general
lists which anyone is free (and encouraged) to join:
List
Purpose
&a.advocacy.name;
FreeBSD Evangelism
&a.announce.name;
Important events and project milestones
&a.arch.name;
Architecture and design discussions
&a.bugbusters.name;
Discussions pertaining to the maintenance of the FreeBSD
problem report database and related tools
&a.bugs.name;
Bug reports
&a.chat.name;
Non-technical items related to the FreeBSD
community
&a.current.name;
Discussion concerning the use of
&os.current;
&a.isp.name;
Issues for Internet Service Providers using
FreeBSD
&a.jobs.name;
FreeBSD employment and consulting
opportunities
&a.policy.name;
FreeBSD Core team policy decisions. Low volume, and
read-only
&a.questions.name;
User questions and technical support
&a.security-notifications.name;
Security notifications
&a.stable.name;
Discussion concerning the use of
&os.stable;
&a.test.name;
Where to send your test messages instead of one of
the actual lists
Technical lists: 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.
List
Purpose
&a.acpi.name;
ACPI and power management development
&a.afs.name;
Porting AFS to FreeBSD
&a.aic7xxx.name;
Developing drivers for the &adaptec; AIC 7xxx
&a.alpha.name;
Porting FreeBSD to the Alpha
&a.amd64.name;
Porting FreeBSD to AMD64 systems
&a.apache.name;
Discussion about Apache related ports
&a.arm.name;
Porting FreeBSD to &arm; processors
&a.atm.name;
Using ATM networking with FreeBSD
&a.audit.name;
Source code audit project
&a.binup.name;
Design and development of the binary update system
&a.bluetooth.name;
Using &bluetooth; technology in FreeBSD
&a.cluster.name;
Using FreeBSD in a clustered environment
&a.cvsweb.name;
CVSweb maintenance
&a.database.name;
Discussing database use and development under
FreeBSD
&a.doc.name;
Creating FreeBSD related documents
&a.drivers.name;
Writing device drivers for &os;
&a.eclipse.name;
FreeBSD users of Eclipse IDE, tools, rich client
applications and ports.
&a.embedded.name;
Using FreeBSD in embedded applications
&a.eol.name;
Peer support of FreeBSD-related software that
is no longer supported by the FreeBSD project.
&a.emulation.name;
Emulation of other systems such as
Linux/&ms-dos;/&windows;
&a.firewire.name;
FreeBSD &firewire; (iLink, IEEE 1394) technical
discussion
&a.fs.name;
File systems
&a.geom.name;
GEOM-specific discussions and implementations
&a.gnome.name;
Porting GNOME and GNOME applications
&a.hackers.name;
General technical discussion
&a.hardware.name;
General discussion of hardware for running
FreeBSD
&a.i18n.name;
FreeBSD Internationalization
&a.ia32.name;
FreeBSD on the IA-32 (&intel; x86) platform
&a.ia64.name;
Porting FreeBSD to &intel;'s upcoming IA64 systems
&a.ipfw.name;
Technical discussion concerning the redesign of the IP
firewall code
&a.isdn.name;
ISDN developers
&a.jail.name;
Discussion about the &man.jail.8; facility
&a.java.name;
&java; developers and people porting &jdk;s to
FreeBSD
&a.kde.name;
Porting KDE and KDE applications
&a.lfs.name;
Porting LFS to FreeBSD
&a.libh.name;
The second generation installation and package
system
&a.mips.name;
Porting FreeBSD to &mips;
&a.mobile.name;
Discussions about mobile computing
&a.mozilla.name;
Porting Mozilla to FreeBSD
&a.multimedia.name;
Multimedia applications
&a.newbus.name;
Technical discussions about bus architecture
&a.net.name;
Networking discussion and TCP/IP source code
&a.openoffice.name;
Porting OpenOffice.org and
&staroffice; to FreeBSD
&a.performance.name;
Performance tuning questions for high
performance/load installations
&a.perl.name;
Maintenance of a number of
Perl-related ports
&a.pf.name;
Discussion and questions about the packet filter
firewall system
&a.platforms.name;
Concerning ports to non &intel; architecture
platforms
&a.ports.name;
Discussion of the Ports Collection
&a.ports-bugs.name;
Discussion of the ports bugs/PRs
&a.ppc.name;
Porting FreeBSD to the &powerpc;
&a.proliant.name;
Technical discussion of FreeBSD on HP ProLiant server platforms
&a.python.name;
FreeBSD-specific Python issues
&a.qa.name;
Discussion of Quality Assurance, usually pending a release
&a.rc.name;
Discussion related to the rc.d system and its development
&a.realtime.name;
Development of realtime extensions to FreeBSD
&a.ruby.name;
FreeBSD-specific Ruby discussions
&a.scsi.name;
The SCSI subsystem
&a.security.name;
Security issues affecting FreeBSD
&a.small.name;
Using FreeBSD in embedded applications
(obsolete; use &a.embedded.name; instead)
&a.smp.name;
Design discussions for [A]Symmetric
MultiProcessing
&a.sparc.name;
Porting FreeBSD to &sparc; based systems
&a.standards.name;
FreeBSD's conformance to the C99 and the &posix;
standards
&a.sun4v.name;
Porting FreeBSD to &ultrasparc; T1 based systems
&a.threads.name;
Threading in FreeBSD
&a.testing.name;
FreeBSD Performance and Stability Tests
&a.tokenring.name;
Support Token Ring in FreeBSD
&a.usb.name;
Discussing &os; support for USB
&a.virtualization.name;
Discussion of various virtualization techniques supported
by &os;
&a.vuxml.name;
Discussion on VuXML infrastructure
&a.x11.name;
Maintenance and support of X11 on FreeBSD
+
+
+ &a.xen.name;
+ Discussion of the freebsd port to xen - implementation and usage
+
Limited lists: 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.
List
Purpose
&a.hubs.name;
People running mirror sites (infrastructural
support)
&a.usergroups.name;
User group coordination
&a.vendors.name;
Vendors pre-release coordination
&a.wip-status.name;
FreeBSD Work-In-Progress Status
&a.www.name;
Maintainers of www.FreeBSD.org
Digest lists: All of the above lists
are available in a digest format. Once subscribed to a list,
you can change your digest options in your account options
section.
CVS & SVN lists: The following lists
are for people interested in seeing the log messages for changes to
various areas of the source tree. They are
Read-Only lists and should not have mail sent to
them.
List
Source area
Area Description (source for)
&a.cvsall.name;
/usr/(CVSROOT|doc|ports)
All changes to any place in the tree (superset of other CVS commit lists)
&a.cvs-doc.name;
/usr/(doc|www)
All changes to the doc and www trees
&a.cvs-ports.name;
/usr/ports
All changes to the ports tree
&a.cvs-projects.name;
/usr/projects
All changes to the projects tree
&a.cvs-src.name;
/usr/src
All changes to the src tree (generated by the svn-to-cvs
importer commits)
&a.svn-src-all.name;
/usr/src
All changes to the Subversion repository (except
for user
and projects)
&a.svn-src-head.name;
/usr/src
All changes to the head
branch of
the Subversion repository (the &os;-CURRENT
branch)
&a.svn-src-projects.name;
/usr/projects
All changes to the projects
area of the src Subversion repository
&a.svn-src-release.name;
/usr/src
All changes to the releases
area of the src Subversion repository
&a.svn-src-releng.name;
/usr/src
All changes to the releng
branches of the src Subversion repository (the
security / release engineering branches)
&a.svn-src-stable.name;
/usr/src
All changes to the all stable branches of the src
Subversion repository
&a.svn-src-stable-6.name;
/usr/src
All changes to the stable/6
branch of the src Subversion repository
&a.svn-src-stable-7.name;
/usr/src
All changes to the stable/7
branch of the src Subversion repository
&a.svn-src-stable-other.name;
/usr/src
All changes to the
older stable branches of the src
Subversion repository
&a.svn-src-svnadmin.name;
/usr/src
All changes to the administrative scripts, hooks,
and other configuration data of the src Subversion
repository
&a.svn-src-user.name;
/usr/src
All changes to the
experimental user area of the src
Subversion repository
&a.svn-src-vendor.name;
/usr/src
All changes to the vendor work area of the src
Subversion repository
How to Subscribe
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.
To actually post to a given list you simply send mail to
listname@FreeBSD.org. It will then
be redistributed to mailing list members world-wide.
To unsubscribe yourself from a list, click on the URL
found at the bottom of every email received from the list. It
is also possible to send an email to
listname-unsubscribe@FreeBSD.org to unsubscribe
yourself.
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.
List Charters
All 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 postmaster@FreeBSD.org, 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.
Rules of the road:
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.
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 & -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.
You are still responsible for your
own cross-postings, no matter who the originator might have
been.
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.
However, 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.
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.
Individual list charters:
&a.acpi.name;
ACPI and power management
development
&a.afs.name;
Andrew File System
This list is for discussion on porting and using AFS from
CMU/Transarc
&a.announce.name;
Important events / milestones
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.
&a.arch.name;
Architecture and design
discussions
This list is for discussion of the FreeBSD
architecture. Messages will mostly be kept strictly
technical in nature. Examples of suitable topics
are:
How to re-vamp the build system to have several
customized builds running at the same time.
What needs to be fixed with VFS to make Heidemann layers
work.
How do we change the device driver interface to be able
to use the same drivers cleanly on many buses and
architectures.
How to write a network driver.
&a.audit.name;
Source code audit project
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.
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.
&a.binup.name;
FreeBSD Binary Update Project
This list exists to provide discussion for the binary
update system, or binup.
Design issues, implementation details,
patches, bug reports, status reports, feature requests, commit
logs, and all other things related to
binup are fair game.
&a.bluetooth.name;
&bluetooth; in FreeBSD
This is the forum where FreeBSD's &bluetooth; users
congregate. Design issues, implementation details,
patches, bug reports, status reports, feature requests,
and all matters related to &bluetooth; are fair
game.
&a.bugbusters.name;
Coordination of the Problem Report handling effort
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.
&a.bugs.name;
Bug reports
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 WEB
interface to it.
&a.chat.name;
Non technical items related to the FreeBSD
community
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.
&a.core.name;
FreeBSD core team
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.
&a.current.name;
Discussions about the use of
&os.current;
This is the mailing list for users of &os.current;. It
includes warnings about new features coming out in -CURRENT that
will affect the users, and instructions on steps that must be
taken to remain -CURRENT. Anyone running CURRENT
must subscribe to this list. This is a technical mailing list
for which strictly technical content is expected.
&a.cvsweb.name;
FreeBSD CVSweb Project
Technical discussions about use, development and maintenance
of FreeBSD-CVSweb.
&a.doc.name;
Documentation project
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
The FreeBSD Documentation Project
. It is an open
list; feel free to join and contribute!
&a.drivers.name;
Writing device drivers for &os;
This is a forum for technical discussions related to
device drivers on &os;. It is primarily a place
for device driver writers to ask questions about
how to write device drivers using the APIs in the
&os; kernel.
&a.eclipse.name;
&os; users of Eclipse IDE, tools, rich
client applications and ports.
The intention of this list is to provide mutual
support for everything to do with choosing, installing,
using, developing and maintaining the Eclipse IDE,
tools, rich client applications on the &os; platform and
assisting with the porting of Eclipse IDE and plugins to
the &os; environment.
The intention is also to facilitate exchange of
information between the Eclipse community and the &os;
community to the mutual benefit of both.
Although this list is focused primarily on the needs
of Eclipse users it will also provide a forum for those
who would like to develop &os; specific applications
using the Eclipse framework.
&a.embedded.name;
Using FreeBSD in embedded
applications
This list discusses topics related to using FreeBSD in
embedded systems. This is a technical mailing list for which
strictly technical content is expected. For the purpose of
this list we define embedded systems as those computing
devices which are not desktops and which usually serve a
single purpose as opposed to being general computing
environments. Examples include, but are not limited to,
all kinds of phone handsets, network equipment such as
routers, switches and PBXs, remote measuring equipment,
PDAs, Point Of Sale systems, and so on.
&a.emulation.name;
Emulation of other systems such as
Linux/&ms-dos;/&windows;
This is a forum for technical discussions related to
running programs written for other operating systems on &os;.
&a.eol.name;
Peer support of FreeBSD-related software that is
no longer supported by the FreeBSD project.
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).
&a.firewire.name;
&firewire; (iLink, IEEE 1394)
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.
&a.fs.name;
File systems
Discussions concerning FreeBSD file systems. This is a
technical mailing list for which strictly technical content is
expected.
&a.geom.name;
GEOM
Discussions specific to GEOM and related implementations.
This is a technical mailing list for which strictly technical
content is expected.
&a.gnome.name;
GNOME
Discussions concerning The GNOME Desktop Environment for
FreeBSD systems. This is a technical mailing list for
which strictly technical content is expected.
&a.ipfw.name;
IP Firewall
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.
&a.ia64.name;
Porting FreeBSD to IA64
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.
&a.isdn.name;
ISDN Communications
This is the mailing list for people discussing the
development of ISDN support for FreeBSD.
&a.java.name;
&java; Development
This is the mailing list for people discussing the
development of significant &java; applications for FreeBSD and the
porting and maintenance of &jdk;s.
&a.jobs.name;
Jobs offered and sought
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
not a mailing list for general
employment issues since adequate forums for that
already exist elsewhere.
Note that this list, like other FreeBSD.org mailing
lists, is distributed worldwide. Thus, you need to be
clear about location and the extent to which
telecommuting or assistance with relocation is
available.
Email should use open formats only —
preferably plain text, but basic Portable Document
Format (PDF), HTML, and a few others
are acceptable to many readers. Closed formats such as
µsoft; Word (.doc) will be
rejected by the mailing list server.
&a.kde.name;
KDE
Discussions concerning KDE on
FreeBSD systems. This is a technical mailing list for
which strictly technical content is expected.
&a.hackers.name;
Technical discussions
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.
&a.hardware.name;
General discussion of FreeBSD
hardware
General discussion about the types of hardware that FreeBSD
runs on, various problems and suggestions concerning what to buy
or avoid.
&a.hubs.name;
Mirror sites
Announcements and discussion for people who run FreeBSD
mirror sites.
&a.isp.name;
Issues for Internet Service
Providers
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.
&a.openoffice.name;
OpenOffice.org
Discussions concerning the porting and maintenance
of OpenOffice.org and
&staroffice;.
&a.performance.name;
Discussions about tuning or speeding up FreeBSD
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,
are experiencing performance problems, or are pushing
the limits of FreeBSD. Concerned parties that are
willing to work toward improving the performance of
FreeBSD 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
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
performance related topics.
&a.pf.name;
Discussion and questions about the packet filter
firewall system
Discussion concerning the packet filter (pf) firewall
system in terms of FreeBSD. Technical discussion and user
questions are both welcome. This list is also a place to
discuss the ALTQ QoS framework.
&a.platforms.name;
Porting to Non &intel; platforms
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.
&a.policy.name;
Core team policy decisions
This is a low volume, read-only mailing list for FreeBSD
Core Team Policy decisions.
&a.ports.name;
Discussion of
ports
Discussions concerning FreeBSD's ports
collection
(/usr/ports), ports infrastructure, and
general ports coordination efforts. This is a technical mailing list
for which strictly technical content is expected.
&a.ports-bugs.name;
Discussion of
ports
bugs
Discussions concerning problem reports for FreeBSD's ports
collection
(/usr/ports), proposed
ports, or modifications to ports. This is a technical mailing list
for which strictly technical content is expected.
&a.proliant.name;
Technical discussion of FreeBSD on HP
ProLiant server platforms
This mailing list is to be used for the technical
discussion of the usage of FreeBSD on HP ProLiant servers,
including the discussion of ProLiant-specific drivers,
management software, configuration tools, and BIOS
updates. As such, this is the primary place to discuss
the hpasmd, hpasmcli, and hpacucli modules.
&a.python.name;
Python on FreeBSD
This is a list for discussions related to improving Python-support
on FreeBSD. This is a technical mailing list. It is for individuals
working on porting Python, its 3rd party modules and Zope stuff to
FreeBSD. Individuals interested in following the technical discussion
are also welcome.
&a.questions.name;
User questions
This is the mailing list for questions about FreeBSD. You
should not send how to
questions to the technical
lists unless you consider the question to be pretty
technical.
&a.ruby.name;
FreeBSD-specific Ruby
discussions
This is a list for discussions related to the Ruby
support on FreeBSD. This is a technical mailing
list. It is for individuals working on Ruby ports,
3rd party libraries and frameworks.
Individuals interested in the technical discussion
are also welcome.
&a.scsi.name;
SCSI subsystem
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.
&a.security.name;
Security issues
FreeBSD computer security issues (DES, Kerberos, known
security holes and fixes, etc). This is a technical mailing
list for which strictly technical discussion is expected. Note
that this is not a question-and-answer list, but that
contributions (BOTH question AND answer) to the FAQ are
welcome.
&a.security-notifications.name;
Security Notifications
Notifications of FreeBSD security problems and
fixes. This is not a discussion list. The discussion
list is FreeBSD-security.
&a.small.name;
Using FreeBSD in embedded
applications
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.
This list has been obsoleted by &a.embedded.name;.
&a.stable.name;
Discussions about the use of
&os.stable;
This is the mailing list for users of &os.stable;. It
includes warnings about new features coming out in -STABLE that
will affect the users, and instructions on steps that must be
taken to remain -STABLE. Anyone running STABLE
should subscribe to this list. This is a technical mailing list
for which strictly technical content is expected.
&a.standards.name;
C99 & POSIX Conformance
This is a forum for technical discussions related to
FreeBSD Conformance to the C99 and the POSIX standards.
&a.usb.name;
Discussing &os; support for
USB
This is a mailing list for technical discussions
related to &os; support for USB.
&a.usergroups.name;
User Group Coordination List
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.
&a.vendors.name;
Vendors
Coordination discussions between The FreeBSD Project and
Vendors of software and hardware for FreeBSD.
&a.virtualization.name;
Discussion of various virtualization
techniques supported by &os;
A list to discuss the various virtualization
techniques supported by &os;. On one hand the focus will
be on the implementation of the basic functionality as
well as adding new features. On the other hand users
will have a forum to ask for help in case of problems
or to discuss their use cases.
&a.wip-status.name;
&os; Work-In-Progress Status
This mailing list can be used to announce creation
and progress of your &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
the topical list, as no discussion is allowed on this
list.
Look inside the archives for examples of suitable
messages.
An editorial digest of the messages to this list
might be posted to the &os; website every few month
as part of the Status Reports
.
You can find more
examples and past reports there, too.
+
+
+ &a.xen.name;
+
+
+ Discussion of the freebsd port to xen
+ - implementation and usage
+
+ A list that focuses on the FreeBSD Xen port. The
+ anticipated traffic level is small enough that it is
+ intended as a forum for both technical discussions of
+ the implementation and design details as well as
+ administrative deployment issues.
+
+
Filtering on the Mailing Lists
The &os; mailing lists are filtered in multiple ways to
avoid the distribution of spam, viruses, and other unwanted emails.
The filtering actions described in this section do not include all
those used to protect the mailing lists.
Only certain types of attachments are allowed on the
mailing lists. All attachments with a MIME content type not
found in the list below will be stripped before an email is
distributed on the mailing lists.
application/octet-stream
application/pdf
application/pgp-signature
application/x-pkcs7-signature
message/rfc822
multipart/alternative
multipart/related
multipart/signed
text/html
text/plain
text/x-diff
text/x-patch
Some of the mailing lists might allow attachments of
other MIME content types, but the above list should be
applicable for most of the mailing lists.
If an email contains both an HTML and a plain text version,
the HTML version will be removed. If an email contains only an
HTML version, it will be converted to plain text.
Usenet Newsgroups
In addition to two FreeBSD specific newsgroups, there are many
others in which FreeBSD is discussed or are otherwise relevant to
FreeBSD users. Keyword
searchable archives are available for some of these newsgroups
from courtesy of Warren Toomey wkt@cs.adfa.edu.au.
BSD Specific Newsgroups
comp.unix.bsd.freebsd.announce
comp.unix.bsd.freebsd.misc
de.comp.os.unix.bsd (German)
fr.comp.os.bsd (French)
it.comp.os.freebsd (Italian)
tw.bbs.comp.386bsd (Traditional Chinese)
Other &unix; Newsgroups of Interest
comp.unix
comp.unix.questions
comp.unix.admin
comp.unix.programmer
comp.unix.shell
comp.unix.user-friendly
comp.security.unix
comp.sources.unix
comp.unix.advocacy
comp.unix.misc
comp.bugs.4bsd
comp.bugs.4bsd.ucb-fixes
comp.unix.bsd
X Window System
comp.windows.x.i386unix
comp.windows.x
comp.windows.x.apps
comp.windows.x.announce
comp.windows.x.intrinsics
comp.windows.x.motif
comp.windows.x.pex
comp.emulators.ms-windows.wine
World Wide Web Servers
&chap.eresources.www.inc;
Email Addresses
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.
Domain
Facilities
User Group
Administrator
ukug.uk.FreeBSD.org
Forwarding only
ukfreebsd@uk.FreeBSD.org
Lee Johnston
lee@uk.FreeBSD.org
diff --git a/en_US.ISO8859-1/share/sgml/mailing-lists.ent b/en_US.ISO8859-1/share/sgml/mailing-lists.ent
index 09c2a426ad..aa5f32cdee 100644
--- a/en_US.ISO8859-1/share/sgml/mailing-lists.ent
+++ b/en_US.ISO8859-1/share/sgml/mailing-lists.ent
@@ -1,500 +1,504 @@
FreeBSD list server">
&a.mailman.listinfo;">
FreeBSD ACPI mailing list">
freebsd-acpi">
FreeBSD advocacy mailing list">
freebsd-advocacy">
FreeBSD AFS porting mailing list">
freebsd-afs">
FreeBSD Adaptec AIC7xxx discussions mailing list">
freebsd-aic7xxx">
FreeBSD Alpha porting mailing list">
freebsd-alpha">
Porting FreeBSD to AMD64 systems">
freebsd-amd64">
FreeBSD announcements mailing list">
freebsd-announce">
FreeBSD Apache mailing list">
freebsd-apache">
FreeBSD architecture and design mailing list">
freebsd-arch">
FreeBSD ARM porting mailing list">
freebsd-arm">
FreeBSD ATM networking mailing list">
freebsd-atm">
FreeBSD source code audit mailing list">
freebsd-audit">
FreeBSD binary update system mailing list">
freebsd-binup">
FreeBSD Bluetooth mailing list">
freebsd-bluetooth">
FreeBSD bugbusters mailing list">
freebsd-bugbusters">
FreeBSD problem reports mailing list">
freebsd-bugs">
FreeBSD chat mailing list">
freebsd-chat">
FreeBSD clustering mailing list">
freebsd-cluster">
&os.current; mailing list">
freebsd-current">
CTM announcements">
ctm-announce">
CTM distribution of CVS files">
ctm-cvs-cur">
CTM 4-STABLE src branch distribution mailing list">
ctm-src-4">
CTM -CURRENT src branch distribution mailing list">
ctm-src-cur">
CTM user discussion mailing list">
ctm-users">
FreeBSD CVS commit message mailing list">
cvs-all">
FreeBSD CVS doc commit list">
cvs-doc">
FreeBSD CVS ports commit list">
cvs-ports">
FreeBSD CVS projects commit list">
cvs-projects">
FreeBSD CVS src commit list">
cvs-src">
FreeBSD CVSweb maintenance mailing list">
freebsd-cvsweb">
FreeBSD based Databases mailing list">
freebsd-database">
FreeBSD documentation project mailing list">
freebsd-doc">
Writing device drivers for FreeBSD">
freebsd-drivers">
FreeBSD users of Eclipse IDE, tools, rich client applications and ports">
freebsd-eclipse">
FreeBSD-embedded mailing list">
freebsd-embedded">
FreeBSD-emulation mailing list">
freebsd-emulation">
FreeBSD-eol mailing list">
freebsd-eol">
FreeBSD FireWire (IEEE 1394) discussion mailing list">
freebsd-firewire">
FreeBSD file system project mailing list">
freebsd-fs">
FreeBSD GEOM mailing list">
freebsd-geom">
FreeBSD GNOME and GNOME applications mailing list">
freebsd-gnome">
FreeBSD technical discussions mailing list">
freebsd-hackers">
FreeBSD hardware and equipment mailing list">
freebsd-hardware">
FreeBSD mirror sites mailing lists">
freebsd-hubs">
FreeBSD internationalization mailing list">
freebsd-i18n">
FreeBSD i386-specific issues mailing list">
freebsd-i386">
FreeBSD IA32 porting mailing list">
freebsd-ia32">
FreeBSD IA64 porting mailing list">
freebsd-ia64">
FreeBSD IPFW code mailing list">
freebsd-ipfw">
FreeBSD ISDN mailing list">
freebsd-isdn">
FreeBSD Internet service provider's mailing list">
freebsd-isp">
FreeBSD jails mailing list">
freebsd-jail">
FreeBSD Java Language mailing list">
freebsd-java">
FreeBSD related employment mailing list">
freebsd-jobs">
FreeBSD KDE/Qt and KDE applications mailing list">
freebsd-kde">
FreeBSD LFS porting mailing list">
freebsd-lfs">
FreeBSD libh installation and packaging system mailing list">
freebsd-libh">
FreeBSD MIPS porting mailing list">
freebsd-mips">
FreeBSD mirror site administrators">
mirror-announce">
FreeBSD laptop computer mailing list">
freebsd-mobile">
FreeBSD port of the Mozilla browser mailing list">
freebsd-mozilla">
FreeBSD multimedia mailing list">
freebsd-multimedia">
FreeBSD networking mailing list">
freebsd-net">
FreeBSD new users mailing list">
freebsd-newbies">
FreeBSD new-bus mailing list">
freebsd-new-bus">
FreeBSD OpenOffice mailing list">
freebsd-openoffice">
FreeBSD performance mailing list">
freebsd-performance">
FreeBSD Perl mailing list">
freebsd-perl">
FreeBSD packet filter mailing list">
freebsd-pf">
FreeBSD non-Intel platforms porting mailing list">
freebsd-platforms">
FreeBSD core team policy decisions mailing list">
freebsd-policy">
FreeBSD ports mailing list">
freebsd-ports">
FreeBSD ports bugs mailing list">
freebsd-ports-bugs">
FreeBSD PowerPC porting mailing list">
freebsd-ppc">
Technical discussion of FreeBSD on HP ProLiant server platforms">
freebsd-proliant">
FreeBSD Python mailing list">
freebsd-python">
FreeBSD Quality Assurance mailing list">
freebsd-qa">
FreeBSD general questions mailing list">
freebsd-questions">
FreeBSD boot script system mailing list">
freebsd-rc">
FreeBSD realtime extensions mailing list">
freebsd-realtime">
FreeBSD Ruby mailing list">
freebsd-ruby">
FreeBSD SCSI subsystem mailing list">
freebsd-scsi">
FreeBSD security mailing list">
freebsd-security">
FreeBSD security notifications mailing list">
freebsd-security-notifications">
FreeBSD-small mailing list">
freebsd-small">
FreeBSD symmetric multiprocessing mailing list">
freebsd-smp">
FreeBSD SPARC porting mailing list">
freebsd-sparc64">
&os.stable; mailing list">
freebsd-stable">
FreeBSD C99 and POSIX compliance mailing list">
freebsd-standards">
FreeBSD sun4v porting mailing list">
freebsd-sun4v">
SVN commit messages for the entire src tree (except for user
and projects
)">
svn-src-all">
SVN commit messages for the src tree for head/-current">
svn-src-head">
SVN commit messages for the src projects
tree">
svn-src-projects">
SVN commit messages for releases in the src tree">
svn-src-release">
SVN commit messages for the release engineering / security commits to the src tree">
svn-src-releng">
SVN commit messages for all the -stable branches of the src tree">
svn-src-stable">
SVN commit messages for only the 6-stable src tree">
svn-src-stable-6">
SVN commit messages for only the 7-stable src tree">
svn-src-stable-7">
SVN commit messages for the old stable src trees">
svn-src-stable-other">
SVN commit messages for the admin / configuration tree">
svn-src-svnadmin">
SVN commit messages for the experimental user
src tree">
svn-src-user">
SVN commit messages for the vendor work area tree">
svn-src-vendor">
FreeBSD test mailing list">
freebsd-test">
FreeBSD performance and stability testing mailing list">
freebsd-testing">
FreeBSD threads mailing list">
freebsd-threads">
FreeBSD tokenring mailing list">
freebsd-tokenring">
FreeBSD USB mailing list">
freebsd-usb">
FreeBSD user group coordination mailing list">
freebsd-user-groups">
FreeBSD vendors pre-release coordination mailing list">
freebsd-vendors">
Discussion of various virtualization techniques supported by FreeBSD">
freebsd-virtualization">
Discussion on the VuXML
infrastructure">
freebsd-vuxml">
FreeBSD Work-In-Progress Status">
freebsd-wip-status">
FreeBSD Webmaster mailing list">
freebsd-www">
FreeBSD X11 mailing list">
freebsd-x11">
+
+Discussion of the freebsd port to xen - implementation and usage">
+freebsd-xen">
+
bug-followup@FreeBSD.org">
majordomo@FreeBSD.org">