| Issue |
Last updated |
diff --git a/en/support.sgml b/en/support.sgml
index 78e76c1ce4..757534490a 100644
--- a/en/support.sgml
+++ b/en/support.sgml
@@ -8,417 +8,22 @@
&header;
-
+ FreeBSD has a wide variety of community and commercial support options available for users.
+ The Community section of this website details the support options
+ available to users from the FreeBSD community, including
+ a number of mailing lists.
-
+ Commercial support is also available from one of the many vendors
+ offering commercial products, services, and/or consulting for FreeBSD.
-
+ Problem Reporting
- Mailing lists are the primary communication channels for the FreeBSD
- community, and cover many topic areas.
+ Found a bug in FreeBSD? Noticed a mistake in the documentation? Please read over
+ our problem reporting guidelines
+ and then report the problem using our problem report form.
-
-
- Mailing list archives
-
- You can
- search
- or browse
- the mailing list archives at
- www.FreeBSD.org.
- It is also possible to
- browse
- the mailing lists via Mailman webinterface.
-
-
-
- Non-English Mailing lists
-
- Several non-English mailing lists are also available:
-
-
-
- If you create other FreeBSD mailing lists, let us know about them.
-
-
-
- Newsgroups
-
- There are a few FreeBSD specific newsgroups, along with
- numerous other newsgroups on topics of interest to FreeBSD users, though
- the mailing lists remain the most reliable way to get in touch with the
- FreeBSD developers. For miscellaneous FreeBSD discussion, see comp.unix.bsd.freebsd.misc.
- For important announcements, see comp.unix.bsd.freebsd.announce.
-
- The
- BSD Usenet News Searcher have archives of all
- BSD-related Usenet newsgroups from June 1992 onwards.
-
-
-
- IRC
- While #freebsd channels exist on various IRC networks, the FreeBSD
- project does not control them or endorse IRC as a support medium.
- You may be ignored, insulted, or kicked out if you ask questions on
- any channel in IRC, though you may have slightly better luck
- in channels named #freebsdhelp where such exist. If you
- want to try these or any other channels on IRC, it is nonetheless
- at your own risk and any complaints about conduct on those channels
- should not be directed to the FreeBSD project. See also
- the FAQ entry for
- more information.
-
-
-
- Web Resources
-
-
- Our web pages remain one of the best sources of information, and
- are also mirrored at many sites around the world. Try connecting to
- www.yourcountry.FreeBSD.org (e.g. www.de.FreeBSD.org for
- Germany or www.au.FreeBSD.org for
- Australia), or select a mirror from the drop-down list on the
- front page.
-
- The FreeBSD web pages are translated into several
- languages. Links to the translated versions of these web
- pages can be found on the front
- page.
- Several other non-English resources exist:
-
-
- For information on recent FreeBSD progress and releases, see the
- Newsflash page.
-
-
-
- Current FreeBSD problem reports are tracked using the GNATS
- database.
-
- A FreeBSD problem report (PR) is not necessarily a bug with FreeBSD
- itself. In some cases it may be reporting a mistake in the
- documentation (which could be a simple typo). In other cases it may
- be a 'wishlist' item that the submitter would like to see incorporated
- in to FreeBSD. In many cases a PR contains a port which has been
- prepared for inclusion in the FreeBSD
- Ports and Packages collection.
-
- Problem reports start 'open', and are closed as the issue they report
- is resolved. In addition, each PR is assigned a unique tracking ID
- to ensure that it is not lost. Many FreeBSD changes include the
- tracking ID of the PR that prompted the change.
-
-
-
- Problem reports may also be submitted to the development team using the
- send-pr(1) command on a FreeBSD system,
- or by sending an email message to freebsd-bugs@FreeBSD.org.
- Please note that send-pr is preferred
- since messages sent to the mailing list are not tracked as
- official problem reports, and may get lost in the noise!
-
- Before submitting a problem report, you might find it useful to
- read the Writing
- FreeBSD Problem Reports article. This article describes
- when you should submit a problem report, what you are expected
- to include in one, and what the best way to submit your problem
- report is. Some useful background information is also contained
- in the Problem
- Report Handling Guidelines article.
-
-
-
-
-
- CVS (the
- Concurrent Version System) is the tool we use for keeping our sources
- under control. Every change (with accompanying log message explaining
- its purpose) from FreeBSD 2.0 to the present is stored here. It can be
- easily viewed from the web interface mentioned below. To obtain a complete copy
- of the FreeBSD CVS repository or any of the development branches inside
- it, you may choose any one of following options:
-
-
- - cvsup if you are looking
- for on-demand, low overhead access using a custom utility (written in
- Modula-3 no less).
-
- - anoncvs
- if you are looking for on-demand access that has higher overhead than
- cvsup (in terms of wall time and bytes transferred) but is easier to use
- for checking out small pieces of the tree and requires nothing more
- than the cvs tools already bundled with FreeBSD.
-
- - CTM if you are looking for
- very low overhead, batch-mode access (basically, patches through
- email).
-
- - The web interface
- if you are looking to simply browse the repository in search of a
- specific change or file revision.
-
- - Finally, if you have got bandwidth to burn or you prefer / are forced
- to use FTP, you can simply mirror the CVS repository from ftp.FreeBSD.org.
-
-
-
- Mirrors of the CVS Repository cgi script are available in
- Germany,
- Japan,
- Portugal,
- San Marino,
- Spain,
- USA/California and
- Ukraine.
-
- A public Subversion mirror of the FreeBSD src/ CVS repository is
- provided at svn://svn.clkao.org/freebsd/. A web interface is
- also available. This is intended for people who would like to
- try the svk distributed version control system.
-
-
-
-
-
- FreeBSD's widespread popularity has spawned a number of user groups
- around the world. If you know of a FreeBSD user group not listed here,
- let us know about it.
-
-
-
-
-
- In addition to the mainstream development path of FreeBSD, a number of
- developer groups are working on the cutting edge to expand FreeBSD's
- range of applications in new directions.
-
-
-
- Security resources available to FreeBSD users:
- PGP Key for Security Officers, advisories, patches and mailing lists.
-
-
-
- Whether you are just starting out with FreeBSD, or need to
- complete a large project, a consultant or two might be your answer.
-
-
-
-
-
- General &unix; Information
-
-
-
-
-
- The X Window System
-
-
- - The X.Org and XFree86™ projects provide
- users of a variety of Intel based UNIX systems, including FreeBSD,
- with an excellent X Window system.
-
- - The WINE project is working to
- provide the ability to run Microsoft Windows® software on Intel based UNIX
- systems such as FreeBSD, NetBSD and Linux.
-
-
-
-
- Hardware
-
-
-
-
-
- Related Operating System Projects
-
-
- - NetBSD is
- another free 4.4BSD-Lite based operating system which runs on several
- different architectures.
-
- - OpenBSD
- is another 4.4BSD derivative with focus on security.
-
- - Linux is
- another free UNIX like system.
-
- - Darwin
- is the free system that forms the core of Apple's
- Mac OS X system.
-
- - Lites
- is a 4.4 BSD Lite based server and emulation library that provides
- free UNIX functionality to a Mach based system.
-
- - The GNU
- HURD project is another effort to develop a free
- UNIX like operating system.
-
- - DragonFly
- BSD is based on FreeBSD 4.X but has a different
- set of development goals than FreeBSD 5.X.
-
+ You can also view the open problem reports and
+ search problem reports on this website.
&footer;