diff --git a/en/applications.sgml b/en/applications.sgml index dc8262bf16..9d82ecaed0 100644 --- a/en/applications.sgml +++ b/en/applications.sgml @@ -1,147 +1,147 @@ + %includes; ]> &header;

Experience the possibilities with FreeBSD

FreeBSD can handle nearly any task you would expect of a &unix; workstation, as well as many you might not expect:


FreeBSD is a true open system with full source code.

There is no doubt that so-called open systems are the requirement for today's computing applications. But no commercial vendor-supplied solution is more open than one which includes full source code to the entire operating system, including the kernel and all of the system daemons, programs, and utilities. You can modify any part of FreeBSD to suit your personal, organizational, or corporate needs.

With its generous licensing policy, you can use FreeBSD as the basis for any number of free or commercial applications.


FreeBSD runs thousands of applications.

Because FreeBSD is based on 4.4BSD, an industry-standard version of UNIX, it is easy to compile and run programs. FreeBSD also includes an extensive packages collection and ports collection that bring precompiled and easy-to-build software right to your desktop or enterprise server. There is also a growing number of commercial applications written for FreeBSD.

Here are some examples of the environments in which FreeBSD is used:


FreeBSD is an operating system that will grow with your needs.

Though FreeBSD is free software, it is also user supported software. Any questions you have can be posted to hundreds of FreeBSD developers and users simply by e-mailing the freebsd-questions@FreeBSD.ORG mailing list.

FreeBSD also has a worldwide group of programmers and writers who fix bugs, add new features and document the system. Support for new devices or special features is an almost constant development process, and the team keeps a special eye out for problems which affect system stability. FreeBSD users are quite proud of not only how fast but how reliable their systems are.

What experts have to say . . .

``FreeBSD handles [our] heavy load quite well and it is nothing short of amazing. Salutations to the FreeBSD team.''

---Mark Hittinger, administrator of WinNet Communications, Inc.

&footer; diff --git a/en/copyright/trademarks.sgml b/en/copyright/trademarks.sgml index 565db94f21..11a8bf65d9 100644 --- a/en/copyright/trademarks.sgml +++ b/en/copyright/trademarks.sgml @@ -1,52 +1,58 @@ - + %includes; ]> &header;

FreeBSD is a registered trademark of Wind River Systems, Inc. This is expected to change soon.

Adobe, Acrobat, Acrobat Reader, and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.

+

AMD, Am486, Am5X86, AMD Athlon, AMD Duron, AMD Opteron, AMD-K6, + Élan, and PCnet are trademarks of Advanced Micro Devices, + Inc.

+

IBM and PowerPC are trademarks of International Business Machines Corporation in the United States, other countries, or both.

IEEE, POSIX, and 802 are registered trademarks of The Institute of Electrical and Electronics Engineers, Inc.

Motif, OSF/1, and UNIX are registered trademarks and IT DialTone and The Open Group are trademarks of The Open Group in the United States and other countries.

MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries.

Silicon Graphics, SGI, and OpenGL are registered trademarks of Silicon Graphics, Inc., in the United States and/or other countries worldwide.

Sparc, Sparc64, SPARCEngine, and UltraSPARC are trademarks of SPARC International, Inc in the United States and other countries. Products bearing SPARC trademarks are based upon architecture developed by Sun Microsystems, Inc.

Sun, Sun Microsystems, SunOS, Solaris, and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.

+

XFree86 is a trademark of The XFree86 Project, Inc.

+

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear on this website, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the '™' or the '®' symbol.

&footer; diff --git a/en/projects/cvsweb.sgml b/en/projects/cvsweb.sgml index 1ead60316b..e7d8ab8905 100644 --- a/en/projects/cvsweb.sgml +++ b/en/projects/cvsweb.sgml @@ -1,116 +1,116 @@ - + %includes; %developers; ]> &header;

Contents

What is CVSweb?

CVSweb is a WWW interface for CVS repositories with which you can browse a file hierarchy on your browser to view each file's revision history in a very handy manner.

