diff --git a/en/advocacy/myths.sgml b/en/advocacy/myths.sgml index a07bcbe43e..ab4cfc2498 100644 --- a/en/advocacy/myths.sgml +++ b/en/advocacy/myths.sgml @@ -1,390 +1,390 @@ %includes; ]> &header;

As the BSD projects (FreeBSD, NetBSD, and OpenBSD) have grown in size, a number of persistent myths have grown up around them. Some of these are perpetuated by well meaning but misguided individuals, others by people pursuing their own agendas.

This page aims to dispel those myths while remaining as dispassionate as possible.

Note: Throughout this page, ``*BSD'' refers to all three of the BSD Projects. Where a myth or response is specific to a particular project it is indicated as such.
If you are aware of an omission or error on this page, please let the maintainer, Tom Rhodes <trhodes@FreeBSD.org> know.

Index

Myths

*BSD has a closed development model, it's more ``Cathedral'' than ``Bazaar''

Eric Raymond wrote an influential paper, ``The Cathedral and the Bazaar'' in which the Linux development model (and the model Eric used for fetchmail) is held up as an example of how to do ``open'' development. By contrast, the model employed by *BSD is often characterized as closed.

The implicit value judgment is that ``bazaar'' (open) is good, and ``cathedral'' (closed) is bad.

If anything, *BSD's development model is probably more akin to the ``bazaar'' that Eric describes than either Linux or fetchmail.

Consider the following;

Also, see this article written by Jordan Hubbard in Performance Computing, titled What is FreeBSD?


You cannot make your own distributions or derivative works of *BSD

You can. You just need to say in the documentation and source files where the code is derived from.

For example, PicoBSD is a tailored distribution of FreeBSD that fits on a floppy. It's great for turning a diskless 386 PC into a router or a network print server.

The Whistle Interjet is a ``network appliance'' that acts as a router, web server, mailhost (and other functionality), and can be configured using a web browser. The underlying operating system is FreeBSD, and Whistle have contributed many of their code enhancements back to the FreeBSD project (while keeping enough of them proprietary that they can stay in business).

The OpenBSD project started as a spinoff from the NetBSD project, and has since evolved its own distinctive approach.


*BSD makes a great server, but a poor - (Unix) desktop

+ (&unix;) desktop

*BSD makes a great server. It also makes a great desktop. Many of the requirements for a server (responsiveness under load, stability, effective use of system resources) are the same requirements as for a desktop machine.

*BSD has access to the same desktop tools (KDE, GNOME, windowmanagers) as Linux. And ``office'' applications such as WordPerfect or StarOffice work under BSD's Linux emulation layer.


The BSD codebase is old, outdated, and dying

While the BSD codebase may be more than 20 years old, it is neither outdated or dying. Many professional users like the stability that years of testing has provided FreeBSD.

Technological enhancements continue to be added to *BSD, including, but not limited to;


The *BSD projects are at war with one another, splinter groups form each week

No. While occasional advocacy may get a touch heated, the *BSD flavors continue to work with one another. FreeBSD's Alpha port was initially heavily based on the work done by the NetBSD team. Both NetBSD and OpenBSD used the FreeBSD ports collection to bootstrap their own port sets. FreeBSD and NetBSD both integrate security fixes first discovered by the OpenBSD team.

This cooperation extends to the commercial company BSDi, who graciously donated their DOS emulation layer to FreeBSD.

The FreeBSD and NetBSD projects separated more than five years ago. OpenBSD is the only new BSD project to split off in the last five years.

The *BSD projects cooperate in other areas as well. For example, the monthly publication DaemonNews is a collaborative effort by members of all three projects.


You can't cluster *BSD systems (parallel computing)

The following URLs should disprove this;

In addition to this, Tom Rhodes is currently writing an article designed to walk a user through setting up a Parallel Computing environment using FreeBSD and other utilities. Keep an eye out for this article in late 2002 early 2003.


There's no commercial support for *BSD

FreeBSD: The FreeBSD Commercial Consulting Page lists companies that offer commercial support for FreeBSD.

The FreeBSD Mall also offer commercial support, along with shirts, hats, books, software, and promotional items.

For training, one might try BSDMall.com, but they sell other items too, like shirts, hats, books and software! Definitely worth a look.

OpenBSD: The OpenBSD Commercial Consulting Page lists companies that offer commercial support for OpenBSD.


There are no applications for *BSD

The free software community started running on predominantly BSD systems(SunOS and similar). *BSD users can generally compile software written for these systems without needing to make any changes.

