--- introduction.mm	2002/03/24 07:19:06	4.1
+++ introduction.mm	2003/05/18 00:29:56
@@ -1,12 +1,14 @@
 .\" This file is in -*- nroff-fill -*- mode
-.\" STATUS: review draft 4th edition
-.\" $Id: introduction.mm,v 4.1 2002/03/24 07:19:06 grog Exp $
+.\" STATUS: 4th edition
+.\" $Id: introduction.mm,v 4.23 2003/05/18 00:29:56 grog Exp $
 .Chapter \*[nchintro] "Introduction"
-FreeBSD is a free, state of the art operating system derived from AT&T's
-\fIUNIX\fP\| operating system.\*F
+FreeBSD is a free operating system derived from AT&T's \fIUNIX\fP\/ operating
+system.\*F
 .FS
 FreeBSD no longer contains any AT&T proprietary code, so it may be distributed
-freely.  See page \*[history] for more details.
+freely.  See page
+.Sref \*[history] \&
+for more details.
 .FE
 It runs on the following platforms:
 .Ls B
@@ -16,234 +18,264 @@
 .LI
 The Compaq/Digital Alpha processor.
 .LI
+64 bit SPARC machines from Sun Microsystems.
+.LI
 In addition, significant development efforts are going towards porting FreeBSD
-to other hardware, notably SPARC64 and PowerPC.
+to other hardware, notably the Intel 64 bit architecture and the IBM/Motorola
+PowerPC architecture.
 .Le
 This book describes the released versions of FreeBSD for Intel and Alpha
-processors.
+processors.  Current support for SPARC 64 processors is changing too fast for it
+to be practical to give details specific to this processor, but nearly
+everything in this book also applies to SPARC 64.
 .H2 "How to use this book"
-This book is divided into three parts:
+This book is intended for a number of different audiences.  It attempts to
+present the material without too many forward references.  It contains the
+following parts:
 .Ls
 .LI
-The first part, chapters \*[nchintro] to \*[nchextras], tells you how to install
-FreeBSD and what to do if things go wrong.
-.LI
-Chapters \*[nchxtheory] to \*[nchemulate] introduce you to life with FreeBSD,
-including setting up optional features, building custom kernels and keeping up
-to date with FreeBSD.
-.LI
-Chapters \*[nchnetintro] to \*[nchmicronet] introduce you to FreeBSD's rich
-network support.
+The first part, Chapters
+.Sref \*[nchintro] \&
+to
+.Sref \*[nchpostinstall] ,
+tells you how to install FreeBSD and what to do if things go wrong.
+.LI
+Chapters
+.Sref \*[nchunixref] \&
+to
+.Sref \*[nchprinters] \&
+introduce you to life with FreeBSD, including setting up optional features and
+system administration.
+.LI
+Chapters
+.Sref \*[nchnetintro] \&
+to
+.\" XXX .Sref \*[nchmicronet] \&
+.Sref \*[nchmta] \&
+introduce you to FreeBSD's rich network support.
+.LI
+Finally, Chapters
+.Sref "\*[nchxtheory]" \&
+to
+.Sref "\*[nchbuild]" \&
+look at system administration topics that build on all the preceding material.
 .Le
 In more detail, we'll discuss the following subjects:
 .Ls B
 .LI
 In the rest of this chapter, we'll look at what FreeBSD is, what you need to run
-it, and what resources are available:
-.LB 16p 0 0 0 \(rh
-.LI
-On page \*[features], we'll look at FreeBSD's features.
-.LI
-Starting on page \*[history], we'll look at how FreeBSD came to be.
-.LI
-On page \*[unixclones], we'll compare FreeBSD to other free UNIX-like operating
-systems.
+it, and what resources are available, including FreeBSD's features and history,
+how it compares to other free UNIX-like operating systems, other sources of
+information about FreeBSD, the world-wide FreeBSD community, and support for
+FreeBSD.  In addition, we'll look at the BSD's daemon emblem.
 .LI
-On page \*[docco], we'll look at other sources of information about FreeBSD.
-.LI
-On page \*[FreeBSD-community], we'll look at the world-wide FreeBSD community.
-.LI
-On page \*[support], we'll consider what kinds of support are available for
+.Sref "\*[chconcepts]" ,
+discusses the installation requirements and theoretical background of installing
 FreeBSD.
 .LI
-Finally, on page \*[bsdd], we'll look at the BSD's emblem, the dmon on the cover
-of this book.
-.Le
-.LI
-\*[chconcepts], discusses the installation requirements and theoretical
-background of installing FreeBSD.  You don't \fIreally\fP\| need to read this
-chapter, but it'll make you feel a whole lot more confident if you do.
-.LI
-\*[chthirded], describes the changes that have taken place in FreeBSD since the
-introduction of version 3.
-.LI
-\*[chquickinstall], presents a quick installation overview.  If you're
-reasonably experienced, this may be all you need to install FreeBSD.  Otherwise,
-read on...
-.LI
-In \*[chshareinstall], we'll look at the differences you will encounter if you
-install FreeBSD on a system which already contains another operating system.
-.LI
-In \*[chinstall], we'll walk through a typical installation.  Read this chapter
-if you are installing FreeBSD on a disk by itself.
-.LI
-\*[chpostinstall], explains the configuration you need to do after installation
-to get a complete functional system.
-.LI
-In \*[chdesktop], we'll look at the options FreeBSD gives you to set up a
-``desktop''.
-.LI
-\*[chports], describes the thousands of free software packages which you can
-optionally install on a FreeBSD system.
-.LI
-\*[chproblems], discusses what to do if you run into problems during or after
-installation.
-.LI
-FreeBSD offers a number of optional features.  We'll look at some of them,
-including support for multiprocessors and laptops, in \*[chextras].
-.LI
-In \*[chxtheory], we'll look at the theory behind getting X11 working.
-.LI
-\*[chunixref], presents a number of aspects of FreeBSD which are of interest
-to newcomers (particularly from a Microsoft environment), in particular the
-concepts of \fIusers\fP\| and \fIprocesses\fP.  We'll also consider the basics
-of using the \fIshell\fP, as well as the importance of timekeeping.
-.LI
-\*[chstarting], describes how to start and stop a FreeBSD system and all the
-things you can do to customize it.  In particular, we'll look at the more common
-configuration files and what they should contain.
-.LI
-\*[chfilesys], contains information about the FreeBSD directory structure and
-device names.  You'll find the section on device names (starting on page
-\*[devices]) interesting even if you're an experienced UNIX hacker.
-.LI
-\*[chdisks], describes how to format and integrate hard disks, and how to handle
-disk errors.
-.LI
-In \*[cdburn], we'll look at how to use FreeBSD to write CD-Rs.
+.Sref "\*[chquickinstall]" ,
+presents a quick overview of the installation process.  If you're reasonably
+experienced, this may be all you need to install FreeBSD.
+.LI
+In
+.Sref "\*[chshareinstall]" ,
+we'll look at preparing to install FreeBSD on a system that already contains
+another operating system.
+.LI
+In
+.Sref "\*[chinstall]" ,
+we'll walk through a typical installation in detail.
+.LI
+.Sref "\*[chpostinstall]" ,
+explains the configuration you need to do after installation to get a complete
+functional system.
+.LI
+.Sref "\*[chunixref]" ,
+presents a number of aspects of FreeBSD that are of interest to newcomers
+(particularly from a Microsoft environment).  We'll look at setting up a
+``desktop,'' the concept of \fIusers\fP and file naming.  We'll also consider
+the basics of using the \fIshell\fP and editor, and how to shut down the
+machine.
+.LI
+.Sref "\*[chunixadmin]" ,
+goes into more detail about the specifics of working with UNIX, such as
+processes, daemons, timekeeping and log files.  We'll also look at features
+unique to FreeBSD, including multiple processor support, removable I/O devices
+and emulating other systems.
+.LI
+.Sref "\*[chports]" ,
+describes the thousands of free software packages that you can optionally
+install on a FreeBSD system.
+.LI
+.Sref "\*[chfilesys]" ,
+contains information about the FreeBSD directory structure and device names.
+You'll find the section on device names (starting on page
+.Sref \*[devices] \/)
+interesting even if you're an experienced UNIX hacker.
+.LI
+.Sref "\*[chdisks]" ,
+describes how to format and integrate hard disks, and how to handle disk errors.
+.LI
+Managing disks can be a complicated affair.
+.Sref "\*[chvinum]" ,
+describes a way of managing disk storage.
+.LI
+In
+.Sref "\*[cdburn]" ,
+we'll look at how to use FreeBSD to write CD-Rs.
 .LI
 FreeBSD provides professional, reliable data backup services as part of the base
 system.  Don't ever let yourself lose data because of inadequate backup
-provisions.  Read all about it in \*[chtapes].
+provisions.  Read all about it in
+.Sref "\*[chtapes]" .
 .LI
-\*[chprinters], describes the BSD spooling system and how to use it both on
-local and networked systems.
-.LI
-\*[chbuild], discusses how to build a customized version of FreeBSD.
-.LI
-In \*[chcurrent], we'll discuss how to ensure that your system is always running
-the most appropriate version of FreeBSD.
-.LI
-FreeBSD can run software written for a number of other operating systems.  Read
-about it in \*[chemulate].
-.LI
-Starting at \*[chnetintro], we'll look at the Internet and the more important
-services.
-.LI
-\*[chnetsetup], describes how to set up local networking.
-.LI
-\*[chisp], discusses the issues in selecting an Internet Service Provider (ISP)
-and establishing a presence on the Internet.
-.LI
-\*[chmodems], discusses serial hardware and the prerequisites for PPP and SLIP
-communications.
-.LI
-In \*[chppp], we look at FreeBSD's two PPP implementations and what it takes to
-set them up.
-.LI
-In \*[chdns], we'll consider the use of names on the Internet.
-.LI
-Security is an increasing problem on the Internet.  In \*[chfirewall], we'll
-look at some things we can do to improve it.  We'll also look at \fIIP
-aliasing\fP, since it goes hand-in-hand with firewalls.
-.LI
-Networks sometimes become \fInotwork\fP\|s.  In \*[chnetdebug], we'll see what
-we can do to solve network problems.
-.LI
-\*[chnfs], describes Sun's classic system for sharing file systems between
-networked computers.
+.Sref "\*[chprinters]" ,
+describes the BSD spooling system and how to use it both on local and networked
+systems.
 .LI