CVSweb was originally written by &a.fenner; for the FreeBSD Project, and instantly won great popularity among software developers for its usability.

FreeBSD-CVSweb, formerly known as knu-CVSweb, is an enhanced version of CVSweb based on and kept in sync with Henner Zeller's CVSweb, which is an extended version of the original CVSweb. &a.knu; made numerous cleanups, bug-fixes, security enhancements and feature improvements over the version and brought it back where it was born. FreeBSD-CVSweb is currently maintained by &a.scop;.

FreeBSD-CVSweb is freely available under the terms of The BSD License. It is currently used by such projects as FreeBSD, KDE, Mandrake Linux, NetBSD, OpenDarwin, Ruby, and - XFree86.

+ XFree86™.


Downloads

Download the tarball from the following sites. The latest stable release is 2.0.6, see ChangeLog for changes.

The latest beta version, 2.9.1, is also available for testing, see the beta/ subdirectory in the above, and ChangeLog for changes.

A number of operating system distributions contain a pre-packaged FreeBSD-CVSweb:


Resources

Project mailing list:
freebsd-cvsweb@FreeBSD.org is the mailing list for people discussing the development of FreeBSD-CVSweb. Patches, bug reports and feature requests are welcome. To join the list, follow the instructions described here. List archives are also available.
CVS repository
FreeBSD-CVSweb is available through anonymous CVS pserver. The module name is /projects/cvsweb. The current stable branch is rel-2_0-branch, HEAD contains the development version.
CVSweb on CVSweb
You can browse the FreeBSD-CVSweb source via itself here.
&footer; diff --git a/en/support.sgml b/en/support.sgml index 11382f10f4..bdd774f45f 100644 --- a/en/support.sgml +++ b/en/support.sgml @@ -1,1084 +1,1084 @@ + %includes; ]> &header;

Mailing lists

Mailing lists are the primary support channel for FreeBSD users, with numerous mailing lists covering different topic areas. When in doubt about what list to post a question to, post to freebsd-questions@FreeBSD.ORG. To get an up to the minute view of the mailing lists available or to subscribe to a mailing list, use FreeBSD.org's Mailman web interface. All mailman lists are available in a digest format and have threaded archives available. See the individual list's web page for details.

You can search or browse the mailing list archives at www.FreeBSD.org.

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

Problem Report Database

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 Repository

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:

Mirrors of the CVS Repository cgi script are available in Germany, Japan, Portugal, San Marino, Spain, USA/California and Ukraine.

User Groups

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.

Australia

Europe

North America

Rest of the world

FreeBSD Development Projects

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.

FreeBSD Security Guide

Security resources available to FreeBSD users: PGP Key for Security Officers, advisories, patches and mailing lists.

Commercial Consulting Services

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

Hardware

Related Operating System Projects

&footer; diff --git a/en/usergroups.sgml b/en/usergroups.sgml index 11382f10f4..bdd774f45f 100644 --- a/en/usergroups.sgml +++ b/en/usergroups.sgml @@ -1,1084 +1,1084 @@ + %includes; ]> &header;

Mailing lists

Mailing lists are the primary support channel for FreeBSD users, with numerous mailing lists covering different topic areas. When in doubt about what list to post a question to, post to freebsd-questions@FreeBSD.ORG. To get an up to the minute view of the mailing lists available or to subscribe to a mailing list, use FreeBSD.org's Mailman web interface. All mailman lists are available in a digest format and have threaded archives available. See the individual list's web page for details.

You can search or browse the mailing list archives at www.FreeBSD.org.

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

Problem Report Database

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 Repository

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:

Mirrors of the CVS Repository cgi script are available in Germany, Japan, Portugal, San Marino, Spain, USA/California and Ukraine.

User Groups

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.

Australia

Europe

North America

Rest of the world

FreeBSD Development Projects

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.

FreeBSD Security Guide

Security resources available to FreeBSD users: PGP Key for Security Officers, advisories, patches and mailing lists.

Commercial Consulting Services

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

Hardware

Related Operating System Projects

&footer;