In addition, each *BSD project uses a ``ports'' system to make the building of ported software much easier.

FreeBSD: There are currently more than 6,000 applications ready to download and install in the FreeBSD ports collection. On both the i386 and Alpha, the Linux emulation layer will also run the vast majority of Linux applications.

NetBSD: The Linux emulation layer will run the vast majority of i386 Linux applications, and the majority of SunOS4 applications can be run on a SPARCStation.

OpenBSD: There are currently slightly more than 400 applications ready to download and install in the OpenBSD ports collection. The Linux emulation layer will also run the vast majority of i386 Linux applications, and the majority of SunOS4 applications can be run on a SPARCStation.

Both NetBSD and OpenBSD are able to use applications in FreeBSD's ports collection with minimal effort. Their lower number of ported applications reflects this.

It is true that most companies when porting to PC Unix will choose Linux first. Fortunately, *BSD's Linux emulation layer will run these programs (Acrobat, StarOffice, Mathematica, WordPerfect, Quake, Intel ICC compiler, Compaq's Alpha compiler ...) with few, if any, problems.

As a historical note, the first version of Netscape Navigator that ran on FreeBSD with Java support was the Linux version. Now you can also use a native FreeBSD version of Mozilla with a native Java plugin, all compiled conveniently from the ports!


*BSD uses the a.out executable format, which is outdated technology

FreeBSD: Quite a while ago (before 1998) FreeBSD used the a.out format by default. There were no pressing reasons to switch earlier. In particular, FreeBSD did not (and does not) have the problems building shared libraries that spurred the Linux conversion from a.out to ELF. As of FreeBSD version 3.0, FreeBSD uses the ELF executable format.

Check out the wonderful article that Tom Rhodes wrote about upgrading an a.out to ELF system, it has information on the way FreeBSD uses a.out and ELF, along with tons of other useful information. The html version can be found here: http://www.Pittgoth.com/~darklogik/aout/article.html, but its also available in the PDF (article.pdf), dvi (article.dvi), postscript (article.ps), sgml (article.sgml), and TeX (article.tex) versions. Just change the extension as appropriate.


*BSD is better than (insert other system)

This is user opinion only.


(insert some other system) is better than *BSD

This is user opinion only


Contributors

Members of the FreeBSD, NetBSD, and OpenBSD projects have contributed to this page;

Nik Clayton <nik@FreeBSD.ORG> Jordan Hubbard <jkh@FreeBSD.ORG>
Ian F. Darwin <ian@DarwinSys.com>
Adrian Filipi-Martin <adrian@ubergeeks.com>
Tom Rhodes <trhodes@FreeBSD.org
&footer diff --git a/en/applications.sgml b/en/applications.sgml index a5a37d8f17..76342b0fc6 100644 --- a/en/applications.sgml +++ b/en/applications.sgml @@ -1,147 +1,147 @@ + %includes; ]> &header;

Experience the possibilities with FreeBSD

-

FreeBSD can handle nearly any task you would expect of a UNIX +

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


FreeBSD is a true open system with full source code.

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

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


FreeBSD runs thousands of applications.

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

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


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

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

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

What experts have to say . . .

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

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

&footer; diff --git a/en/copyright/daemon.sgml b/en/copyright/daemon.sgml index 47b6e9d66d..9f8db83601 100644 --- a/en/copyright/daemon.sgml +++ b/en/copyright/daemon.sgml @@ -1,71 +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 + 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 beanie daemon. 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/docs.sgml b/en/docs.sgml index 47d2659e15..167f18f45f 100644 --- a/en/docs.sgml +++ b/en/docs.sgml @@ -1,618 +1,618 @@ + %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 (faq)
Frequently Asked Questions, and answers, covering all aspects of FreeBSD.

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

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

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

Chapter 2 of "The Design and Implementation of the 4.4BSD Operating System" (design-44bsd)
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" (corp-net-guide)
Donated by Addison-Wesley, provides an in-depth look at using FreeBSD to provide printing services to Windows, NT, and Novell hosts.

The FreeBSD Documentation Project Primer for New Contributors (fdp-primer)
Everything you need to know in order to start contributing to the FreeBSD Documentation Project.

Articles

The Roadmap for 5-STABLE (5-roadmap)
Describes medium-term development and release engineering plans leading to the 5-STABLE branch point.

Integration of Checkpoint VPN-1/Firewall-1 and FreeBSD IPsec (checkpoint)
How to configure Checkpoint VPN-1/Firewall-1 and FreeBSD IPsec.