-We'll look at the basic network access programs in \*[chbasics].
+Starting at
+.Sref "\*[chnetintro]" ,
+we'll look at the Internet and the more important services.
+.LI
+.Sref "\*[chnetsetup]" ,
+describes how to set up local networking.
+.LI
+.Sref "\*[chisp]" ,
+discusses the issues in selecting an Internet Service Provider (ISP) and
+establishing a presence on the Internet.
+.LI
+.Sref "\*[chmodems]" ,
+discusses serial hardware and the prerequisites for PPP and SLIP communications.
+.LI
+In
+.Sref "\*[chppp]" ,
+we look at FreeBSD's two PPP implementations and what it takes to set them up.
+.LI
+In
+.Sref "\*[chdns]" ,
+we'll consider the use of names on the Internet.
+.LI
+Security is an increasing problem on the Internet.  In
+.Sref "\*[chfirewall]" ,
+.X "IP aliasing"
+.X "proxy server"
+we'll look at some things we can do to improve it.  We'll also look at \fIIP
+aliasing\fP, since it goes hand-in-hand with firewalls, and \fIproxy servers\fP.
+.LI
+Networks sometimes become \fInotwork\fP\/s.  In
+.Sref "\*[chnetdebug]" ,
+we'll see what we can do to solve network problems.
+.LI
+.Sref "\*[chclient]" ,
+describes the client viewpoint of network access, including Web browsers,
+.Command ssh ,
+.Command ftp ,
+.Command rsync
+.X "nfs"
+and \fInfs\fP clients for sharing file systems between networked computers.
+.LI
+Network clients talk to network servers.  We'll look at the corresponding server
+viewpoint in
+.Sref "\*[chserver]" .
 .LI
 Despite the World Wide Web, traditional two-way personal communication is still
-very popular.  We'll look at it in \*[chemail].
+very popular.  We'll look at how to use mail clients in
+.Sref "\*[chmua]" .
 .LI
-Most people think the World Wide Web \fIis\fP\| the Internet.  We'll look at
-both client and server access in \*[chwww].
-.LI
-Before Microsoft and Novell discovered the Internet, they created a number of
-less powerful networking systems, some of which are still in use.  We'll look at
-them in \*[chmicronet].
-.LI
-\*[terminology], explains some of the terms used in this book.
-.LI
-\*[biblio], suggests some books for further reading.
+Mail servers are an important enough topic that there's a separate
+.Sref "\*[chmta]" .
+.\" XXX .LI
+.\" XXX Before Microsoft and Novell discovered the Internet, they created a number of
+.\" XXX less powerful networking systems, some of which are still in use.  We'll look at
+.\" XXX them in
+.\" XXX .Sref "\*[chmicronet]" .
+.LI
+In
+.Sref "\*[chxtheory]" ,
+we'll look at the theory behind getting X11 working.
+.LI
+.Sref "\*[chstarting]" ,
+describes how to start and stop a FreeBSD system and all the things you can do
+to customize it.
+.LI
+In
+.Sref "\*[chconfigfiles]" ,
+we'll look at the more common configuration files and what they should contain.
+.LI
+In
+.Sref "\*[chcurrent]" ,
+we'll discuss how to ensure that your system is always running the most
+appropriate version of FreeBSD.
+.LI
+FreeBSD keeps changing.  We'll look at some aspects of what that means to you in
+.Sref "\*[chupgrading]" .
+.LI
+.Sref "\*[chbuild]" ,
+discusses optional kernel features.
+.LI
+.Sref "\*[biblio]" ,
+suggests some books for further reading.
+.LI
+.Sref "\*[appthirded]" ,
+describes the changes that have taken place in FreeBSD since it was introduced
+nearly ten years ago.
 .Le
 .H2 "FreeBSD features"
 .Pn features
-FreeBSD is derived from ``Berkeley UNIX'', the flavour of UNIX developed by the
-Computer Systems Research Group at the University of California at Berkeley and
-previously released as the \fIBerkeley Software Distribution\fP\| (BSD) of UNIX.
+.X "Berkeley Software Distribution"
+FreeBSD is derived from \fIBerkeley UNIX\fP\/, the flavour of UNIX developed by
+the Computer Systems Research Group at the University of California at Berkeley
+and previously released as the \fIBerkeley Software Distribution\fP\/ (BSD) of
+UNIX.
 .Aside
-UNIX is a registered trademark of the Open Group, so legally FreeBSD may not be
-called UNIX.  The technical issues are different, of course: make up your own
-mind how much difference this makes.
+UNIX is a registered trademark of the Open Group, so legally, FreeBSD may not be
+called UNIX.  The technical issues are different, of course; make up your own
+mind as to how much difference this makes.
 .End-aside
 Like commercial UNIX, FreeBSD provides you with many advanced features,
 including:
 .Ls B
 .LI
-.X "preemptive multitasking"
-.X "multitasking"
-FreeBSD uses \fIpreemptive multitasking\fP\| with dynamic priority adjustment to
+FreeBSD uses \fIpreemptive multitasking\fP\/ with dynamic priority adjustment to
 ensure smooth and fair sharing of the computer between applications and users.
 .LI
-.X "multiuser"
-FreeBSD is a \fImulti-user system\fP\|: many people can use a FreeBSD system
+FreeBSD is a \fImulti-user system\fP\/: many people can use a FreeBSD system
 simultaneously for unrelated purposes.  The system shares peripherals such as
 printers and tape drives properly between all users on the system.
 .P
 Don't get this confused with the ``multitasking'' offered by some commercial
-systems.  FreeBSD is a true multi-user system which protects users from each
+systems.  FreeBSD is a true multi-user system that protects users from each
 other.
 .LI
-.X "security"
 FreeBSD is secure.  Its track record is borne out by the reports of the
 \fICERT\fP, the leading organization dealing with computer security.  See
-\fIhttp://www.cert.org/\fP\| for more information.  The FreeBSD project has a
+\fIhttp://www.cert.org/\fP\/ for more information.  The FreeBSD project has a
 team of security officers concerned with maintaining this lead.
 .LI
