diff --git a/en/alpha/alpha.sgml b/en/alpha/alpha.sgml index 4ede3c70e1..a4056dff90 100644 --- a/en/alpha/alpha.sgml +++ b/en/alpha/alpha.sgml @@ -1,36 +1,35 @@ - + %includes; ]> - &header;

This page contains information about porting FreeBSD to Alpha systems.

FreeBSD/Alpha Specific Links

Other Links of Interest

Hardware

Projects

&footer; diff --git a/en/applications.sgml b/en/applications.sgml index dbf63cbf31..b0299c1651 100644 --- a/en/applications.sgml +++ b/en/applications.sgml @@ -1,148 +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/auditors.sgml b/en/auditors.sgml index 3acac39ada..baac41db18 100644 --- a/en/auditors.sgml +++ b/en/auditors.sgml @@ -1,744 +1,743 @@ + %includes; ]> - &header;

General Information

- Last Updated: $FreeBSD: www/en/auditors.sgml,v 1.30 1999/12/12 16:24:00 jhb Exp $ + Last Updated: $FreeBSD: www/en/auditors.sgml,v 1.31 2000/04/03 10:41:11 kuriyama Exp $

Overview

In light of our recent (and still ongoing) security concerns, it has become rather obvious that nothing less than a rigorous and comprehensive security review of the FreeBSD source tree will enable us to really have much confidence in the security of our operating system, an OS that many have come increasingly to rely upon and must be made more than reasonably secure if they are to continue to be able to do so.

The sheer amount of legacy code & code from outside sources in FreeBSD also makes it especially easy for security holes to go unnoticed until it's rather too late, and no truly large-scale attempt has been made up to this point to really go through the codebase with a specific focus on security issues, that being a rather big project and most FreeBSD developers being more than busy enough elsewhere. This situation must now change, however, if we are to remain the kind of operating system that people can continue to rely upon as the Internet continues to grow and (I suspect) become an ever-more hostile environment for improperly protected systems. Proper security is something of a cooperative arrangement between the local administrator and the OS vendor, and this "OS vendor" needs to do its part.

The core team's first step in becoming more serious about security was to bring the project's security officer, Guido van Rooij, into the team so that one of the "voices at the table" would have security as his primary mandate and representation in all the important security mailing lists external to the FreeBSD Project. He will also keep the rest of us in core much more aware of security concerns as they arise, hopefully not to be taken quite so by surprise as we have a few times in the past.

Our second step will be this audit, an attempt to methodically go through every line of source in FreeBSD looking for obvious buffer overflows (sprintf()/strcpy() vs snprintf()/strncpy() and so on), less obvious security holes, instances of insufficiently defensive coding, amusing comment strings to forward to freebsd-chat, whatever we run across.

Using the modules database as an outline, we will split the source tree into more manageable pieces, keeping a sign-up sheet in a prominent place so that people can see which modules are covered and which are not. A carefully selected team of individuals is now also being formed, that team being composed of "auditors" and "reviewers" (most members of the team being both). An auditor has principle responsibility, which may be shared with another auditor, for actually going through the code and looking for security holes and/or bugs. Once a reasonable pile of diffs have been accumulated, assuming that any problems were found, they are send to one or more reviewers who are responsible for giving the changes another once-over and, if the auditor does not have commit privileges, to actually commit the changes when & if they're deemed acceptable.

Requirements:

In order to be an auditor, you should either have commit privileges on freefall.FreeBSD.org or an arrangement with another auditor/reviewer who does. You should also be running or have immediate access to FreeBSD-current sources since all of our changes will be made relative to that branch and then brought back (as necessary) into the 2.1 and 2.2 branches.

What to look for and what the general rules to follow are is sufficiently complex that I have turned it into a FreeBSD Security Guide. Please read this now if you haven't already. Other excellent documents are the Secure Programming Checklist and the Unix Security Checklist, both available from AUSCERT.

Sign-Up sheet:

Here is the sign-up sheet as it sits so far. This is *very* skeletal at this stage, given that we've just now started, and as people indicate which module(s) they're willing to either audit or review, we'll fill it in. If this tabular format also becomes unwieldy as it fills up, we can change it or put it on a web page or something. :) I've left some sample entries open just as place-holders, and they in no way imply that someone has to be willing to pick up pieces that large.

Anything in the modules database represents a potential auditing target - from ones as small as "cat" to ones as large as "lib", the most important being that people bite off pieces no larger than they think they can chew. If you take 15 things onto your plate and deal with only 5, you're not doing anyone any favors since the other auditors will be assuming that the other 10 items are handled!

To sign up for something, please send mail to jmb@FreeBSD.org.

Module Auditor(s) Reviewer(s) Status
bin ac ee* gvr* jh ka mu vk imp* jmb* md* gvr* Open
contrib cg gvr* Open
eBones mrvm* gvr* Open
games ab ee* xaa gvr* Open
init gl gvr* Open
lib ak bjn pst* dg* imp* jkh* gvr* Open
libc ee* mu gvr* Open
libexec crh ee* imp* mr witr gvr* Open
lkm dob* gvr* Open
sbin ee* imp* or* tao jmb* md* gvr* Open
secure dc mrvm* gvr* Open
telnetd ac dn imp* gvr* Open
usr.bin bob ee* jha jm ky* rb rd rjk vk md* gvr* Open
usr.sbin ee* ejc gl imp* jm marc rd md* gvr* Open

Auditor/Reviewer keys

This is the list of people who have volunteered to participate as auditors or reviewers in this process. They may also be reached collectively by sending mail to the auditors@FreeBSD.org alias at times when it is appropriate to send mail to all auditors. If you wish to reach just the auditors & reviewers for a specific category, say usr.sbin for example, then you would send mail to audit-usr.sbin@FreeBSD.org.

Key Auditor/Reviewer Name and Email address
ab Aaron Bornstein aaronb@j51.com
ac Adrian Chadd adrian@psinet.net.au
ak Adam Kubicki apk@itl.waw.pl
am Albert Mietus gam@gamp.hacom.nl
avk Alexander V. Kalganov top@sonic.cris.net
bb Bob Bishop rb@gid.co.uk
bjn Brent J. Nordquist nordquist@platinum.com
bob Bob Willcox bob@luke.pmr.com
btm Brian T. Michely brianm@cmhcsys.com
cg Coranth Gryphon gryphon@healer.com
cl Chris Lambertus cmlambertus@ucdavis.edu
crh Charles Henrich henrich@crh.cl.msu.edu
dc Dan Cross tenser@spitfire.ecsel.psu.edu
dg* David Greenman davidg@FreeBSD.org
din Dinesh Nair dinesh@alphaque.com
dn David Nugent davidn@labs.usn.blaze.net.au
dob* David E. O'Brien obrien@NUXI.com
dz Danny J. Zerkel dzerkel@phofarm.com
ee* Eivind Eklund eivind@FreeBSD.org
eh Elijah Hempstone avatar@gandalf.bss.sol.net
ehu Ernest Hua hua@chromatic.com
ejc Eric J. Chet ejc@gargoyle.bazzle.com
gl Giles Lean giles@nemeton.com.au
gvr* Guido van Rooij guido@FreeBSD.org
gw Graham Wheeler gram@oms.co.za
imp* Warner Losh imp@FreeBSD.org
jb Jim Bresler jfb11@inlink.com
jh Jake Hamby jehamby@lightside.com
jha John H. Aughey jha@cs.purdue.edu
jk Jerry Kendall Jerry@kcis.com
jkh* Jordan K. Hubbard jkh@FreeBSD.org
jm Josef Moellers mollers.pad@sni.de
jmb* Jonathan M. Bresler jmb@FreeBSD.org
joe* Joe Greco jgreco@solaria.sol.net
ka Kalganov Alexander top@bird.cris.net
ki Kenneth Ingham ingham@i-pi.com
ky* Kazutaka YOKOTA yokota@zodiac.mech.utsunomiya-u.ac.jp
marc Marc Slemko marcs@znep.com
md* Matt Dillon dillon@best.net
mr Mike Romaniw msr@cuc.com
mrvm* Mark Murray mark@grondar.za
mu Mudge mudge@l0pht.com
or* Ollivier Robert roberto@keltia.freenix.fr
pb Peter Blake ppb@baloo.tcp.co.uk
peter* Peter Wemm peter@FreeBSD.org
phk* Poul-Henning Kamp phk@FreeBSD.org
pst* Paul Traina pst@FreeBSD.org
rb Reinier Bezuidenhout rbezuide@oskar.nanoteq.co.za
rd Rajiv Dighe rajivd@sprynet.com
rel Roger Espel Llima espel@llaic.univ-bpclermont.fr
rjk Richard J Kuhns rjk@grauel.com
rm Robin Melville robmel@nadt.org.uk
rs Robert Sexton robert@kudra.com
sc Sergei Chechetkin csl@whale.sunbay.crimea.ua
tao Brian Tao taob@risc.org
tdr Thomas David Rivers ponds!rivers@dg-rtp.dg.com
vk Vadim Kolontsov vadim@tversu.ac.ru
witr Robert Withrow witr@rwwa.com
xaa Mark Huizer xaa@stack.nl

* = Has CVS commit privileges.

&footer; diff --git a/en/availability.sgml b/en/availability.sgml index 5674c9ae4b..9c9892b640 100644 --- a/en/availability.sgml +++ b/en/availability.sgml @@ -1,84 +1,83 @@ + %includes; ]> - &header;

Availability of FreeBSD

FreeBSD is free and is available for downloading over the Internet or on CDROM for a small fee.


Hardware requirements.

FreeBSD runs on a variety of PC and Alpha hardware. Please review the supported configurations section of the FreeBSD Handbook for more information.


Where to get it.

FreeBSD can be downloaded over the Internet for free, using a variety of different protocols (FTP, CVS, AFS, and more). If bandwidth is expensive for you then it can also be purchased on CDROM from a variety of vendors.

For more information on obtaining FreeBSD, please see the Handbook Chapter on obtaining FreeBSD.

For more information on installing FreeBSD, please see the Handbook Chapter on installing FreeBSD.


About the FreeBSD Project.

FreeBSD is developed and supported by a worldwide team of programmers. Jordan Hubbard, one of the project's founders, has written a brief history of the FreeBSD project. Information about who's responsible for what is also available. If you are curious, take a look at some pictures of the team members. A more complete listing of contributors is available in the Contributors section of the FreeBSD Handbook. FreeBSD is an open project, and welcomes the help of individuals who have time and or skills to offer.

This "about" section was created by Sean Kelly.

Inside your PC is a daemon waiting to be unleashed. Free it with FreeBSD.

&footer; diff --git a/en/commercial/commercial.sgml b/en/commercial/commercial.sgml index c85c60528b..fcf6976970 100644 --- a/en/commercial/commercial.sgml +++ b/en/commercial/commercial.sgml @@ -1,48 +1,47 @@ - + %includes; %vendorincludes; ]> - &header; &vendorintroduction;

Please note that the inclusion of vendors in our list does not signify our endorsement of their products or services.

&footer; diff --git a/en/commercial/consulting.sgml b/en/commercial/consulting.sgml index 24affdbf2a..1022d74382 100644 --- a/en/commercial/consulting.sgml +++ b/en/commercial/consulting.sgml @@ -1,29 +1,28 @@ - + %includes; %vendorincludes; ]> - &header; &vendorintroduction;

Consulting Services

This file has been indexed by alphabetic order for easy navigating. Should you wish to find a specific entry, please use the shortcuts below for quick access.

&consulting;

Commercial Vendors Home &footer; diff --git a/en/commercial/consulting_bycat.sgml b/en/commercial/consulting_bycat.sgml index b308f3e172..d6dd7b5fdc 100644 --- a/en/commercial/consulting_bycat.sgml +++ b/en/commercial/consulting_bycat.sgml @@ -1,29 +1,28 @@ - + %includes; %vendorincludes; ]> - &header; &vendorintroduction;

Consulting Services

This file has been divided into sub-categories for your convenience. Please use the following shortcuts to assist you to the proper gallery entries.

&consultingbycat;

Commercial Vendors Home &footer; diff --git a/en/commercial/hardware.sgml b/en/commercial/hardware.sgml index 88a767b3c8..00868a461a 100644 --- a/en/commercial/hardware.sgml +++ b/en/commercial/hardware.sgml @@ -1,29 +1,28 @@ - + %includes; %vendorincludes; ]> - &header; &vendorintroduction;

Hardware Vendors

This file has been indexed by alphabetic order for easy navigating. Should you wish to find a specific entry, please use the shortcuts below for quick access.

&hardware;

Commercial Vendors Home &footer; diff --git a/en/commercial/misc.sgml b/en/commercial/misc.sgml index 5d78700167..9f91fc063c 100644 --- a/en/commercial/misc.sgml +++ b/en/commercial/misc.sgml @@ -1,29 +1,28 @@ - + %includes; %vendorincludes; ]> - &header; &vendorintroduction;

Miscellaneous Vendors

This file has been indexed by alphabetic order for easy navigating. Should you wish to find a specific entry, please use the shortcuts below for quick access.

&misc;

Commercial Vendors Home &footer; diff --git a/en/commercial/software.sgml b/en/commercial/software.sgml index 39f7a13595..d065b53665 100644 --- a/en/commercial/software.sgml +++ b/en/commercial/software.sgml @@ -1,29 +1,28 @@ - + %includes; %vendorincludes; ]> - &header; &vendorintroduction;

Software Vendors

This file has been indexed by alphabetic order for easy navigating. Should you wish to find a specific entry, please use the shortcuts below for quick access.

&software;

Commercial Vendors Home &footer; diff --git a/en/commercial/software_bycat.sgml b/en/commercial/software_bycat.sgml index cfb26cd224..96fc581db2 100644 --- a/en/commercial/software_bycat.sgml +++ b/en/commercial/software_bycat.sgml @@ -1,29 +1,28 @@ - + %includes; %vendorincludes; ]> - &header; &vendorintroduction;

Software Vendors

This file has been divided into sub-categories for your convenience. Please use the following shortcuts to assist you to the proper gallery entries.

&softwarebycat;

Commercial Vendors Home &footer; diff --git a/en/copyright/copyright.sgml b/en/copyright/copyright.sgml index 6ab207694b..1ffa826fd1 100644 --- a/en/copyright/copyright.sgml +++ b/en/copyright/copyright.sgml @@ -1,24 +1,23 @@ - + %includes; ]> - &header;

The FreeBSD Copyright

The BSD Copyright

The BSD Daemon

FreeBSD Ports redistribution restrictions

GNU GENERAL PUBLIC LICENSE

GNU LIBRARY GENERAL PUBLIC LICENSE

&footer; diff --git a/en/copyright/daemon.sgml b/en/copyright/daemon.sgml index 8cead42449..c95386ae25 100644 --- a/en/copyright/daemon.sgml +++ b/en/copyright/daemon.sgml @@ -1,72 +1,71 @@ - + %includes; ]> - &header;

The little red fellow that graces many of these pages is the BSD Daemon. In the context of Unix systems, daemons are process that run in the background attending to various tasks without human intervention. In the general sense, daemon is an older form of the word demon. In the Unix System Administration Handbook, Evi Nemeth has this to say about daemons:

"Many people equate the word ``daemon'' with the word ``demon,'' implying some kind of Satanic connection between UNIX and the underworld. This is an egregious misunderstanding. ``Daemon'' is actually a much older form of ``demon''; daemons have no particular bias towards good or evil, but rather serve to help define a person's character or personality. The ancient Greeks' concept of a ``personal daemon'' was similar to the modern concept of a ``guardian angel'' --- ``eudaemonia'' is the state of being helped or protected by a kindly spirit. As a rule, UNIX systems seem to be infested with both daemons and demons." (p403)

The earliest (and most popular) renditions of the BSD Daemon were created by John Lasseter. More recent FreeBSD-specific renditions have done by Tatsumi Hosokawa, but the basic inspiration was definitely John's. The copyright holder and creator of the daemon image is Marshall Kirk McKusick. A short pictorial history is also available. There is a gallery of FreeBSD related publications that use variations of the daemon graphic.

Various size stuffed and beanie daemons are available from the FreeBSD Mall . In Europe, German-made stuffed daemons are also available from Liebscher & Partner.

ScotGold produce 1" case badges featuring BSD Daemon.

BSD Daemon Copyright 1988 by Marshall Kirk McKusick. All Rights Reserved.

Permission to use the daemon may be obtained from:

Marshall Kirk McKusick
1614 Oxford St
Berkeley, CA 94709-1608
USA

or via email at mckusick@mckusick.com.

Copyright Home &footer; diff --git a/en/copyright/freebsd-license.sgml b/en/copyright/freebsd-license.sgml index dfe2da4b9e..9067bba5e6 100644 --- a/en/copyright/freebsd-license.sgml +++ b/en/copyright/freebsd-license.sgml @@ -1,55 +1,54 @@ - + %includes; ]> - &header;

Copyright 1994-2001 FreeBSD, Inc. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE FREEBSD PROJECT ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the FreeBSD Project or FreeBSD, Inc.

Copyright Home &footer; diff --git a/en/copyright/license.sgml b/en/copyright/license.sgml index 8c96346e65..1192d2cb40 100644 --- a/en/copyright/license.sgml +++ b/en/copyright/license.sgml @@ -1,103 +1,102 @@ - + %includes; ]> - &header;

All of the documentation and software included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by The Regents of the University of California.

Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
    This product includes software developed by the University of California, Berkeley and its contributors.
  4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The Institute of Electrical and Electronics Engineers and the American National Standards Committee X3, on Information Processing Systems have given us permission to reprint portions of their documentation.

In the following statement, the phrase ``this text'' refers to portions of the system documentation.

Portions of this text are reprinted and reproduced in electronic form in the second BSD Networking Software Release, from IEEE Std 1003.1-1988, IEEE Standard Portable Operating System Interface for Computer Environments (POSIX), copyright C 1988 by the Institute of Electrical and Electronics Engineers, Inc. In the event of any discrepancy between these versions and the original IEEE Standard, the original IEEE Standard is the referee document.

In the following statement, the phrase ``This material'' refers to portions of the system documentation.

This material is reproduced with permission from American National Standards Committee X3, on Information Processing Systems. Computer and Business Equipment Manufacturers Association (CBEMA), 311 First St., NW, Suite 500, Washington, DC 20001-2178. The developmental work of Programming Language C was completed by the X3J11 Technical Committee.

The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the Regents of the University of California.

Copyright Home &footer; diff --git a/en/docproj/current.sgml b/en/docproj/current.sgml index ee1fe1bc14..1087bb0d7e 100644 --- a/en/docproj/current.sgml +++ b/en/docproj/current.sgml @@ -1,240 +1,239 @@ - + %includes; ]> - &header;

Here are the projects currently under way (or being actively contemplated on the freebsd-doc mailing list). I have also included some that have not really been talked about, but would probably be a good idea. Each project lists the contact person for that project (if I know who it is).

If you think you can contribute to any of these, please do not hesitate to stand up and be counted. You should talk to the person responsible for that particular project, who can then bring you up to speed on what is happening.

Any omissions in this list are entirely my fault (Nik Clayton, <nik@FreeBSD.ORG>), sorry in advance to anyone whose project I have missed.

Open documentation problem reports

Current FreeBSD problems reports are tracked using the GNATS database. You can view the open documentation problem reports.

FreeBSD for Linux users

Responsible: Annelise Anderson < andrsn@andrsn.stanford.edu>

Synopsis: Linux users coming to FreeBSD can be confused by some of the differences between the systems (the different default shells, how boot time configuration is performed, and so on). Annelise is coordinating the development of a tutorial/FAQ section that will address these points.

The list of current questions is at http://freebsd.stanford.edu/FreeBSD/linux.html.

Fixup the FOO.TXT files

Responsible: Doug <studded@dal.net>

Synopsis: The "FOO.TXT" files are the README files, the INSTALL.TXTs. the ABOUT.TXTs and so on that you get with FreeBSD. Doug (and others) are going through these trying to make sure they are accurate, consistent, and easy to understand. A very worthwhile task.

Write a section in the Handbook and/or FAQ

Responsible: No one

Synopsis: Chunks of the FAQ and Handbook have empty sections in them. They need filling. If you have just had to use one of these documents to complete a task, and found them lacking, please find the time to write up your experiences as a possible replacement.

Alternatively, if you have just had to do something that had no entry in the FAQ and/or Handbook, please consider writing a new section. Then submit it as outlined above.

Write some new Papers

The New SCSI layer for FreeBSD (CAM)

Responsible: <doc@FreeBSD.org>, <scsi@FreeBSD.org>

Synopsis: See The Design and Implementation of the FreeBSD SCSI Subsystem for a first snapshot.

Write some new Tutorials

Responsible: <doc@FreeBSD.org>

Synopsis:

Write Manpages for the kernel

Responsible: <doc@FreeBSD.org>

Synopsis: Document kernel functions, section 9

CGI Scripts

Responsible: <doc@FreeBSD.org>, Wolfram Schneider <wosch@FreeBSD.org>

Synopsis:

Here are some hints how to write the ports module

A single line in /usr/ports/INDEX looks like

    xfig-3.2.2|/usr/ports/graphics/xfig|/usr/X11R6|A drawing program for X11|/usr/ports/graphics/xfig/pkg/DESCR|ports@FreeBSD.ORG|graphics x11|XFree86-3.3.2 Xaw3d-1.3 jpeg-6b xpm-3.4k|XFree86-3.3.2 Xaw3d-1.3 jpeg-6b netpbm-94.3.1 tiff-3.4 transfig-3.2 xpm-3.4k
         

The format is

    distribution-name|port-path|installation-prefix|comment| \
        description-file|maintainer|categories|build deps|run deps
        

The above INDEX line parsed into an anonymous hash object

 $port = {	
 	DISTRIBUTION_NAME   => 'xfig-3.2.2',
 	PORT_PATH           => '/usr/ports/graphics/xfig',
 	INSTALLATION_PREFIX => '/usr/X11R6',
 	COMMENT             => 'A drawing program for X11',
 	DESCRIPTION_FILE    => '/usr/ports/graphics/xfig/pkg/DESCR',
 	MAINTAINER          => 'ports@FreeBSD.ORG',
 	CATEGORIES          => ['graphics', 'x11'],
 	BUILD_DEPS          => ['XFree86-3.3.2', 'Xaw3d-1.3', 'jpeg-6b', 
 	                        'xpm-3.4k'],
 	RUN_DEPS            => ['XFree86-3.3.2',  'Xaw3d-1.3', 'jpeg-6b',
 				'netpbm-94.3.1', 'tiff-3.4', 'transfig-3.2',
 				'xpm-3.4k'] 
 };
       

Now we need some functions

Finally

Modify the cgi script url.cgi, ports.cgi , pds.cgi and the script portindex to use this module.

Contact Nik Clayton <nik@FreeBSD.ORG> for a first snapshot of the ports module.

Multilingual Web scripts

Responsible: <doc@FreeBSD.org>

Synopsis:

Our main Web pages are written in (American) English. The FreeBSD Translations Projects translate the web pages, Handbook and FAQ to other languages.

We must translate the cgi scripts and web build scripts too. The scripts should support multiple languages, not only one. Most scripts are written in perl.

Translations of the FreeBSD Documentation

Responsible: <doc@FreeBSD.org>

Translate the FreeBSD documentation (Web pages, FAQ, handbook, manpages) into other languages. See the FreeBSD translations projects

Search engine enhancements

Responsible: <doc@FreeBSD.org>

When searching the website, the output from the search engine includes the filename that was found, which might be something like FAQ34.html.

It would be more useful if the results included the question text, allowing the user to see whether or not the result was relevant.

FreeBSD Documentation Project Home &footer diff --git a/en/docproj/doc-set.sgml b/en/docproj/doc-set.sgml index e80ce0f700..16319587e9 100644 --- a/en/docproj/doc-set.sgml +++ b/en/docproj/doc-set.sgml @@ -1,61 +1,60 @@ - + %includes; ]> - &header;

