diff --git a/en/applications.sgml b/en/applications.sgml index 4ebaa6e909..c1eada3136 100644 --- a/en/applications.sgml +++ b/en/applications.sgml @@ -1,124 +1,133 @@ + %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 plus 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:

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 to 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 effect 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 0cc1dd4e58..aeb6405ebd 100644 --- a/en/auditors.sgml +++ b/en/auditors.sgml @@ -1,429 +1,438 @@ + %includes; ]> - + &header;

General Information

-Last Updated: $Date: 1999-03-27 15:43:32 $ +Last Updated: $Date: 1999-06-10 19:40:35 $

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.

ModuleAuditor(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 5b227c3971..51d12a9bb7 100644 --- a/en/availability.sgml +++ b/en/availability.sgml @@ -1,87 +1,96 @@ + %includes; ]> - + &header;

Availability of FreeBSD

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

Hardware requirements.

FreeBSD requires a PC-type personal computer running with an Intel, AMD, Cyrix, or compatible 386, 486, or Pentium CPU. You computer needs an ISA, EISA, VESA, or PCI bus. You will also need 5 megabytes of RAM to install FreeBSD (but 4 megabytes to run it after installation). For best performance, you should have 8 megabytes or more. 60MB of disk space is required for a minimal installation.

FreeBSD supports most popular Ethernet adaptors, SCSI controllers, IDE hard drives, multiport serial cards, CD-ROM drives, tape drives, sound cards, mice, and other hardware. See both the Frequently Asked Questions list and the &a.latest.not;release notes for complete information on supported hardware.

Where to get it.

You can get FreeBSD free via anonymous FTP from ftp://ftp.freebsd.org/pub/FreeBSD. You might also want to check a geographically close mirror site.

If you have a CD-ROM drive, you can get FreeBSD on CD-ROM for a modest price from Walnut Creek CDROM:

Walnut Creek CDROM
4041 Pike Lane, Suite F
Concord, CA 94520
USA
Phone: +1 925 674-0783
Phone: +1 800 786-9907
Fax: +1 925 674-0821
Email: info@cdrom.com

In addition to FreeBSD, the CD-ROM comes with hundreds of ready-to-run programs. It is backed by an unconditional money back guarantee.

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 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/docs.sgml b/en/docs.sgml index f5b647641b..fbe3718d39 100644 --- a/en/docs.sgml +++ b/en/docs.sgml @@ -1,272 +1,281 @@ + %includes; ]> - + &header;

FreeBSD in the Press

The press about FreeBSD.

Year 2000 Compatibility

This is the FreeBSD project's current statement about its Year 2000 compatibility.

Newsletter

The FreeBSD Newsletter, published and distributed free of charge by Walnut Creek CDROM.

FreeBSD Real-Quick (TM) Newsletter (RQN)

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

The FreeBSD Handbook

This is an evolving, comprehensive on-line resource for FreeBSD users. Please address comments and contributions to <freebsd-doc@FreeBSD.ORG>.

A Japanese translation of the handbook (EUC encoding) is also available.

Frequently Asked Questions (FAQ)

If you have a question, chances are that someone else has the same question. The most common of these have been compiled here in a brief question-answer format.

&i.new; We now offer a Russian translation and a Chinese translation of the FAQ.

A Japanese translation of the FAQ (EUC encoding) is also available.

Tutorials

Here lie assorted 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.

Additional Resources

www.FreeBSD.org is not the only place to get information on FreeBSD and various independent efforts have also produced a great deal of useful information on FreeBSD:

Books

Online documentation is useful, but any serious FreeBSD user should consider getting some of the books listed here. Most books that cover BSD systems apply well to 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, 4.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 Slackware, NetBSD, OpenBSD, Plan 9, SunOS 4.x, SunOS 5.x, ULTRIX 4.2, and XFree86.

This service is provided courtesy of Wolfram Schneider. There is another script available with the manual pages for FreeBSD 2.0 and XFree86 release 3.1, courtesy of Hinrich Eilts.

4.4BSD Documents