-.X "reliability"
-FreeBSD is reliable.  It is used in ISPs around the world and regularly attains
-up times of several years.  The main causes of outages are power failures and
-catastrophic hardware failures.
-.LI
-.X "TCP/IP"
-FreeBSD provides complete \fITCP/IP networking\fP\| including PPP, NFS and NIS
-support.  This means that your FreeBSD machine can interoperate easily with
-other systems and also act as an enterprise server, providing vital functions
-such as NFS (remote file access) and e-mail services, or putting your
-organization on the Internet with WWW, ftp, routing and firewall services.  In
-addition, the Ports Collection includes software for communicating with
-proprietary protocols\(emsee \*[chmicronet] for more details.
+FreeBSD is reliable.  It is used by ISPs around the world.  FreeBSD systems
+regularly go several years without rebooting.  FreeBSD can fail, of course, but
+the main causes of outages are power failures and catastrophic hardware
+failures.
+.LI
+FreeBSD provides a complete \fITCP/IP networking\fP\/ implementation.  This
+means that your FreeBSD machine can interoperate easily with other systems and
+also act as an enterprise server, providing vital functions such as NFS (remote
+file access) and electronic mail services, or putting your organization on the
+Internet with WWW, FTP, routing and firewall services.  In addition, the Ports
+Collection includes software for communicating with proprietary protocols.
+.\" XXX \(emsee
+.\" .Sref "\*[chmicronet]"
+.\" for more details.
 .LI
-.X "memory protection"
-\fIMemory protection\fP\| ensures that neither applications nor users can
+\fIMemory protection\fP\/ ensures that neither applications nor users can
 interfere with each other.  If an application crashes, it cannot affect other
 running applications.
 .LI
-.X "X Window System"
-.X "X11R6"
-.X "graphical user interface"
-.X "GUI"
-.X "XFree86"
-FreeBSD includes the \fIXFree86\fP\| implementation of the industry standard
-\fIX Window System\fP\| (\fIX11R6\fP\|) \fIgraphical user interface\fP\|
-(\fIGUI\fP\|).
-.LI
-.X "binary compatibility"
-.X "compatibility, SCO"
-.X "compatibility, BSD/OS"
-.X "compatibility, Linux"
-.X "compatibility, NetBSD"
-.X "compatibility, 386BSD"
-.X "SCO, compatibility"
-.X "BSD/OS, compatibility"
-.X "NetBSD, compatibility"
-.X "386BSD, compatibility"
-.X "Linux, compatibility"
-FreeBSD can run most programs built for SCO UNIX and UnixWare, Solaris on the
-i386 platform, BSD/OS, NetBSD, 386BSD, and Linux.
+FreeBSD includes the \fIXFree86\fP\/ implementation of the \fIX11\fP\/ graphical user
+interface.
+.LI
+FreeBSD can run most programs built for versions of SCO UNIX and UnixWare,
+Solaris, BSD/OS, NetBSD, 386BSD and Linux on the same hardware platform.
 .LI
 The FreeBSD Ports Collection includes thousands of ready-to-run applications.
 .LI
@@ -253,34 +285,33 @@
 Most freely available software was developed on BSD-like systems.  As a result,
 FreeBSD is one of the easiest platforms you can port to.
 .LI
-.X "virtual memory"
-.X "memory, virtual"
-Demand paged \fIvirtual memory\fP\| (\fIVM\fP\|) and ``merged VM/buffer cache''
+Demand paged \fIvirtual memory\fP\/ (\fIVM\fP\/) and ``merged VM/buffer cache''
 design efficiently satisfies applications with large appetites for memory while
 still maintaining interactive response to other users.
 .LI
-The base system contains a full complement of C, C++ and Fortran development
-tools.  Many additional languages for advanced research and development are also
-available in the Ports Collection.
+The base system contains a full complement of C, C++ and FORTRAN development
+tools.  All commonly available programming languages, such as
+.Command perl ,
+.Command python
+and
+.Command ruby ,
+are available.  Many additional languages for advanced research and development
+are also available in the Ports Collection.
 .LI
-.X "source code"
-FreeBSD provides the complete \fIsource code\fP\| for the entire system, so you
+FreeBSD provides the complete \fIsource code\fP\/ for the entire system, so you
 have the greatest degree of control over your environment.  The licensing terms
-are the freest that you will find anywhere (``hey, use it, don't pretend you
-wrote it, don't complain to us if you have problems'').
+are the freest that you will find anywhere (``Hey, use it, don't pretend you
+wrote it, don't complain to us if you have problems'').  Those are just the
+licensing conditions, of course.  As we'll see later in the chapter, there are
+plenty of people prepared to help if you run into trouble.
 .LI
-.X "online documentation"
-.X "documentation, online"
-.X "man pages"
-.X "online handbook"
-.X "handbook, online"
-Extensive \fIonline documentation\fP, including traditional \fIman pages\fP\| and
+Extensive \fIonline documentation\fP, including traditional \fIman pages\fP\/ and
 a hypertext-based \fIonline handbook\fP.
 .LE
 .P
 FreeBSD is based on the 4.4BSD UNIX released by the Computer Systems Research
 Group (CSRG) at the University of California at Berkeley.  The FreeBSD Project
-has spent many thousands of hours fine tuning the system for maximum performance
+has spent many thousands of hours fine-tuning the system for maximum performance
 and reliability.  FreeBSD's features, performance and reliability compare very
 favourably with those of commercial operating systems.
 .P
@@ -292,89 +323,125 @@
 .P
 .Ls B
 .LI
-.X "Internet Services"
-\fIInternet Services\fP\|: the Internet grew up around Berkeley UNIX.  The
+\fIInternet Services\fP\/: the Internet grew up around Berkeley UNIX.  The
 original TCP/IP implementation, released in 1982, was based on 4.2BSD, and
 nearly every current TCP/IP implementation has borrowed from it.  FreeBSD is a
 descendent of this implementation, which has been maintained and polished for
-decades.  It is the most mature TCP/IP available at any price.  This makes it an
-ideal platform for a variety of Internet services such as FTP servers, World
-Wide Web servers, Gopher servers, Electronic Mail servers, USENET News servers,
-and Bulletin Board Systems.  Need a new router?  A DNS name server?  A firewall
-to keep people out of your internal network?  FreeBSD can easily turn that
-obsolete 386 or 486 PC sitting in the corner into an advanced router with
-sophisticated packet filtering capabilities.
+decades.  It is the most mature and reliable TCP/IP available at any price.
+This makes it an ideal platform for a variety of Internet services such as FTP
+servers, World Wide Web servers, electronic mail servers, USENET news servers,
+DNS name servers and firewalls.  With the \fISamba\fP\/ suite, you can replace a
+Microsoft file server.
 .LI
-\fIEducation:\fP\| FreeBSD is an ideal way to learn about operating systems,
+\fIEducation:\fP\/ FreeBSD is an ideal way to learn about operating systems,
 computer architecture and networking.  A number of freely available CAD,
 mathematical and graphic design packages also make it highly useful to those
-whose primary interest in a computer is to get \fIother\fP\| work done.
+whose primary interest in a computer is to get \fIother\fP\/ work done.
 .LI
-\fIResearch:\fP\| FreeBSD is an excellent platform for research in operating
+\fIResearch:\fP\/ FreeBSD is an excellent platform for research in operating
 systems as well as other branches of computer science, since the source code for
 the entire system is available.  FreeBSD's free availability also makes it
 possible for remote groups to collaborate on ideas or shared development without
 having to worry about special licensing agreements or limitations on what may be
 discussed in open forums.
 .LI
-.X "X Window workstation"
-\fIX Window workstation:\fP\| FreeBSD makes an excellent choice for an
+\fIX Window workstation:\fP\/ FreeBSD makes an excellent choice for an
 inexpensive graphical desktop solution.  Unlike an X terminal, FreeBSD allows
 many applications to be run locally, if desired, thus relieving the burden on a
-central server.  FreeBSD can even boot ``diskless'', making individual
+central server.  FreeBSD can even boot ``diskless,'' making individual
 workstations even cheaper and easier to administer.
 .LI
-.X "software development"
-\fISoftware Development:\fP\| The basic FreeBSD system comes with a full
-complement of development tools included the renowned GNU C/C++ compiler and
+\fISoftware Development:\fP\/ The basic FreeBSD system comes with a full
+complement of development tools including the renowned GNU C/C++ compiler and
 debugger.
 .nr ll -1
 .P
 .LE
+.SPUP
+.H2 "Licensing conditions"
+.Pn BSD-license
+As the name suggests, FreeBSD is free.  You don't have to pay for the code, you
+can use it on as many computers as you want, and you can give away copies to
+your friends.  There are some restrictions, however.  Here's the BSD license as
+used for all new FreeBSD code:
+.P
+.in .1i
+.ll -.1i
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+.Ls
+.LI
+Redistributions of source code must retain the above copyright notice, this list
+of conditions and the following disclaimer.
+.LI
+Redistributions in binary form must reproduce the above copyright notice, this
+list of conditions and the following disclaimer in the documentation and/or
+other materials provided with the distribution.
+.Le
+This software is provided by the FreeBSD project ``as is'' and any express or
+implied warranties, including, but not limited to, the implied warranties of
+merchantability and fitness for a particular purpose are disclaimed.  In no
+event shall the FreeBSD project or contributors be liable for any direct,
+indirect, incidental, special, exemplary, or consequential damages (including,
+but not limited to, procurement of substitute goods or services; loss of use,
+data, or profits; or business interruption) however caused and on any theory of
+liability, whether in contract, strict liability, or tort (including negligence
+or otherwise) arising in any way out of the use of this software, even if
+advised of the possibility of such damage.
+.ll +.1i
+.in -.1i
+.P
+The last paragraph is traditionally written in ALL CAPS, for reasons which don't
+seem to have anything to do with the meaning.  Older versions of the license
+also contained additional clauses relating to advertising.
 .H2 "A little history"
 .Pn history
 FreeBSD is a labour of love: big commercial companies produce operating systems
-and charge lots of money for them.  The FreeBSD team produces a
+and charge lots of money for them; the FreeBSD project produces a
 professional-quality operating system and gives it away.  That's not the only
 difference.
 .P
 .X "QDOS"
 .X "Quick and Dirty Operating System"
+.X "86/DOS"
+.X "Paterson, Tim"
 In 1981, when IBM introduced their Personal Computer, the microprocessor
-industry was still in its infancy.  The PC had a minimum of 16 kB and a maximum
-of 64 kB on-board memory.  UNIX wouldn't run on this hardware, so Microsoft, who
-at the time marketed XENIX, their own version of UNIX, went looking for
-something simpler.  The ``operating system'' they chose was correspondingly
-primitive: a clone of Digital Resarch's successful CP/M operating system,
-written by Tim Patterson of Seattle Computer Products and originally called
-\fIQDOS\fP\| (\fIQuick and Dirty Operating System\fP\|).  At the time, it seemed
-just the thing: it would run just fine without a hard disk (in fact, the
-original PC didn't \fIhave\fP\| a hard disk, not even as an option), and it
-didn't use up too much memory.  The only thing that they really had to do was to
-change the name.  IBM called its version PC-DOS, while Microsoft marketed its
-version under the name MS-DOS.
+industry was still in its infancy.  They entrusted Microsoft to supply the
+operating system.  Microsoft already had their own version of UNIX, called
+XENIX, but the PC had a minimum of 16 kB and no disk. UNIX was not an
+appropriate match for this hardware.  Microsoft went looking for something
+simpler.  The ``operating system'' they chose was correspondingly primitive:
+86/DOS, a clone of Digital Research's successful CP/M operating system, written
+by Tim Paterson of Seattle Computer Products and originally called \fIQDOS\fP\/
+(\fIQuick and Dirty Operating System\fP\/).  At the time, it seemed just the
+thing: it ran fine without a hard disk (in fact, the original PC didn't
+\fIhave\fP\/ a hard disk, not even as an option), and it didn't use up too much
+memory.  The only thing that they really had to do was to change the name.  IBM
+called its version PC-DOS, while Microsoft marketed its version under the name
+MS-DOS.
 .P
 .X "CSRG"
 .X "Berkeley UNIX"
+.X "Internet Protocol"
 By this time, a little further down the US West Coast, the Computer Systems
-Research Group (\fICSRG\fP\|) of the University of California at Berkeley had
-just modified AT&T's UNIX operating system to run on the new DEC VAX 11/780
-machine, which sported virtual memory, and had turned their attention to
-implementing some new protocols for the ARPANET: the so-called \fIInternet
-Protocols\fP.  The version of UNIX that they had developed was now sufficiently
-different from AT&T's system that it had been dubbed \fIBerkeley UNIX\fP\|.
+Research Group (CSRG) of the University of California at Berkeley had just
+modified AT&T's UNIX operating system to run on the new DEC VAX 11/780 machine,
+which sported virtual memory, and had turned their attention to implementing
+some new protocols for the ARPANET: the so-called \fIInternet Protocols\fP.  The
+version of UNIX that they had developed was now sufficiently different from
+AT&T's system that it had been dubbed \fIBerkeley UNIX\fP\/.
 .P
 .X "Fast File System"
 .X "UNIX File System"
-As time went on, both MS-DOS and UNIX evolved.  Before long MS-DOS was modified
+As time went on, both MS-DOS and UNIX evolved.  Before long, MS-DOS was modified
 to handle hard disks\(emnot well, but it handled them, and for the PC users, it
 was so much better than what they had before that they ignored the
 inefficiencies.  After all, the PC gave you your own hard disk on your desk, and
 you didn't have to share it with all the other people in the department.
-Microsoft even tried to emulate the UNIX directory structure, but only succeeded
+Microsoft even tried to emulate the UNIX directory structure, but succeeded only
 in implementing the concept of nested directories.  At Berkeley, they were
-developing a higher performance disk subsystem, the \fIFast File System\fP\|,
-now known as the \fIUNIX File System\fP\|.
+developing a higher performance disk subsystem, the \fIFast File System\fP\/,
+now known as the \fIUNIX File System\fP\/.
 .P
 By the late 80s, it was evident that Microsoft no longer intended to
 substantially enhance MS-DOS.  New processors with support for multitasking and
@@ -393,7 +460,7 @@
 ``Windows'' platform until much later, and the solutions still leave a lot to be
 desired.
 .P
-.X "Research Version"
+.X "Research UNIX"
 .X "Berkeley Software Distribution"
 .X "System V"
 .X "Santa Cruz Operation"
@@ -401,18 +468,18 @@
 when the PC was introduced.  As a result, Microsoft-based environments have had
 little influence on the development of UNIX.  UNIX development was determined by
 other factors: changes in legal regulations in the USA between 1977 and 1984
-enabled AT&T first to license UNIX to other vendors, noticably Microsoft, who
-announced XENIX in 1981, and then to market UNIX itself.  AT&T developed System
-III in 1982, and System V in 1983.  The differences between XENIX and System V
-were initially small, but they grew: by the mid-80s, there were four different
-versions of UNIX: the \fIResearch Version\fP, used only inside AT&T, and derived
-from 4.1cBSD, the \fIBerkeley Software Distribution\fP (BSD) from Berkeley, the
-commercial \fISystem V\fP\| from AT&T, and XENIX, which no longer interested
-Microsoft, and was marketed by the company which had developed it, the \fISanta
-Cruz Operation\fP, or \fISCO\fP.
+enabled AT&T first to license UNIX to other vendors, noticeably Microsoft, who
+announced XENIX in 1981, and then to market its own version of UNIX.  AT&T
+developed System III in 1982, and System V in 1983.  The differences between
+XENIX and System V were initially small, but they grew: by the mid-80s, there
+were four different versions of UNIX: the \fIResearch Version\fP, used almost
+only inside AT&T, which from the eighth edition on derived from 4.1cBSD, the
+\fIBerkeley Software Distribution\fP (BSD) from Berkeley, the commercial
+\fISystem V\fP\/ from AT&T, and XENIX, which no longer interested Microsoft, and
+was marketed by the company that had developed it, the \fISanta Cruz
+Operation\fP, or \fISCO\fP.
 .P
 .X "USL"
-.X "UNIX Systems
 .X "Berkeley Software Design
 .X "BSDI"
 One casualty of UNIX's maturity was the CSRG in Berkeley.  UNIX was too mature
@@ -421,20 +488,21 @@
 PC\(emafter all, SCO had ported its version of UNIX to the PC years earlier.  In
 the Berkeley tradition, however, they wanted to give it away.
 .Pn unixwars
+.X "UNIX Systems Laboratories"
 The industry's reaction was not friendly.  In 1992, AT&T's subsidiary
-\fIUSL\fP\| (\fIUNIX Systems Laboratories\fP\|) filed a lawsuit against
-\fIBerkeley Software Design Inc.\fP\| (\fIBSDI\fP\|), the manufacturer of the
-BSD/386 and (later) the BSD/OS operating systems, both very similar to FreeBSD,
-for alleged distribution of AT&T source code in violation of licence agreements.
-They subsequently extended the case to the University of California at Berkeley.
-The suit was settled out of court, and the exact conditions were not all
-disclosed.  The only one that became public was that BSDI would migrate their
-source base to the newer 4.4BSD-Lite sources, a thing that they were preparing
-to do in any case.  Although not involved in the litigation, it was suggested to
-FreeBSD that they should also move to 4.4BSD-Lite, which was done with the
-release of FreeBSD version 2.0 in late 1994.
+\fIUSL\fP\/ (\fIUNIX Systems Laboratories\fP\/) filed a lawsuit against
+\fIBerkeley Software Design, Inc.\fP\/ (\fIBSDI\fP\/), the manufacturer of the
+BSD/386 operating system, later called BSD/OS, a system very similar to FreeBSD.
+They alleged distribution of AT&T source code in violation of licence
+agreements.  They subsequently extended the case to the University of California
+at Berkeley.  The suit was settled out of court, and the exact conditions were
+not all disclosed.  The only one that became public was that BSDI would migrate
+their source base to the newer 4.4BSD-Lite sources, a thing that they were
+preparing to do in any case.  Although not involved in the litigation, it was
+suggested to FreeBSD that they should also move to 4.4BSD-Lite, which was done
+with the release of FreeBSD release 2.0 in late 1994.
 .P
-Now, in the early 21st century, FreeBSD is the best-known of the BSD operating
+Now, in the early 21st century, FreeBSD is the best known of the BSD operating
 systems, one that many consider to follow in the tradition of the CSRG.  I can
 think of no greater honour for the development team.  It was developed on a
 shoestring budget, yet it manages to outperform commercial operating systems by
@@ -442,103 +510,27 @@
 .H3 "The end of the UNIX wars"
 In the course of the FreeBSD project, a number of things have changed about
 UNIX.  Sun Microsystems moved from a BSD base to a System V base in the late
-80s, a move which convinced most people that BSD was dead and that System V was
-the future.  Things turned out differently: in 1992, AT&T sold USL to Novell
+80s, a move that convinced many people that BSD was dead and that System V was
+the future.  Things turned out differently: in 1992, AT&T sold USL to Novell,
 Inc., who had introduced a product based on System V.4 called UnixWare.
 Although UnixWare has much better specifications than SCO's old System V.3 UNIX,
 it was never a success, and Novell finally sold their UNIX operation to SCO.
-SCO itself was then bought out by Caldera, while the ownership of the UNIX trade
-mark has passed to the Open Group.  System V UNIX is essentially dead: current
-commercial versions of UNIX deviate so much from System V that they can't be
+SCO itself was then bought out by Caldera (which recently
+.\" XXX September 2002
+changed its name back to SCO), while the ownership of the UNIX trade mark has
+passed to the Open Group.  System V UNIX is essentially dead: current commercial
+versions of UNIX have evolved so far since System V that they can't be
 considered the same system.  By contrast, BSD is alive and healthy, and lives on
-in FreeBSD, NetBSD and OpenBSD.
+in FreeBSD, NetBSD, OpenBSD and Apple's Mac OS X.
 .P
 The importance of the AT&T code in the earlier versions of FreeBSD was certainly
 overemphasized in the lawsuit.  All of the disputed code was over 10 years old
 at the time, and none of it was of great importance.  In January 2002, Caldera
 released all ``ancient'' versions of UNIX under a BSD license.  These
-specifically included those versions of UNIX from which BSD was derived: the
-first to seventh editions of Research UNIX and 32V, the predecessor to 3BSD.  As
-a result, all versions of BSD, including those over which the lawsuit was
-conducted, are now freely available.  As a result, it's now possible to compare
-the code.  Here's one example.  In the Seventh edition of UNIX, dated 1978, the
-file \fI/usr//sys/sys/clock.c\fP\| contained the following definition for the
-function \fItimeout\fP\|:
-.Dx
-timeout(fun, arg, tim)
-int (*fun)();
-caddr_t arg;
-{
-	register struct callo *p1, *p2;
-	register int t;
-	int s;
-
-	t = tim;
-	p1 = &callout[0];
-	s = spl7();
-	while(p1->c_func != 0 && p1->c_time <= t) {
-		t -= p1->c_time;
-		p1++;
-	}
-	if (p1 >= &callout[NCALL-1])
-		panic("Timeout table overflow");
-	p1->c_time -= t;
-	p2 = p1;
-	while(p2->c_func != 0)
-		p2++;
-	while(p2 >= p1) {
-		(p2+1)->c_time = p2->c_time;
-		(p2+1)->c_func = p2->c_func;
-		(p2+1)->c_arg = p2->c_arg;
-		p2--;
-	}
-	p1->c_time = t;
-	p1->c_func = fun;
-	p1->c_arg = arg;
-	splx(s);
-}
-.De
-The corresponding definition in 4.3BSD \fI/sys/kern/kern_clock.c\fP\| was:
-.Dx
-timeout(fun, arg, t)
-	int (*fun)();
-	caddr_t arg;
-	register int t;
-{
-	register struct callout *p1, *p2, *pnew;
-	register int s = splhigh();
-
-	if (t <= 0)
-		t = 1;
-	pnew = callfree;
-	if (pnew == NULL)
-		panic("timeout table overflow");
-	callfree = pnew->c_next;
-	pnew->c_arg = arg;
-	pnew->c_func = fun;
-	for (p1 = &calltodo; (p2 = p1->c_next) && p2->c_time < t; p1 = p2)
-		if (p2->c_time > 0)
-			t -= p2->c_time;
-	p1->c_next = pnew;
-	pnew->c_next = p2;
-	pnew->c_time = t;
-	if (p2)
-		p2->c_time -= t;
-	splx(s);
-}
-.De
-Two things are clear here:
-.Ls N
-.LI
-Yes, the 4.3BSD code was definitely derived from AT&T UNIX.  So far, the lawyers
-were correct.
-.LI
-The function is trivial.  It could have been written by any undergraduate with
-the appropriate understanding of the data structures involved.
-.Le
-In fact, FreeBSD's \fItimeout\fP\| function has changed completely.  This is an
-issue of technical progress, not placating lawyers.  The code about which they
-complained was not worth keeping.
+specifically included all versions of UNIX from which BSD was derived: the first
+to seventh editions of Research UNIX and 32V, the predecessor to 3BSD.  As a
+result, all versions of BSD, including those over which the lawsuit was
+conducted, are now freely available.
 .H2 "Other free UNIX-like operating systems"
 .Pn unixclones
 FreeBSD isn't the only free UNIX-like operating system available\(emit's not
@@ -548,61 +540,67 @@
 .Ls B
 .LI
 .X "386/BSD"
-\fI386/BSD\fP\| was the original free BSD operating system, introduced by
+\fI386/BSD\fP\/ was the original free BSD operating system, introduced by
 William F. Jolitz in 1992.  It never progressed beyond a test stage: instead,
 two derivative operating systems arose, FreeBSD and NetBSD.  386/BSD has been
-dead for years.
+obsolete for years.
 .LI
 .X "NetBSD"
-\fINetBSD\fP\| is an operating system which, to the casual observer, is almost
-identical to FreeBSD.  The main differences are in the fact that NetBSD runs on
-just about any hardware, whereas FreeBSD concentrates on mainly Intel hardware.
-FreeBSD tries harder to be easy to understand for a beginner.  You can find more
+\fINetBSD\fP\/ is an operating system which, to the casual observer, is almost
+identical to FreeBSD.  The main differences are that NetBSD concentrates on
+hardware independence, whereas FreeBSD concentrates on performance.  FreeBSD
+also tries harder to be easy to understand for a beginner.  You can find more
 information about NetBSD at \fIhttp://www.NetBSD.org\fP.
 .LI
 .X "OpenBSD"
-\fIOpenBSD\fP\| is a spinoff of NetBSD which focuses on security.  You can find
-more information at \fIhttp://www.OpenBSD.org\fP.
+\fIOpenBSD\fP\/ is a spin-off of NetBSD that focuses on security.  It's also
+very similar to FreeBSD.  You can find more information at
+\fIhttp://www.OpenBSD.org\fP.
 .LI
 .X "MacOS X"
-Apple computer introduced version 10 (X) of its \fIMacOS\fP\| in early 2001.  It
-is a big deviation from previous versions of MacOS: it is based on a Mach
+Apple computer introduced Version 10 (X) of its \fIMac OS\fP\/ in early 2001.
+It is a big deviation from previous versions of Mac OS: it is based on a Mach
 microkernel with a BSD environment.  The base system (Darwin) is also free.
 FreeBSD and Darwin are compatible at the user source code level.
 .Le
-You might get the impression that there are lots of different, incompatible BSD
-versions.  In fact, they're all very similar to each other, much more than the
-individual distributions of Linux, which we'll look at next.
+You could get the impression that there are lots of different, incompatible BSD
+versions.  In fact, from a user viewpoint they're all very similar to each
+other, much more than the individual distributions of Linux, which we'll look at
+next.
 .H3 "FreeBSD and Linux"
-Linux is a clone of UNIX written by Linus Torvalds, a student in Helsinki,
-Finland.  At the time, the BSD sources were not freely available, and so Linus
-wrote his own version of UNIX.
+.X "Linux"
+.Pn Linux
+In 1991, Linus Torvalds, then a student in Helsinki, Finland, decided he wanted
+to run UNIX on his home computer.  At that time the BSD sources were not freely
+available, and so Linus wrote his own version of UNIX, which he called Linux.
 .P
 Linux is a superb example of how a few dedicated, clever people can produce an
 operating system that is better than well-known commercial systems developed by
 a large number of trained software engineers.  It is better even than a number
 of commercial UNIX systems.
 .P
-Obviously, I don't think Linux is as good as FreeBSD, or I wouldn't be writing
-this book, but the differences between FreeBSD and Linux are more a matter of
-philosophy rather than of concept.  Here are a few contrasts:
+Obviously, I prefer FreeBSD over Linux, or I wouldn't be writing this book, but
+the differences between FreeBSD and Linux are more a matter of philosophy rather
+than of concept.  Here are a few contrasts:
 .br
 .ne 1i
-.TB "Differences between FreeBSD and Linux"
+.Table-heading "Differences between FreeBSD and Linux"
 .TS H
 tab(#) ;
- lw31  lw31 .
+ lw34  lw35 .
 .TH
 T{
 FreeBSD is a direct descendent of the original UNIX, though it contains no
 residual AT&T code.
 T}#T{
-Linux is a clone and never contained any AT&T code
+Linux is a clone and never contained any AT&T code.
 T}
 .sp .9v
 T{
 FreeBSD is a complete operating system, maintained by a central group of
-software developers.  There is only one distribution of FreeBSD.
+software developers under the Concurrent Versions System which maintains a
+complete history of the project development.  There is only one distribution of
+FreeBSD.
 T}#T{
 Linux is a kernel, personally maintained by Linus Torvalds and a few trusted
 companions.  The non-kernel programs supplied with Linux are part of a
@@ -611,6 +609,21 @@
 T}
 .sp .9v
 T{
+The FreeBSD development style emphasizes accountability and documentation of
+changes.
+T}#T{
+The Linux kernel is maintained by a small number of people who keep track of all
+changes.  Unofficial patches abound.
+T}
+.sp .9v
+T{
+The kernel supplied with a specific release of FreeBSD is clearly defined.
+T}#T{
+Linux distributions often have subtly different kernels.  The differences are
+not always documented.
+T}
+.sp .9v
+T{
 FreeBSD aims to be a stable production environment.
 T}#T{
 Many versions of Linux are still ``bleeding edge'' development environments.
@@ -621,17 +634,16 @@
 As a result of the centralized development style, FreeBSD is straightforward and
 easy to install.
 T}#T{
-The ease of installation of Linux depends on the ``distribution''.  If you
+The ease of installation of Linux depends on the \fIdistribution\fP.  If you
 switch from one distribution of Linux to another, you'll have to learn a new set
 of installation tools.
 T}
 .sp .9v
 T{
-FreeBSD is still relatively unknown, since its distribution was restricted for a
-long time due
-to the AT&T lawsuits.
+FreeBSD is still relatively unknown, since its distribution was initially
+restricted due to the AT&T lawsuits.
 T}#T{
-Linux did not have any lawsuits to contend with, so for a long time it was
+Linux did not have any lawsuits to contend with, so for some time it was
 thought to be the only free UNIX-type system available.
 T}
 .sp .9v