FreeBSD's documentation falls into four basic categories;

  1. The manual pages

    The Project does not really concern itself with these, since they are a part of the base system. The exception to this is the Japanese team, who are translating them. There is no reason other volunteers could not step in to translate the manual pages to other languages as well.

    That is not to say that the manual pages are unimportant, far from it. It is just that they are intimately tied to specific systems of FreeBSD, and most of the time the best person to write the manual page is the person that wrote that part of FreeBSD.

  2. The FAQ

    This is maintained by the project. The aim is to address (in short question and answer format) questions that are asked or should be asked on the various mailing lists and newsgroups devoted to FreeBSD. The format does not permit long winded and comprehensive answers.

  3. The Handbook

    This is maintained by the project. Topics that need a more in depth discussion are addressed in the Handbook.

  4. The Tutorials

    Some of these tutorials are maintained by Project committers, others are not. The maintenance of these documents is up to the individual authors, although, to the best of my knowledge, they have all kept them up to date, solicit comments from the readership and so on.

    Some of the tutorials are stored on the FreeBSD web site. For these tutorials the authors submit their changes to one of the committers, and the committer makes the change. Other tutorials are stored on the author's private webspace, and the author can make changes as and when they wish. Sometimes this is a deliberate choice on the part of the author, and sometimes it is a historical accident.

FreeBSD Documentation Project Home &footer diff --git a/en/docproj/sgml.sgml b/en/docproj/sgml.sgml index 0f2b357c6c..8760c34de5 100644 --- a/en/docproj/sgml.sgml +++ b/en/docproj/sgml.sgml @@ -1,188 +1,187 @@ - + %includes; ]> - &header;

The Documentation Project is trying to use SGML as the standard method of representing the documentation.

SGML is the Standard Generalised Markup Language.

In a nutshell (and apologies to any SGML purists in the audience that are offended) SGML is a language for writing other languages.

You have probably already used SGML, but you did not know it. HTML, the language that web pages are written in, has a formal description. That description is written in SGML. When you are writing HTML you are not writing SGML (per se), but you are using a language that is defined using SGML.

There are many, many markup languages that are defined using SGML. HTML is one of them. Another is called "LinuxDoc". As you can probably guess, it was originally created by the Linux documentation group to write their documentation, and the FreeBSD Documentation Project adopted it as well.

Another markup language defined using SGML is called "DocBook". This is a language designed specifically for writing technical documentation, and as such it has many tags (the things inside the <...>) to describe technical documentation related things.

For example, this is how you might write a brief paragraph in HTML (do not worry about the content, just look at the tags):

The system's passwords are stored in /etc/passwd. To edit
       this file you should use vipw. However, if you just
       want to add a new user you can use adduser.

]]>

The same paragraph, marked up using DocBook, looks like

The system's passwords are stored in
       /etc/passwd. To edit this file you should use
       vipw. However, if you just want to add a new user
       you can use adduser.
 ]]>

As you can see, DocBook is much more 'expressive' than HTML. In the HTML example the filename is marked up as being displayed in a 'typewriter' font. In the DocBook example the filename is marked up as being a 'filename', the presentation of the filename is not described.

There are a number of advantages to this more expressive form of markup:

If you are familiar with them, this is a bit like Microsoft Word stylesheets, only vastly more powerful.

Of course, with this power comes a price;

Right now, the Project is still using LinuxDoc for the Handbook and the FAQ. That's changing, and in particular there's a project underway to convert the documentation to DocBook.

What if you don't know LinuxDoc/DocBook? Can you still contribute?

Yes you can. Quite definitely. Any documentation is better than no documentation. If you've got some documentation to contribute and it's not marked up in LinuxDoc or DocBook, don't worry.

Submit the documentation as normal. Someone else on the Project will grab your committed documentation, mark it up for you, and commit it. With a bit of luck they'll then send you the marked up text back. This is handy because you can do a "before and after" shot of the plain documentation and the marked up stuff, and hopefully learn a bit more about the markup in the process.

Obviously, this slows down the committing process, since your submitted documentation needs to be marked up, which may take an evening or too. But it will get committed.

More information about SGML and DocBook?

You should first read the Documentation Project Primer. This aims to be a comprehensive explanation of everything you need to know in order to work with the FreeBSD documentation.

This is a long document, split in to many smaller files. You can also view it as one large file.

http://www.oasis-open.org/cover/sgml-xml.html

The SGML/XML web page. Includes countless pointers to more information about SGML.

http://www-tei.uic.edu/orgs/tei/sgml/teip3sg/index.html

The "Gentle Introduction to SGML". Recommended reading for anyone who wants to learn more about SGML from a beginners perspective.

http://www.oasis-open.org/docbook/

The DocBook DTD is maintained by OASIS. These pages are aimed users who are already comfortable with SGML, and who want to learn DocBook.

http://fallout.campusview.indiana.edu/~jfieber/docbook/

John Fieber's page containing links to DocBook resources and sample documents. It also includes the beginnings of a markup guide for FreeBSD.

http://www.nothing-going-on.demon.co.uk/FreeBSD/

Nik Clayton's page contains links to documentation written in DocBook and then converted to HTML. The original DocBook files are available, and give a reasonable example of how the various elements in DocBook can be used.

http://wolfram.schneider.org/papers/webbuild.html
&webbuild;

FreeBSD Documentation Project Home &footer; diff --git a/en/docproj/submitting.sgml b/en/docproj/submitting.sgml index 3430b9b421..2c48132abc 100644 --- a/en/docproj/submitting.sgml +++ b/en/docproj/submitting.sgml @@ -1,135 +1,134 @@ - + %includes; ]> - &header;

I have written some documentation. How do I submit it?

First, thank you for taking the time to do this.

You should make your documentation available for review. If you can, put it on an FTP site or a website.

Then post a message to the -doc mailing list, with a brief outline of the documentation and the pointer to its location, and solicit feedback.

If, for some reason, you can not put the documentation up for FTP or on a web site somewhere you can send it directly to the -doc mailing list. If you do this, please only send plain text documents.

You should probably cc: this request for comments to other appropriate mailing lists. For example, something that relates to how to use CVSup to keep your source tree up to date would be of interest to the subscribers of the FreeBSD-current and FreeBSD-stable mailing lists.

After people have looked over your documentation, and you have had the chance to incorporate any of their suggestions, you are ready to submit it.

To do this, wrap it up into a tar file. If your documentation consists of three files,

     % tar cf doc.tar one two three
     

which does just that. Then compress the tar file,

     % gzip -9 doc.tar
     

which will produce doc.tar.gz.

Finally, encode the file so that it will not be mangled by any e-mail programs.

     % uuencode doc.tar.gz doc.tar.gz > doc.uue
     

You should then let the Documentation Project know about it. The correct way to do this is to use a command called send-pr, which should be installed on your machine.

You do this so that your submission can be tracked. When you submit a PR (Problem Report) it is assigned a unique number. One of the committers can then assign the PR to themselves, and liase with you on committing the new documentation.

send-pr itself is pretty simple. All it does is send an e-mail with some special formatting to a particular address. When you run send-pr you will be put into your editor (probably vi or emacs) with a template to fill out, and some instructions on how to fill it out.

Make sure the "Category" is set to "docs" and that the "Class" is set to one of "change-request". You should include the .uue file you created earlier in to the PR.

When you come out of the editor the PR will be sent as an e-mail to the right place. You will get a notification message shortly afterwards telling you what number your PR has been given, and this number can be used to track its progress.

Alternatively, you can use the web interface at http://www.FreeBSD.org/send-pr.html.

I have made some changes to existing documentation, how do I submit them?

Again, thank you for taking the time to do this.

First off, you need to produce a special file, called a diff. This diff shows just the changes that you have made. This makes it easier for the person doing the committing to see what you have changed, and means you do not need to spend lots of time explaining what you have changed (although you should still explain why you think the change should be made).

To make a 'diff', you should;

  1. Make a copy of the file you are going to change. If you are changing

         % cp foo.sgml foo.sgml.old
     	
  2. Then, make your changes to foo.sgml

         % vi foo.sgml
         ... tap tap tap ...
     
         ... test the changes, read them for typos and so on ...
     	
  3. Make the diff. The command to do this is

         % diff -c foo.sgml.old foo.sgml > foo.diff
     	

    This looks at the difference between the two files, and writes them to the file

You can then send

FreeBSD Documentation Project Home &footer diff --git a/en/docproj/translations.sgml b/en/docproj/translations.sgml index 24088051e9..87143b9ffb 100644 --- a/en/docproj/translations.sgml +++ b/en/docproj/translations.sgml @@ -1,158 +1,157 @@ - + %includes; ]> - &header;

The FreeBSD Chinese Documentation Project

Web: -
E-Mail: foxfair@FreeBSD.org
Mailing list available
Send a mail to majordomo@freebsd.sinica.edu.tw with the words "subscribe freebsd-chinese-doc" in the body of the message.
Posting is allowed for the members at freebsd-chinese-doc@freebsd.sinica.edu.tw
Documents available
FAQ
Documents currently at working
Handbook

The FreeBSD Estonian Documentation Project

Web: http://www.matti.ee/~vallo/
Documents available
FreeBSD handbook userppp section

The FreeBSD French Documentation Project

Web: http://www.freebsd-fr.org
Mailing lists available
Send a mail to listserver@freebsd-fr.org with the words "SUB freebsd-questions" in the body of the message for subscribing to the questions mailing list in French.
Send a mail to listserver@freebsd-fr.org with the words "SUB annonces" in the body of the message for subscribing to the announce mailing list in French.
Documents available
FAQ
Some tutorials
Really Quick Newsletters
PicoBSD
Documents currently at working
Handbook
CVS repository
CVS web
Send a mail to listserver@freebsd-fr.org with the words "SUB cvs" in the body of the message for subscribing to the French CVS update mailing list in French.

The FreeBSD German Documentation Project

Web: http://www.de.FreeBSD.org/de/uebersetzung.html
E-Mail: de-bsd-translators@de.FreeBSD.org
Documents currently at working
Handbook, FAQ, WWW

The FreeBSD Italian Documentation Project

Web: http://www.gufi.org/
E-Mail: info@gufi.org
Documents currently at working
Handbook

The FreeBSD Japanese Documentation Project

Web: http://www.jp.FreeBSD.org/doc-jp/
E-Mail: doc-jp@jp.FreeBSD.org
Documents available
Handbook, FAQ, Web, FreeBSD NewsLetter Issue #2
Documents currently at working
FreeBSD Tutorials

The FreeBSD Korean Documentation Project

Web: http://www.kr.FreeBSD.org/projects/doc-kr/
E-Mail: doc@kr.FreeBSD.org
Documents currently at working
Handbook

The FreeBSD Russian Documentation Project

Web: http://www.FreeBSD.org.ua
E-Mail: ru-freebsd-doc@FreeBSD.ru
Documents available
FAQ
WWW
Q&A
Porter's handbook
Documents currently at working
Handbook

The FreeBSD Spanish Documentation Project

Web: http://www.es.FreeBSD.org/es/
E-Mail: jesusr@es.FreeBSD.org
Documents available
FAQ
Documents currently at working
Handbook

FreeBSD Documentation Project Home &footer diff --git a/en/docproj/who.sgml b/en/docproj/who.sgml index 5ba14475be..1e3ab48d66 100644 --- a/en/docproj/who.sgml +++ b/en/docproj/who.sgml @@ -1,33 +1,32 @@ - + %includes; ]> - &header;

The project is a fairly loosely knit group of people, and the only thing we have got in common is that we are subscribed to the mailing list FreeBSD-doc@FreeBSD.ORG.

Some of us can commit changes directly to the FreeBSD documentation tree. The complete list of people with commit ``privs'' is in the Handbook.

Others do not have commit privs, but they write and submit documentation nonetheless. One of the committers will then include it in the documentation set.

If you want to help out with the documentation project (and I fervently hope you do) all you have to do is subscribe to the mailing list and participate. As soon as you have done that you're a member of the project.

FreeBSD Documentation Project Home &footer diff --git a/en/docs.sgml b/en/docs.sgml index 12ad83e1c8..85d73dd8e7 100644 --- a/en/docs.sgml +++ b/en/docs.sgml @@ -1,395 +1,394 @@ + %includes; ]> - &header;

A wide variety of documentation is available for FreeBSD, on this web site, on other web sites, and available over the counter.

On this site

All the documentation on this site can be downloaded in a variety of different formats (HTML, Postscript, PDF, and more) and compression schemes (GZip, BZip2, Zip) from the FreeBSD FTP site.

This documentation is provided and maintained by the FreeBSD Documentation Project, and we are always looking for people to contribute new documentation and maintain existing documentation.

Books

The FreeBSD FAQ
Frequently Asked Questions, and answers, covering all aspects of FreeBSD.

The FreeBSD Handbook
A constantly evolving, comprehensive resource for FreeBSD users.

The FreeBSD Developer's Handbook
For people who want to develop software for FreeBSD (and not just people who are developing FreeBSD itself).

Chapter 2 of "The Design and Implementation of the 4.4BSD Operating System"
Donated by Addison-Wesley, provides a design overview of 4.4BSD, from which FreeBSD was originally derived.

Chapter 8 of "The FreeBSD Corporate Networker's Guide"
Donated by Addison-Wesley, provides an in-depth look at using FreeBSD to provide printing services to Windows, NT, and Novell hosts.

The Pedantic PPP Primer
Everything you need to know about configuring PPP on FreeBSD.

The Porter's Handbook
Essential reading if you plan on providing a port of a third party piece of software.

The FreeBSD Documentation Project Primer for New Contributors
Everything you need to know in order to start contributing to the FreeBSD Documentation Project.

Articles

The Committer's Guide
Introductory information for FreeBSD committers.

Dialup firewalling with FreeBSD
How to set up a firewall using PPP and ipfw over a dialup link with dynamically assigned IP addresses.

Creating a diskless X server
How to create a diskless X server.

Filtering Bridges
Configuring firewalls and filtering on FreeBSD hosts acting as bridges rather than routers.

Fonts and FreeBSD
A description of the various font technologies in FreeBSD, and how to use them with different programs.

Formatting media on FreeBSD
How to slice, partition, and format fixed and removable media on FreeBSD.

How to get the best results from the FreeBSD-questions mailing list
Tips and tricks to help you maximize the chances of getting useful information from the -questions mailing list.

An MH Primer
An introduction to using the MH mail reader on FreeBSD.

Using FreeBSD with other operating systems
How to install FreeBSD alongside one or more different operating systems on the same computer.

FreeBSD First Steps
For people coming to FreeBSD and Unix for the first time.

Programming Tools on FreeBSD
A user's guide to the various tools for software development on FreeBSD.

PXE booting FreeBSD
How to create an Intel PXE server using FreeBSD, and how to configure a FreeBSD client to boot from a PXE server.

FreeBSD and Solid State Devices
The use of solid state disk devices in FreeBSD.

Design elements of the FreeBSD VM system
An easy to follow description of the design of the FreeBSD virtual memory system.

Zip-drives and FreeBSD
How to format, mount, and use an Iomega Zip (SCSI, IDE, or parallel) Drive on FreeBSD.

Manual pages

FreeBSD
For release: 1.0, 1.1, 1.1.5.1, 2.0, 2.0.5, 2.1.0, 2.1.5, 2.1.6.1, 2.1.7.1, 2.2.1, 2.2.2, 2.2.5, 2.2.6, 2.2.7, 2.2.8, 3.0, 3.1, 3.2, 3.3, 3.4, 3.5.1, 4.0, 4.1, 4.2, 4.3, 5.0-current, Ports.
Other Systems
Unix Seventh Edition (V7), 2.8BSD, 2.9.1BSD, 2.10BSD, 2.11BSD, 4.3BSD Reno, NET/2, 386BSD 0.1, 4.4BSD Lite2, Linux, NetBSD, OpenBSD, Darwin, Plan 9, SunOS 4.x, SunOS 5.x, ULTRIX 4.2, and XFree86.

Other documentation

4.4BSD Documents: This is a hypertext version of the 4.4BSD documents from /usr/share/doc, where you will find the documents on a FreeBSD machine (if you install the doc distribution).

Info Documents: This is a hypertext version of the Info documents from /usr/share/info, where you will find the Info documents on a FreeBSD machine (if you install the info distribution).

On other web sites

Various independent efforts have also produced a great deal of useful information about FreeBSD.

Books

  • A Comprehensive Guide to FreeBSD - an attempt at a more readable, "book-like" tutorial explaining the FreeBSD Operating System. Intended for people new to both FreeBSD and UNIX. Currently a work in progress.

Articles

Links

In the real world...

FreeBSD in the Press

Articles in the press about FreeBSD.

Additional resources

Year 2000 Compatibility

The FreeBSD project's current statement about its Year 2000 compatibility.

BSD Real-Quick (TM) Newsletter

A monthly (sometimes bi-weekly) newsletter announcing recent developments in the FreeBSD arena. Subscribe to freebsd-announce to receive this newsletter via e-mail.

The Source Code

If you like digging your fingers into source code, here is a hypertext version of the FreeBSD kernel source. This is brought to you courtesy of Warren Toomey.

Daemon News

The industry leader in BSD news.

The FreeBSD 'zine

A monthly collection of easy to read (we hope) articles written by FreeBSD users and administrators just like you.

Like FreeBSD itself, this documentation is the product of a volunteer effort. The goals of the project are outlined here, as are the procedures for submitting corrections and new material.

The FreeBSD Diary

The FreeBSD Diary is a collection of how-to entries aimed at UNIX novices. The aim is to provide a set of step-by-step guides to installing and configuring various ports.

&footer; diff --git a/en/features.sgml b/en/features.sgml index 139f7461aa..e6f4a48e1a 100644 --- a/en/features.sgml +++ b/en/features.sgml @@ -1,97 +1,96 @@ + %includes; ]> - &header;

FreeBSD offers many advanced features.

No matter what the application, you want your system's resources performing at their full potential. FreeBSD's advanced features enable you to do just that.


A complete operating system based on 4.4BSD.

FreeBSD's distinguished roots derive from the latest BSD software releases from the Computer Systems Research Group at the University of California, Berkeley. The book The Design and Implementation of 4.4BSD Operating System, written by the 4.4BSD system architects, thus describes much of FreeBSD's core functionality in detail.

Drawing on the skills and experience of a diverse and world-wide group of volunteer developers, the FreeBSD Project has worked to extend the feature set of the 4.4BSD operating system in many ways, striving constantly to make each new release of the OS more stable, faster and containing new functionality driven by user requests.


FreeBSD provides higher performance, greater compatibility with other operating systems and less system administration.

FreeBSD's developers attacked some of the more difficult problems in operating systems design to give you these advanced features:

  • A merged virtual memory and filesystem buffer cache continuously tunes the amount of memory used for programs and the disk cache. As a result, programs receive both excellent memory management and high performance disk access, and the system administrator is freed from the task of tuning cache sizes.
  • Compatibility modules enable programs for other operating systems to run on FreeBSD, including programs for Linux, SCO UNIX, NetBSD, and BSD/OS.
  • Kernel Queues allow programs to respond more efficiently to a variety of asynchronous events including file and socket IO, improving application and system performance.
  • Accept Filters allow connection-intensive applications, such as web servers, to cleanly push part of their functionality into the operating system kernel, improving performance.
  • Soft Updates allow improved file system performance without sacrificing safety and reliability, by intelligently analyzing, caching and rewriting or reordering disk meta-data operations.
  • Support for IPsec and IPv6 allows improved security in networks, and support for the next-generation Internet Protocol, IPv6.

Work in-progress includes support for fine-grained SMP locking in kernel, allowing higher performance on multi-processor machines, support for Scheduler Activations, allowing parallelism in threaded programs, file system snapshots, fsck-free booting, network optimizations such as zero-copy sockets and event-driven socket IO, ACPI support, and advanced security features such as Mandatory Access Control.

&footer; diff --git a/en/gallery/cgallery.sgml b/en/gallery/cgallery.sgml index a9db175b41..392f8fb840 100644 --- a/en/gallery/cgallery.sgml +++ b/en/gallery/cgallery.sgml @@ -1,19 +1,19 @@ - + %includes; ]> - + &header;

All over the world, FreeBSD is powering innovative Internet applications and services. This gallery is a showcase of commercial organizations who have put FreeBSD to work for them. Browse and find out more about what FreeBSD can do for you!

    &cgallery;

Gallery Home &footer; diff --git a/en/gallery/gallery.sgml b/en/gallery/gallery.sgml index 3ef1c09802..e9919029fd 100644 --- a/en/gallery/gallery.sgml +++ b/en/gallery/gallery.sgml @@ -1,60 +1,59 @@ - + %includes; %gallery; ]> - &header;

All over the world, FreeBSD is powering innovative Internet applications and services. This gallery is a showcase of &num.total; organizations and individuals who have put FreeBSD to work for them. Browse and find out more about what FreeBSD can do for you!

To have your site added to these lists, simply fill out this form.

The "Powered by FreeBSD" logos above may be downloaded and displayed on personal or commercial home pages served by FreeBSD machines. Use of this logo or the likeliness of the BSD Daemons for profitable gain requires the consent of Brian Tao (creator of the "power" logo) and Marshall Kirk McKusick (trademark holder for the BSD Daemon image).

&footer; diff --git a/en/gallery/npgallery.sgml b/en/gallery/npgallery.sgml index 9d08fa1983..c7b511d26b 100644 --- a/en/gallery/npgallery.sgml +++ b/en/gallery/npgallery.sgml @@ -1,20 +1,19 @@ - + %includes; ]> - &header;

All over the world, FreeBSD is powering innovative Internet applications and services. This gallery is a showcase of non-profit organizations who have put FreeBSD to work for them. Browse and find out more about what FreeBSD can do for you!

    &npgallery;

Gallery Home &footer; diff --git a/en/gallery/pgallery.sgml b/en/gallery/pgallery.sgml index 6f25f58d1d..bb11ae4e40 100644 --- a/en/gallery/pgallery.sgml +++ b/en/gallery/pgallery.sgml @@ -1,20 +1,19 @@ - + %includes; ]> - &header;

All over the world, FreeBSD is powering innovative Internet applications and services. This gallery is a showcase of personal sites who have put FreeBSD to work for them. Browse and find out more about what FreeBSD can do for you!

    &pgallery;

Gallery Home &footer; diff --git a/en/internal/about.sgml b/en/internal/about.sgml index f496f08893..bd4acb6e68 100644 --- a/en/internal/about.sgml +++ b/en/internal/about.sgml @@ -1,91 +1,90 @@ - + %includes; ]> - &header;

The Machine

The machine www.FreeBSD.org, otherwise known as freefall.FreeBSD.org, is 800MHz Pentium III set up with 1024 megabytes of RAM and about 50 gigabytes of disk space. The mail duties for the domain are handled by hub.FreeBSD.org, a 400 MHz Pentium II with 256 megabytes RAM and about 16 gigabytes disk space.

Naturally, these systems all run FreeBSD. The hardware and network connection have been generously provided by BSDi, Yahoo!, and other contributors to the FreeBSD project.

A complete list of all host names in the FreeBSD.org domain is available at the The FreeBSD.org Network page.

The Software

These pages are served up by the versatile and efficient Apache http server. In addition, there are a few locally crafted CGI scripts. Indexing of these pages and the mailing list archive are provided by freewais-sf, a derivative of the CNIDR freewais.

The Urchin web statistics package is used to provide these statistics on web server usage.

The Pages

These Web pages have been put together by John Fieber <jfieber@FreeBSD.org> with input from the FreeBSD community and you. The Webmaster is <wosch@FreeBSD.org>. The FreeBSD pages are HTML 3.2 compliant and best viewed with your browser.

See also the FreeBSD Documentation Project

Page Design

Original page design by Megan McCormack

Building and updating the FreeBSD Web Pages

&webbuild;

Update of the FreeBSD Web Pages

The FreeBSD Web Pages are updated daily at 0800 and 2000 UTC.

Mirroring the FreeBSD Web Pages

You can (and are encouraged to) mirror the FreeBSD web pages on www.FreeBSD.org.

Usage statistics for this server are updated daily.