The Committer's Guide (committers-guide)
Introductory information for FreeBSD committers.

Console Server Tutorial (console-server)
How to setup a FreeBSD based console server with a cheap multi-port serial card.

Contributing to FreeBSD (contributing)
How to contribute to the FreeBSD Project.

The List of FreeBSD Contributors (contributors)
A list of organizations and individuals who have helped enhance FreeBSD.

Setting up a CVS repository - The FreeBSD way (cvs-freebsd)
How to set up a CVS repository that uses the same CVSROOT infrastructure as the FreeBSD project.

CVSup Advanced Points (cvsup-advanced)
An article with some tips about the subtleties of CVSup.

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

Creating a diskless X server (diskless-x)
How to create a diskless X server.

The Euro symbol on FreeBSD (euro)
How to configure FreeBSD and related applications to display the new Euro symbol.

Explaining BSD (explaining-bsd)
An answer to the question ``What is BSD?''

FreeBSD From Scratch (fbsd-from-scratch)
How to automatically compile, install and configure a system from scratch (i.e. to an empty file system), including your favorite ports.

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

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

Formatting media on FreeBSD (formatting-media)
How to slice, partition, and format fixed and removable media on FreeBSD.

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

Working with Hats (hats)
A committer's guide to working with ``hats'' (other committers with authority over specific areas of FreeBSD).

Mirroring FreeBSD (hubs)
The all in one guide for mirroring the FreeBSD website, CVSup servers, FTP servers, and more.

Independent Verification of IPsec Functionality in FreeBSD (ipsec-must)
A method for experimentally verifying IPsec functionality.

Java, and Jakarta Tomcat (java-tomcat)
Information on setting up Java and Jakarta Tomcat on a FreeBSD system.

FreeBSD on Laptops (laptop)
Information about running FreeBSD on a laptop.

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

Using FreeBSD with other operating systems (multi-os)
How to install FreeBSD alongside one or more different operating systems on the same computer.

FreeBSD First Steps (new-users)
- For people coming to FreeBSD and Unix for the first + For people coming to FreeBSD and &unix; for the first time.

Pluggable Authentication Modules (pam)
A guide to the PAM system and modules under FreeBSD.

FreeBSD Problem Report Handling Guidelines (pr-guidelines)
Recommended practices for handling FreeBSD problem reports.

Writing FreeBSD Problem Reports (problem-reports)
How to best formulate and submit a problem report to the FreeBSD Project.

Programming Tools on FreeBSD
This document has moved into The Developer's Handbook.

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

FreeBSD Release Engineering (releng)
Describes the approach used by the FreeBSD release engineering team to make production quality releases of the FreeBSD Operating System. It describes the tools available for those interested in producing customized FreeBSD releases for corporate rollouts or commercial productization.

FreeBSD Release Engineering for Third Party Packages (releng-packages)
Describes the approach used by the FreeBSD release engineering team to produce a high quality package set suitable for official FreeBSD release media. This document is a work in progress, but eventually it will cover the process used to build a clean package set on the FreeBSD.org "Ports Cluster", how to configure any other set of machines as a ports cluster, how to split up the packages for the release media, and how to verify that a package set is consistent.

Serial and UART devices (serial-uart)
Detailed information about the use of serial ports on FreeBSD, including several multi-port serial cards.

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

Storage Devices (storage-devices)
Detailed information about using storage devices with FreeBSD, including ESDI disks, and SCSI disks, tape drives, and CDROM drives.

Bootstrapping Vinum: A Foundation for Reliable Servers (vinum)
A gentle introduction to failure-resilient servers and step-by-step instructions for building one with Vinum.

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

Zip-drives and FreeBSD (zip-drive)
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, 4.4, 4.5, 4.6, 4.7, 4.8, 4.x-stable, 5.0, 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, HP-UX, 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

Articles

Links

In the real world...

FreeBSD in the Press

Articles in the press about FreeBSD.

Newsgroups

The following newsgroups contain discussion pertinent to FreeBSD users:

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.

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.

The O'Reilly Network BSD Dev Center

The BSD Dev Center includes two regular columns on FreeBSD, featuring tips and tutorials.

&footer; diff --git a/en/internet.sgml b/en/internet.sgml index a6fb01f081..371d12a623 100644 --- a/en/internet.sgml +++ b/en/internet.sgml @@ -1,161 +1,161 @@ + %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 +

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 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/publish.sgml b/en/publish.sgml index e3b3e71f29..65c761b405 100644 --- a/en/publish.sgml +++ b/en/publish.sgml @@ -1,620 +1,620 @@ + %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