@@ -650,171 +662,173 @@
 T}
 .sp .9v
 T{
-Because of the lack of commercial applications and drivers, FreeBSD will run
-most Linux programs, whether commercial or not.
+Because of the lack of commercial applications and drivers for FreeBSD, FreeBSD
+runs most Linux programs, whether commercial or not.
 T}#T{
 Linux appears not to need to be able to run FreeBSD programs.
 T}
 .sp .9v
 T{
-FreeBSD has a large number of afficionados who are prepared to flame
-anybody who
+FreeBSD is licensed under the BSD license\(emsee page
+.Sref \*[BSD-license] .
+There are very few restrictions on its use.
+T}#T{
+Linux is licensed under the GNU General Public License.  Further details are at
+.URI http://www.gnu.org/licenses/gpl.html .
+By comparison with the BSD license, it imposes significant
+restrictions on what you can do with the source code.
+T}
+.sp .9v
+T{
+FreeBSD has aficionados who are prepared to flame anybody who
 dares suggest that it's not better than Linux.
 T}#T{
-Linux has a large number of afficionados who are prepared to flame anybody who
+Linux has aficionados who are prepared to flame anybody who
 dares suggest that it's not better than FreeBSD.
 T}
 .TE
-.sp 1.5v
-In summary, Linux is also a very good operating system.  For many, it's better
-than FreeBSD.  It's a pity that so many people on both sides are prepared to
-flame\*F
-.FS
-To quote Eric Raymond's ``The New Hacker's Dictionary'':
 .P