FreeBSD Internal Home &footer; diff --git a/en/internal/developer.sgml b/en/internal/developer.sgml index f11464dd6f..7c804c5dd9 100644 --- a/en/internal/developer.sgml +++ b/en/internal/developer.sgml @@ -1,59 +1,58 @@ - + %includes; ]> - &header;

Committers Guide

Almost everything a new committer to the FreeBSD Project needs to know (see the Ports Guide and FDP Primer for more info).

Build the FreeBSD Web Pages

&webbuild;

FreeBSD Documentation Project Primer for New Contributors

This primer covers everything you will need to know in order to start contributing to the FreeBSD Documentation Project, from the tools and software you will be using (both mandatory and recommended) to the philosophy behind the Documentation Project.

FreeBSD Porter's Handbook

A Guide for FreeBSD Ports Committers

FreeBSD Projects

Other Resources

FreeBSD Internal Home &footer; diff --git a/en/internal/homepage.sgml b/en/internal/homepage.sgml index 92894f2b5a..67d24ab512 100644 --- a/en/internal/homepage.sgml +++ b/en/internal/homepage.sgml @@ -1,20 +1,19 @@ - + %includes; ]> - &header;
    &homepage;

FreeBSD Internal Home &footer; diff --git a/en/internal/internal.sgml b/en/internal/internal.sgml index 97e60663ac..b0bcbff246 100644 --- a/en/internal/internal.sgml +++ b/en/internal/internal.sgml @@ -1,61 +1,60 @@ - + %includes; ]> - &header;

The FreeBSD.org Network

This page documents, for those with accounts on the FreeBSD.org network, just what machine resources are currently available and the sorts of jobs they are being provided for.

Resources for FreeBSD Committers

This page documents resources for FreeBSD committers.

About the FreeBSD WWW Server

The Machine, the software, mirroring the FreeBSD Web Pages, Usage statistics.

FreeBSD Project Staff

The FreeBSD Project is managed and operated by the following groups of people: FreeBSD Core Team, FreeBSD Developers; who is responsible for what.

Photos from Social Events

Personal Homepages

A list of private home pages hosted on people.FreeBSD.org.

FreeBSD 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.

Contacting FreeBSD

FreeBSD Copyright

The FreeBSD Copyrights.

Search the FreeBSD Site

FreeBSD Search Services.

FreeBSD Statistics

Web statistic, FTP traffic, Release usage.

&footer; diff --git a/en/internal/machines.sgml b/en/internal/machines.sgml index 6cf16f4ef0..18659aa43d 100644 --- a/en/internal/machines.sgml +++ b/en/internal/machines.sgml @@ -1,219 +1,218 @@ - + %includes; ]> - &header;

This page documents, for those with accounts on the FreeBSD.org network, just what machine resources are currently available and the sorts of jobs they are being provided for.

For a list of SSH host keys and their fingerprints for the public FreeBSD.org machines, please see this file.

All host names in the FreeBSD.org domain

Host OS Purpose Owner(s)
builder 5.0-current Build server for -current packages ports team
beast 5.0-current Alpha box for FreeBSD/alpha testing jkh
bento 4-stable Package build master ports team
eatmorepie OS X PPC for OS X/Darwin testing jkh
freefall 4-stable CVS master repository committers
gohan10-17 3-stable/4-stable/5-current Ports building cluster ports team
hub 4-stable Mail & WWW services post/webmaster
mx1 4-stable Mail services postmaster
ref4 4-stable Reference machine for testing 4-stable changes committers
ref5 5-current Reference machine for testing 5-current changes committers

Hardware configurations

Host Type Hardware
builder Intel x86 400MHz Pentium II, 256MB mem, NCR 53c875, 9GB IBM SCSI drive, Winbond 100bTX NIC.
beast Aspen Durango 500MHz Alpha 21164A on DEC PCI64 MB, 128MB mem, NCR 53c875 SCSI controller, 2x4GB SCSI WIDE drives (one NetBSD/alpha, one FreeBSD/alpha), DEC 21140 NIC.
eatmorepie Power Macintosh G4 500MHz PowerPC G4, 256MB mem, 30GB IDE drive
bento Intel x86 MP 2x733MHz Pentium III, 1024MB mem, 2xLSI53C1010, 1x18GB SCSI U160 drive, 5x36GB SCSI U160 drives. Intel EtherExpress Pro 10/100B NIC.
freefall Intel x86 800MHz Pentium III, 1024MB mem, Mylex DAC960 PCI SCSI RAID controller, 5x18GB SCSI U2W drives, Intel EtherExpress Pro 10/100B NIC.
gohan10-17 Intel x86 800MHz Pentium III, 512MB mem, Intel ICH ATA66 controller, 1x30GB ATA66 drive, Intel EtherExpress Pro 10/100B NIC.
hub Intel x86 400MHz Pentium II, 256MB mem, Mylex DAC960 PCI SCSI RAID controller, 3x9GB SCSI WIDE drives, Intel EtherExpress Pro 10/100B NIC.
mx1 Intel x86 800MHz Pentium III, 512MB mem, Intel ICH ATA66 controller, 1x30GB ATA66 drive, Intel EtherExpress Pro 10/100B NIC.
ref4 Intel x86 400MHz Pentium II, 128MB mem, 1x20GB IDE drive, Intel EtherExpress Pro 10/100B NIC.
ref5 Intel x86 400MHz Pentium II, 128MB mem, 1x20GB IDE drive, Intel EtherExpress Pro 10/100B NIC.

All machines, as a general rule, are connected at 100Mbits to the FreeBSD network (a 100Mbit network switch) unless some other reason requires that they communicate at 10Mbits.

Administrative Policies

If the machine in question is "owned" by someone specific, please direct queries to them first when asking about administrative issues, this includes changes to user accounts or filesystem layout.

All new user accounts must be cleared with the admin staff, admin@FreeBSD.org, and are given only to FreeBSD developers, either in the docs, ports or general src hacking category. Accounts may be given to non-project developers if they have a specific need to test something of a truly experimental nature and need access to a FreeBSD machine for the purpose. Accounts are not given to the general public for "vanity domain" mail or other such uses, so please don't ask. Thanks.

Jordan Hubbard
jkh@FreeBSD.org

FreeBSD Internal Home &footer; diff --git a/en/internal/mirror.sgml b/en/internal/mirror.sgml index 340fcbafef..0f6c3e5716 100644 --- a/en/internal/mirror.sgml +++ b/en/internal/mirror.sgml @@ -1,62 +1,61 @@ - + %includes; ]> - &header;

You can (and are encouraged to) mirror the FreeBSD web pages www.FreeBSD.org. To do this, you need to obtain and install a program called cvsup on your web server. CVSup is a software package for distributing and updating collections of files across a network.

Installing CVSup

To build and install it, do the following:

  # cd /usr/ports/net/cvsup-bin
  # make all install clean
 

Running CVSup

If you keep your mirrored FreeBSD web pages in the directory /usr/FreeBSD-mirror and are owned by the user `fred', then run the following command as user `fred':

      $ cvsup supfile-www
 
The file supfile-www contain:
        *default host=cvsup.FreeBSD.org
        *default prefix=/usr/FreeBSD-mirror
        *default base=/usr/local/etc/cvsup
        www release=current delete use-rel-suffix compress
 

This will mirror the FreeBSD web pages into /usr/FreeBSD-mirror. You can install this into fred's crontab, so that it runs once a day. The pages on www.FreeBSD.org are updated daily at about 4:30am California time.

More Information on CVSup

See the CVSup introduction in the handbook.

FreeBSD Internal Home &footer; diff --git a/en/internal/photos.sgml b/en/internal/photos.sgml index f5d141b66e..1f6dabee44 100644 --- a/en/internal/photos.sgml +++ b/en/internal/photos.sgml @@ -1,86 +1,85 @@ - + %includes; ]> - &header;

BSDCon 2000, Monterey, October 2000

Photos by Will

LinuxWorld 2000, February 2000

Photos by jkh.

BSD Social Event Berlin, October 1999

Oxford (UK) FreeBSD meeting, November 1998

Photos and text by Nik. Organised by Paul Richards.

Dutch FreeBSD meeting, October 1998

Photos by Jordan and Wilko

BSD Social Event Hamburg, June 1998

Aled Morris, Andre Oppermann, Andreas Klemm, Andrew Gordon, Christoph Badura, Dirk Meyer, Frank Nobis, Harald Klatte, Joerg Wunsch, Jonathan Laventhol, Lars Gerhard Kuehl, Martin Cracauer, Stefan Bethke, Stefan Esser, Stefan Huerter, Stefan Zehl, Stephan Forth, Thomas Gellekum

AUUG Spring conference, Sydney, September 1998

Richard Stallman, Peter Wemm, Mark White, Andrew McRae, Greg Rose, many unidentified.

Summer 1998 USENIX, New Orleans

Branson, David Greenman, David O'Brien, Greg Lehey, Guido van Rooij, John Polstra, Jonathan Bresler, Jordan Hubbard, Justin Gibbs, Luigi Rizzo, Mark Murray, Mike Smith, Monique van Rooij, Ollivier Robert, Philippe Regnauld, Poul-Henning Kamp, Sharon, Steve Mann

FreeBSD Social Event Aachen, 1995

Aled Morris, Christoph Kukulies, Guido van Rooij, Jonathan Leventhol, Jörg Wunsch, Martin Welk, Michael Reifenberger, Patrick Hausen, Paul Richard, Paul Richards, Poul-Henning Kamp, René de Vries, Stefan Esser, Ulf Kieber, Wilko Bulte

FreeBSD People

Aled Morris, Andrey Chernov, Christoph Kukulies, Gary Jennejohn, Gary Palmer, Guido Van Rooij, Guy Helmer, Hellmuth Michaelis, James Robinson, Joerg Wunsch, John Fieber, Jon Loeliger, Jonathan Leventhol, Jordan Hubbard, Julian Stacey, Mark Murray, Martin Welk, Michael Reifenberger, Mike Smith, Ollivier Robert, Patrick Hausen, Paul Richards, Paul Traina, Poul-Henning Kamp, Rene de Vries, Stefan Esser, Thomas Gellekum, Timo Rinne, Ulf Kieber, Wilko Bulte, Wolfram Schneider

FreeBSD Internal Home &footer; diff --git a/en/internal/statistic.sgml b/en/internal/statistic.sgml index 872aadda4e..07cc617d45 100644 --- a/en/internal/statistic.sgml +++ b/en/internal/statistic.sgml @@ -1,67 +1,66 @@ - + %includes; ]> - &header;

Web Statistic

Analog

The Web usage statistics for this server are updated daily with the analog(1) tool.

Urchin

Urchin Logo

The Urchin web statistics package is used to provide these statistics on web server usage.

FreeBSD Release Usage Statistic

A snapshot of the current FreeBSD release usage is available at http://www.FreeBSD.org/statistic/release_usage/images/.

The FreeBSD Counter Page

The FreeBSD Counter Page page is the start of a project which will attempt to determine the world-wide installed base of FreeBSD users. The FreeBSD development community currently has only the vaguest idea as to how large our user base is, and this makes it all the more difficult to persuade hardware and software vendors to take it seriously.

FTP traffic at ftp.FreeBSD.org

We set a new traffic record for TerraSolutions and Lightning Internet Services at 29-Sep-2000, over 2TB.
Previous record was set for wcarchive at 23-May-1999, 1.39TB.

FreeBSD Internal Home &footer; diff --git a/en/internet.sgml b/en/internet.sgml index 1206f6aa32..c248be5b71 100644 --- a/en/internet.sgml +++ b/en/internet.sgml @@ -1,160 +1,159 @@ + %includes; ]> - &header;

FreeBSD was designed for the Internet

FreeBSD includes what many consider the reference implementation for TCP/IP software, the 4.4 BSD TCP/IP protocol stack, thereby making it ideal for network applications and the Internet.


FreeBSD supports standard TCP/IP protocols.

Like most UNIX systems, the FreeBSD operating system enables you to

  • Share filesystems with NFS
  • Distribute network information with NIS
  • Support remote logins
  • Do remote SNMP configuration and management
  • Serve files with FTP
  • Resolve Internet hostnames with DNS/BIND
  • Route packets between multiple interfaces, including PPP and SLIP lines
  • Use IP Multicast services (the MBONE)

FreeBSD lets you to turn a PC into a World Wide Web server or Usenet news relay with included software. Using the included SAMBA software you can even share filesystems or printers with your Win95 and NT machines and, with the supplied PCNFS authentication daemon, you can support machines running PC/NFS. FreeBSD also supports Appletalk and Novell client/server networking (using an optional commercial package), making it a true "Intranet" networking solution.

FreeBSD also handles TCP extensions like the RFC-1323 high performance extension and RFC-1644 extension for transactions, plus SLIP and dial-on-demand PPP. It is an operating system suitable for a home-based net surfer as well as a corporate systems administrator.


FreeBSD's networking is stable and fast.

If you need an Internet server platform that is reliable and offers the best performance under heavy load, then consider FreeBSD. Here are just a few of the companies that make use of FreeBSD every day:

  • BSDi's Open Source Division outside of San Francisco runs one of the most popular FTP servers on the net - ftp.freesoftware.com. It is a FreeBSD machine supporting 5000 connections, and is capable of transferring more than 30 terabytes (as of June, 1999; yes that is terabytes!) worth of files every month to more than 10 million people. The configuration details are available to those interested in building similar systems.
  • Yahoo Inc. runs the ultimate index of the Internet, serving scads of daily net surfers with information about the World Wide Web. Yahoo, as well the companies that advertise on Yahoo, rely on FreeBSD to run reliable and responsive web servers.
  • If that is not enough, visit our Gallery of satisfied FreeBSD users.

FreeBSD makes an ideal platform for these and other Internet services:

  • Company-wide or world-wide WWW service
  • Proxy WWW service
  • Anonymous FTP service
  • Enterprise file and print services

The FreeBSD ports collection contains ready-to-run software that makes it easy to set up your own Internet server.


High performance and security.

The FreeBSD developers are as concerned about security as they are about performance. FreeBSD includes kernel support for IP firewalling, as well other services, such as IP proxy gateways. If you put your corporate servers on the Internet, any 386 PC (or better) running FreeBSD can act as a network firewall to protect them from outside attack.

Encryption software, secure shells, Kerberos, end-to-end encryption and secure RPC facilities are also available (subject to export restrictions).

Furthermore, the FreeBSD team is proactive in detecting and disseminating security information and bug reports with a security officer and ties to the Computer Emergency Response Team (CERT).

What experts have to say . . .

``FreeBSD ... provides what is probably the most robust and capable TCP/IP stack in existence ...''

---Michael O'Brien, SunExpert August 1996 volume 7 number 8.

&footer; diff --git a/en/mailto.sgml b/en/mailto.sgml index aa9a041a5f..46094deeb7 100644 --- a/en/mailto.sgml +++ b/en/mailto.sgml @@ -1,53 +1,52 @@ + %includes; ]> - &header;

Questions about FreeBSD...

Questions regarding FreeBSD should be addressed to the FreeBSD Questions mailing list, freebsd-questions@FreeBSD.ORG.

Mailing lists are the primary support channel for FreeBSD users, with numerous mailing lists covering different topic areas. Several non-English mailing lists are also available.

Questions about the contents of this WWW server...

Questions or suggestions about our documentation (Handbook, FAQ, Tutorials) should be addressed to the FreeBSD Documentation Project mailing list, freebsd-doc@FreeBSD.ORG.

Snail mail, phone and fax

For CDROM orders: The FreeBSD Mall

For commercial support: The FreeBSD Mall

Who Is Responsible for What

Public Relations & Corporate Liaison, Security Officer, Postmaster, Webmaster etc.

&footer; diff --git a/en/news/1996/index.sgml b/en/news/1996/index.sgml index 0a80c4f651..05ac618641 100644 --- a/en/news/1996/index.sgml +++ b/en/news/1996/index.sgml @@ -1,55 +1,54 @@ - + %includes; News Home'> %newsincludes; ]> - &header;

December 1996

  • 24-Dec-1996 FreeBSD 2.2-BETA has been released. Please see the Release Notes for more information.

  • 13-Dec-1996 FreeBSD 2.2-RELEASE will not support installation on machines with less than 5MB of RAM or 1.2MB floppy drives. Please see the original announcement for more information.

November 1996

  • 15-Nov-1996 FreeBSD 2.1.6-RELEASE is out. Please see the release notes for more information.

  • 4-Nov-1996 The FreeBSD CVS development tree has branched again. See here for more information.

&newshome; &footer; diff --git a/en/news/1997/index.sgml b/en/news/1997/index.sgml index 48f52c9eee..02273fba90 100644 --- a/en/news/1997/index.sgml +++ b/en/news/1997/index.sgml @@ -1,273 +1,272 @@ - + %includes; News Home'> %newsincludes; ]> - &header;

December 1997

  • 26-Dec-97 A convenient front-end tool for installing and configuring the CVSup utility is now available. To use it, simply login or su to root and run: pkg_add &ftp;/development/CVSup/cvsupit.tgz

  • 2-Dec-97 The "FOOF" bug has now been fixed in our 3.0-current and 2.2-stable branches and can either be incorporated by using the CVSup utility, as described below for the LAND attack fix, or by applying these patches.

  • 1-Dec-97 The "LAND attack" bug in TCP/IP has now been fixed in all relevant branches and can be incorporated by using the CVSup utility to track the latest 2.2 or 3.0 sources.

  • 1-Dec-97 Team FreeBSD is a group of FreeBSD users and supporters contributing CPU idle time in an effort to crack RSA's 64-bit encryption code. For more information, visit Team FreeBSD's WWW site.

November 1997

  • 21-Nov-97 Pentium bug -- We are aware of the "F00F" Pentium halting bug and are working with Intel on a fix. When we have a fix ready for public consumption it will be announced here, on the mailing list announce@FreeBSD.org and to the Usenet newsgroup comp.unix.bsd.freebsd.announce. Your patience is appreciated.

  • 09-Nov-97 FreeBSD 2.2.5-RELEASE CDROMS are now in stock and shipping to customers worldwide. More information is available at http://www.wccdrom.com/titles/os/fbsd25.htm.

October 1997

  • 22-Oct-97 FreeBSD 2.2.5 has been released. See the Release Information page for details. Also be sure to check the release errata after installation for any late-breaking issues with 2.2.5 that you should know about.

September 1997

  • 01-Sep-97 FreeBSD performed well in an Internet Week review of WWW server platforms.

August 1997

  • 11-Aug-97 Researchers in Duke University's Trapeze Project have developed a high-speed Myrinet driver for FreeBSD. More information about the driver, Trapeze Project, and its parent project, the Collaborative Cluster Computing Iniative, including the code for the Myrinet driver, are available from the CCCI's WWW page.

  • 03-Aug-97 Netscape Communications has released a beta version of Netscape Communicator v4.0 for FreeBSD. It can be obtained via FTP from ftp.netscape.com or its mirrors.

July 1997

June 1997

  • 17-Jun-97 FreeBSD 2.2.2-RELEASE CD-ROM discs are now in stock; subscription customers should receive them shortly.

May 1997

April 1997

March 1997

February 1997

  • 20-Feb-1997 FreeBSD 2.1.7-RELEASE is now available. Read the README.TXT file or the Release Notes for more information.

  • 10-Feb-1997 FreeBSD 3.0-970209-SNAP has been released. Read the README.TXT file for more information about this release.

  • 06-Feb-1997 A serious security problem affecting FreeBSD 2.1.6 and earlier systems was found. The problem has been corrected within the -stable, -current, and RELENG_2_2 source trees. As an additional precaution, FreeBSD 2.1.6 is no longer available from the FTP distribution sites. You can read more about the problem and solution from the FreeBSD-SA-97:01.setlocale security announcement.

  • 06-Feb-1997 The final pre-release version of FreeBSD 2.2-GAMMA, is now available. The README.TXT file has more information.

  • 02-Feb-1997 A snap-of-the-day server has been set up for the most current snapshot release of FreeBSD 2.2. Read the README.TXT file for more information.

January 1997

&newshome; &footer; diff --git a/en/news/1998/index.sgml b/en/news/1998/index.sgml index 0c1b1b819b..921e23c642 100644 --- a/en/news/1998/index.sgml +++ b/en/news/1998/index.sgml @@ -1,243 +1,242 @@ - + %includes; News Home'> %newsincludes; ]> - &header;

December 1998

  • 28-Dec-98 Unless circumstances dictate otherwise, FreeBSD 3.0 will depart the -CURRENT branch late in the day on 15 January 1999. The 3.1 release will follow 30 days later, on 15 February 1999. Developers should consider this as ADVANCE NOTICE of these events.

  • 13-Dec-98 Walnut Creek CDROM has opened the FreeBSD Mall, a site devoted to the commercial aspects of FreeBSD, including add-ons, hardware, and commercial tech-support. To advertise or sell your products or services at the FreeBSD Mall, contact BSDi.

November 1998

  • 30-Nov-98 FreeBSD 2.2.8 has been released. Please see the Release Information page for more details. Also be sure to check the release errata after installation for any late-breaking issues with 2.2.8 that you might need to be aware of.

  • 26-Nov-98 FreeBSD Rocks is an initiative designed to provide the FreeBSD community with the latest FreeBSD news, software and resources. All areas include search facilities, making keyword searching of historical posts a breeze. The pages are updated daily and everyone is invited to sign up an post an article. If it happened today, you'll see it on FreeBSDRocks.

October 1998

  • 15-Oct-98 FreeBSD 3.0 has been released. See the Release Information page for details. Also be sure to check the release errata after installation for any late-breaking issues with 3.0 that you might need to be aware of.

September 1998

  • 15-Sep-98 September 15th is the scheduled date for entering BETA with the 3.0-CURRENT tree. As all of you already (should) know, 3.0 is scheduled for release on October 15th so this gives us a nice 30 day BETA period. During this time, I don't expect anyone to drop in significant new work or otherwise perturb the 3.0-CURRENT tree in such a way that violates the general idea of a BETA (you're supposed to test what you have, not move the goalposts every couple of days :).

  • 13-Sep-98 After more than a year of development, the Common Access Method SCSI layer for FreeBSD will be integrated into 3.0-CURRENT on Sunday, September 13th. The CAM development team is currently busy ensuring that the integration process goes as smoothly as possible, so please understand that we may be slow to respond to questions about CAM during that time.

  • 09-Sep-98 Perl5 is now imported into the 3.0-CURRENT source tree.

  • 05-Sep-98 The BSD CD Giveaway List. If somebody has a CD to give away (recipient pays for shipping) or to lend locally, they can put their email address on the list. Hardware and literature can also be given away. We encourage people to donate CDs to local libraries and put them on the list as well.

  • 01-Sep-98 First issue of Daemon News arrives day earlier. This ezine is by the BSD community for the BSD community. See http://www.daemonnews.org/

August 1998

  • 31-Aug-98 FreeBSD -CURRENT branch (the future 3.0-RELEASE) has switched to ELF from a.out format. People involved did a great job; transition went smooth. Check the freebsd-current@FreeBSD.org mail archive for more information on the transition to ELF.

  • 23-Aug-98 Suidcontrol-0.1 utility has been released. The suidcontrol is an experimental utility for managing suid/sgid policy under FreeBSD. You can get more information at http://www.watson.org/fbsd-hardening/suidcontrol.html

  • 09-Aug-98 FreeBSD Security How-To has been published. This work is currently in beta and can be found at http://www.best.com/~jkb/howto.txt

July 1998

May 1998

  • 30-May-98 FreeBSD and Apache are used in this very useful article on implementing a web farm using round-robin DNS in WEBTechniques.com.

  • 23-May-98 The second issue of the FreeBSD Newsletter is now available in Adobe PDF format (also by FTP). A help file is available to assist you in selecting and using a PDF viewer. Article submissions, advertisements, and letters to the editor should be sent to newsletter@FreeBSD.org.

  • 01-May-98 The FreeBSD Project set up Anonymous CVS for the FreeBSD CVS tree. Among other things, it allows users of FreeBSD to perform, with no special privileges, read-only CVS operations against one of the FreeBSD project's official anoncvs servers.