If you like reading BSD manuals online, here is a hypertext version of the 4.4BSD documents from /usr/share/doc, where you would find the documents on a FreeBSD machine (if the doc distribution was installed).

Info Documents

If you like reading FreeBSD Info documents online, here is a hypertext version of the Info documents from /usr/share/info, where you would find the Info documents on a FreeBSD machine (if the info distribution was installed).

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.

The FreeBSD Documentation Project

Daemon News

The industry leader in BSD news.

FreeBSD ezine

The FreeBSD 'zine is 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 cdcef76f1a..051b87a26b 100644 --- a/en/features.sgml +++ b/en/features.sgml @@ -1,96 +1,105 @@ + %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:

Naturally, since FreeBSD is an ongoing effort, you can expect newer features and higher levels of stability with each release.

What experts have to say . . .

``FreeBSD has an outline-structured visual configuration editor ... you can enter the configuration of every device the OS supports and can therefore get a successful installation on the first try almost every time. IBM, Microsoft, and others would do well to emulate FreeBSD's approach.''

---Brett Glass, Infoworld, April 8 1996.

&footer; + + diff --git a/en/includes.sgml b/en/includes.sgml index 9bf91a716e..a1aa2e87a1 100644 --- a/en/includes.sgml +++ b/en/includes.sgml @@ -1,61 +1,70 @@ - + '> '> &email@FreeBSD.ORG
©right;'> FreeBSD Home Page'> &title;Navigation Bar

&title;


Top Applications Support Documentation Vendors Search Index Top Top '>
&author;
&date;
'> '> '> + + diff --git a/en/index.sgml b/en/index.sgml index 0504446f3a..ae08dd4fc5 100644 --- a/en/index.sgml +++ b/en/index.sgml @@ -1,320 +1,329 @@ - + %includes; ]> The FreeBSD Project
FreeBSD: The Power to Serve

Select a server near you:

Language: Japanese, Spanish, Other

     

What is FreeBSD?

FreeBSD is an advanced BSD UNIX operating system for "PC-compatible" computers, developed and maintained by a large team of individuals.

Cutting edge features

FreeBSD offers advanced networking, performance, security and compatibility features today which are still missing in other operating systems, even some of the best commercial ones.

Powerful Internet solutions

FreeBSD makes an ideal Internet or Intranet server. It provides robust network services, even under the heaviest of loads, and uses memory efficiently to maintain good response times for hundreds, or even thousands, of simultaneous user processes. Visit our gallery for examples of FreeBSD powered applications and services.

Run a huge variety of applications

The quality of FreeBSD combined with today's low-cost, high-speed PC hardware makes FreeBSD a very economical alternative to commercial UNIX workstations. It is well-suited for a great number of both desktop and server applications.

Easy to install

FreeBSD can be installed from a variety of media including CD-ROM, floppy disk, magnetic tape, an MS-DOS partition, or if you have a network connection, you can install it directly over anonymous FTP or NFS. All you need is pair of blank, 1.44MB floppies and these directions.

FreeBSD is free

While you might expect an operating system with these features to sell for a high price, FreeBSD is available free of charge and comes with full source code. If you would like to try it out, more information is available.


To learn more about FreeBSD, register to receive the FreeBSD Newsletter, visit our gallery of FreeBSD related publications or FreeBSD in the press, and browse through this website!.

News
  Announcements
  In the Press
  More ...

Software
  Getting FreeBSD
  Release Information
  Ported Applications

Documentation
  For Newbies
  Handbook
  Tutorials
  FAQ
  Books
  Year 2000
  More...

Support
  Mailing lists
  Newsgroups
  User Groups
  Web Resources
  Security
  More...

Development
  Projects
  Bug Reports
  CVS Repository

Vendors
  Software
  Hardware
  Consulting
  Misc

This Site
  Site Map
  Search
  More ...

  Search for:
[FreeBSD Mall] [Sponsored by Walnut Creek CD-ROM] [Sponsor of Unix Guru Universe] [Powered by Apache] [Powered by FreeBSD]

Changes to the web site go live at 0400 PST every day.