book cover A 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).
book cover (Japanese FreeBSD book with 2.0.5, titled "FreeBSD: Fun and easy Installation")
book cover (Japanese FreeBSD book with 2.0.5, titled "FreeBSD Introductory Kit")
book cover This is BSDi's "The Complete FreeBSD" with installation guide, manual pages and installation CDs inside.
book cover This book was recently published (early 1997) in Taiwan. Its title is "FreeBSD: introduction and applications" and the author is Jian-Da Li.
book cover 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.
book cover The "Personal Unix Starter Kit - FreeBSD" from ASCII. Includes - history of Unix, a guide to build a Japanese documentation + 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.
book cover 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,-.
book cover 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.
book cover 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.
book cover 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.
book cover 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.
book cover Onno W Purbo, Dodi Maryanto, Syahrial Hubbany, Widjil Widodo: Building Internet Server with FreeBSD (in Indonesia Language), published by Elex Media Komputindo, 2000.
book cover The FreeBSD Handbook 1st Edition is a comprehensive FreeBSD Tutorial and reference. It covers installation, day-to-day use of FreeBSD, and much more. April 2000, BSDi. ISBN 1-57176-241-8
book cover 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
book cover The FreeBSD Handbook 2nd Edition is a comprehensive FreeBSD Tutorial and reference. It covers installation, day-to-day use of FreeBSD, and much more. November 2001, Wind River Systems. ISBN 1-57176-303-1
book cover "The FreeBSD Corporate Networker's Guide" Mittelstaedt, Ted. Addison Wesley, 2000.
There are two printings: the first has disk 1 of FreeBSD 4.2, the second has disk 1 of FreeBSD 4.4. 400 pages. The Japanese translation was published in 2001.
The Networker's Guide covers integration of FreeBSD into typical corporate networks with special emphasis on interoperation with Windows 95/98/ME/NT/2K.
English version: 2000, Addison Wesley. ISBN 0-201-70481-1
Japanese version: 2001, Pearson Education Japan. ISBN 4-89471-464-7
book cover "FreeBSD, An Open-Source Operating System for Your Personal Computer", Annelise Anderson.
An introduction to FreeBSD for users new to both FreeBSD and UNIX. This book includes a 4.4 installation CD-ROM and covers everything you need to know about installation of the system and third-party software; getting sound, X Window, your network, and printing working; building your own kernel; and upgrading. Second Edition. December 2001, The Bit Tree Press. ISBN 0-9712045-1-9
Absolute BSD book cover Absolute BSD. This book discusses management of FreeBSD-based servers in high-performance enterprise environments. June 2002, No Starch Press. ISBN 1-886411-74-3

CDROMs

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

CD cover 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.
CD cover This is the original 4.4 BSD Lite2 release from UC Berkeley, the core technology behind much of FreeBSD.
CD cover The first of Laser5's "BSD" series. Contains FreeBSD-2.0.5R, NetBSD-1.0, XFree86-3.1.1 and FreeBSD(98) kernel.
CD cover 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).
CD cover This is the Laser5 Japanese edition of the FreeBSD CDROM. It is a 4 CD set.
CD cover 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.
CD cover 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.
CD cover 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.
CD cover 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.
CD cover 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.
CD cover 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.
CD cover The FreeBSD 2.0.5 release CD. This was the first CD to feature Tatsumi Hosokawa's daemon artwork.
CD cover The FreeBSD 2.1 release CD. This was the first CD release on the 2.1 branch (the last being 2.1.7).
CD cover The FreeBSD 2.1.5 release CD.
CD cover The FreeBSD 2.1.6 release CD.
CD cover 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.
CD cover 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
CD cover An early release SNAPshot of 2.2 (done before 2.2.1 was released).
CD cover The FreeBSD 2.2.1 release CD. This was the first CD on the 2.2 branch.
CD cover The FreeBSD 2.2.2 release CD.
CD cover The FreeBSD 3.0 snapshot CD.
CD cover 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...
CD cover FreeBSD Toolkit: Six disc set of resources to make your FreeBSD experience more enriching.
CD cover FreeBSD Alpha 4.2 - The full version of the DEC Alpha 64-bit UNIX operating system.
CD cover FreeBSD 4.2: The full version of the PC 32-bit UNIX operating system.
CD cover FreeBSD 4.2 CD-ROM. Lehmanns CD-ROM Edition. January 2001, 4 CD-ROMs. Lehmanns Fachbuchhandlung. Germany. ISBN 3-931253-72-4.
CD cover FreeBSD 4.3 RELEASE CDROM. April 2001, Wind River Systems. ISBN 1-57176-300-7.
CD cover FreeBSD Toolkit: Six disc set of resources to make your FreeBSD experience more enriching. June 2001, Wind River Systems. ISBN 1-57176-301-5.
CD cover FreeBSD 4.4 CD-ROM. Lehmanns CD-ROM Edition. November 2001, 6 CD-ROMs in Jewelcase. Lehmanns Fachbuchhandlung. Germany. ISBN 3-931253-84-8.
CD cover FreeBSD 4.4 RELEASE CDROM. Wind River Systems. September 2001. ISBN 1-57176-304-X.
CD cover FreeBSD 4.5 RELEASE CDROM. February 2002, FreeBSD Mall Inc. ISBN 1-57176-306-6.