April 1998

  • 16-Apr-98 The new 4 CD set of FreeBSD 2.2.6 is now in stock and should start shipping to subscription and back-order customers tomorrow. More information on the CD contents are available from http://www.wccdrom.com/.

  • 11-Apr-98 The new FreeBSD project FreeBSD Mozilla Group is created. The FreeBSD Mozilla Group supports and improves the free available Netscape web browser, otherwise known as Mozilla.

March 1998

  • 25-Mar-98 FreeBSD 2.2.6 has been released. See the Release Information page for details. Also be sure to check the release errata after installation for any late-breaking issues with 2.2.6 that you should know about.

February 1998

January 1998

  • 08-Jan-98 Improved support for Plug-n-Play cards has now been integrated into both 3.0-CURRENT and 2.2-STABLE branches now. This is available in source form via the CVSup utility or in binary release snapshots from current.FreeBSD.org

&newshome; &footer; diff --git a/en/news/1999/index.sgml b/en/news/1999/index.sgml index 5689ad2a49..4a98420e7b 100644 --- a/en/news/1999/index.sgml +++ b/en/news/1999/index.sgml @@ -1,371 +1,370 @@ - + %includes; News Home'> %newsincludes; ]> - &header;

December 1999

  • 30-Dec-1999 A new committer: Gerard Roudier (Symbios SCSI driver)

  • 20-Dec-1999 FreeBSD 3.4 has been released. Please see the Release Information page for more details. Also be sure to check the release errata after installation for any late-breaking issues with 3.4 that occur.

  • 18-Dec-1999 A new committer: Robert Watson (Coda, POSIX.1e ACLs/Capabilities/Auditing/MAC, FFS extended attributes, Jail code improvements/documentation, IPFW/BPF cleanup)

  • 16-Dec-1999 Remove a committer: James Raynard, "I have decided to resign as a committer as it's been a very long time since I last had the time to work on FreeBSD and things have now got to the point where not even "speed reading" can help me keep up with the commit mail." Our thanks to James for the time and effort he has contributed to FreeBSD.

    A new committer: Jeroen Ruigrok van der Werven (Docs, in particular mdoc, low-level interfaces, and other source tree related documentation)

  • 15-Dec-1999 A new committer: Chris D. Faulhaber

  • 14-Dec-1999 A new committer: Neil Blakey-Milner (Docs)

October 1999

  • 24-Oct-1999 The FreeBSD Con '99 event this year was a big success! Over 350 people attended, and both the vendors and attendees alike said they found the event to be both entertaining and valuable. Many thanks to Walnut Creek CDROM for producing this event and to Dr. Marshall Kirk McKusick for teaching two kernel internals tutorials and giving his History of BSD talk at the conference.

  • 10-Oct-1999 A new committer: Josef Karthauser

September 1999

August 1999

  • 23-Aug-1999 A new committer: John Baldwin (Docs)

  • 11-Aug-1999 New committers: Alfred Perlstein (SMP) and Jim Mock (Docs)

  • 10-Aug-1999 C-Forge, an Integrated Development Environment, has been released (beta) for FreeBSD, supporting C, C++, Perl, Tcl, and many other languages.

  • 06-Aug-1999 A new committer: Chris Costello (Docs)

  • 04-Aug-1999 A new committer: Peter Holm (Docs)

July 1999

June 1999

May 1999

April 1999

March 1999

February 1999

  • 25-Feb-1999 A new committer: Shigeyuki FUKUSHIMA

  • 23-Feb-1999 A new committer: Alan Cox (VM)

  • 19-Feb-1999 A new committer: Kris Kennaway

  • 17-Feb-1999 The Gartner Group has released a report, Divorcing Thin Server Software from the Hardware, examining the trend in the OEM market of using software and hardware from different vendors.

  • 15-Feb-1999 FreeBSD 3.1 has been released. Please see the Release Information page for more details. Also be sure to check the release errata after installation for any late-breaking issues with 3.1 that you might need to be aware of.

  • 04-Feb-1999 The FreeBSD Diary, a collection of how-to entries aimed at Unix novices, is now available.

  • 03-Feb-1999 A new committer: Daniel Sobral (Bootloader)

January 1999

  • 21-Jan-1999 A new committer: Roger Hardiman (bt8x8 driver)

  • 20-Jan-1999 3.0-STABLE has now departed the -CURRENT branch. The next release on this branch will be 3.1-RELEASE, in mid-February 1999.

  • 15-Jan-1999 A new committer: Andrew Gallatin (Alpha)

  • 13-Jan-1999 The FreeBSD ezine is a monthly collection of easy to read (we hope) articles written by FreeBSD users and administrators just like you.

  • 10-Jan-99 Jordan Hubbard's "State of the Union", a look back at 1998, and a look forward to the future.

  • 02-Jan-1999 A new committer: Hidetoshi Shimokawa (Alpha/Ports)

&newshome; &footer; diff --git a/en/news/2000/index.sgml b/en/news/2000/index.sgml index 4e828caf42..6de076aa52 100644 --- a/en/news/2000/index.sgml +++ b/en/news/2000/index.sgml @@ -1,457 +1,456 @@ - + %includes; News Home'> %newsincludes; ]> - &header;

December 2000

November 2000

  • 30-Nov-2000 Individual porting efforts were moved into the platforms directory. Separate pages for the Alpha, IA-64, PowerPC, and SPARC porting projects can be found there.

  • 22-Nov-2000 FreeBSD 4.2 has been released. Please see the Release Information page for more details. Also be sure to check the release errata after installation for any late-breaking issues with 4.2 that occur.

  • 22-Nov-2000 And yet another new committer: Peter Pentchev (ports)

  • 13-Nov-2000 Yet another new committer: OKAZAKI Tetsurou (ports)

  • 13-Nov-2000 Another new committer: Kazuhiko Kiriyama (ports)

  • 13-Nov-2000 New committer: Dmitry Sivachenko (Mainly ports)

  • 12-Nov-2000 Another new committer: Issei Suzuki (Ports)

  • 06-Nov-2000 Another new committer: Jing-Tang Keith Jang (ports, mostly in the chinese category)

  • 02-Nov-2000 Another new committer: Benno Rice (PowerPC port and OpenFirmware /boot/loader)

October 2000

  • 26-Oct-2000 Yet another new committer: Doug Barton (mergemaster, and whatever other trouble I can get into)

  • 26-Oct-2000 A new committer: Garance A Drosehn (lpr and friends)

  • 18-Oct-2000 New FreeBSD Core Team Elected! Read the official press release for more information.

  • 16-Oct-2000 A new committer: Jonathan Chen (newcard cardbus)

  • 03-Oct-2000 The complete track schedule for BSDCon has been released. BSDCon is the premiere annual technical conference for BSD users and will be held from October 14-20 in Monterey, CA.

  • 02-Oct-2000 Doug Rabson has made a series of commits to -CURRENT with early IA64 support. The kernel will now reach the mountroot prompt. Please follow the ia64 mailing list for more information.

  • 01-Oct-2000 A new committer: Trevor Johnson (sundry ports, mostly in the audio category)

  • 01-Oct-2000 A new committer: James Housley (ports, especially RTEMS. Side interest in IPv6)

  • 01-Oct-2000 A new committer: Mário Sérgio Fujikawa Ferreira

September 2000

August 2000

July 2000

June 2000

  • 30-June-2000 http://freshports.org/ has been upgraded to FreshPorts 1.1. The FreshPorts website contains the latest details of which ports have been create/updated/removed. This upgrade, the first since FreshPorts was release in early May, gives you an improved home page, which together with a commit history means you can find out about your ports faster and easier.

  • 29-June-2000 Tucows has added a BSD section.

  • 26-June-2000 A new committer: Shunsuke Akiyama (Optical disk driver)

  • 24-June-2000 FreeBSD 3.5 has been released. Please see the Release Information page for more details. Also be sure to check the release errata after installation for any late-breaking issues with 3.5 that occur.

  • 20-June-2000 A new committer: MIHIRA Sanpei Yoshiro (PC-Card)

    A new committer: Coleman Kane (3dfx voodoo for glide/Mesa)

  • 19-June-2000 A new committer: CHOI Junho (Ports)

  • 08-June-2000 Jordan Hubbard and Warner Losh will be in Japan during the first part of June 2000. They will be giving talks at: the BSD BOF at Networld+Interop 2000 Tokyo (8th), the JUS seminor at Tokyo (9th), the NBUG event at Nagoya (10th), and, the K*BUG seminor at Osaka (10th). Please see http://www.jp.FreeBSD.org/.

    A new article is available, explaining how to use PPP, natd, and ipfw to implement a firewall with a PPP dialup connection.

    A new committer: Alexander Langer (Ports, Docs)

  • 06-Jun-2000 The first FreeBSD Conspectus has been added, providing a summary of events on the -stable mailing list over the past week.

May 2000

April 2000

  • 16-Apr-2000 New mailing lists available: freebsd-i18n (FreeBSD Internationalization) and freebsd-ppc (Porting FreeBSD to the PowerPC)

  • 04-Apr-2000 A new committer: Murray Stokely (sysinstall)

March 2000

February 2000

  • 26-Feb-2000 A new committer: Hajimu UMEMOTO (IPv6)

  • 23-Feb-2000 A new committer: Paul Saab

  • 22-Feb-2000 32BitsOnline.com has a review of FreeBSD 3.4 by Clifford Smith available on their web site. All in all, a good review.

  • 18-Feb-2000 A new committer: Brian S Dean (Kernel support for IA32 hardware debug registers, misc fixes/feature enhancements in other areas)

  • 17-Feb-2000 A new issue of The FreeBSD 'zine came out on the 15th. This is the first issue of the 'zine in 7 months; lots of changes have been made, and many new features have been added. Be sure to check it out.

  • 10-Feb-2000 Michael Lucas has written an excellent article on the differences between the BSD license and the GPL. This article is definitely worth reading.

    New committers: Greg Sutter and Bill Swingle (Docs)

January 2000

  • 22-Jan-2000 The FreeBSD Diary, a chronicle of what one guy is doing with FreeBSD, has been around for almost two years. Until today, it was tucked away in a corner of his site. Following significant growth, a new-look site was launched today. The site contains a huge number of how-to guides and the readership includes NetBSD, OpenBSD, and Linux users.

  • 13-Jan-2000 A new committer: Wilko Bulte

  • 04-Jan-2000 The Compaq Testdrive program is now making testdrives available of the latest FreeBSD 4.0-20000101-CURRENT release running on an Alpha XP1000 EV6.7. running at 667MHz and loaded with two gigs of ram. To get a free shell account as a participant in the testdrive program, all you need to do is register at the site. These accounts aren't for playing, the goal of the program is to make brand new systems available to developers so they can test, build and port their apps to the world's fastest computer. The testdrive program also offers other systems running FreeBSD, including a Proliant 5500 dual Xeon 450MHz and a DPW500a.

  • 03-Jan-2000 A new committer: Patrick Gardella (JDK/WWW)

  • 02-Jan-2000 A new committer: Ade Lovett (Ports)

  • 01-Jan-2000 A new committer: Jeremy Lea (Ports)

&newshome; &footer; diff --git a/en/news/news.sgml b/en/news/news.sgml index 2b39d19c54..b195390587 100644 --- a/en/news/news.sgml +++ b/en/news/news.sgml @@ -1,89 +1,88 @@ - + %includes; %newsincludes; ]> - &header;

Local news

Other sites

&footer; diff --git a/en/news/press-rel-1.sgml b/en/news/press-rel-1.sgml index 5957626089..cdf0d0b3b6 100644 --- a/en/news/press-rel-1.sgml +++ b/en/news/press-rel-1.sgml @@ -1,60 +1,59 @@ - + %includes; %newsincludes; ]> - &header;

FreeBSD Used to Generate Spectacular Special Effects

Concord, CA, April 22, 1999: 32 Dual-Processor FreeBSD systems were used to generate a large number of special effects in the cutting edge Warner Brothers film, The Matrix.

Manex Visual Effects used 32 Dell Precision 410 Dual P-II/450 Processor systems running FreeBSD as the core CG Render Farm. Charles Henrich, the senior systems administrator at Manex, says, "We came to a point in the production where we realized we just did not have enough computing power on our existing SGI infrastructure to get through the 3-D intensive sequences. It was at that point we decided on going with a FreeBSD based solution, due to the ability to get the hardware quickly as well as the reliability and ease of administration that FreeBSD provides us. Working with Dell, we purchased 32 of these systems on a Wednesday, and had them rendering in production by Saturday afternoon. It was truly an amazing effort on everyone's part, and I don't believe it would've been possible had we chosen to go with any other Operating System solution."

The FreeBSD operating system is a powerful, completely open-source system based on the Berkeley Software Distribution of UNIX. It is available free of charge from numerous Internet websites and also on CD-ROM from Walnut Creek CDROM, and includes thousands of ported applications including 3-D graphics rendering and many other equally powerful tools. FreeBSD is optimized for use on the Intel x86 processor line that is the heart of today's versatile commodity personal computers. Infinitely customizable, FreeBSD is at the heart of such Internet powerhouse applications as Yahoo! and U.S. West because it is unencumbered by commercial license restrictions and can be copied and modified freely.

For more information on FreeBSD, visit http://www.FreeBSD.org/ and http://www.wccdrom.com/. For more information about Manex Visual Effects, please visit http://www.mvfx.com/ .

&footer; diff --git a/en/news/press-rel-2.sgml b/en/news/press-rel-2.sgml index 1ba5e4d773..f9ada6a418 100644 --- a/en/news/press-rel-2.sgml +++ b/en/news/press-rel-2.sgml @@ -1,90 +1,89 @@ - + %includes; %newsincludes; ]> - &header;

Complete XML Development System Integrated with FreeBSD

Concord, CA, April 29, 1999: Included with FreeBSD 3.1 is a complete, integrated SGML/XML development system that installs with a simple, easy to use command sequence.

FreeBSD's Ports system and multitasking architecture makes it easy for an SGML/XML developer to download and install all the latest versions of the tools and reference material he needs to develop SGML and XML formatting languages and documents, and the online Internet mailing lists help him learn and keep up-to-date with the evolving XML implementation.

FreeBSD is a full-featured open-source operating system which runs on virtually all Intel x86-based personal computers. Its 580 page "Handbook" has recently been completely done over into DocBook format, and it is a living example of an evolving document built with SGML tools. The Handbook is available on the Internet at:

The FreeBSD Documentation Project is also making available the "FreeBSD Documentation Project Primer" to make it as painless as possible for newcomers to contribute to the FreeBSD Documentation Set. Much of the information in the primer is appropriate to all SGML/XML users, and is freely available. The primer, which is constantly being updated by the Documentation Project team, can be found at:

Features of the Document Project SGML/XML System include:

  • James Clark's Jade 1.2.1 and SP suite version 1.3.3, enabling formatting and validation of SGML and XML documents.
  • A complete set of 19 ISO SGML character set entities
  • The DocBook (v2.4.1, v3.0, v3.1), HTML (all versions), and LinuxDoc Document Type Definitions (DTD)
  • Norm Walsh's Modular DocBook Stylesheets, allowing fine control over the appearance and formatting of DocBook documents.
  • Emacs and Xemacs, in conjunction with the PSGML extension package, provide a customizable industrial-strength SGML editing solution.
  • The teTeX-beta package in conjunction with the JadeTeX macros make it possible to convert DocBook documents to DVI, Postscript, and PDF formats with embedded hyperlinks.
  • Additional SGML-aware programs and utilities can be found in the FreeBSD ports system.

The FreeBSD Documentation Project is actively migrating from the LinuxDoc DTD to the DocBook DTD, and has been providing feedback to the DocBook maintainers regarding new features and possible implementations for the past year. For more information about the FreeBSD Documentation Project, please contact the freebsd-doc@FreeBSD.org mailing list.

The FreeBSD operating system is available on the Internet from the master FreeBSD website and from various mirror systems around the world, and it can also be obtained on convenient CDROMs from Walnut Creek CDROM. Information on all of these options is available through:

&footer; diff --git a/en/news/press-rel-3.sgml b/en/news/press-rel-3.sgml index cf3d4eed64..50ed0ef7b8 100644 --- a/en/news/press-rel-3.sgml +++ b/en/news/press-rel-3.sgml @@ -1,91 +1,90 @@ - + %includes; %newsincludes; ]> - &header;

BSD Community Welcomes Apple's New Open Source Operating System

Concord, CA, June 7, 1999: Today, at the start of the UNIX development community's annual Usenix convention, operating system influentials embraced Apple Computer's Darwin (www.apple.com/darwin) as a new member of the Berkeley Software Distribution (BSD) operating system family.

"We're very pleased to have Apple's participation in the BSD community," said Jordan Hubbard, chairman of the USENIX convention's Freenix track and co-founder of the FreeBSD Project. "As more smart businesses discover the incredible free resource that is BSD software, they'll realize that contributing to open source development is in their best interest."

According to Herb Peyerl of the NetBSD Project, "Our interaction with Apple on the Darwin project has been extremely rewarding for NetBSD and is the kind of open cooperation of which we would like to see more."

"Leveraging the twenty-year BSD heritage allows Apple developers to concentrate on adding a unique user experience to the solid, robust foundation of the BSD code," according to Avie Tevanian, Apple Computer's senior vice president of Software Engineering. "We believe that by embracing the open source movement with our Darwin software, the result will be better products for millions of Mac customers worldwide. The BSD code in Darwin is an essential part of our operating system strategy."

This type of reciprocation is a return to the original software development model that was universal in the early days of computing, before PCs. Wilfredo Sanchez, technical lead for the Darwin Project, will speak on Darwin at this week's Freenix track, a series of programs at Usenix devoted exclusively to this sort of open source software development.

About NetBSD and FreeBSD

NetBSD and FreeBSD are open source operating systems based on the last public release of BSD UNIX, 4.4BSDLite2. Each effort has kept up with the latest technologies in processors and software architectures. While having different priorities, the BSD development teams share a friendly competitive rivalry, spurring each other on to produce better product for their worldwide users. Over the twenty years of development, a huge base of software has been developed around BSD -- including much of the Internet infrastructure -- enabling the OS to be used effectively in almost any computing application. The open development model means there are no secrets, creating a worldwide understanding of the code which enables BSD developers to build on the efforts of prior developers without the hassles endemic to proprietary operating systems and applications.

For More Information, Contact:

The FreeBSD Project
Concord, California
925-682-7859
freebsd-questions@FreeBSD.org
http://www.FreeBSD.org

The NetBSD Project
C/O Charles M. Hannum
81 Bromfield Rd, #2
Somerville, MA 02144
mindshare@netbsd.org
http://www.netbsd.org

&footer; diff --git a/en/news/press-rel-4.sgml b/en/news/press-rel-4.sgml index b33f6d5bfe..b0cd22b02a 100644 --- a/en/news/press-rel-4.sgml +++ b/en/news/press-rel-4.sgml @@ -1,234 +1,233 @@ - + %includes; %newsincludes; ]> - &header;

FOR IMMEDIATE RELEASE

BSD SUPPLIERS UNITE TO DELIVER THE WORLD'S MOST POPULAR INTERNET OPERATING SYSTEMS

The New BSDI To Deliver Renowned BSD Operating System Technologies And Back The Rapidly Growing FreeBSD Open Source Community

Colorado Springs, Colo., March 9, 2000: Berkeley Software Design, Inc. (BSDI) announced today that it has merged with Walnut Creek CDROM, the distributor of the popular FreeBSD operating system. As a merged company, the new BSDI unites the leading developers and suppliers of the Berkeley Software Distribution operating system BSDI will develop and deliver advanced BSD® Internet operating systems and platforms, while providing the open source FreeBSD Project with technology, backing and expanded support.

BSD operating systems run some of the Internet's most highly trafficked sites and largest service providers, including Yahoo!, Microsoft's Hotmail and UUNET, an MCI WorldCom company. BSD and Linux are today's fastest-growing operating systems, according to Survey.com, the leading eResearch company.

BSD operating system, networking and Internet technologies have achieved widespread acceptance in the Internet infrastructure. Over 100,000 commercial Internet customers run BSD operating systems on more than 2,000,000 BSD-powered servers. It is estimated that nine out of 10 Internet Service Providers (ISPs) and Network Service Providers (NSPs) as well as 15 percent of all Internet sites run BSD systems. BSD operating systems are also embedded in innovative Internet appliances from Intel, IBM, Lucent, F5 Labs, Hitachi and many others.

BSDI also announced that Yahoo! Inc. will take an equity interest in the new company. BSDI will leverage the equity interest to execute on its plan to build a bridge between open source innovation and commercial requirements. The equity position will be used to grow BSDI's presence as a leading provider of the most advanced Internet operating systems for the Internet infrastructure.

BSDI intends to form a united front for the BSD operating systems. The company will deliver, support and enhance both BSD/OS and FreeBSD. BSDI and the FreeBSD Project are jointly evaluating the technology and market requirements for merging parts of the code bases for the two operating systems.

The New BSDI's Leadership

"BSD technologies have evolved from a long history of advanced computing at the core of the Internet," said Dr. Marshall Kirk McKusick, BSDI's chairman of the board. "The new BSDI will further enrich the popular BSD computing platform, which is already widely deployed throughout the world." McKusick was a founding member of the University of California at Berkeley's Computer Systems Research Group (CSRG) and is widely acknowledged as a key early contributor to the open source movement.

To drive the new BSDI's vision, roadmap and continued profitable growth, Gary J. Johnson has been appointed chief executive officer. Johnson is an experienced technology executive who has served in a variety of senior management, sales, marketing and operations capacities with leading Silicon Valley companies including Tandem Computers (Compaq), Convergent Technologies (Unisys) and SCO. Johnson most recently served as president of ClickService Software, a leading provider of e-commerce, customer relationship management (CRM) software.

"Innovation in the operating systems arena relies heavily on work in the open source community," said Johnson. "To date, Linux suppliers, such as Red Hat Software and VA Linux, have captured impressive attention for the open source approach to development. At the core of the Internet, however, BSD technologies are pervasive. The new BSDI will be working closely with the open source community to ensure that advanced BSD Internet operating systems and platforms continue to meet the ever-increasing demands for Internet servers, applications, appliances and other elements vital to the Internet infrastructure."

In addition to his current responsibilities, Mike Karels, BSDI's vice president of engineering and the former chief system architect and principal programmer for the University of California at Berkeley's CSRG, plans to join the architectural team for the FreeBSD Project. Karels, who replaced Sun Microsystems co-founder Bill Joy at the CSRG, is recognized as one of the world's foremost developers of Unix internals and TCP/IP networking software.

"BSD technologies have contributed to Yahoo!'s continued success by offering the reliability and level of service necessary to ensure the availability and scalability we need to keep Yahoo! up and running around the clock regardless of increasing user demand," said David Filo, co-founder and Chief Yahoo, Yahoo! Inc.

BSDI Continues To Deliver BSD/OS And FreeBSD; Expands And Accelerates FreeBSD Open Source Initiatives

The new BSDI will sell and support FreeBSD, BSD/OS, BSDI Internet Super Server and value-added BSD product lines through its worldwide sales channels to Internet infrastructure providers, appliance developers and business users. BSDI will offer commercially supported BSD operating systems and related applications, Internet appliance platforms, technical support and services, open source software development, and consulting services. The company will deliver its BSD Internet and networking technologies on leading microprocessor platforms, including Intel, SPARC, Alpha, PowerPC and StrongARM.

BSDI will continue to develop, enhance and distribute BSD/OS and FreeBSD according to the terms of the business-friendly, unencumbered Berkeley software license, which encourages development for open source software projects, embedded systems, specialized applications, information appliances and other operating system-enabled products.

BSDI will expand and accelerate Walnut Creek CDROM's FreeBSD open source initiatives by sharing BSD/OS technical innovations with the FreeBSD Project and by providing this open source project with operational and technical support, marketing and funding. BSDI will continue to distribute packaged versions of FreeBSD and also plans to develop value-added products based on FreeBSD as well as to provide technical support, consulting services, educational services and training for FreeBSD customers. These steps are expected to promote and invigorate the BSD open source computing movement. The FreeBSD Project develops the popular FreeBSD operating system and aggregates and integrates contributed software from more than 5,000 developers worldwide.