+ $Date: 1999-06-10 19:40:40 $
Contact us
- $Date: 1999-06-08 22:06:31 $		 Copyright © 1995-1999 FreeBSD Inc.
All rights reserved.
+ + diff --git a/en/internet.sgml b/en/internet.sgml index a82d2aaf96..d3f3958c85 100644 --- a/en/internet.sgml +++ b/en/internet.sgml @@ -1,135 +1,144 @@ + %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

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:

FreeBSD makes an ideal platform for these and other Internet 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 development team is 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 b5d90e6c86..2d89ba8804 100644 --- a/en/mailto.sgml +++ b/en/mailto.sgml @@ -1,45 +1,54 @@ + %includes; ]> - + &header;

Questions about FreeBSD...

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

Questions about the contents of this WWW server...

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

Other FreeBSD Mailing Lists

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.

Snail mail, phone and fax

For CDROM orders: Walnut Creek CDROM
For commercial support: The FreeBSD Mall

Who Is Responsible for What

&footer; + + diff --git a/en/publish.sgml b/en/publish.sgml index d3aeb6eed0..dc74c94cc3 100644 --- a/en/publish.sgml +++ b/en/publish.sgml @@ -1,252 +1,261 @@ + %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.

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 Walnut Creek CDROM's "FreeBSD Complete" with installation guide, manual pages and 2 installation CDs inside.
This is Walnut Creek CDROM's "Installing & Running FreeBSD", a product which contained installation instructions and was shipped with each 2 CD set. It has since been replaced by the larger "FreeBSD Complete" book.
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 transtation 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.

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 "Jaunary", 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...

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

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.
questions@FreeBSD.ORG
Copyright © 1995-1997 FreeBSD Inc. - All rights reserved.
$Date: 1999-01-17 22:01:44 $
+ All rights reserved.
$Date: 1999-06-10 19:40:43 $ + + diff --git a/en/register.sgml b/en/register.sgml index 98e0311ca4..353151cef0 100644 --- a/en/register.sgml +++ b/en/register.sgml @@ -1,92 +1,101 @@ + %includes; ]> - + &header;
Register to receive the FreeBSD Newsletter and subscribe to 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/send-pr.sgml b/en/send-pr.sgml index da17b37402..cc669f4d7d 100644 --- a/en/send-pr.sgml +++ b/en/send-pr.sgml @@ -1,77 +1,86 @@ + %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/support.sgml b/en/support.sgml index ccb796712b..1e2f1fde84 100644 --- a/en/support.sgml +++ b/en/support.sgml @@ -1,552 +1,561 @@ + %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.

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.

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 xferred) 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) access.
  • 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

  • Denmark The Danish *BSD user group, BSD/DK, is being created. Send mail subscription request to bsd-dk-request@hotel.prosa.dk. No initial meeting planned yet.

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

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

  • 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

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

  • 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 Contact Ingrid Kast Fuller for more 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.

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

  • New Mexico FUUNM (Free Unix Users of New Mexico) meets on the 2nd Saturday of the month from 4:30-6:00pm at the Farris Engineering Center, room 141, University of new Mexico. This is not specifically a FreeBSD user group, but if you are in the area, your presence is welcome. The group operates a mailing list (fuunm@astro.phys.unm.edu). Contact Alan Lundin for more information.

  • New York NT D'Artagnan's FreeBSD Users Group.
  • 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.

  • Phoenix AZ The Phoenix BSD Users group is fully open for businness. I now have the mailing list setup and ready to go. If anyone else here is from the phoenix area please feel free to join in http://bsd.phoenix.az.us.

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

  • 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

  • San Francisco Bay Area BAFUG (Bay Area FreeBSD Users Group) meets semi-monthly at Silicon Reef. Those interested in attending should visit the web site or send mail to the mailing list

  • Seattle WA The Seattle FreeBSD Users Group (SeaFUG) meets on a monthly basis. Those interested in attending should vist the web site or contact Bill Swingle for more info.

  • 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. The first meeting is planned for mid May 1999.

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

  • 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 user's group has been created in Wichita, Ks. We are fairly new and working on our site, but I wanted to get it up as soon as we had it availble. 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) is now forming for *BSD, Solaris, SCO, etc. 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 by going to the web site for WUUG, which is located at http://unix.windsor.on.ca/

  • 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

  • Israel The Israeli BSD Users Group is an effort to promote the use of *BSD throught 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.

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

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. More information is available from the WINE FAQ.

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.
  • The FreeBSD hardware guide makes some specific recommendations for hardware that's known to 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.
  • The GNU HURD project is another effort to develop a free Unix-like operating system.