Magazines

magazine cover Cover of Korean UNIX magazine, May 1997 issue. Also included FreeBSD 2.2.1 with cover CDs.
magazine cover UNIX User Magazine November 1996 issue. Also included FreeBSD 2.1.5 on cover CD.
magazine cover 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.
magazine cover Quality Unix for FREE, by Brett Glass in Sm@rt Reseller Online September 1998
magazine cover 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

newletter cover This is issue #1 of the FreeBSD Newsletter, published and distributed free of charge by Walnut Creek CDROM.
newsletter cover This is issue #2 of the FreeBSD Newsletter, published and distributed free of charge by Walnut Creek CDROM.
&footer; diff --git a/en/support.sgml b/en/support.sgml index 7a0480daf1..b822c253ff 100644 --- a/en/support.sgml +++ b/en/support.sgml @@ -1,1059 +1,1059 @@ + %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.

To get an up to the minute view of the mailing lists available or to subscribe to a mailing list, use FreeBSD.org's Mailman web interface. All mailman lists are available in a digest format and have threaded archives available. See the individual list's web page for details.

Several non-English mailing lists are also available:

If you create other FreeBSD mailing lists, let us know about them.

Newsgroups

There are a few FreeBSD specific newsgroups, along with numerous other newsgroups on topics of interest to FreeBSD users, though the mailing lists remain the most reliable way to get in touch with the FreeBSD developers. For miscellaneous FreeBSD discussion, see comp.unix.bsd.freebsd.misc. For important announcements, see comp.unix.bsd.freebsd.announce.

The BSD Usenet News Searcher have archives of all BSD-related Usenet newsgroups from June 1992 onwards.

IRC

While #freebsd channels exist on various IRC networks, the FreeBSD project does not control them or endorse IRC as a support medium. You may be ignored, insulted, or kicked out if you ask questions on any channel in IRC, though you may have slightly better luck in channels named #freebsdhelp where such exist. If you want to try these or any other channels on IRC, it is nonetheless at your own risk and any complaints about conduct on those channels should not be directed to the FreeBSD project. See also the FAQ entry for more information.

WEB Resources

Problem Report Database

Current FreeBSD problem reports are tracked using the GNATS database.

A FreeBSD problem report (PR) is not necessarily a bug with FreeBSD itself. In some cases it may be reporting a mistake in the documentation (which could be a simple typo). In other cases it may be a 'wishlist' item that the submitter would like to see incorporated in to FreeBSD. In many cases a PR contains a port which has been prepared for inclusion in the FreeBSD Ports and Packages collection.

Problem reports start 'open', and are closed as the issue they report is resolved. In addition, each PR is assigned a unique tracking ID to ensure that it is not lost. Many FreeBSD changes include the tracking ID of the PR that prompted the change.

Problem reports may also be submitted to the development team using the send-pr(1) command on a FreeBSD system, or by sending an email message to freebsd-bugs@FreeBSD.ORG. Please note that send-pr is preferred since messages sent to the mailing list are not tracked as official problem reports, and may get lost in the noise!

Before submitting a problem report, you might find it useful to read the Writing FreeBSD Problem Reports article. This article describes when you should submit a problem report, what you are expected to include in one, and what the best way to submit your problem report is. Some useful background information is also contained in the Problem Report Handling Guidelines article.

CVS Repository

CVS (the Concurrent Version System) is the tool we use for keeping our sources under control. Every change (with accompanying log message explaining its purpose) from FreeBSD 2.0 to the present is stored here, 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:

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