Internet and Open Source Leaders Support The New BSDI

"We are delighted that BSDI is backing the FreeBSD open source community," said Jordan Hubbard, chief evangelist and co-founder of the FreeBSD Project. "The new BSDI has considerable expertise in commercializing, maintaining, distributing and supporting the world's most advanced Internet operating systems. We are excited and greatly looking forward to partnering with BSDI's chief developers, especially Mike Karels and other original members of UC Berkeley's CSRG, to accelerate operating system, networking and Internet innovation."

"Open source operating systems like BSD offer better technology and more choices to the customer," said Eric Raymond, president of the Open Source Initiative. "I expect BSDI to prove yet again that the open source and business communities can really to do great things together, driving the industry forward as dramatically as the Internet."

"Our research shows that BSD and Linux will increase their share of enterprise servers by between 100 percent and 500 percent over the next two years in the fundamental applications that run U.S. business," said Dave Trowbridge, senior analyst at Survey.com. "This new company will help ensure that BSD gets its place in the sun, which its rich heritage and solid technical foundations deserve."

About the Berkeley Software Distribution Operating System

Berkeley Software Distribution operating system technologies were originally developed from 1979 to 1992 by the Computer Systems Research Group (CSRG) at the University of California at Berkeley. Berkeley-derived operating system and networking technologies are at the heart of most modern Unix and Unix-like operating systems. Today, virtually every major Internet infrastructure provider uses BSD operating systems. BSD operating system technologies are used by leading mission-critical network computing environments and are embedded in Internet appliance platforms that require advanced Internet functionality, reliability and security.

About the FreeBSD Project

FreeBSD is a popular open source operating system developed by the FreeBSD Project and its worldwide team, consisting of more than 5,000 developers funneling their work to 185 "committer" developers. It is available free of charge from ftp.FreeBSD.org and also distributed as a shrink-wrap software product through CompUSA, Fry's, Borders, Ingram, FreeBSDmall.com and others. FreeBSD includes thousands of ported applications, including the most popular Web, Internet and E-mail applications. FreeBSD is distributed under the Berkeley Software Distribution license, which means that it can be copied and modified freely. For more information about the FreeBSD Project, visit www.FreeBSD.org.

About Walnut Creek CDROM

Walnut Creek CDROM was founded in 1991 and began publishing Linux software in 1992, and BSD software in 1993. The company has a long history of working closely with the free software community and providing funding, staffing and other resources for open source projects. Walnut Creek CDROM publishes numerous software titles, including FreeBSD and Slackware, the most BSD-like version of Linux.

About Berkeley Software Design, Inc. (BSDI)

Leading BSD developers founded Berkeley Software Design, Inc. in 1991 to commercialize BSD technologies and continue the Berkeley Unix tradition of robust, reliable and extremely secure Internet operating systems for network computing. By merging Berkeley Software Design, Inc. and Walnut Creek CDROM, BSDI becomes the world's leading supplier of advanced Internet operating systems for the Internet infrastructure. Contact BSDI at info@BSDI.com or at www.BSDI.com or call 1-719-593-9445 (toll free: 1-800-800-4273).

# # #

BSD is a registered trademark and BSD/OS and BSDI are trademarks of Berkeley Software Design, Inc. Yahoo! and the Yahoo! logo are registered trademarks of Yahoo! Inc. All trademarks mentioned in this document are the property of their respective owners.

Contact:
Kevin Rose
BSDI
801-553-8166
kgr@bsdi.com

Jordan Hubbard
FreeBSD Project
925-691-2863
jkh@FreeBSD.org

Brigid Fuller
ZNA Communications
831-425-1581
brigid@zna.com

&footer; diff --git a/en/news/press-rel-5.sgml b/en/news/press-rel-5.sgml index f3a1896bcc..7e0db0868c 100644 --- a/en/news/press-rel-5.sgml +++ b/en/news/press-rel-5.sgml @@ -1,136 +1,135 @@ - + %includes; %newsincludes; ]> - &header;

New FreeBSD Core Team Elected

BSD Conference, Monterey, CA, October 18, 2000 The FreeBSD Project announced today the election of a new Core Team, the project's management board. This marks the first occasion on which the team has been selected by means of an election among the project's developers. Joining the Core team as new members are Greg Lehey, Warner Losh, Mike Smith, and Robert Watson. Re-elected members are Satoshi Asami, David Greenman, Jordan Hubbard, Doug Rabson, and Peter Wemm.

FreeBSD Project co-founder and continuing Core Team member Jordan Hubbard expressed excitement over the results, "For the first time since the FreeBSD project was formed, open elections have determined the composition of its core team and set an important precedent whereby any developer can now become part of the project's leadership." The new core team also well-represents FreeBSD's diverse and highly skilled group of international developers, with expertise ranging from RAID file system and device-driver development to extensive security backgrounds.

New Core Team members were elected from and by the FreeBSD committers team, the formal development staff of the FreeBSD project. Committers have direct access to the FreeBSD source repository, and perform the majority of software development associated with the project. Until this point, the Core Team was a self-selected board providing architectural and administrative direction.

This summer, the committers voted to move to a democratic model allowing the project to adapt to the changing development requirements of the open source operating system community. However, with over half of the prior Core Team re-elected from the old team, strong continuity exists.

Departing Core Team member Poul-Henning Kamp said, "I'm very proud of what we have done together in the Core Team over the last 8 years. The new Core, and the fact that they are elected by the committers, means that the project will be much more responsive to change in the future."

The changing of the guard in project leadership comes amid good feelings, Kamp indicated: all past Core members will continue on with the project with increased emphasis on development, "Now I get to spend more time on the FreeBSD source code instead of on project management."

Elected Core Team Members

Satoshi Asami is a co-founder and CTO of DecorMagic, Inc., and manages the FreeBSD Ports Collection.

David Greenman is a co-founder of the FreeBSD Project and is currently President of TeraSolutions, Inc., a company that manufactures Internet servers and RAID storage systems.

Jordan Hubbard is a co-founder of the FreeBSD Project as well as its public relations officer and release engineer. He is also Vice President for Open Source Solutions at BSDi.

Greg Lehey is an Open Source Researcher with Linuxcare; he has spent most of his professional career in Germany, where he worked for computer manufacturers such as Univac, Tandem, and Siemens-Nixdorf. He is the author of the Vinum volume management and RAID software for FreeBSD, has been involved in the FreeBSD SMPng project, and is the author of Porting Unix Software and The Complete FreeBSD.

Warner Losh has been porting NetBSD's pccard code to FreeBSD and has been FreeBSD Security Officer for the past two years.

Doug Rabson is a co-founder of Qube Software Ltd., which specializes in 3D graphics technology. His work on FreeBSD includes the alpha and ia64 ports, and he was the main architect for FreeBSD's device driver framework.

Mike Smith is Principal Engineer in BSDi's Open Source Solutions group and has been active in the FreeBSD developer community as a developer resource, OEM liaison, sometime architect and device driver author.

Robert Watson is a research scientist at NAI Labs, working on network and operating system security research. His contributions to the FreeBSD Project include work on trusted operating system extensions (TrustedBSD), security architecture, and work on the security-officer team.

Peter Wemm has been involved with FreeBSD since the early days of the ISP Industry in Australia and has since relocated to the US to work as a Software Engineer for Yahoo!, Inc. His involvement in FreeBSD includes management of the FreeBSD source code repository and kernel development.

About FreeBSD

FreeBSD is a liberally-licensed open source operating system with its origins in BSD Net/2 and 4.4 Lite, the Berkeley Software Distributions developed at the University of California at Berkeley until 1994. It is developed and maintained by a global organization of paid and volunteer contributors. FreeBSD is distinguished by its high performance networking and file system support, and is widely used among Internet service providers, including industry-recognized companies such as Yahoo!, above.net, and Verio. FreeBSD is also frequently used as a platform for embedded networking devices, including products from IBM, Inktomi, Juniper Networks, and Network Alchemy - a Nokia Company.

More information may be found at http://www.FreeBSD.org/.

Press Contact

Jordan Hubbard
The FreeBSD Project
925-682-7859
jkh@FreeBSD.org

# # #

BSD is a registered trademark of Berkeley Software Design, Inc. Other trademarks are property of their respective owners. BSD technologies were originally developed by the University of California, Berkeley and its contributors.

&footer; diff --git a/en/news/press.sgml b/en/news/press.sgml index f7e53534c7..233866e0cf 100644 --- a/en/news/press.sgml +++ b/en/news/press.sgml @@ -1,1541 +1,1540 @@ - + %includes; %newsincludes; ]> - &header;

If you miss an entry please send the URL to www@FreeBSD.ORG

You also can visit FreeBSD/Java Press page for information about FreeBSD Java Project's Press News

July 2001

June 2001

February 2001

  • Byte 05 February 2001
    For Servers: Linux 2.4 vs. FreeBSD 4.1.1
    by Moshe Bar
    BYTE's Linux guru finds himself wondering why he isn't running FreeBSD --- a comparision (with informal benchmarks) of FreeBSD 4.1.1 and a Linux based distribution running the v2.4.0 Linux kernel.

January 2001

December 2000

November 2000

October 2000

September 2000

August 2000

July 2000

June 2000

May 2000

April 2000

March 2000

February 2000

January 2000

December 1999

November 1999

October 1999

September 1999

August 1999

July 1999

June 1999

May 1999

April 1999

March 1999

February 1999

  • Linux Weekly News February 1999
    LWN interviews Alan Cox
    There is a small but interesting FreeBSD mention in LWN in an interview with Linux's Alan Cox.

  • The Economist 20 February 1999
    Hackers rule
    Software that has been developed by thousands of volunteers and is given away is often better than the stuff for sale.
    Note: The article is no longer available online without registration.

January 1999

  • O'Reilly and Associates January 1999
    Twenty Years of Berkeley Unix
    From AT&T-Owned to Freely Re-distributable
    by Marshall Kirk McKusick
    A short history of Berkeley Unix.

  • LINUX JOURNAL January 1999
    WWWsmith: Installation and Configuration of FreeBSD
    by Sean Eric Fagan
    Here is how to set up a web server using another freely available operating system, FreeBSD, a high performance, mature, Unix-like system.

  • SunWorld January 1999
    The return of BSD - What are the BSD flavors and why might you use them?
    by Greg Lehey
    Introduces the modern BSD OSes to the general public.

  • GartnerGroup 18 January 1999
    Divorcing Thin Server Software from the Hardware
    by J. Staten
    While finished thin servers should be optimized in both hardware and software for the task at hand, who says the software and hardware must come from the same developer? This Perspective examines the emerging trend in the OEM market of divorcing the software layer from the hardware layer. Many operating systems are vying to be the OS of choice for thin servers. This document examines this issue in detail, particularly the differences between Linux and FreeBSD, the current de facto leaders in the market.
    Note: The article is no longer available online without registration.

  • Nature 7 January 1999
    Nature Web Matters: Internet tomography
    by K.C. Claffy, Tracie Monk & Daniel McRobb, UCSD/CAIDA, USA.
    The article describes a network management tool built on FreeBSD that has even used network connections to www.FreeBSD.org for performing network research.

December 1998

  • LinuxWorld December 1998
    The story on FreeBSD
    by Cameron Laird and Kathryn Soraiz
    This issue has a good article on FreeBSD and why it's worth a look by Linux folks.

November 1998

October 1998

September 1998

August 1998

July 1998

June 1998

May 1998

April 1998

March 1998

February 1998

August 1997

June 1997

May 1997

November 1996

&newshome; &footer; diff --git a/en/news/pressreleases.sgml b/en/news/pressreleases.sgml index 5feed49c04..ce8f588cf6 100644 --- a/en/news/pressreleases.sgml +++ b/en/news/pressreleases.sgml @@ -1,61 +1,60 @@ - + %includes; %newsincludes; ]> - &header;
October 18, 2000 : New Core
First FreeBSD Core Team Elections

March 9, 2000
BSD Suppliers Unite to Deliver the World's Most Popular Internet Operating Systems

June 7, 1999
BSD Community Welcomes Apple's New Open Source Operating System.

April 29, 1999
Complete XML Development System Integrated with FreeBSD.

April 22, 1999: The Matrix
FreeBSD Used to Generate Spectacular Special Effects for the Warner Brothers film The Matrix.

&footer; diff --git a/en/news/sou1999.sgml b/en/news/sou1999.sgml index c1df875ce7..4c2c83f579 100644 --- a/en/news/sou1999.sgml +++ b/en/news/sou1999.sgml @@ -1,375 +1,374 @@ - + %includes; ]> - &header;

From Jordan Hubbard <jkh@FreeBSD.ORG>, Sunday January 10th, 1999.

Well, it's another year behind us, folks, and probably high time for another state of the union report!

Ahem... I'm never quite sure how to word these things since I'm always reminded of a U.S. president sitting in front of fireplace, trying to sound down-home and folksy for the corn growing states, or perhaps England's Queen on Christmas day, giving her usual somber-yet-hopeful address on how things went for Britannia during the previous year and what everyone should perhaps think about for the next. Neither one of those is really me, basically, so perhaps I'll just cut to the chase and focus on the most pertinent lessons (and objectives) to come out of the year 1998 for me.

1998 was, of course, the year that the Internet got bigger (no surprise), various "internetpraneurs" (gag) got richer and FreeBSD's user base, as measured by the ftp download stats grew at its usual 200-300% rate. More companies also entered the FreeBSD arena, either offering add-ons for or solutions incorporating FreeBSD, and our PR machine, as flimsy and low-key as it often is, managed to ratchet things up another notch. All in all, it was a very good year for FreeBSD and I don't think that even the most paranoid of us could claim otherwise - Microsoft took one in the shorts, we got bigger and just a bit better known, life was good.

Well, mostly. Whipping off my rosy glasses for a second, I can also say that there were still a number of rocks in the road and unexpected bends that left us not always in the best of control there. While downloads have gone up, CD sales aren't quite following suit since the whole CD market in general is suffering from increased Internet availability and its erosion of some of the CD's fundamental advantages. We still did quite well, considering the market's gradual implosion, but it would be foolish to continue to rely on a single CD product to provide the kinds of subsidies that have been steadily oiling the project's gears (we more than doubled the size of the FreeBSD.org computing cluster, for example, and significantly enlarged our developer equipment grant program in 1998, all things which cost $$$). It's fairly obvious that Walnut Creek CDROM will need to increase the number of products it offers if it wishes to remain an effective player in the FreeBSD game and we must continue, as a project, to be flexible in exploring all types of relationships with those who may now have a vested interest in FreeBSD's success. Things are well past the point where we can do everything that needs to be done as a serious and "grown up" solution just on good will and volunteerism alone.

With that in mind, sites like the FreeBSD Mall have been set up to try and market a wider variety of FreeBSD-related products and we've also begun exploring relationships with various companies who can derive measurable value from any PR campaign that enhances FreeBSD's reputation (translation: we want them to help pay for it :). As many people have somewhat bitterly pointed out by now, this business has become a 10% technology and 90% perception equation as far as the direction in which people stampede is concerned, and hate them for the mindless little sheep that they are, you still need to understand people's tendencies and behavioral patterns when it comes to dealing with anything they don't really understand. We've done a great job on the technology, we really have (and should be proud of that), but all too frequently we just throw up our hands over the perception issue and tell people to think whatever the hell they want to. Bad techies! Myopic techies! :-)

What can we do to change this in 1999? Well, I've also heard our advocate corps calling for logistical support ("Backup! We need some backup here!!") and I've listened to them, part of my project for the new years being to get more digital daemon imagery made available (which I have already commissioned), more glossies with various handy comparison charts on them ("FreeBSD and NT", "FreeBSD and Solaris", "FreeBSD and Linux", etc) and more newsletters for passing out to people. We can also produce more marketing periphenalia like buttons, stickers, new T-shirts, etc. to give people a wider array of stuff to proudly point to in support of the "emerging FreeBSD phenomenon." If we can manage to raise more money for PR, we can also perhaps buy some of these items in bulk to use as give-aways in various promotional deals. Other than that, I'm always open to suggestions. We need to do more effective PR, that much is inarguable, it's only a question of picking our targets for maximum effect given a limited operating budget.

The core team:

1998 also ended with a bit of a bang as far as FreeBSD's project management was concerned, frustration with a mostly recumbent core team goading a couple of bearded Danish Vikings into staging a midnight raid on -current, ruthlessly culling the weak and the lame from the source tree. Unfortunately, some of those weak or lame bits of code were still in use at the time and, with no prior public warning having been given, it did not exactly leave the various followers of -current with the feeling that the event was going to be the highlight of their Christmas season. Their complaints led, in turn, to something of a constitutional crisis within core, the rival factions each accusing one another of either impeding progress or using cowboy tactics to achieve that progress, and each faction had its legitimate points just as it had its wholly unreasonable ones. Coming out of this, various suggestions were bandied about concerning how we might put together a "better core team" to which such things simply did not happen (or, if they did, would not be our fault since we'd all be long gone :-) and many of these suggested cures were eventually deemed, quite rightly, to be worse than the disease. So what did we learn from the exercise then?

First off, I think everyone is now pretty much in agreement that these sorts of drive-by shootings are just not an option for the future, no matter what the justification. Anyone who contemplates a major addition or removal of functionality from the source tree MUST communicate those intentions well in advance and give the readership of -current, -stable or -announce (the former two depending on the branch the changes affect and the latter on the extent of the changes) ample time to respond. If there is a conclusively negative response to a proposed change, it just doesn't happen until and unless the proposal somehow manages to win people over through sheer dint of persuasive argument in its favor. If it's more a mixed bag of reactions, or there is little reaction at all, the developer is free to proceed at his or her discretion but still never without advance notice.

Second, in reaction to the various proposals put forward to either gut core or have core elected by popular vote, let me just say that we're not going to do that. There are probably several people currently in core who would gladly step aside and retire if they felt that adequate replacements had been found and the project was in good hands, but none of us like the scenario where anyone is overtly forced out of core. It's just not a reasonable way of going about it when so many less painful alternatives exist, and I, for one, would far rather simply grow core and let the inactive members fall off when they themselves have come to a decision that they have nothing left to contribute at a "core level", resignation from core having not stopped several folks from remaining as effective committers or making other valuable contributions.

We're a free software project and nobody's paid to be in core, no matter how seriously we may be tempted to take the whole core thing sometimes, and we need to remember that all of this started as a bunch of folks who simply wanted to work together in creating something useful and interesting. The day we lose that kind of informal atmosphere of productivity over politics is the day that something pretty fundamental goes out at the center of core and also the day that I'll retire from it myself, handing my hat to a replacement and wishing everyone the very best of luck.

I can also only sound a similar cautionary note about the idea of electing core from the user base, or with committers serving as a kind of "electoral college", as nice and democratic an idea as that might sound. The FreeBSD core team does not represent a democratically selected body and was, in fact, very carefully put together in a very non-democratic way. We picked core with the specific intention that it represent as diverse a set of hard-core FreeBSD evangelist/developers as we knew how to find and we've continued to add people using the same criteria.

In bringing someone into core, we don't look at whether they've been winning popularity contests lately or won the Programming Olympiad 3 times in a row, we ask ourselves: "Does this person bring a unique talent or viewpoint to the group? Will the resulting whole be greater than the sum of its parts?" These are our two most overriding concerns and, in fact, are the only grounds on which we've ever felt it necessary to actually ask for someone's resignation from core. We can tolerate quite a bit from people but not when it impacts core's fundamental ability to work together or seeks to undermine the very diversity of opinion we've worked so hard to cultivate. It's good to be an effective group of decision makers as a core team, and we do have our moments (both ways), but sometimes it's even better to know simply when to stay out of the way and just make sure the train stays roughly on the tracks. We've prevented a lot more stupidity through having such a diverse and carefully selected core team than I think we've ever caused and I do not trust the democratic process to leave us with the same thing after a few elections.

Core is also continuing to work on drafting some internal documents which cover, in much better detail, just what our rules as committers are, those superseding any "core member privileges", governing how large-scale code removal and addition operations should be carried out. We'll post something to committers just as soon as we finally flesh it out to our mutual satisfaction but, in a nutshell, it basically just insists that people need to be warned before such changes happen and that the owner of a given body of code should be given first say as to whether or not it's time to kill it in the name of obsolescence or redundancy. Finally, we are looking at the general issue of communication inside and outside core and the question of whether or not to bring in some new member(s) at this time. That discussion is ongoing and I'll do my best to keep everyone up to date on that as things progress.

Release numbering:

Other decisions on the horizon concern returning to our former practice of using "major" version numbers for branches and "minor" numbers for releases, the revision number field only being used to denote point-releases which were done for some reason significant enough to merit such a special release. This means that the next release will be 3.1, not 3.0.1, and the new branch will be 4.0-current instead of 3.1-current. Is this just a marketing ploy? No, it's not, though marketing has indeed been a frequent casualty of our current numbering scheme.

We have frequently made fairly large changes between our "point releases", jumps like 2.2.5->2.2.6 and 2.2.6->2.2.7 being a lot bigger than most folks gave them credit for given that it was just one little revision number being changed. This one simple facet of human nature reduced the effectiveness of these releases and under-sold the work being done by our developers to substantially improve every release we do, regardless of which branch it's on.

This is not a trend which seems to be reversing itself and so I feel quite safe in saying that 3.1 will be a "full release" over 3.0 in its own right and not merely the "3.0.1" which conveys such a different impression. It's also very important to note that since our branches seem to typically last from 12-18 months these days, no matter what we try in attempting to kill a branch earlier, a major version bump (4.0) is entirely merited for something which won't see full release status until sometime in the year 2000. This will make the marketing people happy since they won't have such an uphill battle on number perception and it will make the users happy since they'll get a clearer picture of what changed in, say, 3.1 to 3.2 vs 3.1 to 3.1.1 (which might be an important security update). It will also make this particular developer happy since I'll have the revision number space back again for doing point releases. It's a win and so we're going to do it. 3.0.1 is dead, long live 3.1! :)

Technology:

This last year also saw a successful transition to ELF from a.out format and a new kernel loadable module scheme which allows modules to be read in without a runtime dependency on /usr/bin/ld. We also got a new boot loader (with a forth interpreter!) to aggregate a "kernel" at boot time. These are both powerful new mechanisms and, coupled with some new stuff which will be coming in 1999, should give us a far more dynamic and extensible system than we've ever had before.

Not to be overlooked is also our new SCSI CAM system, giving us more robust behavior with large drive arrays and supporting more of the high-end SCSI controllers, or the support for multiple processors on the x86. We made considerable progress all across the board with the release of 3.0, finally reaching a point with the DEC Alpha architecture port where people starting worrying more about the packages collection than they did about working kernels or a /usr/src which built. That represents considerable progress towards "genuine usefulness" and I hope that 1999 will see a fully desktop capable release of FreeBSD/axp (to say nothing of a server capable one), various difficulties with X server technology making the Alpha desktop a unique milestone in its own right, especially if it's on an ARC or AlphaBIOS machine. 1999 may also see the early release of a SPARC port, though it's still far too early to say anything more definite than that. Join the sparc@FreeBSD.org mailing list if you want to follow these efforts.

IPv6 and IPSec were also hotly debated topics in 1998, FreeBSD's refusal to back any specific implementation being cited by many as an example of core's over-conservatism in action. Happily for everyone, our wait-and-see attitude proved to be the right one when the two major "competing" groups, KAME and INRIA, finally agreed to merge their implementations. We have, in turn, committed to adopting this merged implementation and have several people from the KAME/INRIA groups on the FreeBSD development team who will be importing and maintaining this code as it becomes available.

There is also substantial work underway with the VM system and the filesystem code, much of which is either being tested quietly in small groups (Dillon/Dyson/Greenman) or is awaiting the 4.0 branch event, still scheduled for January 15th, 1999. In other areas, we have Kazu's very welcome total redesign of the console driver coming into -current along with USB support, courtesy of Nick Hibma and others. This is just to name a few of the projects underway and I don't mean to slight anyone by not mentioning theirs directly, these are just 3 ongoing projects right off the top of my head. We seem to be gaining a lot of technical momentum, and that's great, just so long as we can also keep our heads during the times where not everyone is in total agreement about which technical direction to take.