-:flame: 1. /vi./ To post an email message intended to insult and provoke.
-2. /vi./ To speak incessantly and/or rabidly on some relatively uninteresting
-subject or with a patently ridiculous attitude.  3. /vt./ Either of senses 1 or
-2, directed with hostility at a particular person or people.  4. /n./ An
-instance of flaming.  When a discussion degenerates into useless controversy,
-one might tell the participants ``Now you're just flaming'' or ``Stop all that
-flamage!'' to try to get them to cool down (so to speak).
-.FE
-each other.  There are signs that both sides are learning to appreciate each
-other, and a number of people are now running both systems.
+.ne 2v
+In summary, Linux is also a very good operating system.  For many, it's better
+than FreeBSD.
 .\" XXX http://keystone.westminster.edu/~fullermd/bsdvlin.htm
-.H2 "Other documentation on FreeBSD"
-.Pn docco
-FreeBSD users have access to probably more top-quality documentation than just
-about any other operating system.  Remember that word UNIX\(rg.  Sure, the
-lawyers tell us that we can't refer to FreeBSD as UNIX, because UNIX belongs to
-the Open Group.  That doesn't make the slightest difference to the fact that
-just about any book on UNIX will apply more directly to FreeBSD than any other
-flavour of UNIX.  Why is this?
-.P
-Commercial UNIX vendors have a problem, and FreeBSD doesn't help them: why
-should people buy their products when you can get it free from the FreeBSD
-Project (or, for that matter, from other free UNIX-like operating systems such
-as NetBSD, OpenBSD and Linux)?  One obvious reason would be ``value-added
-features''.  So they add features or fix weak points in the system, put a
-copyright on the changes, and help lock their customers in to their particular
-implementation.  As long as the changes are really useful, this is legitimate,
-but it does make the operating system less compatible with ``standard UNIX'',
-and the books about standard UNIX are less applicable.
-.P
-In addition, many books are written by people with an academic background.  In
-the UNIX world, this means that they are more likely than the average user to
-have been exposed to BSD.  Many general UNIX books handle primarily BSD,
-possibly with an additional chapter on the commercial System V version.
-.P
-In \*[biblio], you'll find a list of books which I find particularly worthwhile.
-I'd like to single out some which I find particularly good, and which I
-frequently use myself:
-.Ls B
-.LI
+.H2 "FreeBSD system documentation"
 .X "online handbook"
 .X "handbook, online"
-.Pn handbook
-.X "Live Filesystem"
-The FreeBSD \fIonline handbook\fP\| contains a lot of information specifically
-about FreeBSD, including a deeper discussion of many topics in this book.  It is
-available on the World Wide Web at \fIhttp://www.FreeBSD.org/handbook.html\fP,
-and also on each FreeBSD system in the directory \fI/usr/share/doc/handbook\fP.
-In addition, a printed version is available.  Before installation, you can
-access it from the \fILive Filesystem\fP\| CD-ROM.  We'll look at how to do that
-in the next section.
+.X "lynx, command"
+FreeBSD comes with a considerable quantity of documentation which we'll look at
+in the following few pages:
+.Ls B
 .LI
-.X "FAQ"
-.X "Frequently Asked Questions"
-.X "/usr/share/doc/FAQ"
-The FreeBSD \fIFAQ\fP\| (\fIFrequently Asked Questions\fP\|) is just what it
-says it is: a list of questions that people frequently ask about FreeBSD, with
-answers of course.  It is located in the directory \fI/usr/share/doc/FAQ\fP.  If
-you run MS-DOS, you can view it before installation with the \fIVIEW\fP\|
-program.  Check the CD-ROM booklet for the location, which could change.
+The FreeBSD Documentation Project maintains a collection of ``books,''
+documents in HTML or PDF format which can also be accessed online.  They're
+installed in the directory hierarchy
+.Directory /usr/share/doc .
+.LI
+The traditional UNIX document format is \fIman pages\fP, individual documents
+describing specific functionality.  They're short and to the point of being
+cryptic, but if you know what you're looking for, they have just the right
+amount of detail.  They're not a good introduction.
 .LI
-.X "Peek, Jerry"
-.X "O'Reilly, Tim"
-.X "Loukides, Mike"
-\fIUNIX Power Tools\fR, by Jerry Peek, Tim O'Reilly, and Mike Loukides, is a
-superb collection of interesting information, including a CD-ROM.  Recommended
-for everybody, from beginners to experts.
+The GNU project introduced their own document format, \fIGNU info\fP.  Some GNU
+programs have no other form of documentation.
+.Le
+.H3 "Reading online documentation"
+You'll find a number of HTML documents in the directory
+.Directory /usr/share/doc/en/books \/:
+.Ls B
 .LI
-.X "Abrahams, Paul W."
-.X "Larson, Bruce R."
-\fIUNIX for the Impatient\fP\|, by Paul W. Abrahams and Bruce R. Larson, is more
-similar to this book, but it includes a lot more material on specific products,
-such as shells and the \fIEmacs\fP\| editor.
+.X "FAQ"
+.X "Frequently Asked Questions"
+.File /usr/share/doc/en/books/faq/index.html
+contains the FreeBSD \fIFAQ\fP\/ (\fIFrequently Asked Questions\fP\/).  It's
+just what it says it is: a list of questions that people frequently ask about
+FreeBSD, with answers of course.
 .LI
-.X "Nemeth, Evi"
-.X "Snyder, Garth"
-.X "Seebass, Scott"
-.X "Hein, Trent R."
-The \fIUNIX System Administration Handbook\fP, by Evi Nemeth, Garth Snyder,
-Scott Seebass, and Trent R. Hein, is one of the best books on systems
-administration I have seen.  It covers a number different UNIX systems,
-including FreeBSD.
+.File /usr/share/doc/en/books/fdp-primer/index.html
+is a primer for the \fIFreeBSD Documentation Project\fP,
 .LI
-There are a large number of active Internet groups which deal with FreeBSD.
-..if verylong
-We'll look at them in the rest of this chapter, starting on page.
-.Sref \*[fdafdsa] XXX
-..else
-Read about them in the online handbook.
-..endif
+.X "online handbook"
+.X "handbook, online"
+.Pn handbook
+.X "Live Filesystem"
+.File /usr/share/doc/en/books/handbook/index.html
+is the FreeBSD \fIonline handbook\fP.  It contains a lot of information
+specifically about FreeBSD, including a deeper discussion of many topics in this
+book.
+.LI
+.File /usr/share/doc/en/books/porters-handbook/index.html
+is a handbook for contributors to the FreeBSD Ports Collection, which we'll
+discuss in
+.Sref "\*[chports]" .
+.LI
+.File /usr/share/doc/en/books/ppp-primer/index.html
+contains a somewhat dated document about setting up PPP.  If you have trouble
+with
+.Sref "\*[chppp]" ,
+you may find it useful.
 .Le
-.H3 "Reading the handbook"
-.X "lynx, command"
-If you're running X, you can use a browser like \fInetscape\fP\| to read the
-handbook.  If you don't have X running yet, use \fIlynx\fP\|.  Both of these
-programs are included on the CD-ROM.  To install them, use \fIsysinstall\fP,
-which is described on page \*[sysinstall].
-.P
-Note that \fIlynx\fP\| is not a complete substitute for \fInetscape\fP\|: since
-it is text-only, it is not capable of displaying the large majority of web pages
-correctly.  It's good enough for reading most of the handbook, however.
+In addition to the directory
+.Directory /usr/share/doc/en/books ,
+there's also a directory
+.Directory /usr/share/doc/en/articles
+with a number of shorter items of documentation.
+.P
+Note the component \fIen\fP\/ in the pathnames above.  That stands for
+\fIEnglish\fP.  A number of these books are also installed in other languages:
+change \fIen\fP\/ to \fIde\fP\/ for a German version, to \fIes\fP\/ for Spanish,
+to \fIfr\fP\/ for French, to \fIja\fP\/ for Japanese, to \fIru\fP\/ for Russian,
+or to \fIzh\fP\/ for Chinese.  Translation efforts are continuing, so you may
+find documentation in other languages as well.
+.P
+.ne 3v
+If you're running X, you can use a browser like
+.Command mozilla
+to read the documents.  If you don't have X running yet, use
+.Command lynx .
+Both of these programs are included in the CD-ROM distribution.  To install
+them, use
+.Command sysinstall ,
+which is described on page
+.Sref \*[sysinstall] .
+.P
+.Command lynx
+is not a complete substitute for complete web browsers such as
+.Command mozilla :
+since it is text-only, it is not capable of displaying the large majority of web
+pages correctly.  It's good enough for reading most of the FreeBSD online
+documentation, however.
 .P
-In either case, you start the browser with the name of the handbook:
+In each case, you start the browser with the name of the document, for example:
 .Dx
-$ \f(CBlynx /usr/share/doc/handbook/handbook.html\fP
-$ \f(CBnetscape /usr/share/doc/handbook/handbook.html &\fP
+$ \f(CBlynx /usr/share/doc/en/books/handbook/index.html\fP
+$ \f(CBmozilla /usr/share/doc/en/books/handbook/index.html &\fP
 .De
-You enter the \f(CW&\fP after the invocation of \fInetscape\fP\| to free up the
-window in which you invoke it: \fInetscape\fP\| opens its own window.
+Enter the \f(CW&\fP after the invocation of
+.Command mozilla
+to free up the window in which you invoke it:
+.Command mozilla
+opens its own window.
+.P
+If you haven't installed the documentation, you can still access it from the
+Live Filesystem CD-ROM.  Assuming the CD-ROM is mounted on
+.Directory /cdrom ,
+choose the file
+.File -n /cdrom/usr/share/doc/en/books/handbook/index.html .
 .P
-You can look at the FAQ in the same way\(emjust substitute the name
-\fIFAQ/freebsd-faq.html\fP\| for \fIhandbook/handbook.html\fP.
-.P
-If you haven't installed the handbook, you can still access it from the Live
-Filesystem CD-ROM.  Assuming the CD-ROM is mounted on \fI/cdrom\fP, choose the
-directory \fI/cdrom/usr/share/doc/handbook/handbook.html\fP.
-.P
-.X "ghostscript command"
-.X "command, ghostscript"
-.X "dvips command"
-.X "command, dvips"
 Alternatively, you can print out the handbook.  This is a little more difficult,
 and of course you'll lose the hypertext references, but you may prefer it in
 this form.  To format the handbook for printing, you'll need a PostScript
-printer or \fIghostscript\fP.  See page \*[PostScript] for more details of how
-to print PostScript.
-.P
-You can also see the latest version of the handbook at
-\fIhttp://www.FreeBSD.org/handbook.html\fP, or you you can download it from
-\fIftp://ftp.FreeBSD.ORG/pub/FreeBSD/doc/handbook.ps.gz\fP.  Use \fIftp\fP\|
-(page \*[ftp]) to transfer the document.
+printer or
+.Command ghostscript .
+See page
+.Sref \*[PostScript] \&
+for more details of how to print PostScript.
+.P
+The printable version of the documentation doesn't usually come with the CD-ROM
+distribution.  You can pick it up with
+.Command ftp
+(see page
+.Sref \*[ftp] )
+from
+.URI ftp://ftp.FreeBSD.ORG/pub/FreeBSD/doc/ ,
+which has the same directory structure as described above.  For example, you
+would download the handbook in PostScript form from
+.URI ftp://ftp.FreeBSD.ORG/pub/FreeBSD/doc/en/books/handbook/book.ps.bz2 .
 .H3 "The online manual"
 .Pn man
-.X "man command"
 .X "man page"
-.X "command, man"
-The most comprehensive documentation on FreeBSD is the online manual, generally
-referred to as the \fIman pages\fP.  Nearly every program on the system comes
-with a short reference manual explaining the basic operation and various
-arguments.
-.P
-When online, you view the man pages with the command \fIman\fP.  For example, to
-learn more about the command \fIls\fP, type:
+The most comprehensive documentation on FreeBSD is the online manual, usually
+referred to as the \fIman pages\fP.  Nearly every program, file, library
+function, device or interface on the system comes with a short reference manual
+explaining the basic operation and various arguments.  If you were to print it
+out, it would run to well over 8,000 pages.
+.P
+When online, you view the man pages with the command
+.Command man .
+For example, to learn more about the command
+.Command ls ,
+type:
 .Dx
 $ \f(CBman ls \fP
 LS(1)                      FreeBSD Reference Manual                      LS(1)
@@ -829,7 +843,7 @@
      For each operand that names a file of a type other than directory, \f(CBls\fP
      displays its name as well as any requested, associated information.  For
      each operand that names a file of type directory, ls displays the names.
-\fI(etc)\fP\|
+\fI(etc)\fP\/
 .De
 In this particular example, with the exception of the first line, the text in
 \f(CBconstant width bold\fP is not input, it's the way it appears on the screen.
@@ -855,42 +869,47 @@
 .LI
 Kernel interface documentation
 .Le
-.X "chmod command"
-.X "command, chmod"
-In some cases, the same topic may appear in more than one section of the on-line
-manual.  For example, there is a user command \fIchmod\fP\| and a system call
-\f(CWchmod()\fP.  In this case, you can tell the man command which you want by
-specifying the section number:
+In some cases, the same topic may appear in more than one section of the online
+manual.  For example, there is a user command
+.Command chmod
+and a system call \f(CWchmod()\fP.  In this case, you can tell the
+.Command man
+command which you want by specifying the section number:
 .Dx
 $ \f(CBman 1 chmod \fP
 .De
-.X "chmod(1)"
-.X "chmod(2)"
-This will display the manual page for the user command chmod.  References to a
-particular section of the on-line manual are traditionally placed in parentheses
-in written documentation.  For example, \fIchmod(1)\fP\| refers to the user
-command \fIchmod\fP, and \fIchmod(2)\fP\| means the system call.
+This command displays the manual page for the user command chmod.  References to
+a particular section of the online manual are traditionally placed in
+parentheses in written documentation.  For example, \fIchmod(1)\fP\/ refers to
+the user command
+.Command chmod ,
+and \fIchmod(2)\fP\/ means the system call.
 .P
-.X "apropos command"
+.X "apropos, command"
 .X "command, apropos"
 This is fine if you know the name of the command and forgot how to use it, but
-what if you can't recall the command name?  You can use man to search for
-keywords in the command descriptions by using the \f(CW-k\fP option, or by
-starting the program \fIapropos\fP\|:
+what if you can't recall the command name?  You can use
+.Command man
+to search for keywords in the command descriptions by using the \f(CW-k\fP
+option, or by starting the program
+.Command apropos \/:
 .Dx
 $ \f(CBman -k mail \fP
 $ \f(CBapropos mail \fP
 .De
 Both of these commands do the same thing: they show the names of the man pages
-that have the keyword \fImail\fP\| in their descriptions.
+that have the keyword \fImail\fP\/ in their descriptions.
 .P
-Alternatively, you may browse through the \fI/usr/bin\fP\| directory, which
-contains most of the system executables.  You'll see lots of file names, but you
-don't have any idea what they do.  To find out, enter one of the lines:
+Alternatively, you may browse through the
+.Directory /usr/bin
+directory, which contains most of the system executables.  You'll see lots of
+file names, but you don't have any idea what they do.  To find out, enter one of
+the lines:
 .Dx
 $ \f(CBcd /usr/bin; man -f * \fP
 $ \f(CBcd /usr/bin; whatis * \fP
 .De
+.ne 2v
 Both of these commands do the same thing: they print out a one-line summary of
 the purpose of the program:
 .Dx
@@ -898,67 +917,185 @@
 a2p(1)           - Awk to Perl translator
 addftinfo(1)     - add information to troff font files for use with groff
 apply(1)         - apply a command to a set of arguments
-apropos(1)       - search the whatis database for strings
+apropos(1)       - search the whatis database
 \fI\&...etc\fP
 .De
-..if short
-Part II of this book, starting on page
-.Sref \*[partii] ,
-contains a number of man pages which you may find useful when installing the
-system.
-..endif
-.H3 "GNU \fIinfo\fP\|"
-.X "info command"
-.X "command, info"
-.X "emacs command"
+.SPUP
+.H4 "Printing man pages"
+.Pn howto-print-manpages
+If you prefer to have man pages in print, rather than on the screen, you can do
+this in two different ways:
+.Ls B
+.LI
+The simpler way is to redirect the output to the spooler:
+.Dx
+$ \f(CBman ls | lpr\fP
+.De
+This gives you a printed version that looks pretty much like the original on
+the screen, except that you may not get bold or underlined text.
+.LI
+You can get typeset output with
+.Command troff \/:
+.Dx
+$ \f(CBman -t ls | lpr\fP
+.De
+This gives you a properly typeset version of the man page, but it requires that
+your spooling system understand PostScript\(emsee page
+.Sref \*[PostScript] \&
+for more details of printing PostScript, even on printers that don't understand
+PostScript.
+.Le
+.H3 "GNU info"
+.X "emacs, command"
+.X "command, emacs"
+The Free Software Foundation has its own online hypertext browser called
+.Command info .
+Many FSF programs come with either no man page at all, or with an excuse for a
+man page
+.Command ( gcc ,
+for example).  To read the online documentation, you need to browse the
+.Command info
+files with the
+.Command info
+program, or from
+.X "emacs, command"
 .X "command, emacs"
-The Free Software Foundation has its own on-line hypertext browser called
-\fIinfo\fP.  Many FSF programs come with either no man page at all, or with an
-excuse for a man page (\fIgcc\fP, for example).  To read the online
-documentation, you need to browse the \fIinfo\fP\| files with the \fIinfo\fP\|
-program, or from \fIEmacs\fP\| with the \fIinfo\fP\| mode.  To start \fIinfo\fP,
+.Command -n Emacs
+with the
+.Command info
+mode.  To start
+.Command info ,
 simply type:
 .Dx
 $ \f(CBinfo \fP
 .De
-In \fIEmacs\fP, enter \fBCTRL-h i\fP or \fBALT-X\fP \f(CWinfo\fP.  Whichever way
-you start \fIinfo\fP, you can get brief introduction by typing \f(CWh\fP, and a
-quick command reference by typing \f(CW?\fP.
+In
+.Command -n Emacs ,
+enter \fBCTRL-h i\fP or \fBALT-x\fP \f(CWinfo\fP.  Whichever way you start
+.Command info ,
+you can get brief introduction by typing \f(CBh\fP, and a quick command
+reference by typing \f(CB?\fP.
+.H2 "Other documentation on FreeBSD"
+.X "documentation, online"
+.Pn docco
+FreeBSD users have access to probably more top-quality documentation than just
+about any other operating system.  Remember that word UNIX is trademarked.
+Sure, the lawyers tell us that we can't refer to FreeBSD as UNIX, because UNIX
+belongs to the Open Group.  That doesn't make the slightest difference to the
+fact that nearly every book on UNIX applies more directly to FreeBSD than any
+other flavour of UNIX.  Why?
+.P
+.ne 3v
+Commercial UNIX vendors have a problem, and FreeBSD doesn't help them: why
+should people buy their products when you can get it free from the FreeBSD
+Project (or, for that matter, from other free UNIX-like operating systems such
+as NetBSD, OpenBSD and Linux)?  One obvious reason would be ``value-added
+features.''  So they add features or fix weak points in the system, put a
+copyright on the changes, and help lock their customers in to their particular
+implementation.  As long as the changes are really useful, this is legitimate,
+but it does make the operating system less compatible with ``standard UNIX,''
+and the books about standard UNIX are less applicable.
+.P
+In addition, many books are written by people with an academic background.  In
+the UNIX world, this means that they are more likely than the average user to
+have been exposed to BSD.  Many general UNIX books handle primarily BSD,
+possibly with an additional chapter on the commercial System V version.
+.P
+In
+.Sref "\*[biblio]" ,
+you'll find a list of books that I find worthwhile.  I'd like to single out some
+that I find particularly good, and that I frequently use myself:
+.Ls B
+.LI
+.X "Peek, Jerry"
+.X "O'Reilly, Tim"
+.X "Loukides, Mike"
+\fIUNIX Power Tools\fR, by Jerry Peek, Tim O'Reilly, and Mike Loukides, is a
+superb collection of interesting information, including a CD-ROM.  Recommended
+for everybody, from beginners to experts.
+.LI
+.X "Abrahams, Paul W."
+.X "Larson, Bruce R."
+\fIUNIX for the Impatient\fP\/, by Paul W. Abrahams and Bruce R. Larson, is more
+similar to this book, but it includes a lot more material on specific products,
+such as shells and the
+.X "command, emacs"
+.X "emacs, command"
+.Command -n Emacs
+editor.
+.LI
+.X "Nemeth, Evi"
+.X "Snyder, Garth"
+.X "Seebass, Scott"
+.X "Hein, Trent R."
+The \fIUNIX System Administration Handbook\fP, by Evi Nemeth, Garth Snyder,
+Scott Seebass, and Trent R. Hein, is one of the best books on systems
+administration I have seen.  It covers a number different UNIX systems,
+including an older version of FreeBSD.
+.Le
+There are also many active Internet groups that deal with FreeBSD.
+..if verylong
+We'll look at them in the rest of this chapter, starting on page.
+.Sref \*[fdafdsa] XXX
+..else
+Read about them in the online handbook.
+..endif
 .H2 "The FreeBSD community"
+.X "community, FreeBSD"
+.X "FreeBSD, community"
 .Pn FreeBSD-community
 FreeBSD was developed by a world-wide group of developers.  It could not have
-happened without the Internet.  Most of the key players have never even met each
-other in person: the main communication is via the Net.  If you have any kind of
-Internet connection, you can participate as well.  If you don't have an Internet
-connection, it's about time you got one.  The connection doesn't have to be
-complete: if you can receive email, you can participate.  On the other hand,
-FreeBSD includes all the software you need for a complete Internet connection,
-not the very limited subset that most PC-based ``Internet'' packages offer you.
-..if verylong
-.H2 "Registering FreeBSD"
-You don't have to pay money for FreeBSD, but we still would like to know how
-many people use it (apart from anything else, we have a running rivalry with
-atLinux users \f(CW:-)\fP Registering doesn't oblige you to anything.
-.P
-One advantage of registering your use of FreeBSD is that you will establish
-contact with the FreeBSD community.  As we'll see in the next section, this can
-be a significant advantage.
-XXX Say how to register!
-..endif
-.H2 "Support"
+happened without the Internet.  Many of the key players have never even met each
+other in person; the main means of communication is via the Internet.  If you
+have any kind of Internet connection, you can participate as well.  If you don't
+have an Internet connection, it's about time you got one.  The connection
+doesn't have to be complete: if you can receive email, you can participate.  On
+the other hand, FreeBSD includes all the software you need for a complete
+Internet connection, not the very limited subset that most PC-based ``Internet''
+packages offer you.
+.H2 "Mailing lists"
+.X "mailing lists"
 .Pn support
-.X "Support"
-.X "Installation support"
+.X "support"
+.X "installation support"
 As it says in the copyright, FreeBSD is supplied as-is, without any support
-liability.  If you're on the Net, you're not alone, however.  Liability is one
-thing, but there are plenty of people prepared to help you, most for free, some
-for fee.  A good place to start is with the mailing list
-\f(CWFreeBSD-questions@FreeBSD.org\fP.  You'll frequently see this name
-abbreviated to \f(CW-questions\fP.  To sign up, send a mail message to
-\f(CWmajordomo@FreeBSD.org\fP with the text
+liability.  If you're on the Internet, you're not alone, however.  Liability is
+one thing, but there are plenty of people prepared to help you, most for free,
+some for fee.  A good place to start is with the mailing lists.  There are a
+number of mailing lists that you can join:
+.Ls B
+.LI
+\f(CWFreeBSD-questions@FreeBSD.org\fP is the list to which you may send general
+questions, in particular on how to use FreeBSD.  Use this one if you're not sure
+which is the most appropriate.
+.LI
+\f(CWFreeBSD-newbies@FreeBSD.org\fP is a list for newcomers to FreeBSD.  It's
+intended for people who feel a little daunted by the system and need a bit of
+reassurance.  It's not the right place to ask any kind of technical question.
+.LI
+\f(CWFreeBSD-hackers@FreeBSD.org\fP is a technical discussion list.
+.LI
+\f(CWFreeBSD-current@FreeBSD.org\fP is an obligatory list for people who run the
+development version of FreeBSD, called \f(CWFreeBSD-CURRENT\fP.  We'll talk
+about \f(CW-CURRENT\fP, as it is usually called, on pages
+.Sref "\*[release-tags]" \&
+and
+.Sref "\*[current]" .
+.Le
+You can find a complete list on the web site.
+.P
+To join a list, send a mail message to \f(CWmajordomo@FreeBSD.org\fP with the
+names of the lists you want to join:
 .Dx
+subscribe FreeBSD-newbies
 subscribe FreeBSD-questions
 .De
+If the mail ID that you want to add to the list is different from the ID you're
+sending from, put the ID at the end of the line.  This requires manual
+intervention to confirm that the user really wants to be on the list, so it can
+take longer.  It's always better to send the mail from the ID at which you want
+to receive the mail.
+.P
 You don't need a subject line; if you include one, it will be ignored.  You'll
 get a reply back saying that the request must be authenticated: it'll look
 something like this:
@@ -984,7 +1121,7 @@
 If your mailer will not allow you to send the entire command as a single
 line, you may split it using backslashes, like so:
 
-        auth b2c64f95 subscribe freebsd-questions \
+        auth b2c64f95 subscribe freebsd-questions \e
         grog@example.org
 
 If you have any questions about the policy of the list owner, please
@@ -1030,57 +1167,75 @@
 question to be pretty technical.
 .De
 When submitting questions to \f(CW-questions\fP, remember that people are under
-no obligation to answer your question.  Make them want to answer it: submit the
-question in a clear, understandable manner.  For more details, see
+no obligation to answer them.  Make them want to answer it: submit the question
+in a clear, understandable manner.  For more details, see
 \fIhttp://www.lemis.com/questions.html\fP.  You may also like to check out the
 FreeBSD World Wide Web (WWW) site at \fIhttp://www.FreeBSD.org\fP, in particular
 the support page at \fIhttp://www.FreeBSD.org/support.html\fP.
 .P
 In addition, a number of companies offer support for FreeBSD.  See the web page
-\fIhttp://www.freebsd.org/commercial/consulting_bycat.html\fP\| for some
+\fIhttp://www.freebsd.org/commercial/consulting_bycat.html\fP\/ for some
 possibilities.
-.H3 "User Groups"
+.H3 "Unsubscribing from the mailing lists"
+There's a lot of traffic on the mailing lists, particularly on
+\f(CW-questions\fP.  You may find you can't take it and want to get out again.
+Again, send mail to \f(CWmajordomo@FreeBSD.org\fP, \f(BInot\fP\/ to the list.
+Each message you get from the mailing lists finishes with the following text:
+.Dx
+To Unsubscribe: send mail to majordomo@FreeBSD.org
+with "unsubscribe freebsd-questions" in the body of the message
+.De
+Don't be one of those people who send the unsubscribe request to the mailing
+list instead.
+.H3 "User groups"
+.X "user, groups"
 But how about meeting FreeBSD users face to face?  There are a number of user
 groups around the world.  If you live in a big city, chances are that there's
-one near you.  Check \fIhttp://www.freebsd.org/support.html#user\fP\| for a
-list.  If you don't find one, you might want to take the initiative and start
-one.
+one near you.  Check \fIhttp://www.freebsd.org/support.html#user\fP\/ for a
+list.  If you don't find one, consider taking the initiative and starting one.
 .P
+.X "BSDCon"
 In addition, USENIX holds an annual conference, the \fIBSDCon\fP, which deals
 with technical aspects of the BSD operating systems.  It's also a great
 opportunity to get to know other users from around the world.  If you're in
 Europe, there is also a BSDCon Europe, which at the time of writing was not run
-by USENIX.  See \fIhttp://www.eurobsdcon.org/\fP\| for more details.
+by USENIX.  See \fIhttp://www.eurobsdcon.org/\fP\/ for more details.
 .H3 "Reporting bugs"
-If you find something wrong with FreeBSD, we want to know about it.  There are
-two ways to report a bug:
-.Ls B
-.LI
-Report it via the World Wide Web at \fIhttp://www.FreeBSD.org/send-pr.html\fP.
-.LI
-Use the \fIsend-pr\fP\| program to send it as a mail message.
-.Le
-The second choice is preferable, since the web form enters text one line per
-paragraph, which irritates a lot of people.
-.H2 "The Berkeley d\(aemon"
+.X "reporting bugs"
+.X "bugs, reporting"
+If you find something wrong with FreeBSD, we want to know about it, so that we
+can fix it.  To report a bug, use the
+.Command send-pr
+program to send it as a mail message.
+.P
+There used to be a web form at
+.URI http://www.FreeBSD.org/send-pr.html ,
+but it has been closed down due to abuse.
+.H2 "The Berkeley daemon"
 .Pn bsdd
 .X "Branagan, Linda"
-.X "Berkeley d\(aemon"
-.X "d\(aemon, Berkeley"
+.X "Berkeley daemon"
+.X "daemon, Berkeley"
 .X "daemon, Berkeley"
 .X "Kolstad, Rob"
 .X "McKusick, Kirk"
-The little d\(aemon XXX check this XXX on the cover of this book symbolizes BSD.
-It is included with kind permission of Marshall Kirk McKusick, one of the
-leading members of the former Computer Sciences Research Group at the University
-of California at Berkeley, and owner of the d\(aemon's copyright.
-.P
-The d\(aemon has occasionally given rise to a certain amount of confusion.  In
-fact, it's a joking reference to processes which run in the background\(emsee
-\*[chunixref], page
+.XPSPIC -R -W 1.4i -0 images/daemon.ps
+.ll -1.6i
+The little daemon at the right symbolizes BSD.  It is included with kind
+permission of Marshall Kirk McKusick, one of the leading members of the former
+Computer Sciences Research Group at the University of California at Berkeley,
+and owner of the daemon's copyright.  Kirk also wrote the foreword to this book.
+.P
+The daemon has occasionally given rise to a certain amount of confusion.  In
+fact, it's a joking reference to processes that run in the background\(emsee
+.Sref "\*[chunixadmin]" ,
+page
 .Sref \*[daemon] ,
 for a description.  The outside world occasionally sees things differently, as
 the following story indicates:
+.br
+.ne 5v
+.ll
 .in 1m
 .\" XXX.ft CW
 .nf
@@ -1097,13 +1252,13 @@
 .fi
 .ad
 .sp .3v
-Linda Branagan is an expert on d\(aemons.  She has a T-shirt that sports the
-d\(aemon in tennis shoes that appears on the cover of the 4.3BSD manuals and
-\fIThe Design and Implementation of the 4.3BSD UNIX Operating System\fP\| by
-S. Leffler, M. McKusick, M. Karels, J. Quarterman, Addison-Wesley Publishing
+Linda Branagan is an expert on daemons.  She has a T-shirt that sports the
+daemon in tennis shoes that appears on the cover of the 4.3BSD manuals and
+\fIThe Design and Implementation of the 4.3BSD UNIX Operating System\fP\/ by
+S. Leffler, M. McKusick, M. Karels, J. Quarterman, Addison Wesley Publishing
 Company, Reading, MA 1989.
 .sp .3v
-She tells the following story about wearing the 4.3BSD d\(aemon T-shirt:
+She tells the following story about wearing the 4.3BSD daemon T-shirt:
 .sp .3v
 Last week I walked into a local ``home style cookin' restaurant/watering hole''
 in Texas to pick up a take-out order.  I spoke briefly to the waitress behind
@@ -1178,13 +1333,13 @@
 this all out of proportion.  A lot of people use this `kind of computers.'
 Universities, researchers, businesses.  They're actually very useful.''
 .sp .3v
-Big, big, \fIbig\fP\| mistake.  I should have guessed at what came next.
+Big, big, \fIbig\fP\/ mistake.  I should have guessed at what came next.
 .sp .3v
 Native: ``Does the government use these devil computers?''
 .sp .3v
 Me: ``Yes.''
 .sp .3v
-Another \fIbig\fP\| boo-boo.
+Another \fIbig\fP\/ boo-boo.
 .sp .3v
 Native: ``And does the government pay for 'em?  With our tax dollars?''
 .sp .3v
@@ -1197,8 +1352,10 @@
 Texas.  What a country.
 .in
 .P
-In fact, the d\(aemon tradition goes back quite a way.  As recently as 1996, the
-following message went through the \f(CWFreeBSD-chat\fP mailing list:
+.ne 3v
+The daemon tradition goes back quite a way.  As recently as 1996, after the
+publication of the first edition of this book, the following message went
+through the \f(CWFreeBSD-chat\fP mailing list:
 .in 1m
 .\"XXX.ft CW
 .nf
@@ -1221,7 +1378,7 @@
 .X "Salus, Peter"
 .X "Ferentz, Mel"
         Sherman, set the Wayback Machine for around 1976 or so (see Peter Salus'
-\fIA Quarter Century of UNIX\fP\| for details), when the first really national
+\fIA Quarter Century of UNIX\fP\/ for details), when the first really national
 UNIX meeting was held in Urbana, Illinois.  This would be after the ``forty
 people in a Brooklyn classroom'' meeting held by Mel Ferentz (yeah I was at that
 too) and the more-or-less simultaneous West Coast meeting(s) hosted by SRI, but
@@ -1248,15 +1405,15 @@
 I went down to my lab and shot some Polaroid snaps of the PDP-11 system I was
 running UNIX on at the time, and gave it to Phil with some descriptions of the
 visual puns I wanted: pipes, demons with forks running along the pipes, a ``bit
-bucket'' named \fI/dev/null\fP\|, all that.
+bucket'' named \fI/dev/null\fP, all that.
 .sp .3v
 	What Phil came up with is the artwork that graced the first decade's
-worth of ``UNIX T-shirts'', which were made by a Ma and Pa operation in a
+worth of ``UNIX T-shirts,'' which were made by a Ma and Pa operation in a
 Chicago suburb.  They turned out transfer art using a 3M color copier in their
 basement.  Hence, the PDP-11 is reversed (the tape drives are backwards) but
 since Phil left off the front panel, this was hard to tell.  His trademark
 signature was photo-reversed, but was recopied by the T-shirt people and
-``re-forwardized'', which is why it looks a little funny compared to his real
+``re-forwardized,'' which is why it looks a little funny compared to his real
 signature.
 .sp .3v
 	Dozens and dozens of these shirts were produced.  Bell Labs alone
@@ -1286,9 +1443,9 @@
 art, since it was a `work made for hire', though nothing was in writing (and
 note this was decades before the new copyright law).  I do not now recall if I
 explicitly assigned all rights to DEC.  What is certain is that John Lassiter's
-d\(aemon, whether knowingly borrowed from the original, or created by parallel
-evolution, postdates the first horde of UNIX d\(aemons by at least a decade and
-probably more.  And if Lassiter's d\(aemon looks a lot like a Phil Foglio
+daemon, whether knowingly borrowed from the original, or created by parallel
+evolution, postdates the first horde of UNIX daemons by at least a decade and
+probably more.  And if Lassiter's daemon looks a lot like a Phil Foglio
 creation, there's a reason.
 .sp .3v
         I have never scanned in Phil's artwork; I've hardly ever scanned in
@@ -1302,5 +1459,7 @@
 .P
 .in
 Note the date of this message: it appeared since the first edition of this book.
-Mike has since scanned the original teeshirt, and it may be made available.
-Remember, you read it here first.
+Since then, the daemon image has been scanned in, and you can find a version at
+.URI http://www.mckusick.com/beastie/shirts/usenix.html .
+.\" Here's a scan of the teeshirt.
+.\" .PIC images/olddaemon.ps 4i