&footer; + + diff --git a/en/usergroups.sgml b/en/usergroups.sgml index 412de61f4d..f46e4cba69 100644 --- a/en/usergroups.sgml +++ b/en/usergroups.sgml @@ -1,552 +1,561 @@ + %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.

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.

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 xferred) 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) access.
  • 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

  • Denmark The Danish *BSD user group, BSD/DK, is being created. Send mail subscription request to bsd-dk-request@hotel.prosa.dk. No initial meeting planned yet.

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

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

  • 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

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

  • 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 Contact Ingrid Kast Fuller for more 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.

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

  • New Mexico FUUNM (Free Unix Users of New Mexico) meets on the 2nd Saturday of the month from 4:30-6:00pm at the Farris Engineering Center, room 141, University of new Mexico. This is not specifically a FreeBSD user group, but if you are in the area, your presence is welcome. The group operates a mailing list (fuunm@astro.phys.unm.edu). Contact Alan Lundin for more information.

  • New York NT D'Artagnan's FreeBSD Users Group.
  • 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.

  • Phoenix AZ The Phoenix BSD Users group is fully open for businness. I now have the mailing list setup and ready to go. If anyone else here is from the phoenix area please feel free to join in http://bsd.phoenix.az.us.

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

  • 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

  • San Francisco Bay Area BAFUG (Bay Area FreeBSD Users Group) meets semi-monthly at Silicon Reef. Those interested in attending should visit the web site or send mail to the mailing list

  • Seattle WA The Seattle FreeBSD Users Group (SeaFUG) meets on a monthly basis. Those interested in attending should vist the web site or contact Bill Swingle for more info.

  • 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. The first meeting is planned for mid May 1999.

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

  • 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 user's group has been created in Wichita, Ks. We are fairly new and working on our site, but I wanted to get it up as soon as we had it availble. 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) is now forming for *BSD, Solaris, SCO, etc. 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 by going to the web site for WUUG, which is located at http://unix.windsor.on.ca/

  • 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

  • Israel The Israeli BSD Users Group is an effort to promote the use of *BSD throught 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.

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

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. More information is available from the WINE FAQ.

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.
  • The FreeBSD hardware guide makes some specific recommendations for hardware that's known to 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.
  • 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 500a36958e..ed586dab43 100644 --- a/en/where.sgml +++ b/en/where.sgml @@ -1,129 +1,138 @@ + %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 interesting in a purely experimental snapshot release of FreeBSD-current (AKA 4.0-current), aimed at developers and bleeding-edge testers only, then please see the daily snapshot server FTP site. This site also contains daily snapshots of the 2.2-stable branch.

Applications and Utility Software

The Packages collection

The FreeBSD packages are 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 instead of compiled binaries, the necessary patches and makefiles to compile the source code are provided. 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 0b9e5e5c89..06ba124ef6 100644 --- a/en/y2kbug.sgml +++ b/en/y2kbug.sgml @@ -1,256 +1,265 @@ + %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 vulnerablility to year 2000 issues.

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]
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]
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]
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]
bin/9323
In its obsolescent form, touch doesn't treat the two digit year year specification correctly. Years in the range 00-68 are treated as 1900-1968 instead of 2000-2068.[Fixed v1.7 1999/01/05]
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]
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]
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]
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]
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]
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, input.cc V1.2 1999/06/03]
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]
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]
bin/9506
Cron uses a raw tm_year and will therefore display 100 for 2000. [Fixed v1.7 1999/01/16]
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]

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]
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]
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]
ports/9300
Nntp-t5 suffers from a Y2K problem during the generation of the NEWNEWS command.[Port patched 1999/01/05]
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]
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]

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; + +