Tech support:

A point which should also be obvious to everyone yet still somehow requires frequent reinforcement is the fact that we need to maintain participation in this project as something which is also enjoyable for the developer/participants or they will just as quickly go away again and stop giving each and every one of us the benefit of their volunteer labor (on which a dollar value could not even be put). This is something which each and every one of our users needs to be aware of, at least somewhere in the back of their minds, for those times when they're tempted to start thinking of FreeBSD as just another shrink-wrap solution from Software, Inc. and start treating project members like personal employees. Those looking for actual FreeBSD employees should send mail to jobs@FreeBSD.org and indicate how much money they're willing to pay, otherwise don't do it.

I don't mean to come across so harshly here that people don't even bother asking us for help, I'm simply saying that those users who avail themselves of the various FreeBSD volunteer tech support mechanisms out there (mail, news, irc, etc) should always understand that asking another perfect stranger for help is just not much different from asking a random person on the street for a dollar. If you want to get free handouts, you'd better at the very least learn to ask politely and when to take "no" for an answer! :-) I've seen a lot of abuse of the various tech support forum volunteers this last year and it frankly sucks. People just need to be more considerate and stop regarding free tech support as a god-given right rather than a very special privilege. If you want on-demand tech support, go to www.freebsdmall.com and order yourself a tech support contract. You get what you pay for! :)

Looking forward:

What do I see ahead for 1999? Well, assuming that we don't all vanish in some pre-millennial holocaust, I see more interesting new features, improved marketing, more commercial interest, more magazine articles and press attention, basically more of the same if we can just try to stay reasonably well focused on what we need to do and not get distracted into chasing weird desktop dreams or suddenly become overly minimalist or kitchen-sink biased in /usr/src, continuing to chart the middle course we're more famous for. The FreeBSD core team, one year older and hopefully a little wiser, needs to continue keeping a light but steady hand on the tiller, relying on our developers as usual to provide much of the actual motive force behind FreeBSD.

Our users also need to become more involved and I'm hoping that 1999 will be the year when a lot more local user groups and other self-help type of organizations are formed. The Handbook and FAQ are documents which are getting better, hopefully another trend we'll see continue into 1999 as Nik Clayton, our fearless new Documentation Project leader, continues at the helm. We still have to remember, however, that for many users the handbook and FAQ docs are just not enough.

Linux has succeeded largely because of a large grass-roots support and evangelism network which allows it to reach such people and communicate the message to them. If FreeBSD's own users want to see FreeBSD doing better against whomever they most perceive as its competition, and 1998 was certainly a year where I heard a lot of complaining about this, then they're going to simply have to get off their collective duffs and put in more of this kind of work. When was the last time a bunch of FreeBSD users got together to hand out FreeBSD literature at a Microsoft product launch, for example, or held an install-a-thon at a local computer show?

The Linux folks do things like that all the time, apparently, whereas only a very few die-hard FreeBSD users currently do it now, so why not help these people out? Join the advocacy@FreeBSD.org mailing list and discuss your plans there so that others with more enthusiasm than ideas can also learn from and perhaps help you with yours. Write short articles for the new advocacy sites like www.daemonnews.org or www.freebsdrocks.com and help promote the success of BSD evangelical publications.

Phrases like "this is your FreeBSD" and "it all depends on you" may seem shop-worn and trite, but they're also unfortunately still true when there's so few of us and so many of you. If FreeBSD is to really continue to succeed in 1999, it will only be with substantial user participation and that means you, users! Start a local user group, donate some of your older CD releases to the local library, try and convince a local small business or ISP to use FreeBSD, these are just a few of the many things that can be done if you're truly interested in putting some energy into FreeBSD and ideas for what to do will be the least of your worries if you're truly motivated.

Executive Summary: 1999, rah rah rah, let's do it! :)

&footer; diff --git a/en/news/webchanges.sgml b/en/news/webchanges.sgml index 922038f327..a9559b41f2 100644 --- a/en/news/webchanges.sgml +++ b/en/news/webchanges.sgml @@ -1,296 +1,295 @@ - + %includes; %newsincludes; ]> - &header;

This page lists user visible changes at the FreeBSD Web Server.

December 1999

October 1999

September 1999

August 1999

July 1999

&newshome; &footer; diff --git a/en/platforms/ia64.sgml b/en/platforms/ia64.sgml index c000bfd658..3be813675f 100644 --- a/en/platforms/ia64.sgml +++ b/en/platforms/ia64.sgml @@ -1,72 +1,71 @@ - + %includes; ]> - &header;

This page contains information about porting FreeBSD to Intel's upcoming IA64 architecture.

Latest News

  • 5-Nov-2000 Marcel Moolenaar has written a web page describing the Simulator System Calls.

  • 4-Oct-2000 Doug Rabson has committed code to get FreeBSD as far as start_init() before it dies in the simulator.

  • 30-Sep-2000 Doug Rabson has made a series of commits to -current with early IA64 support. The kernel will now reach the mountroot prompt. Please follow the mailing list for more information.

What needs to be done

A lot of work needs to be done on the Cygnus IA64 toolchain. At the moment it looks like the various Linux camps doing IA64 development have splintered off without merging their respective changes back into Cygnus' tree. Anyone working on toolchain issues should coordinate with David Obrien.

HP's Linux IA64 simulator is currently less than ideal for FreeBSD development. Marcel Moolenaar is currently working on some of these issues.

FreeBSD/IA64 Specific Links

Other Links of Interest

IA64 Documentation

Software Tools

Related Projects

&footer; diff --git a/en/platforms/x86-64.sgml b/en/platforms/x86-64.sgml index d153d6059f..1b2f8245be 100644 --- a/en/platforms/x86-64.sgml +++ b/en/platforms/x86-64.sgml @@ -1,63 +1,62 @@ - + %includes; ]> - &header; BSD Daemon swinging a sledge hammer

This page contains information about porting FreeBSD to AMD's upcoming x86-64 ``Hammer'' architecture.

Latest News

  • 13-April-2001 David O'Brien received the commercial Virtutech Simics-LE "VirtuHammer" x86-64 simulator in order to begin the port.

What needs to be done

David O'Brien is working on modifying the AMD sponsored x86-64 GCC for FreeBSD's needs. Anyone working on toolchain issues should coordinate with David O'Brien.

AMD's SimNow! x86-64 simulator is currently less than ideal for FreeBSD development due to its slowness.

FreeBSD/x86-64 Specific Links

Other Links of Interest

x86-64 Documentation

Software Tools

Related Projects

&footer; diff --git a/en/projects/mozilla.sgml b/en/projects/mozilla.sgml index a2c249c6d6..408717d1bd 100644 --- a/en/projects/mozilla.sgml +++ b/en/projects/mozilla.sgml @@ -1,89 +1,88 @@ - + %includes; ]> - &header;

Overview

Following Netscape's decision to publicly release the source code for their client product, otherwise known as Mozilla, a number of free software groups have become actively involved in supporting and improving this technology for their own uses. The FreeBSD Mozilla Group seeks to provide a focus for such work in the FreeBSD world, providing centralized resources such as a CVS repository, a mailing list and other tools for collaborative development.

Resources

CVSup
CVSup provides ongoing synchronization with the central Mozilla repository, either for the CVS bits themselves (for those wishing to keep a local repository) or for a "checked out" version, suitable for directly building or editing. Fetch the CVSup binaries from ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/ and use a supfile which looks something like this:
 *default prefix=/usr/src/mozilla base=/usr/src/mozilla host=mozilla.FreeBSD.org release=cvs delete compress use-rel-suffix tag=.
 
 ## Main Source Tree
 cvs-mozilla
       
anoncvs
Anonymous CVS allows anyone to check things out of the FreeBSD Mozilla repository using the standard cvs(1) commands. Simply set your CVSROOT environment variable to point to:
       anoncvs@mozilla.FreeBSD.org:/mozilla
       

And you can then use cvs(1) for doing read-only operations on the Mozilla CVS repository.

freebsd-mozilla
The FreeBSD-mozilla mailing list is provided for developers and users of the FreeBSD mozilla port to discuss issues relating to building, using and managing the mozilla sources and any FreeBSD-specific changes to them. To subscribe, send mail to majordomo@FreeBSD.org and say subscribe freebsd-mozilla in the body of your message.

More information

Mozilla.ORG
The Mozilla.org project provides central control over Mozilla for all platforms, not just FreeBSD.
Cyclic Software
Cyclic Software has some good on-line tutorials on CVS
&footer; diff --git a/en/projects/newbies.sgml b/en/projects/newbies.sgml index d12ccb63e2..0de75c0f44 100644 --- a/en/projects/newbies.sgml +++ b/en/projects/newbies.sgml @@ -1,253 +1,252 @@ - + %includes; ]> - &header;

The following resources are some of those which FreeBSD newbies have found most helpful when learning to use FreeBSD. Please send corrections and additions to FreeBSD-Newbies@FreeBSD.org.

Using the FreeBSD web site

This web site is the main source of up to date information about FreeBSD. Newbies have found the following pages particularly helpful:

  • Search the Handbook and FAQ, or the whole web site, or the archives of the FreeBSD-Questions mailing list.

  • The Documentation page has links to the Handbook and FAQ, tutorials, information about contributing to the Documentation Project, documents in languages other than English, and much more.

  • Support page contains a wealth of information about FreeBSD, including mailing lists, user groups, web and FTP sites, release information, and links to some sources of UNIX information.

Learning about FreeBSD

  • If you haven't installed yet, look for the latest mainstream release. (See the Handbook for why you should not be tempted by any of the other branches.) Before you begin, carefully read the installation instructions, as well as each one of the *.TXT files in the FTP directory or on the installation CD. They are there because they contain information that you will need. Also pick up the latest errata file from the web site, in case it has been updated.

    If you decide to download FreeBSD, check whether these illustrated and expanded download instructions for a previous version are still available before you begin. That should make the whole process a lot clearer.

  • A number of tutorials are available. The one For People New to Both FreeBSD and Unix is popular with absolute beginners. You don't have to know much about anything to enjoy this one. It is also available from the author's site and can be downloaded in postscript or RTF format for printing.

  • The first thing many people need to set up is ppp, and there is a lot of documentation to help. You might start with at least those parts of the Pedantic PPP Primer that are relevant to your needs, and explore the ppp page for links to the other valuable information and the latest updates.

  • The Complete FreeBSD by Greg Lehey, published by BSDi. This book assumes minimal UNIX experience and takes the beginner step by step through each stage from installation to everything you need to know to set up and run a FreeBSD system. You also get to understand what you're doing and why.

  • The FreeBSD Handbook and Frequently Asked Questions (FAQ) are the main documents for FreeBSD. Essential reading, they contain a lot of material for newbies as well as some pretty advanced stuff. Don't worry if you can't understand the advanced sections. The handbook contains the installation instructions and also provides lists of books and on line resources, and the FAQ has a troubleshooting section.

  • Join the FreeBSD-Questions mailing list to see the questions you were too afraid to ask, and their answers. Subscribe by sending mail to majordomo@FreeBSD.org with "subscribe freebsd-questions" on its own in the message body (the subject doesn't matter). You can look up old questions and answers via the search page.

  • The main newsgroup for FreeBSD is comp.unix.bsd.freebsd.misc. You might want to keep an eye on comp.unix.bsd.freebsd.announce as well.

  • Man pages are good for reference but not always the best introduction for a novice. The more you work with man pages the more familiar they become. Some are very good for newbies, so always check them out. The ppp man page, for example, is more like a tutorial.

Learning about UNIX

Many of the problems we have as newbies come from being unfamiliar with the UNIX commands needed to fix our FreeBSD problems. Without a UNIX background you'll be faced with two things to learn at once. Fortunately a lot of resources are available to make this easier.

  • There are many easy books, such as the "Dummies" guides, in any large book shop. If you want something really easy, take a look at what is available and pick one that seems to speak your language. Pretty soon you will want to move on to a book that gives more coverage.

  • One book mentioned frequently by newbies is UNIX for the Impatient by Paul W. Abrahams and Bruce R. Larson, published by Addison-Wesley. It is intended both as a book for learning UNIX and a reference, and includes an introduction to UNIX concepts and handy chapter on using the X Window System.

  • Another popular book is UNIX Power Tools by Jerry Peek, Tim O'Reilly and Mike Loukides, published by O'Reilly and Associates. It is organised as a series of short articles each of which solves a problem, and these articles are cross-referenced to other articles with related material. Though not specifically aimed at newbies, the design makes it ideal for a newbie with a burning question or the odd few minutes to browse. More elementary material is near the front of the book, but there are short easy articles throughout.

  • A UNIX Introductory Course from Ohio State University is available online in HTML, postscript and Acrobat PDF formats.

  • UNIXhelp for Users is another introductory guide which is available in HTML at a mirror site near you, or can be installed on your own system.

  • UNIX questions are dealt with in the newsgroup comp.unix.questions and the associated Frequently Asked Questions. You can also get a copy of the FAQ from the RMIT FTP site. Newbies are likely to be most interested in sections 1 and 2 initially.

  • Another interesting newsgroup is comp.unix.user-friendly which also has a FAQ. Although this newsgroup is for discussing user-friendliness, it can contain some good information for newbies. The FAQ is also available by FTP.

  • Many other web sites hold lists of UNIX tutorials and reference material. One of the best places to start looking is the UNIX page at Yahoo!.

Learning about the X Window System

The X Window System is used with a number of operating systems, including FreeBSD. The documentation for X can be found at The XFree86 Project, Inc., including the XFree86 FAQ. Beware, much of this documentation is reference material which is likely to be difficult for newcomers to digest.

  • For basic information about installing, configuring and using the X Window System, two of the books mentioned above have sections dealing with X at beginner level: The Complete FreeBSD and UNIX for the Impatient.

  • There is an easy and informative section on using the X Window System in the Linux Users' Guide. Interesting material will be found elsewhere in that document too, but remember that Linux does not always work exactly the same as FreeBSD.

  • Before you can get X running exactly the way you like, you will need to choose a window manager. Visit the Window Managers for X page and follow the link to the introduction to find out about window managers, then return and read "The Basics". Then go back and compare the different types that are available. (Bonus: there's another beginners guide to UNIX there too.) Most if not all of these window managers are available to install from the FreeBSD ports collection.

Helping other people

Everyone has something to contribute to the FreeBSD community, even newbies! Some are busy working with the new advocacy group and some have become involved with the Documentation Project as reviewers. Other FreeBSD newbies might have particular skills and experiences to share, either computer related or not, or just want to meet new newbies and make them feel welcome. There's always people around who help others simply because they like to. Write to FreeBSD Newbies for more information.

Friends who run FreeBSD are a great resource. No book can replace chatting on the phone or across a pizza with someone who has the same interests, enjoys similar accomplishments, and faces the same challenges. If you don't have many friends who use FreeBSD, consider using your old FreeBSD CDs to create some more :-)

User groups are good places to meet other FreeBSD users. If there's not one nearby, maybe you could start one.

Before talking to real humans about your new skills, you might want to check the Pronunciation Guide and the Jargon File :-)

On line we have the FreeBSD-Newbies mailing list for non-technical discussions about matters of interest to newbies. Another mailing list, FreeBSD-Questions, answers our questions about using FreeBSD.

&footer; diff --git a/en/publish.sgml b/en/publish.sgml index d3ffd596cf..f19f33b08a 100644 --- a/en/publish.sgml +++ b/en/publish.sgml @@ -1,525 +1,524 @@ + %includes; ]> - &header;
FreeBSD Daemon
Here you'll find the covers of many FreeBSD related publications. If you know of any additional FreeBSD publications/CDROMs let us know, at www@FreeBSD.org, so that they may be added to this site.

The FreeBSD Handbook contains a considerably longer bibliography.

Click on any of the graphics to see a larger version.

Books

This is a recent (May 1997) publication from Tatsumi Hosokawa and others. Among computer books, it is a top-seller in Japan and exceeded the sales of Bill Gates' "The Road Ahead" when published (it was #2, this book was #1).
(Japanese FreeBSD book with 2.0.5, titled "FreeBSD: Fun and easy Installation")
(Japanese FreeBSD book with 2.0.5, titled "FreeBSD Introductory Kit")
This is BSDi's "The Complete FreeBSD" with installation guide, manual pages and installation CDs inside.
This book was recently published (early 1997) in Taiwan. Its title is "FreeBSD: introduction and applications" and the author is Jian-Da Li.
This is the "Getting Started with FreeBSD" from Fuki-Shuppan. Other than the standard installation guide and Japanese environment, it emphasizes system administration and low-level information (such as the boot process, etc.) FreeBSD-2.2.2R and XFree86-3.2 on CDROM. 264 pages, 3,400 yen.
The "Personal Unix Starter Kit - FreeBSD" from ASCII. Includes history of Unix, a guide to build a Japanese documentation processing system and how to create ports. 2.1.7.1R and XFree86-3.2 in CDROM. 384 pages, 3,000 yen.
BSD mit Methode, M. Schulze, B. Roehrig, M. Hoelzer und andere, C&L Computer und Literatur Verlag, 1998, 850 pages. 2 CDROMs, FreeBSD 2.2.6, NetBSD 1.2.1 and 1.3.2, OpenBSD 2.2 and 2.3. DM 98,-.
This is the "FreeBSD Install and utilization manual" from Mainichi Communications. General introduction to FreeBSD from installation to utilization with troubleshooting under the supervision of the user group in Japan. 2.2.7-RELEASE FreeBSD(98)2.2.7-Rev01 PAO and distfiles in CDROM. 472 pages, 3,600yen.
The "FreeBSD User's Reference Manual" from Mainichi Communications, under the supervision of "jpman project", the manual translation project by the user group in Japan. Japanese edition of the section 1 of the FreeBSD manual. 2.2.7-RELEASE FreeBSD(98)2.2.7-Rev01 and PAO in CDROM. 1,040 pages, 3,800yen.
The "FreeBSD System Administrator's Manual" from Mainichi Communications, under the supervision of "jpman project", the manual translation project by the user group in Japan. Japanese edition of the section 5 and 8 of the FreeBSD manual. 756 pages, 3,300yen.
This is "About FreeBSD" from Youngjin.com. It is first FreeBSD book in Korea, and covers several topics from installation to Korean environment. 3.5.1-RELEASE/PAO and 4.1-RELEASE in 3 CDROMs. 788 pages, 26,000 won.
Onno W Purbo, Dodi Maryanto, Syahrial Hubbany, Widjil Widodo: Building Internet Server with FreeBSD (in Indonesia Language), published by Elex Media Komputindo, 2000.
The Complete FreeBSD with CDs, 3rd Ed, FreeBSD 4.2. Everything you ever wanted to know about how to get your computer up and running FreeBSD. Includes 4 CDs containing the FreeBSD operating system! Released: November 2000 ISBN: 1-57176-246-9

CDROMs

For more about recent releases go to FreeBSD release information page.

This is InfoMagic's BSDisc, containing FreeBSD 2.0 and NetBSD 1.0 on a single CD. This is the only example I have which had cover art.
This is the original 4.4 BSD Lite2 release from UC Berkeley, the core technology behind much of FreeBSD.
The first of Laser5's "BSD" series. Contains FreeBSD-2.0.5R, NetBSD-1.0, XFree86-3.1.1 and FreeBSD(98) kernel.
The second of Laser5's "BSD" series. From this version, the CDs come in a standard jewel box. Contains FreeBSD-2.1R, NetBSD-1.1, XFree86-3.1.2 and 3.1.2A, and FreeBSD(98) kernel (2.0.5).
This is the Laser5 Japanese edition of the FreeBSD CDROM. It is a 4 CD set.
This is the only FreeBSD CD Pacific Hitech produced before merging their product line with that of Walnut Creek CDROM. PHT now also produces the FreeBSD/J (Japanese) CD product.
This is the cover disc from the Korean magazine. Note the creative cover art! The CD contains the FreeBSD 2.2.1 release with some local additions.
This is it - the very first FreeBSD CD published! Both the FreeBSD Project and Walnut Creek CDROM were fairly young back then, and you'll probably have little difficulty in spotting the differences in production quality between then and now.
This was the second FreeBSD CD published by Walnut Creek CDROM and also the very last on the 1.x branch (ref USL/Novell lawsuit and settlement). The next release, FreeBSD 1.1.5, was only available on the net.
This unusual CD is something of a collector's item now given that almost all existing examples were systematically tracked down and destroyed. An artwork mishap has this CD dated for the wrong year, and on the spine "January" is also misspelled as "January", just to increase the embarrassment factor. Ah, the perils of turning in one's artwork just hours before leaving for a trade show.
This is the fixed-up version of the FreeBSD 2.0 CD. Note that the color scheme has even been changed in the corrected version, something unusual for a fixup and perhaps done to distance it from the earlier mistake.
The FreeBSD 2.0.5 release CD. This was the first CD to feature Tatsumi Hosokawa's daemon artwork.
The FreeBSD 2.1 release CD. This was the first CD release on the 2.1 branch (the last being 2.1.7).
The FreeBSD 2.1.5 release CD.
The FreeBSD 2.1.6 release CD.
The Japanese version of 2.1.6. This was the first and last Japanese localized version published by WC, responsibility for that product then transitioning to a team led by Tatsumi Hosokawa and sponsored by Pacific Hitech and Laser5.
The FreeBSD 2.1.7 release CD. Also the last CD released on the 2.1.x branch. Done primarily as a security fixup for 2.1.6
An early release SNAPshot of 2.2 (done before 2.2.1 was released).
The FreeBSD 2.2.1 release CD. This was the first CD on the 2.2 branch.
The FreeBSD 2.2.2 release CD.
The FreeBSD 3.0 snapshot CD.
The FreeBSD mailing list and newsgroup archives, turned into HTML and semi-indexed by thread. This product ran for 2 releases and then stopped with a thud once it became obvious that there was simply too much data to deal with on one CD. Perhaps when DVD becomes more popular...
FreeBSD Toolkit: Six disc set of resources to make your FreeBSD experience more enriching.
FreeBSD Alpha 4.2 - The full version of the DEC Alpha 64-bit UNIX operating system.
FreeBSD 4.2: The full version of the PC 32-bit UNIX operating system.
FreeBSD 4.2 CD-ROM. Lehmanns CD-ROM Edition. January 2001, 4 CD-ROMs. Lehmanns Fachbuchhandlung. Germany. ISBN 3-931253-72-4.

Magazines

Cover of Korean UNIX magazine, May 1997 issue. Also included FreeBSD 2.2.1 with cover CDs.
UNIX User Magazine November 1996 issue. Also included FreeBSD 2.1.5 on cover CD.
This is the "FreeBSD Full Course" special in April 1997's Software Design (published by Gijutsu Hyoron Sha). There are 80 pages of FreeBSD articles covering everything from installation to tracking -current.
Quality Unix for FREE, by Brett Glass in Sm@rt Reseller Online September 1998
This is the "BSD magazine" published by ASCII corporation, the world's first publication specialized in BSD. BSD magazine covers FreeBSD, NetBSD, OpenBSD and BSD/OS. The premiere issue features articles on the history of BSD, installation, and Ports/Packages; it also includes 4 CD-ROMs containing FreeBSD 3.2-RELEASE, NetBSD 1.4.1 and OpenBSD 2.5.

Newsletters

This is issue #1 of the FreeBSD Newsletter, published and distributed free of charge by Walnut Creek CDROM. You can register to receive it. Submit articles/make comments by sending email to newsletter@FreeBSD.ORG.
This is issue #2 of the FreeBSD Newsletter, published and distributed free of charge by Walnut Creek CDROM. You can register to receive it. Submit articles/make comments by sending email to newsletter@FreeBSD.ORG.
&footer; diff --git a/en/register.sgml b/en/register.sgml index 6507fb47b4..673abf5d29 100644 --- a/en/register.sgml +++ b/en/register.sgml @@ -1,122 +1,121 @@ + %includes; ]> - &header;
Register to receive the FreeBSD Newsletter and subscribe to the announce@FreeBSD.org mailing list.