User Groups

FreeBSD's widespread popularity has spawned a number of user groups around the world. If you know of a FreeBSD user group not listed here, let us know about it.

Australia

Europe

North America

Rest of the world

FreeBSD Development Projects

In addition to the mainstream development path of FreeBSD, a number of developer groups are working on the cutting edge to expand FreeBSD's range of applications in new directions.

FreeBSD Security Guide

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

Commercial Consulting Services

Whether you are just starting out with FreeBSD, or need to complete a large project, a consultant or two might be your answer.

-

General Unix Information

+

General &unix; Information

The X Window System

Hardware

Related Operating System Projects

&footer; diff --git a/en/usergroups.sgml b/en/usergroups.sgml index 7a0480daf1..b822c253ff 100644 --- a/en/usergroups.sgml +++ b/en/usergroups.sgml @@ -1,1059 +1,1059 @@ + %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.

To get an up to the minute view of the mailing lists available or to subscribe to a mailing list, use FreeBSD.org's Mailman web interface. All mailman lists are available in a digest format and have threaded archives available. See the individual list's web page for details.

Several non-English mailing lists are also available:

If you create other FreeBSD mailing lists, let us know about them.

Newsgroups

There are a few FreeBSD specific newsgroups, along with numerous other newsgroups on topics of interest to FreeBSD users, though the mailing lists remain the most reliable way to get in touch with the FreeBSD developers. For miscellaneous FreeBSD discussion, see comp.unix.bsd.freebsd.misc. For important announcements, see comp.unix.bsd.freebsd.announce.

The BSD Usenet News Searcher have archives of all BSD-related Usenet newsgroups from June 1992 onwards.

IRC

While #freebsd channels exist on various IRC networks, the FreeBSD project does not control them or endorse IRC as a support medium. You may be ignored, insulted, or kicked out if you ask questions on any channel in IRC, though you may have slightly better luck in channels named #freebsdhelp where such exist. If you want to try these or any other channels on IRC, it is nonetheless at your own risk and any complaints about conduct on those channels should not be directed to the FreeBSD project. See also the FAQ entry for more information.

WEB Resources

Problem Report Database

Current FreeBSD problem reports are tracked using the GNATS database.

A FreeBSD problem report (PR) is not necessarily a bug with FreeBSD itself. In some cases it may be reporting a mistake in the documentation (which could be a simple typo). In other cases it may be a 'wishlist' item that the submitter would like to see incorporated in to FreeBSD. In many cases a PR contains a port which has been prepared for inclusion in the FreeBSD Ports and Packages collection.

Problem reports start 'open', and are closed as the issue they report is resolved. In addition, each PR is assigned a unique tracking ID to ensure that it is not lost. Many FreeBSD changes include the tracking ID of the PR that prompted the change.

Problem reports may also be submitted to the development team using the send-pr(1) command on a FreeBSD system, or by sending an email message to freebsd-bugs@FreeBSD.ORG. Please note that send-pr is preferred since messages sent to the mailing list are not tracked as official problem reports, and may get lost in the noise!

Before submitting a problem report, you might find it useful to read the Writing FreeBSD Problem Reports article. This article describes when you should submit a problem report, what you are expected to include in one, and what the best way to submit your problem report is. Some useful background information is also contained in the Problem Report Handling Guidelines article.

CVS Repository

CVS (the Concurrent Version System) is the tool we use for keeping our sources under control. Every change (with accompanying log message explaining its purpose) from FreeBSD 2.0 to the present is stored here, 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:

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

User Groups

FreeBSD's widespread popularity has spawned a number of user groups around the world. If you know of a FreeBSD user group not listed here, let us know about it.

Australia

Europe

North America

Rest of the world

FreeBSD Development Projects

In addition to the mainstream development path of FreeBSD, a number of developer groups are working on the cutting edge to expand FreeBSD's range of applications in new directions.

FreeBSD Security Guide

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

Commercial Consulting Services

Whether you are just starting out with FreeBSD, or need to complete a large project, a consultant or two might be your answer.

-

General Unix Information

+

General &unix; Information

The X Window System

Hardware

Related Operating System Projects

&footer; diff --git a/en/y2kbug.sgml b/en/y2kbug.sgml index 54c34c3a05..022530135d 100644 --- a/en/y2kbug.sgml +++ b/en/y2kbug.sgml @@ -1,253 +1,253 @@ + %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 +

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 Unix-like 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.

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]

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;