First Name:
Last Name:
Email Address:
Address:
City:
Country/U.S. State: Country/Zip Code:
Do you wish to receive FreeBSD related commercial email?
Subscribe listed email address to the announce@FreeBSD.org mailing list?
Sign up for FreeBSD Newsletter?

Preview a copy of the newsletter in Adobe PDF format. A help file is available to assist you in selecting and using a PDF viewer.

&footer; diff --git a/en/search/index-site.sgml b/en/search/index-site.sgml index e5198550ca..4470941755 100644 --- a/en/search/index-site.sgml +++ b/en/search/index-site.sgml @@ -1,54 +1,53 @@ - + %includes; ]> - &header;

Site Map

&site;

Meta homepages


A-Z Index

&atoz; &footer; diff --git a/en/search/search-mid.sgml b/en/search/search-mid.sgml index 962fa0072f..4c24a07a0d 100644 --- a/en/search/search-mid.sgml +++ b/en/search/search-mid.sgml @@ -1,41 +1,37 @@ - + %includes; ]> - - - - &header;
Message-ID:
Answers to a Message-ID:

You can search only the mail header keywords Message-ID, Resent-Message-id, In-Reply-to, and References. A Message-ID looks like <199802242058.MAA24843@monk.via.net>. No other mail header keywords are supported. The Message-ID database will be updated every hour.

Full text mailing list archives. &footer; diff --git a/en/search/search.sgml b/en/search/search.sgml index 64c58f46b4..cedc34eef4 100644 --- a/en/search/search.sgml +++ b/en/search/search.sgml @@ -1,433 +1,432 @@ - + %includes; ]> - &header;

FreeBSD Search Services


Web pages (including FAQ and Handbook)

Search for:

Note: Use the operators AND or NOT to limit your search. Look here for more hints.


Limit the number of results to


Mailing list archives

The mailing list archive indexes are now updated weekly!

The mailing lists (as well as many others) have also been archived by GeoCrawler.

Search for:

Note: Use the operators AND or NOT to limit your search. Look here for more hints.


Limit the number of results to sort by Search

In archive(s):

Note: Searching more than three or four archives at once may yield inaccurate results.

General Archives

Advocacy FreeBSD Evangelism
Announce Important events / milestones
Chat Random topics (sometimes) related to FreeBSD
Jobs FreeBSD related job announcements and resumes
Newbies New FreeBSD users activities and discussion
Questions General questions
User-Groups A forum for FreeBSD user groups

System Use and Administration

Bugs Reports and discussion of bugs
Hardware Discussions concerning hardware as it relates to FreeBSD
ISP Discussions for ISPs using FreeBSD
Security FreeBSD computer security issues (DES, Kerberos, etc.)
Stable Discussion of the FreeBSD-stable branch of the development tree

Developer

Afs Porting and using AFS (the Andrew File System) from CMU/Transarc
Alpha Porting FreeBSD to the DEC Alpha
Arch Architecture and design discussions
ARM Porting FreeBSD to the StrongArm
ATM Using ATM networking with FreeBSD
Audit Source code audit project
Commit Changes made to the FreeBSD source tree
Config Development of FreeBSD installation and configuration tools
Current Use of FreeBSD-current sources
Database Discussing database use and development under FreeBSD
Doc Discussions concerning documentation
Emulation Emulating other systems on FreeBSD
Fs Discussions concerning FreeBSD filesystems
Hackers General technical discussions
I18n FreeBSD Internationalization
ia64 Porting FreeBSD to Intel's upcoming IA64 systems
ipfw Technical discussion concerning the redesign of the IP firewall code
ISDN Development of ISDN support for FreeBSD
Java JDK porting and application development
libh The second generation installation and package system
Multimedia Discussions about FreeBSD as a multimedia platform
Mobile Using FreeBSD in a mobile environment
Mozilla Porting mozilla to FreeBSD
Net Networking discussion and TCP/IP source code
New Bus Technical discussions on Bus Architecture
Platforms Cross-platform FreeBSD issues (non-Intel FreeBSD ports)
Policy FreeBSD core team policy decisions.
Ports Discussions concerning FreeBSD's ports collection
PPC Porting FreeBSD to the PowerPC
Realtime Development of realtime extensions to FreeBSD
SCSI Discussions about FreeBSD's SCSI support
Small Using FreeBSD in embedded applications
SMP FreeBSD on multi-processor platforms
SPARC Porting FreeBSD to the SPARC
Tokenring Support Token Ring in FreeBSD

Limited lists

Hubs People running mirror sites (infrastructural support)
Install Installation system development
WWW Web site maintainers

&footer; diff --git a/en/search/searchhints.sgml b/en/search/searchhints.sgml index b6eec1a129..24de4a7ec3 100644 --- a/en/search/searchhints.sgml +++ b/en/search/searchhints.sgml @@ -1,53 +1,52 @@ - + %includes; ]> - &header;

If you got lots of irrelevant results...

  1. If you search for several words such as "quantum hard drives", an OR is implied meaning that to be counted as relevant, only one of the word has to appear in a message. To find only messages with all three words, change the search to "quantum and hard and drives"

  2. If you still get lots of irrelevant messages, see if they have something in common. If so, you can exclude them with the not operator. For example "quantum and hard and drives not ide" will exclude any messages about ide quantum hard drives.

If you do not think you received everything you should have...

  1. If one of your keywords has variant forms, be sure to enter all relevant forms. If you are searching for "buslogic", you might change it to "buslogic or bustek".

  2. Words with varying suffixes can be wildcarded. Searching for "drive*" will pick up words such as drive, drives, driver, drivers and so on.

  3. Try discarding words that could be implied by the context of the message. For example "quantum and hard and drive" might miss some relevant messages that "quantum and drive" would get.

Return to the search page &footer; diff --git a/en/send-pr.sgml b/en/send-pr.sgml index e7c5937749..904b61e6e8 100644 --- a/en/send-pr.sgml +++ b/en/send-pr.sgml @@ -1,106 +1,105 @@ + %includes; ]> - &header;

Thank you for taking the time to let us know about a problem with FreeBSD. Please fill out the form as completely as possible. Make sure you fill in the "Environment" field as requested with the output from the machine on which problem occurred.

Your Electronic Mail Address:

Your Name:

Your Organization or Company:

One line summary of the problem:

Category:
Severity:
Priority:
Class:
Which FreeBSD Release You Are Using :

Environment (output of "uname -a" on the problem machine):

Full Description:

How to repeat the problem:

Fix to the problem if known:

Note: copy/paste will destroy TABs and spacing, and this web form should not be used to submit code as plain text.

&footer; diff --git a/en/smp/index.sgml b/en/smp/index.sgml index 7683d82d3f..3a9112928d 100644 --- a/en/smp/index.sgml +++ b/en/smp/index.sgml @@ -1,19 +1,18 @@ - + %includes; ]> - &header;

The bulk of the information about the FreeBSD SMPng project can be found at http://people.freebsd.org/~jasone/smp/.

Information will be moved under here over the coming weeks.

&footer; diff --git a/en/support.sgml b/en/support.sgml index 6b2a05f3b6..bbed56c58f 100644 --- a/en/support.sgml +++ b/en/support.sgml @@ -1,937 +1,936 @@ + %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. You can browse or search the mailing list archives at www.FreeBSD.org.

The FreeBSD Conspectus is a summary of some of the mailing lists produced each week, giving you an at-a-glance overview of recent discussions and decisions.

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

GNATS Problem Report Database

Current FreeBSD problem reports are tracked using the GNATS database.

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!

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, and can be easily viewed from here (click on the link). 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're looking for on-demand, low overhead access using a custom utility (written in Modula-3 no less).
  • anoncvs if you're 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're looking for very low overhead, batch-mode access (basically, patches through email).
  • The web interface if you're looking to simply browse the repository in search of a specific change or file revision.
  • Finally, if you've 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 California, Germany, Japan and Spain (English, Spanish).

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

  • Austria. The BSD User Group Austria (BUGAT) is german-language oriented user group. Visit our server for more information.

  • The Netherlands. The Dutch FreeBSD User Group (NLFUG) has had its first meeting on oct 2, 1999. On this day 30 years before that, the second IMP was installed in Doug Englebart's lab at SRI. This, as you all know, was the start of something that grew to be the Internet (thanks to Edwin Kremer for bringing this under our attention).

  • Denmark BSD-DK. The Danish BSD user group. Promotion and support of BSD derived Operating Systems in Denmark. Mailing lists, lectures and workshops. Send mail subscription requests to bsd-dk-request@bsd-dk.dk.

  • Köln (Cologne), Germany The CBUG (Cologne BSD Usergroup) caters to BSD users in the Köln area. Meetings are on the fourth Friday of each month at the ``Campi'' Italian restaurant in the Richard-Wallraff-Platz.

  • Duisburg, Germany The Cosmo-Project is a user group with a difference. Instead of just meeting, they actively develop projects such as robots. Most users use FreeBSD, but it isn't a specifically FreeBSD-related group.

  • France The French FreeBSD UG. Please follow the link for details.

  • Frankfurt, Germany FrankfurtBSD is a user group for the Rhein-Main area. We are currently looking for new members. As soon as we've grown larger, we'd like to meet monthly and maintain minor projects.

  • Hamburg, Germany The BSDHH (BSD User Group Hamburg) meets on the first Wednesday of the month at 7.00pm in the Chinese restaurant Lotosblüte, Löwenstraße 22 in Hamburg-Eppendorf. Most members are FreeBSD users, although users of all BSD flavors are welcome.

  • Ireland The BUGI (BSD User Group Ireland) is currently a rather grandiose term for a mailing list and super-minimal web page. All BSD users and enthusiasts are welcome.

  • Italia The GUFI (Gruppo Utenti FreeBSD Italia) is an "italian powered" FreeBSD User Group. It is intended to help Italian FreeBSD users to find support and articles on/about FreeBSD in the Italian language. Please follow this link to know more about us.

  • Lublin, Poland The Lublin BSD Users Group. Please follow the link for details.

  • Lund, Sweden The Lund Linux User Group (LFUG) has nearly 50 members and covers FreeBSD and Solaris in addition to Linux. To join, contact Omar Dedovic

  • Mannheim, Germany The UUGRN (Unix Users Group Rhein-Neckar) provides a regional forum for users of all UNIX flavors, with a stress on Linux and BSD. Meetings are held on the second Wednesday of each month at the "Eichbaum Brauhaus" in Mannheim-Käfertal and the fourth Thursday of each month at the "Vater Rhein" in Heidelberg.

  • München (Munich), Germany The BIM (Berkeley In Munich) group caters for users of BSD-based systems in Oberbayern.

  • Regensburg, Germany The UNIX and Linux User Group is a general UNIX users group for anyone in Regensburg (Bavaria, Germany). We meet on every first Monday of the month in the Pub ``Filmbühne'' in Regensburg. Visit the web site or send a message to m.suess@2use.org.

  • Sweden The BSD Users Sweden (BUS) maintains a mailing list. To join, send mail to majordomo@stacken.kth.se with subscribe bus in the message.

  • Turkey The Turkish FreeBSD Users Group (Türkiye FreeBSD Kullanicilari Grubu) was founded in September 1999. TFUG is intended to help Turkish FreeBSD users to find support and articles on and about FreeBSD in the Turkish language. Contact M. Guven Mucuk for more info.

  • United Kingdom The FreeBSD UKUG (FreeBSD UK User's Group) exists for the benefit of FreeBSD users in the United Kingdom. Please follow the link for details.

North America

  • Ames, Iowa The Ames Free-Unix Group aims to promote the use of Free UNIX. We meet on the campus of Iowa State University once a month and hold a presentation with an open question and answer session afterwards. You can join our mailing list by sending a blank email to aafugit-subscribe@aafugit.org.

  • Berkeley, CA The Berkeley UNIX User Group is a general UNIX users group for anyone in the San Francisco Bay Area. We meet on a weekly basis in downtown Berkeley. Visit the web site or send a message to buug-request@weak.org with subscribe in the body.

  • Chicago IL The Chicago FreeBSD Users Group (ChiFUG).

  • The Connecticut Free Unix user's Group (CFUG) is devoted to free unix, but has resources for almost all Unixen. Their area of operation is Connecticut and Western Massachusetts. More information can be found at http://www.cfug.org.

  • The Houston TX Houston FreeBSD Users Group formed March 1999. Our goal is to promote and educate Houston computer users on FreeBSD Unix. We meet on the fourth Thursday of the month. The group operates a mailing list at http://www.houfug.org/mailman/listinfo/hou-freebsd Visit our website or e-mail houfug@houfug.org for more information.

  • Indianapolis IN Free Unix for Indianapolis is a non-profit organization dedicated to encouraging the use of Free Unix variants in and around Indianapolis. Essentially, we are a bunch of geeks who share a common passion: UNIX. Visit the web site or send a message to info@fufin.org for additional information.

  • Kansas KULUA (Kansas Unix & Linux Users Association) is a Free Unix user group based in Lawrence, Kansas, but with users throughout eastern Kansas and western Missouri. We have about 120 members and meet biweekly. Visit the web site or email kulua@kulua.org for more information.

  • Kansas Wichita Area FreeBSD Users Group (WAFUG) is a free users group provided to anyone in the Wichita area for support with FreeBSD and other UNIX and UNIX-like operating systems. We meet twice a month, usually in a restaraunt where you can smoke or drink if you like. Please send us Email for more information or to find out how to get free shell account, www or ftp space on our system.

  • Las Vegas, NV The Vegas Free UNIX User Group

  • Los Angeles CA The Yahoo Club group is a foundation for a Los Angeles based BSD user group.

  • New Mexico The NMLUG in Albuquerque meets once a month and supports both BSD and Linux users. To join the mailing list, send a message to majordomo@swcp.com with subscribe nmlug in the body.

  • New Orleans LA The New Orleans *BSD User Group meets twice a month. Contact Konrad Rzeszutek for more details. A web page will be posted soon.

  • New York NY D'Artagnan's FreeBSD Users Group.

  • New York NY FUNY (FreeBSD Users of New York) had its inaugural meeting in February 1999. It is based in NYC and serves the surrounding metropolitan area.

  • Northern Arizona Yavapai Free Unix Users Group is now forming for *BSD/Linux, etc., users in Northern Arizona. Please contact Russell Carter ( rcarter@consys.com) for details.

  • Orlando, FL BUGO (BSD Users Group of Orlando) is a group based in Orlando, FL that aims to bring a friendly forum to all UNIX users in the central Florida area, and hopefully beyond. See the BUGO web page for further details.

  • Phoenix AZ The Phoenix BSD Users group is fully open for business. Anyone from the Phoenix area please feel free to join in http://bsd.phoenix.az.us.

  • Portland, OR The Portland (Oregon) FreeBSD Users group meets on the third Thursday of each month. Mail Rick Hamell.

  • Reno NV RUUG (Reno Unix Users Group) meets monthly in Reno Nevada and discusses the use of FreeBSD and Linux. Contact Eric Blood or Todd Crenshaw for more information.

  • Research Triangle, NC The Triangle Area BSD Users Group is a users group for BSD users in the Research Triangle Park area of North Carolina, including the surrounding metropolitan areas of Raleigh, Durham, and Chapel Hill. People interested in this group may subscribe to the mailing list by sending a message to majordomo@tribug.org with subscribe tribug-members in the body.

  • Rhode Island The Rhode Island Free Unix Group supports every form of UNIX that can be obtained freely. They can be contacted at: http://users.tmok.com/~rifug or by e-mail at: rifug@entropy.tmok.com

  • St. Louis, MO The St. Louis BSD User Group (STLBSD) has just formed on July 20, 2000 to promote BSD operating systems in the St. Louis area. We have strong ties to the 10 year old St. Louis Unix Users Group (SLUUG) and expect to be a positive force within our community. Our membership is open to anyone interested in learning more about BSD, several mailing lists are available through our website.

  • San Diego, California San Diego BSD Users Group for users of FreeBSD, OpenBSD and NetBSD. The meeting is first Thursday of every month at Borders Bookstore in Mission Valley Shopping Center. More information can be found here

  • North San Francisco Bay Area The BABUG (Bay Area BSD Users Group) has monthly meetings, alternating between San Francisco and Berkeley. Those interested in attending should visit the web site or send mail to the BABUG Web Master

  • Silicon Valley, CA The SVBUG (Silicon Valley BSD User Group), a forum for BSD and BSD embedded systems, meets on the First Thursday of the month. Meetings are held at the Carl's Jr. on First Street and Trimble Road in San Jose, California. For details on event or what's going on visit the website or send a message to webmaster@svbug.com.

  • The Tampa Florida users group is now being formed. Interested parties can join the mailing list by sending mail to bsd-tug-request@bangheadhere.org with subscribe in the body.

  • Greater Toronto Area, Ontario: The GTABUG usergroup welcomes all BSD users. Monthly meetings give attendees a chance to share ideas, discussion, and information. Installathons and other events help preach the good news of BSD to the community. Come drop by for a meeting!

  • Tucson AZ TFUG: Tucson Free Unix Group, Arizona.

  • Utah SLLUG-BUG is a BSD UNIX User Group affiliated with the Salt Lake Linux User Group (SLLUG). We meet in concert with SLLUG, since the BSD and Linux communities have so much in common. We meet on the third Wednesday of each month, check the web page for details.

  • Vancouver, BC The VanBUG (Vancouver BSD Users Group) is a group of volunteers who are passionate about FreeBSD, NetBSD, and OpenBSD. Their current goal is to raise awareness and also provide local assistance as much as we can.

  • Washington DC (DC Metropolitan Area) FreeBSD User Group is now forming. Please contact Richard Cramer, Sytex Access Ltd. at 703-425-2515, or preferred, email at rcramer@sytex.net to be put on a member distribution list. Initial meeting to be held in May.

  • Wichita, Kansas: A new FreeBSD users group has been created in Wichita, Ks. We are fairly new and working on our site, but we wanted to get it up as soon as we had it available. We do not currently meet. Visit our site http://wafug.dynip.com or E-mail the group organizer (ben177@yahoo.com) for more information!

  • Windsor, Ontario The Windsor Unix Users Group (Windsor, Ontario, Canada) covers BSD, Solaris, SCO, and others. This is not specifically a FreeBSD user group, but we do already have members running FreeBSD. The group operates a mailing list (wuug-list@unixpower.org). More information can be found at http://www.wuug.org/.

  • Wisconsin FreeBSD-Milwaukee Wisconsin meets occasionally and has a mailing list: freebsd-mke-l@ns.sol.net. send mail to freebsd-mke-l-request@ns.sol.net to subscribe.

Rest of the world

  • Ibaraki, Japan The Daibou East *BSD Users Group (DEBUG) is now forming for *BSD users in Tsukuba area.

  • Indonesia The Jogja FreeBSD Users' Group is based in Yogyakarta City, Indonesia. Send email to 22961476@students.ukdw.ac.id for more information.

  • Israel The Israeli BSD Users Group is an effort to promote the use of *BSD throughout the country, and to act as a center of information for all BSD users. It is currently run by FreeBSD users, but all users of bsd Variants are welcome aboard. We have a mailing list, hosted at bsd-il@osem.co.il. To subscribe, simply send mail to majordomo@osem.co.il, with the line "subscribe bsd-il" as the message body.

  • Kansai, Japan The Kansai *BSD User's Group, K*BUG (sorry for Japanese only), was established on November 13, 1999. It is expected to promote communication of any of the BSD variants' users. Some of its activities are to hold friendly parties of the members, and to hold seminars covering wide variety of topics. Please mail here ( kbug-admin@kbug.gr.jp ).

  • New Zealand The New Zealand FreeBSD User's group is located in Wellington. No meetings have been scheduled yet.

  • Sao Paulo, Brazil The FUG_SP_BR (Brazilian FreeBSD User Group) is a Portuguese language oriented user group intended to help Brazilian FreeBSD users to find support and articles on and about FreeBSD in the Portuguese language. The group meets in Sao Paulo, Brazil, every month. To join FUG_SP_BR mailing list, send a blank message to fug_sp_br-subscribe@yahoogroups.com

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

  • The XFree86 Project provides 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 MS-Windows software on Intel based Unix systems such as FreeBSD, NetBSD and Linux.

Hardware

  • The comp.answers pc-hardware-faq is a great reference for people building their own machines.
  • Laptop users looking for PCCARD (aka PCMCIA) support not already provided in the FreeBSD base distribution should see the PAO distribution page for the latest and greatest experimental laptop support.
  • Intel Secrets -- What Intel Doesn't Want You To Know - lots of information about Intel chips.
  • Aad Offerman's Chip List - reference material on chips used in PC clones.
  • ASUS makes motherboards that work well with FreeBSD.

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.
  • Linux is another free Unix-like system.
  • Lites is a 4.4 BSD Lite based server and emulation library that provides free unix functionality to a Mach based system.
  • xMach is a Lites and Mach4 derivative designed to be small and efficient with extended functionality.
  • The GNU HURD project is another effort to develop a free Unix-like operating system.
&footer; diff --git a/en/tutorials/index.sgml b/en/tutorials/index.sgml index e38f42378b..9eadaf6585 100644 --- a/en/tutorials/index.sgml +++ b/en/tutorials/index.sgml @@ -1,107 +1,106 @@ - + %includes; ]> - &header;

Here is a list of documents on various aspects of FreeBSD, FreeBSD software, and hardware. If you have comments or would like to contribute a document, please contact us at freebsd-doc@FreeBSD.org.

Documents related to FreeBSD on other servers:

&footer; diff --git a/en/usergroups.sgml b/en/usergroups.sgml index 6b2a05f3b6..bbed56c58f 100644 --- a/en/usergroups.sgml +++ b/en/usergroups.sgml @@ -1,937 +1,936 @@ + %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. You can browse or search the mailing list archives at www.FreeBSD.org.

The FreeBSD Conspectus is a summary of some of the mailing lists produced each week, giving you an at-a-glance overview of recent discussions and decisions.

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

GNATS Problem Report Database

Current FreeBSD problem reports are tracked using the GNATS database.

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!

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, and can be easily viewed from here (click on the link). 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're looking for on-demand, low overhead access using a custom utility (written in Modula-3 no less).
  • anoncvs if you're 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're looking for very low overhead, batch-mode access (basically, patches through email).
  • The web interface if you're looking to simply browse the repository in search of a specific change or file revision.
  • Finally, if you've 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 California, Germany, Japan and Spain (English, Spanish).

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

  • Austria. The BSD User Group Austria (BUGAT) is german-language oriented user group. Visit our server for more information.

  • The Netherlands. The Dutch FreeBSD User Group (NLFUG) has had its first meeting on oct 2, 1999. On this day 30 years before that, the second IMP was installed in Doug Englebart's lab at SRI. This, as you all know, was the start of something that grew to be the Internet (thanks to Edwin Kremer for bringing this under our attention).

  • Denmark BSD-DK. The Danish BSD user group. Promotion and support of BSD derived Operating Systems in Denmark. Mailing lists, lectures and workshops. Send mail subscription requests to bsd-dk-request@bsd-dk.dk.

  • Köln (Cologne), Germany The CBUG (Cologne BSD Usergroup) caters to BSD users in the Köln area. Meetings are on the fourth Friday of each month at the ``Campi'' Italian restaurant in the Richard-Wallraff-Platz.

  • Duisburg, Germany The Cosmo-Project is a user group with a difference. Instead of just meeting, they actively develop projects such as robots. Most users use FreeBSD, but it isn't a specifically FreeBSD-related group.

  • France The French FreeBSD UG. Please follow the link for details.

  • Frankfurt, Germany FrankfurtBSD is a user group for the Rhein-Main area. We are currently looking for new members. As soon as we've grown larger, we'd like to meet monthly and maintain minor projects.

  • Hamburg, Germany The BSDHH (BSD User Group Hamburg) meets on the first Wednesday of the month at 7.00pm in the Chinese restaurant Lotosblüte, Löwenstraße 22 in Hamburg-Eppendorf. Most members are FreeBSD users, although users of all BSD flavors are welcome.

  • Ireland The BUGI (BSD User Group Ireland) is currently a rather grandiose term for a mailing list and super-minimal web page. All BSD users and enthusiasts are welcome.

  • Italia The GUFI (Gruppo Utenti FreeBSD Italia) is an "italian powered" FreeBSD User Group. It is intended to help Italian FreeBSD users to find support and articles on/about FreeBSD in the Italian language. Please follow this link to know more about us.

  • Lublin, Poland The Lublin BSD Users Group. Please follow the link for details.

  • Lund, Sweden The Lund Linux User Group (LFUG) has nearly 50 members and covers FreeBSD and Solaris in addition to Linux. To join, contact Omar Dedovic

  • Mannheim, Germany The UUGRN (Unix Users Group Rhein-Neckar) provides a regional forum for users of all UNIX flavors, with a stress on Linux and BSD. Meetings are held on the second Wednesday of each month at the "Eichbaum Brauhaus" in Mannheim-Käfertal and the fourth Thursday of each month at the "Vater Rhein" in Heidelberg.

  • München (Munich), Germany The BIM (Berkeley In Munich) group caters for users of BSD-based systems in Oberbayern.

  • Regensburg, Germany The UNIX and Linux User Group is a general UNIX users group for anyone in Regensburg (Bavaria, Germany). We meet on every first Monday of the month in the Pub ``Filmbühne'' in Regensburg. Visit the web site or send a message to m.suess@2use.org.

  • Sweden The BSD Users Sweden (BUS) maintains a mailing list. To join, send mail to majordomo@stacken.kth.se with subscribe bus in the message.

  • Turkey The Turkish FreeBSD Users Group (Türkiye FreeBSD Kullanicilari Grubu) was founded in September 1999. TFUG is intended to help Turkish FreeBSD users to find support and articles on and about FreeBSD in the Turkish language. Contact M. Guven Mucuk for more info.

  • United Kingdom The FreeBSD UKUG (FreeBSD UK User's Group) exists for the benefit of FreeBSD users in the United Kingdom. Please follow the link for details.

North America

  • Ames, Iowa The Ames Free-Unix Group aims to promote the use of Free UNIX. We meet on the campus of Iowa State University once a month and hold a presentation with an open question and answer session afterwards. You can join our mailing list by sending a blank email to aafugit-subscribe@aafugit.org.

  • Berkeley, CA The Berkeley UNIX User Group is a general UNIX users group for anyone in the San Francisco Bay Area. We meet on a weekly basis in downtown Berkeley. Visit the web site or send a message to buug-request@weak.org with subscribe in the body.

  • Chicago IL The Chicago FreeBSD Users Group (ChiFUG).

  • The Connecticut Free Unix user's Group (CFUG) is devoted to free unix, but has resources for almost all Unixen. Their area of operation is Connecticut and Western Massachusetts. More information can be found at http://www.cfug.org.

  • The Houston TX Houston FreeBSD Users Group formed March 1999. Our goal is to promote and educate Houston computer users on FreeBSD Unix. We meet on the fourth Thursday of the month. The group operates a mailing list at http://www.houfug.org/mailman/listinfo/hou-freebsd Visit our website or e-mail houfug@houfug.org for more information.

  • Indianapolis IN Free Unix for Indianapolis is a non-profit organization dedicated to encouraging the use of Free Unix variants in and around Indianapolis. Essentially, we are a bunch of geeks who share a common passion: UNIX. Visit the web site or send a message to info@fufin.org for additional information.

  • Kansas KULUA (Kansas Unix & Linux Users Association) is a Free Unix user group based in Lawrence, Kansas, but with users throughout eastern Kansas and western Missouri. We have about 120 members and meet biweekly. Visit the web site or email kulua@kulua.org for more information.

  • Kansas Wichita Area FreeBSD Users Group (WAFUG) is a free users group provided to anyone in the Wichita area for support with FreeBSD and other UNIX and UNIX-like operating systems. We meet twice a month, usually in a restaraunt where you can smoke or drink if you like. Please send us Email for more information or to find out how to get free shell account, www or ftp space on our system.

  • Las Vegas, NV The Vegas Free UNIX User Group

  • Los Angeles CA The Yahoo Club group is a foundation for a Los Angeles based BSD user group.

  • New Mexico The NMLUG in Albuquerque meets once a month and supports both BSD and Linux users. To join the mailing list, send a message to majordomo@swcp.com with subscribe nmlug in the body.

  • New Orleans LA The New Orleans *BSD User Group meets twice a month. Contact Konrad Rzeszutek for more details. A web page will be posted soon.

  • New York NY D'Artagnan's FreeBSD Users Group.

  • New York NY FUNY (FreeBSD Users of New York) had its inaugural meeting in February 1999. It is based in NYC and serves the surrounding metropolitan area.

  • Northern Arizona Yavapai Free Unix Users Group is now forming for *BSD/Linux, etc., users in Northern Arizona. Please contact Russell Carter ( rcarter@consys.com) for details.

  • Orlando, FL BUGO (BSD Users Group of Orlando) is a group based in Orlando, FL that aims to bring a friendly forum to all UNIX users in the central Florida area, and hopefully beyond. See the BUGO web page for further details.

  • Phoenix AZ The Phoenix BSD Users group is fully open for business. Anyone from the Phoenix area please feel free to join in http://bsd.phoenix.az.us.

  • Portland, OR The Portland (Oregon) FreeBSD Users group meets on the third Thursday of each month. Mail Rick Hamell.

  • Reno NV RUUG (Reno Unix Users Group) meets monthly in Reno Nevada and discusses the use of FreeBSD and Linux. Contact Eric Blood or Todd Crenshaw for more information.

  • Research Triangle, NC The Triangle Area BSD Users Group is a users group for BSD users in the Research Triangle Park area of North Carolina, including the surrounding metropolitan areas of Raleigh, Durham, and Chapel Hill. People interested in this group may subscribe to the mailing list by sending a message to majordomo@tribug.org with subscribe tribug-members in the body.

  • Rhode Island The Rhode Island Free Unix Group supports every form of UNIX that can be obtained freely. They can be contacted at: http://users.tmok.com/~rifug or by e-mail at: rifug@entropy.tmok.com

  • St. Louis, MO The St. Louis BSD User Group (STLBSD) has just formed on July 20, 2000 to promote BSD operating systems in the St. Louis area. We have strong ties to the 10 year old St. Louis Unix Users Group (SLUUG) and expect to be a positive force within our community. Our membership is open to anyone interested in learning more about BSD, several mailing lists are available through our website.

  • San Diego, California San Diego BSD Users Group for users of FreeBSD, OpenBSD and NetBSD. The meeting is first Thursday of every month at Borders Bookstore in Mission Valley Shopping Center. More information can be found here

  • North San Francisco Bay Area The BABUG (Bay Area BSD Users Group) has monthly meetings, alternating between San Francisco and Berkeley. Those interested in attending should visit the web site or send mail to the BABUG Web Master

  • Silicon Valley, CA The SVBUG (Silicon Valley BSD User Group), a forum for BSD and BSD embedded systems, meets on the First Thursday of the month. Meetings are held at the Carl's Jr. on First Street and Trimble Road in San Jose, California. For details on event or what's going on visit the website or send a message to webmaster@svbug.com.

  • The Tampa Florida users group is now being formed. Interested parties can join the mailing list by sending mail to bsd-tug-request@bangheadhere.org with subscribe in the body.

  • Greater Toronto Area, Ontario: The GTABUG usergroup welcomes all BSD users. Monthly meetings give attendees a chance to share ideas, discussion, and information. Installathons and other events help preach the good news of BSD to the community. Come drop by for a meeting!

  • Tucson AZ TFUG: Tucson Free Unix Group, Arizona.

  • Utah SLLUG-BUG is a BSD UNIX User Group affiliated with the Salt Lake Linux User Group (SLLUG). We meet in concert with SLLUG, since the BSD and Linux communities have so much in common. We meet on the third Wednesday of each month, check the web page for details.

  • Vancouver, BC The VanBUG (Vancouver BSD Users Group) is a group of volunteers who are passionate about FreeBSD, NetBSD, and OpenBSD. Their current goal is to raise awareness and also provide local assistance as much as we can.

  • Washington DC (DC Metropolitan Area) FreeBSD User Group is now forming. Please contact Richard Cramer, Sytex Access Ltd. at 703-425-2515, or preferred, email at rcramer@sytex.net to be put on a member distribution list. Initial meeting to be held in May.

  • Wichita, Kansas: A new FreeBSD users group has been created in Wichita, Ks. We are fairly new and working on our site, but we wanted to get it up as soon as we had it available. We do not currently meet. Visit our site http://wafug.dynip.com or E-mail the group organizer (ben177@yahoo.com) for more information!

  • Windsor, Ontario The Windsor Unix Users Group (Windsor, Ontario, Canada) covers BSD, Solaris, SCO, and others. This is not specifically a FreeBSD user group, but we do already have members running FreeBSD. The group operates a mailing list (wuug-list@unixpower.org). More information can be found at http://www.wuug.org/.

  • Wisconsin FreeBSD-Milwaukee Wisconsin meets occasionally and has a mailing list: freebsd-mke-l@ns.sol.net. send mail to freebsd-mke-l-request@ns.sol.net to subscribe.

Rest of the world

  • Ibaraki, Japan The Daibou East *BSD Users Group (DEBUG) is now forming for *BSD users in Tsukuba area.

  • Indonesia The Jogja FreeBSD Users' Group is based in Yogyakarta City, Indonesia. Send email to 22961476@students.ukdw.ac.id for more information.

  • Israel The Israeli BSD Users Group is an effort to promote the use of *BSD throughout the country, and to act as a center of information for all BSD users. It is currently run by FreeBSD users, but all users of bsd Variants are welcome aboard. We have a mailing list, hosted at bsd-il@osem.co.il. To subscribe, simply send mail to majordomo@osem.co.il, with the line "subscribe bsd-il" as the message body.

  • Kansai, Japan The Kansai *BSD User's Group, K*BUG (sorry for Japanese only), was established on November 13, 1999. It is expected to promote communication of any of the BSD variants' users. Some of its activities are to hold friendly parties of the members, and to hold seminars covering wide variety of topics. Please mail here ( kbug-admin@kbug.gr.jp ).

  • New Zealand The New Zealand FreeBSD User's group is located in Wellington. No meetings have been scheduled yet.

  • Sao Paulo, Brazil The FUG_SP_BR (Brazilian FreeBSD User Group) is a Portuguese language oriented user group intended to help Brazilian FreeBSD users to find support and articles on and about FreeBSD in the Portuguese language. The group meets in Sao Paulo, Brazil, every month. To join FUG_SP_BR mailing list, send a blank message to fug_sp_br-subscribe@yahoogroups.com

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

  • The XFree86 Project provides 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 MS-Windows software on Intel based Unix systems such as FreeBSD, NetBSD and Linux.

Hardware

  • The comp.answers pc-hardware-faq is a great reference for people building their own machines.
  • Laptop users looking for PCCARD (aka PCMCIA) support not already provided in the FreeBSD base distribution should see the PAO distribution page for the latest and greatest experimental laptop support.
  • Intel Secrets -- What Intel Doesn't Want You To Know - lots of information about Intel chips.
  • Aad Offerman's Chip List - reference material on chips used in PC clones.
  • ASUS makes motherboards that work well with FreeBSD.

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.
  • Linux is another free Unix-like system.
  • Lites is a 4.4 BSD Lite based server and emulation library that provides free unix functionality to a Mach based system.
  • xMach is a Lites and Mach4 derivative designed to be small and efficient with extended functionality.
  • The GNU HURD project is another effort to develop a free Unix-like operating system.
&footer; diff --git a/en/where.sgml b/en/where.sgml index c4e9c1b009..0aa72e78cb 100644 --- a/en/where.sgml +++ b/en/where.sgml @@ -1,138 +1,137 @@ + %includes; ]> - &header;

Release Information

Detailed descriptions of past, present, and future releases. Look here first to determine what the latest version of FreeBSD is.

Installing FreeBSD

There are many options for installing FreeBSD, including installation from CDROM, floppy disk, an MS-DOS partition, magnetic tape, anonymous ftp, and NFS. Please read through the installation guide before downloading the entire FreeBSD distribution. If you are installing on a machine connected to the Internet, you may only need to download a single installation disk image!

Distribution Sites

The official sources for FreeBSD are:

If you plan on getting FreeBSD via ftp, please check the listing of mirror sites in the handbook to see if there is a site closer to you. For more information about past, present and future releases in general, please visit the release information page.

If you're interested in a purely experimental snapshot release of FreeBSD-current (AKA 5.0-current), aimed at developers and bleeding-edge testers only, then please see the daily snapshot server FTP site.

Applications and Utility Software

The Packages collection

The FreeBSD packages collection is a diverse collection of utility and application software that has been ported to FreeBSD. The packages are pre-compiled binaries ready to drop into your system and run.

The Ports collection

The Ports collection is like the packages collection, but the necessary patches and makefiles to compile the source code are provided instead of compiled binaries. For software with important configuration that must be done at compile time, the "port" version may be more useful than the "package" version.

For information about how you can contribute your favorite piece of software to the port collection, have a look at Porting applications and Contributing to FreeBSD in the FreeBSD handbook.

Commercial software

Beginning with FreeBSD Release 2.0.5, FreeBSD includes demo versions of some commercial as well as some shareware products. In addition to the demos available in the FreeBSD distribution, a number of other commercial vendors offer software products specifically for FreeBSD.

&footer; diff --git a/en/y2kbug.sgml b/en/y2kbug.sgml index e49eb83445..60bd95fcda 100644 --- a/en/y2kbug.sgml +++ b/en/y2kbug.sgml @@ -1,402 +1,401 @@ + %includes; ]> - &header;

As management understanding of the Year 2000 problem (aka, "The Millennium Bug") increases, more and more companies are demanding official statements from the vendors of their hardware and software as to how their product will handle the year 2000 date rollover.

Organizations that use unix and unix like operating systems such as FreeBSD are already one step ahead of the problem. FreeBSD will properly maintain time long after year 2000 passes.

Background information

(This section based on the text from the Linux Y2K compliance page)

As with all Unix and Unixlike operating systems, time and dates in FreeBSD are represented internally as the number of seconds since the 1st of January 1970 (the Unix "epoch"). Currently, that figure is stored as a 32 bit integer, and will run out part way through 2038. By then we should (hopefully) be using a counter of 64 bits (or greater) which should be good until the end of the universe.

Note that the OS being Y2K compliant will not fix errant applications that are not Y2K compliant.

Note also that the OS expects to read the current date and time from the CMOS clock of your computer. Not all of these devices correctly handle the year 2000. You are advised to test each platform individually to ensure that your hardware clock behaves correctly when going from 1999 to 2000, and that it correctly interprets the year 2000 as a leap year.

What you can do

FreeBSD will continue to properly maintain time well into the next century. Third party applications, however, might not. Your best defense against year 2000 issues is a good offense. Listening to stories claiming the coming meltdown of the world as we know it are not the way to solve the millennium bug. Nor is waiting until the last minute. The FreeBSD Project recommends that your organization apply sound system administration principles as the millennium approaches.

There are tests that you can perform to see how your system will respond. Set your clock to a few minutes before midnight on New Year's Eve and watch the system time. Your system should display the year as 2000 and not 1900. If the year is displayed incorrectly, then you will have plenty of time to update your hardware. Operating your organizations information systems under their normal daily load with the clock set forward can provide valuable insight into your vulnerability to year 2000 issues.

Important: Do not do this on a live production system. You may confuse any applications you have which rely on dates (billing systems, backup regimes, and so on). Always conduct tests like this on development systems which can not affect any live data you may have.

FreeBSD Year 2000 Statement

"After extensive analysis and testing, we believe that FreeBSD is 100% Y2K compliant. In the unlikely event that something has been overlooked, we will do our best to fix it as soon as possible."

David Greenman
Principal Architect, The FreeBSD project

Fixed problems

The following Y2K problems have been identified and fixed in FreeBSD.

misc/1380
Several programs have a hardcoded 19%d in responses for the year. Affected programs include: yacc, ftpd, and make. [Fixed: yacc v1.2 1999/01/18; ftpd v1.7 1996/08/05; make v1.4 1996/10/06; fixes in FreeBSD-2.2 and above]
conf/1382
The sed script in /etc/rc.local that builds the host/kernel ID line for the message of the day relies on the year not going past 1999. [Fixed v1.21 1996/10/24; fixes in FreeBSD-2.2 and above]
misc/3465
The etc/namedb/make-localhost command generates the DNS serial number as YYMMDD. In the year 2000, this will be generated as 1YYMMDD. [Fixed v1.2 1997/08/11; fixes in FreeBSD-2.2.5 and above]
gnu/4930 and gnu/8321
groff tmac macros have hardcoded 19 for generating some dates. [Fixed: tmac.e v1.3 1998/12/06; doc-common v1.10 1999/01/19; fixes in FreeBSD-3.1 and above]
bin/9323
In its obsolescent form, touch doesn't treat the two digit year specification correctly. Years in the range 00-68 are treated as 1900-1968 instead of 2000-2068. [Fixed v1.7 1999/01/05; fixes in FreeBSD-3.1 and above]
xntpd/parse/util/dcfd.c
The leap year calculations for the number of days in a year, and the conversion of DCF77 time to seconds since the Epoch were wrong. These errors affected all years. [Fixed v1.6 1999/01/12; fixes in FreeBSD-3.1 and above]
tar/getdate.y
Function Convert() was hard-coded for two digit years in range 70-99. Now adjusted to allow two digit years for 1970-2069. The function does not allow for century non-leap years - y2k1 alert! [Fixed v1.4 1999/01/12; fixes in FreeBSD-3.1 and above]
fetch/http.c
The HTTP protocol includes an obsolete date format which uses a two-digit year. Previous versions of fetch would interpret all such dates in the 1900s; subsequent to this revision, the pivot described in RFC 2068 is employed, which causes two-digit years to be interpreted as always belonging to the current century unless they would be 50 or more years in the future. Since the HTTP servers which use this obsolete format are no longer widespread, this is not expected to have a significant impact. [Fixed v1.24 1999/01/15; fixes in FreeBSD-3.1 and above]
misc/9500
The `edithook' script in the CVSROOT directory uses a raw tm_year and will therefore display 01/01/100 for 2000-JAN-01. [Fixed v1.2 1999/01/17; not relevant to FreeBSD releases]
bin/9501
Several cvs contrib files are not Y2K compliant. The log.pl and sccs2rcs.csh scripts prepend `19' to the year resulting in a display of 19100 for 2000. The log_accum.pl script uses a two digit year in one place and in another place assumes that the tm_year is year within century rather than years since 1900. [Fixed: log.pl v1.2 1999/01/15; sccs2rcs.csh v1.3 1999/01/15; fixes in FreeBSD-3.1 and above]
bin/9502
The groff number register `yr' is assigned from a (struct tm).tm_year and therefore represents the number of years since 1900, not the year within the century (see definition in troff/input.cc). [Fixed, now set mod 100, troff/input.cc V1.2 1999/06/03; fixed in FreeBSD-3.3]
bin/9503
PicoBSD's simple_httpd uses a raw tm_year and will therefore display 01/01/100 for 2000-JAN-01. [Fixed v1.2 1999/01/16; fixes in FreeBSD-3.1 and above]
bin/9505
Adduser uses a raw tm_year and will therefore display 100/01/01 for 2000-JAN-01. [Fixed v1.42 1999/01/15; fixes in FreeBSD-3.1 and above]
bin/9506
Cron uses a raw tm_year and will therefore display 100 for 2000. [Fixed v1.7 1999/01/16; fixes in FreeBSD-3.1 and above]
bin/9507
tcpslice(8) uses a raw tm_year and will therefore display 100y01m01d... for 2000-JAN-01. For compatibility, use a two-digit year until 2000.[Fixed v1.8 1999/01/20; fixes in FreeBSD-3.1 and above]
bin/14472
Date command does not take thousand/hundred digits. [Fixed v1.31 1999/11/10]
misc/14511
Chpass has a problem using 00 for expiration year.
bin/15852 and gnu/16045 and bin/16207
Groff predefined \*(DT [\*(td] string has Y2K bug. [Fixed with import of version 1.15 2000/01/12]
bin/15872
at(1) has a problem with valid time specifications if tm_year is 100, reports `garbled time'.
misc/16238
KerberosIV install does not work properly because there is a hard-wired expiration date of 12/31/99 in the Kerberos source for the ticket granter. [Fixed v1.24 1999/09/19]

Problematic applications

ports/7681
TkDesk 1.0 uses a hardcoded 19 in the file listing window. A file with a date > 2000 is displayed with a year looking like "191xx" where xx is the last two numbers of the real date. This bug has been fixed in version 1.1. [Port updated 1998/10/10; fixes in FreeBSD-3.0 and above]
ports/9295
INN 1.7.2 suffers from 2 Y2K related problems. One occurs when pulling news (-f option to nntpget) and the other relates to the Expire header with relative dates past 2000. [Both INN ports upgraded to INN 2.2 1999/05/02; fixes in FreeBSD-3.2 and above]
ports/9298
Knews suffers from 2 Y2K related problems. One occurs during the generation of the NNTP NEWGROUPS command. The other occurs because knews doesn't think that 2000 is a leap year. Both are fixed in knews-1.0b.1. [Port updated 1999/01/07; fixes in FreeBSD-3.1 and above]
ports/9300
Nntp-t5 suffers from a Y2K problem during the generation of the NEWNEWS command. [Port patched 1999/01/05; fixes in FreeBSD-3.1 and above]
ports/11144
The tiff port has a hardcoded 19xx. While this is in the contrib section (for converting Sun rasterfile format to TIFF), and not installed by default, this should be patched. [Port patched 1999/04/18, followed by upgrade 1999/05/11; fixes in FreeBSD-3.2 and above]
ports/11145
The dgs port suffers from the same TIFF related problem as the tiff port. [contrib routine for converting Sun rasterfiles to TIFF] [Port patched 1999/04/18; fixes in FreeBSD-3.2 and above]
ports/13694
The slurp port has a problem generating a correctly formatted host file name when tm_year is greater than 100. [Port patched 1999/10/27; fixes in FreeBSD-3.3-STABLE and above]
ports/15477
wwwstat port has a hardcoded 19.
ports/15789
proftpd has a minor Y2K problem. [Port patched 1999/12/22]
ports/15820
sendfile has a problem not setting the atime and mtime properly for files sent after year 1999.
ports/15854
dclock uses localtime and in particular the references to tm_year do not take into account the year 2000. [Port patched 2000/01/04]
ports/15868
The reporting function of hylafax (xferstats) is not y2k compatible. [Port patched 2000/01/24]
ports/15926
A y2k bug in leafnode+ 2.9 considers incoming news articles with the (arguably bogus) Date: header like `Wed, 05 Jan 00 15:01:40 GMT' to be too old, so these incoming articles are dropped. [Fixed by upgrading port to version 2.10 2000/01/24]
ports/16062
Japanese e2ps port has hardcoded 19. [Port patched 2000/01/24]
ports/16073
nntp port 1.5.11.5 has Y2K related problems. [Port upgraded to version 1.5.12.2 2000/01/12]
ports/16167
This is a bug-fix release that corrects a y2k bug in INN 2.2.1 that will show up in the NEWNEWS and NEWGROUPS commands after 2000-01-01 00:00:00 when the date specified to the command is before 2000-01-01 00:00:00. [Port upgraded to version 2.2.2 2000/01/28]
NetHack 3.2.2 and earlier versions are not Y2K compliant (the score file used 2 digit years and will be corrupted if added to in the year 2000). [Port updated to version 3.2.3 2000/01/05]
Japanese mnews port has Y2K problems. [Port updated to version 1.22 1999/12/26]

More information

If you have further questions about FreeBSD's year 2000 compliance, or you have discovered an application running under FreeBSD that is not Y2K compliant, please contact the project at freebsd-bugs@FreeBSD.ORG.

&footer;