os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Sync with main branch.

Browse source
This commit is contained in:
davidg 1995-09-17 11:19:45 +00:00
parent a0da1bd663
commit bf41fdb032
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/branches/RELENG_2_1_0/; revision=84
26 changed files with 2729 additions and 1510 deletions

1397
FAQ/freebsd-faq.sgml
View file

File diff suppressed because it is too large Load diff

7
handbook/authors.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: authors.sgml,v 1.3 1995-05-18 03:05:00 jfieber Exp $ -->
<!-- $Id: authors.sgml,v 1.3.4.1 1995-09-17 11:19:21 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
@ -7,6 +7,7 @@ entities when referencing people.
-->
<!ENTITY a.asami "Satoshi Asami <tt>&lt;asami@FreeBSD.org&gt;</tt>">
<!ENTITY a.awebster "Andrew Webster <tt>&lt;awebster@dataradio.com&gt;</tt>">
<!ENTITY a.davidg "David Greenman <tt>&lt;davidg@Root.COM&gt;</tt>">
<!ENTITY a.dufalt "Peter Dufault <tt>&lt;dufault@hda.com&gt;</tt>">
<!ENTITY a.gclarkii "Gary Clark II <tt>&lt;gclarkii@FreeBSD.org&gt;</tt>">
@ -20,5 +21,9 @@ entities when referencing people.
<!ENTITY a.mark "Mark Murray <tt>&lt;mark@grondar.za&gt;</tt>">
<!ENTITY a.martin "Martin Renters <tt>&lt;martin@innovus.com&gt;</tt>">
<!ENTITY a.md "Mark Dapoz <tt>&lt;md@bsc.no&gt;</tt>">
<!ENTITY a.nik "Nik Clayton <tt>&lt;nik@blueberry.co.uk&gt;</tt>">
<!ENTITY a.phk "Poul-Henning Kamp <tt>&lt;phk@FreeBSD.org&gt;</tt>">
<!ENTITY a.paul "Paul Richards <tt>&lt;paul@FreeBSD.org&gt;</tt>">
<!ENTITY a.rgrimes "Rodney Grimes <tt>&lt;rgrimes@FreeBSD.org&gt;</tt>">
<!ENTITY a.whiteside "Don Whiteside <tt>&lt;whiteside@acm.org&gt;</tt>">
<!ENTITY a.wilko "Wilko Bulte <tt>&lt;wilko@yedi.iaf.nl&gt;</tt>">

33
handbook/basics.sgml
View file

@ -1,10 +1,10 @@
<!-- $Id: basics.sgml,v 1.1.1.1 1995-04-28 16:19:59 jfieber Exp $ -->
<!-- $Id: basics.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:22 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Unix Basics</heading>
<chapt><heading>Unix Basics<label id="basics"></heading>
<sect>
<heading>The online manual</heading>
<heading>The online manual<label id="basics:man"></heading>
<p>The most comprehensive documentation on FreeBSD is in
the form of <em>man pages</em>. Nearly every program
@ -14,13 +14,13 @@
<tt><bf>man</bf></tt> command. Use of the
<tt><bf>man</bf></tt> command is simple:
<tscreen>
<tt><bf>man</bf> <it>command</it></tt>
<bf>man</bf> <it>command</it>
</tscreen>
where <it>command</it> is the name of the command
you wish to find. For example, to learn more about
you wish to learn about. For example, to learn more about
<tt><bf>ls</bf></tt> command type:
<tscreen>
<tt><bf>man</bf> ls</tt>
% <bf>man ls</bf>
</tscreen>
<p>The online manual is divided up into numbered
@ -42,7 +42,7 @@
you can tell the <tt><bf>man</bf></tt> command which
you want by specifying the section:
<tscreen>
<tt><bf>man</bf> 1 chmod</tt>
% <bf>man 1 chmod</bf>
</tscreen>
which will display the manual page for the user command
<tt><bf>chmod</bf></tt>.
@ -50,24 +50,29 @@
<p>This is fine if you know the name of the command and
forgot how to use it, but what if you cannot recall the
command name? You can use <tt><bf>man</bf></tt> to
search through the command <em>descriptions</em> by
search for keywords in the command <em>descriptions</em> by
using the <tt><bf>-k</bf></tt> switch:
<tscreen>
<tt><bf>man</bf> -k mail</tt>
% <bf>man -k mail</bf>
</tscreen>
With this command you will be presented with a list of
commands that have the keyword `mail' in their
descriptions.
<sect>
<heading>GNU Info files</heading>
<heading>GNU Info files<label id="basics:info"></heading>
<p>FreeBSD includes many applications and utilities
produced by the Free Software Foundation (FSF). In
addition to man pages, these programs come with more
extensive <em>info</em> files which can be viewed with
the <tt>info</tt> command or, if you installed
<tt>emacs</tt>, the info mode of <tt>emacs</tt>.
extensive hypertext documents called <em>info</em>
files which can be viewed with the <tt>info</tt>
command or, if you installed <tt>emacs</tt>, the info
mode of <tt>emacs</tt>.
To use the <tt>info(1)</tt> command, simply type:
<tscreen>% <bf>info</bf></tscreen> For a brief
introduction, type <tt><bf>h</bf></tt>, and for a quick
command reference, type <tt><bf>?</bf></tt>.
</sect>

96
handbook/bibliography.sgml
View file

@ -1,8 +1,8 @@
<!-- $Id: bibliography.sgml,v 1.1.1.1 1995-04-28 16:19:59 jfieber Exp $ -->
<!-- $Id: bibliography.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:23 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt>
<heading>Bibliography</heading>
<heading>Bibliography<label id="bibliography"></heading>
<p>While the manual pages provide the definative reference
for individual pieces of the FreeBSD operating system,
@ -16,33 +16,52 @@
<heading>Users' guides</heading>
<p><itemize>
<item>Gilley, Daniel. <sl>Unix in a Nutshell</sl>.
O'Reilly &amp; Associates, Inc. 1990</item>
<item>Computer Systems Research Group, UC Berkeley.
<sl>4.4BSD User's Reference Manual</sl>.
O'Reilly &amp; Associates, Inc., 1994.
<newline>ISBN 1-56592-075-9</item>
<item>Computer Systems Research Group, UC Berkeley.
<sl>4.4BSD User's Supplementary Documents</sl>.
O'Reilly &amp; Associates, Inc., 1994.
<newline>ISBN 1-56592-076-7</item>
<item><sl>Unix in a Nutshell</sl>.
O'Reilly &amp; Associates, Inc., 1990.
<newline>ISBN 093717520X</item>
</itemize>
<sect>
<heading>Administrators' guides</heading>
<p><itemize>
<item>Albitz, Paul; Liu, Cricket. <em>DNS and
BIND</em>. O'Reilley &amp; Associates. 1993. ISBN
1-56592-010-4 </item>
<item>Albitz, Paul and Liu, Cricket. <em>DNS and
BIND</em>. O'Reilly &amp; Associates, Inc., 1993.
<newline>ISBN 1-56592-010-4 </item>
<item>Costales, Brian; Allman, Eric; Rickert,
Neil. <em>sendmail</em> O'Reilley &amp;
Associates. 1993. ISBN 1-56592-056-2 </item>
<item>Computer Systems Research Group, UC Berkeley.
<sl>4.4BSD System Manager's Manual</sl>.
O'Reilly &amp; Associates, Inc., 1994.
<newline>ISBN 1-56592-080-5</item>
<item>Costales, Brian, et al.
<em>Sendmail</em>. O'Reilly &amp;
Associates, Inc., 1993. <newline>ISBN 1-56592-056-2 </item>
<item>Frisch, &AElig;leen. <em>Essential System
Administration</em>. O'Reilley &amp;
Associates. 1993. ISBN 0-937175-80-3 </item>
Administration</em>. O'Reilly &amp;
Associates, Inc., 1993. <newline>ISBN 0-937175-80-3 </item>
<item>Hunt, Craig. <em>TCP/IP Network Administration</em>
O'Reilley &amp; Associates. 1992. ISBN 0-937175-82-X</item>
<item>Hunt, Craig. <em>TCP/IP Network Administration</em>.
O'Reilly &amp; Associates, Inc., 1992.
<newline>ISBN 0-937175-82-X</item>
<item>Nemeth, Evi. <em>Unix System Administration
Handbook</em>. Prentice Hall. 1989. ISBN
0-13-933441-6</item>
Handbook</em>. 2nd ed. Prentice Hall, 1995.
<newline>ISBN 0131510517</item>
</itemize>
@ -54,18 +73,27 @@
<p><itemize>
<item>Asente, Paul. <em>X Window System
Toolkit</em>. Digital Press. ISBN
1-55558-051-3</item>
Toolkit</em>. Digital Press.
<newline>ISBN 1-55558-051-3</item>
<item>Computer Systems Research Group, UC Berkeley.
<sl>4.4BSD Programmer's Reference Manual</sl>.
O'Reilly &amp; Associates, Inc., 1994.
<newline>ISBN 1-56592-078-3</item>
<item>Computer Systems Research Group, UC Berkeley.
<sl>4.4BSD Programmer's Supplementary Documents</sl>.
O'Reilly &amp; Associates, Inc., 1994.
<newline>ISBN 1-56592-079-1</item>
<item>Ellis, Margaret A. and Stroustrup,
Bjarne. <em>The Annotated C++ Reference
Manual</em>. Addison-Wesley. 1990. ISBN
0-201-51459-1</item>
Manual</em>. Addison-Wesley, 1990.
<newline>ISBN 0-201-51459-1</item>
<item>Harbison, Samuel P. and Steele, Guy
L. Jr. <em>C: A Reference Manual</em>. Prentice
Hall. 3rd Edition, 1991. ISBN
0-13-110933-2</item>
L. Jr. <em>C: A Reference Manual</em>. 3rd ed. Prentice
Hall, 1991. <newline>ISBN 0-13-110933-2</item>
<item>Jolitz, William. "Porting UNIX to the
386". <em>Dr. Dobb's Journal</em>. January
@ -73,11 +101,11 @@
<item>Leffler, Samuel J. <em>The Design and
implementation of the 4.3BSD UNIX operating
system</em>. Addison-Wesley. 1989.</item>
system</em>. Addison-Wesley, 1989.</item>
<item>Plauger, P. J. <em>The Standard C
Library</em>. Prentice Hall. 1992. ISBN
0-13-131509-9</item>
Library</em>. Prentice Hall, 1992.
<newline>ISBN 0-13-131509-9</item>
<item>Wells, Bill. "Writing Serial Drivers for UNIX".
<em>Dr. Dobb's Journal</em>. 19(15), December
@ -90,9 +118,19 @@
<p><itemize>
<item>Stanley, Tom; Anderson, Don. <em>PCI System
Architechure</em>. Mindshare, Inc. ISBN
1-881609-08-1</item>
<item>Stanley, Tom. <em>ISA System
Architechure</em>. 3rd ed. Reading, Mass. :
Addison-Wesley, 1995.
<newline>ISBN 0201409968</item>
<item>Stanley, Tom. <em>PCI System
Architechure</em>. 3rd ed. Reading, Mass. :
Addison-Wesley, 1995. <newline>ISBN
0201409933</item>
<item>Van Gilluwe, Frank. <em>The Undocumented PC</em>.
Reading, Mass: Addison-Wesley Pub. Co., 1994.
<newline>ISBN 0-201-62277-7</item>
</itemize>

67
handbook/booting.sgml
View file

@ -3,7 +3,7 @@
This conversion has been made by Ollivier Robert.
$Id: booting.sgml,v 1.2 1995-05-10 11:34:06 jfieber Exp $
$Id: booting.sgml,v 1.2.4.1 1995-09-17 11:19:24 davidg Exp $
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
@ -22,7 +22,7 @@
<toc>
-->
<chapt><heading>Booting FreeBSD on a PC</heading>
<chapt><heading>The FreeBSD Booting Process<label id="booting"></heading>
<p><em>Contributed by &a.phk;. v1.1, April 26th.</em>
@ -30,28 +30,25 @@
determine the root filesystem and initialize user-land things. This
leads to some interesting possibilities shown below.
<sect>Loading a kernel
<sect><heading>Loading a kernel</heading>
<p>
We presently have three basic mechanisms for loading the kernel:
<enum>
<item>biosboot
<item>dosboot
<item>netboot
</enum>
Each will be described in detail below. They all pass some
We presently have three basic mechanisms for loading the
kernel as described below:
They all pass some
information to the kernel to help the kernel decide what to do
next.
<sect1>Biosboot
<p>
<descrip>
<tag>Biosboot</tag>
Biosboot is our ``bootblocks'', it consists of two files, which
will be installed in the first 8Kbytes of the floppy or hard-disk
slice to be booted from.
Biosboot can load a kernel from a FreeBSD filesystem.
<sect1>Dosboot
<p>
<tag>Dosboot</tag>
Dosboot was written by DI. Christian Gusenbauer, and is
unfortunately at this time one of the few pieces of code that
isn't compilable under FreeBSD itself because it is written for
@ -63,53 +60,51 @@
high memory on MS/DOS systems and usually wins them for it's
case.
<sect1>Netboot
<p>
<tag>Netboot</tag>
Netboot will try to find a supported ethernet card, and use
BOOTP, TFTP and NFS to find a kernel file to boot.
</descrip>
<sect>Determine the root filesystem
<sect><heading>Determine the root filesystem</heading>
<p>
Once the kernel is loaded and the boot-code jumps to it, the kernel
will initialize itself, trying to determine what hardware is
present and so on, and then it needs to find a root filesystem.
Presently we support the following types of rootfilesystems:
<itemize>
<item>UFS
<item>MSDOS
<item>MFS
<item>CD9660
<item>NFS
</itemize>
<sect1>UFS
<p>
<descrip>
<tag>UFS</tag>
This is the most normal type of root filesystem. It can reside on
a floppy or on harddisk.
<sect1>MSDOS
<p>
<tag>MSDOS</tag>
While this is technically possible, it isn't particular useful,
because of ``FAT'' filesystems inability to make links, device
nodes and such ``UNIXisms''.
<sect1>MFS
<p>
<tag>MFS</tag>
This is actually a UFS filesystem which has been compiled into
the kernel. That means that the kernel does not really need any
disks/floppies or other HW to function.
<sect1>CD9660
<p>
<tag>CD9660</tag>
This is for using a CD-ROM as root filesystem.
<sect1>NFS
<p>
<tag>NFS</tag>
This is for using a fileserver as root filesystem, basically
making it a diskless machine.
</descrip>
<sect>Initialize user-land things
<sect><heading>Initialize user-land things</heading>
<p>
To get the user-land going, when the kernel has finished
initialization, it will create a with ``<tt/pid == 1/'' and execute
@ -124,7 +119,7 @@
1/''.
<sect>Interesting combinations
<sect><heading>Interesting combinations</heading>
<p>
Boot a kernel with a MFS in it with a special <tt>/sbin/init</tt>
which...

24
handbook/ctm.sgml
View file

@ -3,7 +3,7 @@
#
# Converted by Ollivier RObert <roberto@FreeBSD.ORG>
#
# $Id: ctm.sgml,v 1.1.1.1 1995-04-28 16:19:59 jfieber Exp $
# $Id: ctm.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:25 davidg Exp $
#
# ----------------------------------------------------------------------------
# "THE BEER-WARE LICENSE" (Revision 42):
@ -14,7 +14,7 @@
#
-->
<sect><heading>CTM</heading>
<sect><heading>CTM<label id="ctm"></heading>
<p><em>Contributed by &a.phk;. Updated 16-Mar-1995.</em>
@ -25,7 +25,7 @@
this time on the process of creating deltas, so talk to &a.phk;
for more information should you wish to use <tt/CTM/ for other things.
<sect1>Why should I use <tt/CTM/ ?
<sect1><heading>Why should I use <tt/CTM/?</heading>
<p><tt/CTM/ will give you a local copy of the ``FreeBSD-current''
sources. If you are an active developer on FreeBSD, but have lousy
or non-existent TCP/IP connectivity, <tt/CTM/ was made for you.
@ -37,13 +37,9 @@
You will also need to make yourself aware of the various caveats in
running ``current'' sources, and for this it is recommended that
you refer to the relevant FAQ which can be found in
<verb>
/usr/share/FAQ/Text/current-policy.FAQ
</verb>
<!-- XXX -->
you read <ref id="current" name="Staying current with FreeBSD">.
<sect1>What do I need to use <tt/CTM/?
<sect1><heading>What do I need to use <tt/CTM/?</heading>
<p>You will need two things: The ``<tt/CTM/'' program and the initial
deltas to feed it (to get up to ``current'' levels).
@ -86,7 +82,7 @@
posted. Send an email to <tt/majordomo@freebsd.org/ with a single
line of ``<tt/subscribe ctm-announce/'' to get added to the list.
<sect1>Starting off with <tt/CTM/ for the first time:
<sect1><heading>Starting off with <tt/CTM/ for the first time</heading>
<p>Before you can start using <tt/CTM/ deltas, you will need to get a
special ``base'' delta that provides a starting point for all
deltas produced subsequently to it.
@ -104,7 +100,7 @@
Once you've picked a base delta to start from, you will also need
all deltas with higher numbers following it.
<sect1>Using <tt/CTM/ in your daily life:
<sect1><heading>Using <tt/CTM/ in your daily life</heading>
<p>To apply the deltas, simply say
<verb>
cd /where/ever/you/want/the/stuff
@ -134,7 +130,7 @@
make a copy.
<sect1>Future plans for <tt/CTM/
<sect1><heading>Future plans for <tt/CTM/</heading>
<p>
Tons of them:
<itemize>
@ -159,7 +155,7 @@
The bad news is that I am very busy, so any help in doing this will
be most welcome. And don't forget to tell me what you want also...
<sect1>Miscellaneous stuff
<sect1><heading>Miscellaneous stuff</heading>
<p>
All the ``DES infected'' (e.g. export controlled) source is not
included. You will get the ``international'' version only. If
@ -182,7 +178,7 @@
for details.
<sect1>Thanks!
<sect1><heading>Thanks!</heading>
<p>
<descrip>
<tag/Bruce Evans/

6
handbook/current.sgml
View file

@ -1,8 +1,8 @@
<!-- $Id: current.sgml,v 1.2 1995-05-18 03:05:03 jfieber Exp $ -->
<!-- $Id: current.sgml,v 1.2.4.1 1995-09-17 11:19:26 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Staying current with FreeBSD<label id="current:"></heading>
<chapt><heading>Staying current with FreeBSD<label id="current"></heading>
<p><em>Contributed by &a.jkh;.</em>
@ -10,7 +10,7 @@
THE FREEBSD CURRENT POLICY
Last updated: $Date: 1995-05-18 03:05:03 $
Last updated: $Date: 1995-09-17 11:19:26 $
This document attempts to explain the rationale behind FreeBSD-current,
what you should expect should you decide to run it, and states some

54
handbook/dialup.sgml
View file

@ -1,6 +1,6 @@
<!-- This is an SGML document in the linuxdoc DTD of the Tutorial for
Configuring a FreeBSD for Dialup Services by Guy Helmer.
$Id: dialup.sgml,v 1.1.1.1 1995-04-28 16:19:59 jfieber Exp $
$Id: dialup.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:26 davidg Exp $
<!DOCTYPE linuxdoc PUBLIC "-//Linux//DTD linuxdoc//EN">
@ -15,7 +15,7 @@ Configuring FreeBSD for Dialup Services
-->
<sect><heading>Dialup access</heading>
<sect><heading>Dialup access<label id="dialup"></heading>
<p><em>Contributed by &a.ghelmer;.</em>
@ -37,7 +37,7 @@ in a UNIX-like environment, and how to look up manual pages on the
system. As discussed below, you'll need certain versions of FreeBSD,
and knowledge of some terminology &amp; modem and cabling.
<sect2>FreeBSD Version
<sect2><heading>FreeBSD Version</heading>
<p>
First, it is assumed that you are using FreeBSD version 1.1 or higher
@ -47,7 +47,7 @@ device driver (<tt/sio/) has improved in every release of FreeBSD, so
more recent versions of FreeBSD are assumed to have better and more
efficient drivers than earlier versions.
<sect2>Terminology
<sect2><heading>Terminology</heading>
<p>
A quick rundown of terminology:
@ -74,7 +74,7 @@ transitions that may be made in a period of time, while <bf/bps/ (bits
per second) is the ``correct'' term to use (at least it doesn't seem
to bother the curmudgeons quite a much).
<sect2>External vs. Internal Modems
<sect2><heading>External vs. Internal Modems</heading>
<p>
External modems seem to be more convenient for dialup, because
@ -89,7 +89,7 @@ may be limited only to setting DIP switches. If your internal modem
has any signal indicator lights, it is probably difficult to view the
lights when the system's cover is in place.
<sect2>Modems and Cables
<sect2><heading>Modems and Cables</heading>
<p>
A background knowledge of these items is assumed
@ -149,7 +149,7 @@ watching for status reports from the modem. If you are familiar with
connecting modems to PC-based bulletin board systems, this may seem
awkward.
<sect2>Serial Interface Considerations
<sect2><heading>Serial Interface Considerations</heading>
<p>
FreeBSD supports NS8250-, NS16450-, NS16550-, and NS16550A-based EIA
@ -163,7 +163,7 @@ devices, 16550A-based serial interface cards are much prefered. If
the system has many active serial ports or will have a heavy load,
16550A-based cards are better for low-error-rate communications.
<sect1>Quick Overview
<sect1><heading>Quick Overview</heading>
<p>
Here is the process that FreeBSD follows to accept dialup logins. A
@ -192,7 +192,7 @@ by asking for the user's password and then starting the user's shell.
Let's dive into the configuration...
<sect1>Kernel Configuration
<sect1><heading>Kernel Configuration</heading>
<p>
FreeBSD kernels typically come prepared to search for four serial
@ -278,7 +278,7 @@ program <tt/config/ as documented in ``Building Berkeley Kernels with
Config'' and the <tt/config(8)/ manual page to prepare a kernel
building directory, then build, install, and test the new kernel.
<sect1>Device Special Files
<sect1><heading>Device Special Files</heading>
<p>
Most devices in the kernel are accessed through ``device special
@ -297,7 +297,7 @@ and <tt/stty(1)/ for information on the terminal settings, locking
&amp; initializing devices, and setting terminal options,
respectively.
<sect2>Making Device Special Files
<sect2><heading>Making Device Special Files</heading>
<p>
A shell script called <tt/MAKEDEV/ in the <tt>/dev</tt> directory
@ -330,7 +330,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01
These permissions allow the user <tt/uucp/ and users in the group
<tt/dialer/ to use the call-out devices.
<sect1>Configuration Files
<sect1><heading>Configuration Files</heading>
<p>
There are three system configuration files in the <tt>/etc</tt>
@ -376,7 +376,7 @@ The author will try to give balanced configuration information, but is
biased towards having the modem's data rate follow the connection
rate.
<sect2>/etc/gettytab
<sect2><heading>/etc/gettytab</heading>
<p>
<tt>/etc/gettytab</tt> is a <tt/termcap(5)/-style file of
@ -384,14 +384,14 @@ configuration information for <tt/getty(8)/. Please see the
<tt/gettytab(4)/ manual page for complete information on the format of
the file and the list of capabilities.
<sect3>Locked-Speed Config
<sect3><heading>Locked-Speed Config</heading>
<p>
If you are locking your modem's data communications rate at a
particular speed, you probably won't need to make any changes to
<tt>/etc/gettytab</tt>.
<sect3>Matching-Speed Config
<sect3><heading>Matching-Speed Config</heading>
<p>
You'll need to setup an entry in <tt>/etc/gettytab</tt> to give
@ -472,7 +472,7 @@ If you have a slow CPU or a heavily loaded system and you don't have
16550A-based serial ports, you may receive sio ``silo'' errors at 57.6
Kbps.
<sect2>/etc/ttys
<sect2><heading>/etc/ttys</heading>
<p>
<tt>/etc/ttys</tt> is the list of <tt/ttys/ for <tt/init/ to monitor.
@ -521,7 +521,7 @@ to send the signal. If this is your first time setting up the system,
though, you may want to wait until your modem(s) are properly
configured and connected before signalling <tt/init/.
<sect3>Locked-Speed Config
<sect3><heading>Locked-Speed Config</heading>
<p>
For a locked-speed configuration, your <tt/ttys/ entry needs to
@ -537,7 +537,7 @@ If your modem is locked at a different data rate, substitute the
appropriate name for the <tt>std.<em/speed/</tt> entry for
<tt/std.19200/ from <tt>/etc/gettytab</tt> for your modem's data rate.
<sect3>Matching-Speed Config
<sect3><heading>Matching-Speed Config</heading>
<p>
In a matching-speed configuration, your <tt/ttys/ entry needs to
@ -551,7 +551,7 @@ entry for a matching-speed modem that starts at 19.2 Kbps (the
ttyd0 "/usr/libexec/getty V19200" dialup on
</verb></tscreen>
<sect2>/etc/rc.serial or /etc/rc.local
<sect2><heading>/etc/rc.serial or /etc/rc.local</heading>
<p>
High-speed modems, like V.32, V.32bis, and V.34 modems, need to use
@ -590,7 +590,7 @@ Since there isn't an initialization device special file on FreeBSD
1.1, one has to just set the flags on the sole device special file and
hope the flags aren't cleared by a miscreant.
<sect1>Modem Settings
<sect1><heading>Modem Settings</heading>
<p>
If you have a modem whose parameters may be permanently set in
@ -664,7 +664,7 @@ prompt to a modem that is in command mode and the modem echoes the
command or returns a result code. I've heard this sequence can result
in a extended, silly conversation between <tt/getty/ and the modem.
<sect2>Locked-speed Config
<sect2><heading>Locked-speed Config</heading>
<p>
For a locked-speed configuration, you'll need to configure the modem
@ -678,7 +678,7 @@ ATZ
AT&amp;B1&amp;W
</verb></tscreen>
<sect2>Matching-speed Config
<sect2><heading>Matching-speed Config</heading>
<p>
For a variable-speed configuration, you'll need to configure your
@ -693,7 +693,7 @@ ATZ
AT&amp;B2&amp;W
</verb></tscreen>
<sect2>Checking the Modem's Configuration
<sect2><heading>Checking the Modem's Configuration</heading>
<p>
Most high-speed modems provide commands to view the modem's current
@ -706,13 +706,13 @@ switch settings), use the commands <tt/ATZ/ and then <tt/ATI4/.
If you have a different brand of modem, check your modem's manual to
see how to double-check your modem's configuration parameters.
<sect1>Troubleshooting
<sect1><heading>Troubleshooting</heading>
<p>
Here are a few steps you can follow to check out the dialup modem on
your system.
<sect2>Checking out the FreeBSD system
<sect2><heading>Checking out the FreeBSD system</heading>
<p>
Hook up your modem to your FreeBSD system, boot the system, and, if
@ -755,7 +755,7 @@ messages, triple-check the configuration files <tt>/etc/ttys</tt> and
files <tt>/dev/ttyd?</tt>, for any mistakes, missing entries, or
missing device special files.
<sect2>Try Dialing In
<sect2><heading>Try Dialing In</heading>
<p>
Try dialing into the system; be sure to use 8 bits, no parity, 1 stop
@ -794,7 +794,7 @@ perhaps you can send an electronic mail message to
<tt>FreeBSD-Questions@freebsd.org</tt> describing your modem and your
problem, and the good folks on the list will try to help.
<sect1>Acknowledgements
<sect1><heading>Acknowledgements</heading>
<p>
Thanks to these people for comments and advice:

4
handbook/diskless.sgml
View file

@ -1,7 +1,7 @@
<!-- $Id: diskless.sgml,v 1.1.1.1 1995-04-28 16:19:59 jfieber Exp $ -->
<!-- $Id: diskless.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:28 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>Diskless operation</heading>
<sect><heading>Diskless operation<label id="diskless"></heading>
<p><em>Contributed by &a.martin;.</em>

177
handbook/eresources.sgml
View file

@ -1,18 +1,32 @@
<!-- $Id: eresources.sgml,v 1.2 1995-05-18 03:05:06 jfieber Exp $ -->
<!-- $Id: eresources.sgml,v 1.2.4.1 1995-09-17 11:19:28 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt>
<heading>Additional resources on the Internet</heading>
<chapt>
<heading>Resources on the Internet<label id="eresources"></heading>
<p>The rapid pace of FreeBSD progress makes print media
impractical as a means for following the latest
developments. Electronic resources are the best, if not the
only way stay informed of the latest advances. Also, since
FreeBSD is a volunteer effort, the user community also serves
as the technical support department and invariably,
electronic mail and Usenet news are the most effective way of
getting technical problems resolved.
Below, the most important points of contact with the FreeBSD
user community are outlined. If you are aware of other
resources not included, please send them to
<tt>doc@freebsd.org</tt> so they may be included.
<sect>
<heading>Mailing lists<label id="eresources:mailing-lists"></heading>
<heading>Mailing lists<label id="eresources:mail"></heading>
<p><em>Contributed by &a.dufalt;.<newline>
5 May 1995.</em>
20 Jun 1995.</em>
Though many of the FreeBSD development members read USENET, we cannot
always guarantee that we'll get to your questions in a timely fashion
(or at all) if you post them only to one of the comp.os.386bsd.*
(or at all) if you post them only to one of the comp.unix.bsd.*
groups. By addressing your questions to the appropriate mailing list
you will reach both us and a concentrated FreeBSD audience, invariably
assuring a better (or at least faster) response.
@ -22,6 +36,12 @@ the list charter before joining a list. We must strive to
keep the signal to noise ratio of the lists high, especially in
the technical lists.
Archives are kept for all of the mailing lists and can be searched
using the the <url url="http://www.freebsd.org/How/mail-archive.html"
name="FreeBSD World Wide Web server">. The keyword searchable archive
offers an excellent way to find answers to frequently asked questions
and should be consulted before posting a question.
<sect1><heading>List summary</heading>
<p><bf>General lists:</bf> The following are general lists that
@ -47,6 +67,7 @@ freebsd-doc Documentation project
freebsd-fs Filesystems
freebsd-hackers General Technical discussions
freebsd-hardware General discussion of FreeBSD hardware
freebsd-multimedia Multimedia discussions
freebsd-platforms Porting to Non-Intel platforms
freebsd-ports Discussion of "ports"
freebsd-security Security issues
@ -65,6 +86,7 @@ freebsd-admin Administrative issues
freebsd-arch Architecture and design discussions
freebsd-core FreeBSD core team
freebsd-install Installation development
freebsd-user-groups User group coordination
</verb>
<bf>CVS lists:</bf> The following lists are for people seeing the log messages
@ -92,9 +114,10 @@ cvs-usrsbin /usr/src/usr.sbin System binaries
<sect1><heading>How to subscribe</heading>
<p>All mailing lists live on `FreeBSD.ORG', so to post to a list you
simply mail to `&lt;listname&gt;@FreeBSD.ORG'. It will then be redistributed
to mailing list members throughout the world.
<p>All mailing lists live on <tt>FreeBSD.ORG</tt>, so to post to a
list you simply mail to <em>listname</em><tt>@FreeBSD.ORG</tt>. It
will then be redistributed to mailing list members throughout the
world.
To subscribe to a list, send mail to:
<tscreen><verb>
@ -173,12 +196,18 @@ technical lists, but the follow ups should be directed to this
This is an internal mailing list for use by the core members.
<tag/FREEBSD-CURRENT/ <em>Discussions about the use of
FreeBSD-current</em><newline>
This is the mailing list for users of freebsd-current. It includes
warnings about new features coming out in -current that will affect the
users, and instructions on steps that must be taken to remain -current.
FreeBSD-current</em><newline> This is the mailing list for users
of freebsd-current. It includes warnings about new features
coming out in -current that will affect the users, and
instructions on steps that must be taken to remain -current.
Anyone running "current" must subscribe to this list.
<tag/FREEBSD-CURRENT-DIGEST/ <em>Discussions about the use of
FreeBSD-current</em><newline> This is the digest version of the
freebsd-current mailing list. The digest consists of all
messages sent to freebsd-current bundled together and mailed out
as a single message. The average digest size is about 40kB.
<tag/FREEBSD-DOC/ <em>Documentation project</em><newline>
This mailing list belongs to the FreeBSD Doc Project and is for
the discussion of documentation related issues and projects.
@ -193,27 +222,37 @@ is for individuals actively working on FreeBSD, to bring up problems
or discuss alternative solutions. Individuals interested in
following the technical discussion are also welcome.
<tag/FREEBSD-HACKERS-DIGEST/ <em>Technical
discussions</em><newline> This is the digest version of the
freebsd-hackers mailing list. The digest consists of all
messages sent to freebsd-hackers bundled together and mailed out
as a single message. The average digest size is about 40kB.
<tag/FREEBSD-HARDWARE/ <em>General discussion of FreeBSD
hardware</em><newline>
General discussion about the types of hardware that FreeBSD runs on,
various problems and suggestions concerning what to buy or avoid.
hardware</em><newline> General discussion about the types of
hardware that FreeBSD runs on, various problems and suggestions
concerning what to buy or avoid.
<tag/FREEBSD-INSTALL/ <em>Installation discussion</em><newline>
This is the mailing list for people discussing FreeBSD installation
development for the 2.0 release.
<tag/FREEBSD-MULTIMEDIA/ <em>Multimedia discussions</em><newline>
This is a forum about multimedia applications using FreeBSD.
Discussion center around multimedia applications, their installation, their
development and their support within FreeBSD
<tag/FREEBSD-PLATFORMS/ <em>Porting to Non-Intel
platforms</em><newline>
Cross-platform freebsd issues, general discussion and proposals for
non-Intel FreeBSD ports.
platforms</em><newline> Cross-platform freebsd issues, general
discussion and proposals for non-Intel FreeBSD ports.
<tag/FREEBSD-POLICY/ <em>Policy issues and
suggestions</em><newline>
This is a forum for policy discussions related to FreeBSD. This
includes where FreeBSD is going, how to set up a consortium, whether
or not and how to make FreeBSD pay for itself, how to attract more
users, and so on. When a topic relates directly to FreeBSD but has
little or no technical content then it should be sent to this list.
suggestions</em><newline> This is a forum for policy discussions
related to FreeBSD. This includes where FreeBSD is going, how to
set up a consortium, whether or not and how to make FreeBSD pay
for itself, how to attract more users, and so on. When a topic
relates directly to FreeBSD but has little or no technical
content then it should be sent to this list.
<tag/FREEBSD-PORTS/ <em>Discussion of "ports"</em><newline>
Discussions concerning FreeBSD's "ports collection" (/usr/ports), proposed
@ -225,6 +264,12 @@ This is the mailing list for questions about FreeBSD. You should not
send "how to" questions to the technical lists unless you consider the
question to be pretty technical.
<tag/FREEBSD-QUESTIONS-DIGEST/ <em>User questions</em><newline>
This is the digest version of the freebsd-questions mailing list.
The digest consists of all messages sent to freebsd-questions
bundled together and mailed out as a single message. The average
digest size is about 40kB.
<tag/FREEBSD-SCSI/ <em>SCSI subsystem</em><newline>
This is the mailing list for people working on the scsi subsystem
for FreeBSD.
@ -232,66 +277,78 @@ for FreeBSD.
<tag/FREEBSD-SECURITY/ <em>Security issues</em><newline>
FreeBSD computer security issues (DES, Kerberos, known security holes and
fixes, etc).
<tag/FREEBSD-USER-GROUPS/ <em>User Group Coordination List</em><newline>
This is the mailing list for the coordinators from each of the
local area Users Groups to dicuss matters with each other and a
designated individual from the Core Team. This mail list should
be limited to meeting synopsis and coordination of projects that span
User Groups.
</descrip>
<sect>
<heading>Usenet newsgroups</heading>
<heading>Usenet newsgroups<label id="eresources:news"></heading>
<p>While no newsgroups dedicated to FreeBSD exist, there
are many in which FreeBSD is discussed or are otherwise
relevant to FreeBSD users.
<p>In addition to two FreeBSD specific newsgroups, there
are many others in which FreeBSD is discussed or are
otherwise relevant to FreeBSD users. <url
url="http://minnie.cs.adfa.oz.au/BSD-info/bsdnews&lowbar;search.html"
name="Keyword searchable archives"> are available for
some of these newsgroups from courtesy of Warren Toomey
<tt>&lt;wkt@cs.adfa.oz.au&gt;</tt>.
<sect1>
<heading>BSD specific newsgroups</heading>
<p><itemize>
<item> comp.unix.bsd.freebsd.announce
<item> comp.unix.bsd.freebsd.misc
<item>comp.unix.bsd.freebsd.announce
<item>comp.unix.bsd.freebsd.misc
</itemize>
<sect1>
<heading>Other Unix newsgroups of interest</heading>
<p><itemize>
<item> comp.unix
<item> comp.unix.questions
<item> comp.unix.admin
<item> comp.unix.programmer
<item> comp.unix.shell
<item> comp.unix.user-friendly
<item> comp.security.unix
<item> comp.sources.unix
<item> comp.unix.advocacy
<item> comp.unix.misc
<item> comp.os.386bsd.announce
<item> comp.os.386bsd.apps
<item> comp.os.386bsd.bugs
<item> comp.os.386bsd.development
<item> comp.os.386bsd.misc
<item> comp.os.386bsd.questions
<item> comp.bugs.4bsd
<item> comp.bugs.4bsd.ucb-fixes
<item> comp.unix.bsd
<item>comp.unix
<item>comp.unix.questions
<item>comp.unix.admin
<item>comp.unix.programmer
<item>comp.unix.shell
<item>comp.unix.user-friendly
<item>comp.security.unix
<item>comp.sources.unix
<item>comp.unix.advocacy
<item>comp.unix.misc
<item>comp.os.386bsd.announce
<item>comp.os.386bsd.apps
<item>comp.os.386bsd.bugs
<item>comp.os.386bsd.development
<item>comp.os.386bsd.misc
<item>comp.os.386bsd.questions
<item>comp.bugs.4bsd
<item>comp.bugs.4bsd.ucb-fixes
<item>comp.unix.bsd
</itemize>
<sect1>
<heading>X-Window system</heading>
<p><itemize>
<item> comp.windows.x.i386unix
<item> comp.windows.x
<item> comp.windows.x.apps
<item> comp.windows.x.announce
<item> comp.windows.x.intrinsics
<item> comp.windows.x.motif
<item> comp.windows.x.pex
<item> comp.emulators.ms-windows.wine
<item>comp.windows.x.i386unix
<item>comp.windows.x
<item>comp.windows.x.apps
<item>comp.windows.x.announce
<item>comp.windows.x.intrinsics
<item>comp.windows.x.motif
<item>comp.windows.x.pex
<item>comp.emulators.ms-windows.wine
</itemize>
<sect>
<heading>Word Wide Web servers</heading>
<heading>Word Wide Web servers<label id="eresources:web"></heading>
<p><itemize>
<item> <url url="http://www.freebsd.org/"></item>
<item><url url="http://www.freebsd.org/"></item>
</itemize>
</sect>

4
handbook/glossary.sgml
View file

@ -1,5 +1,5 @@
<!-- $Id: glossary.sgml,v 1.1.1.1 1995-04-28 16:19:59 jfieber Exp $ -->
<!-- $Id: glossary.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:30 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Glossary</heading>
<chapt><heading>* Glossary<label id="glossary"></heading>

195
handbook/handbook.sgml
View file

@ -1,53 +1,22 @@
<!-- $Id: handbook.sgml,v 1.7 1995-05-18 03:05:08 jfieber Exp $ -->
<!-- $Id: handbook.sgml,v 1.7.4.1 1995-09-17 11:19:30 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN" [
<!-- Conditional flags for this version of the document -->
<!ENTITY % boothelp.only "IGNORE">
<!ENTITY % handbook.only "INCLUDE">
<!-- Entity shorthand for authors' names and email addresses -->
<!ENTITY % authors SYSTEM "authors.sgml">
%authors;
<!ENTITY bibliography SYSTEM "bibliography.sgml">
<!ENTITY basics SYSTEM "basics.sgml">
<!ENTITY booting SYSTEM "booting.sgml">
<!ENTITY ctm SYSTEM "ctm.sgml">
<!ENTITY current SYSTEM "current.sgml">
<!ENTITY dialup SYSTEM "dialup.sgml">
<!ENTITY diskless SYSTEM "diskless.sgml">
<!ENTITY eresources SYSTEM "eresources.sgml">
<!ENTITY glossary SYSTEM "glossary.sgml">
<!ENTITY history SYSTEM "history.sgml">
<!ENTITY kerberos SYSTEM "kerberos.sgml">
<!ENTITY memoryuse SYSTEM "memoryuse.sgml">
<!ENTITY nfs SYSTEM "nfs.sgml">
<!ENTITY nutshell SYSTEM "nutshell.sgml">
<!ENTITY porting SYSTEM "porting.sgml">
<!ENTITY ports SYSTEM "ports.sgml">
<!ENTITY ppp SYSTEM "ppp.sgml">
<!ENTITY scsi SYSTEM "scsi.sgml">
<!ENTITY slipc SYSTEM "slipc.sgml">
<!ENTITY slips SYSTEM "slips.sgml">
<!ENTITY submitters SYSTEM "submitters.sgml">
<!ENTITY sup SYSTEM "sup.sgml">
<!ENTITY troubleshooting SYSTEM "troubleshooting.sgml">
<!-- Entity definitions for all the parts -->
<!ENTITY % sections SYSTEM "sections.sgml">
%sections;
]>
<!--
Potential target audience:
1. Potential users
a. new to unix
b. somewhat familiar with unix
c. veterans
2. Existing users
a. new to unix
b. somewhat familiar with unix
c. veterans
OUTLINE:
-->
<linuxdoc>
<book>
@ -55,18 +24,20 @@ OUTLINE:
<author>
<name>The FreeBSD Documentation Project</name>
</author>
<date>May 17, 1995</date>
<date>August 31, 1995</date>
<abstract>Welcome to FreeBSD! This handbook covers the
installation and day to day use of FreeBSD.
<abstract>Welcome to FreeBSD! This handbook covers the
installation and day to day use of <bf>FreeBSD Release
2.0.5</bf>.
This manual is a <bf>work in progress</bf> and is the
work of many individials. Many sections do not yet exist
and some of those that do exist need to be updated. If
you are interested in helping with this project, send
email to &a.jfieber; or to the FreeBSD Documentantion
Project mailing list <tt>&lt;doc@freebsd.org&gt;</tt>.
</abstract>
This manual is a <bf>work in progress</bf> and is the
work of many individials. Many sections do not yet exist
and some of those that do exist need to be updated. If
you are interested in helping with this project, send
email to &a.jfieber; or to the FreeBSD Documentation
Project mailing list <tt><htmlurl url="mailto:doc@freebsd.org"
name="&lt;doc@freebsd.org&gt;"></tt>.
</abstract>
<toc>
@ -77,26 +48,13 @@ OUTLINE:
<chapt><heading>Introduction</heading>
&nutshell;
&history;
<sect><heading>About this release</heading>
<sect><heading>FreeBSD now and in the future</heading>
<chapt><heading>Installing FreeBSD</heading>
<sect><heading>Preparing for the installation</heading>
<sect1><heading>Hardware checklist</heading>
<sect2><heading>minimal requirements</heading>
<sect2><heading>IRQs, IO Addresses, and DMA channels</heading>
<sect1><heading>Software checklist</heading>
<sect2><heading>Making the installation floppies</heading>
<sect2><heading>CD-ROM</heading>
<sect2><heading>Tape</heading>
<sect2><heading>Disk</heading>
<sect><heading>Installation</heading>
<sect><heading>Set up a user account</heading>
&relnotes;
&install;
&basics;
<chapt><heading>Installing applications</heading>
<sect><heading>Installing packages</heading>
<sect><heading>* Installing packages</heading>
&ports;
&porting;
@ -104,80 +62,76 @@ OUTLINE:
<part><heading>System Administration</heading>
<chapt><heading>Reconfiguring the kernel</heading>
<chapt><heading>Reconfiguring the Kernel<label id="kernelconfig"></heading>
<p>This section is in progress. Please contact
Deborah Bennett <htmlurl url="mailto:deborah@gallifrey.microunity.com"
name="&lt;deborah@gallifrey.microunity.com&gt;"> for more information.
In the meantime, please refer to
Kernel Configuration section of the <url url="../FAQ/freebsd-faq.html"
name="FreeBSD FAQ">.
<!-- &kernelconfig; -->
<chapt><heading>Users, groups and security</heading>
<sect><heading>DES, MD5 and Crypt</heading>
<sect><heading>* DES, MD5 and Crypt</heading>
<sect><heading>* S/Key</heading>
&kerberos;
<sect><heading>S/Key</heading>
<sect><heading>Firewalls</heading>
<chapt><heading>The X-Window System</heading>
<sect><heading>* Firewalls</heading>
<chapt><heading>Printing</heading>
<p>This section is in progress. Please contact
Sean Kelly <url url="mailto:kelly@fsl.noaa.gov"
name="kelley@fsl.noaa.gov"> for more information.
<chapt><heading>The X-Window System</heading>
<p>Pending the completion of this section, please refer to
documentation supplied by the <url url="http://www.xfree86.org/"
name="The XFree86 Project, Inc">.
<chapt><heading>Managing hardware</heading>
&scsi;
<sect><heading>adding/reconfiguring disks</heading>
<sect><heading>tapes and backups</heading>
<sect><heading>serial ports</heading>
<sect><heading>sound cards</heading>
<sect><heading>* Adding and reconfiguring disks</heading>
<sect><heading>* Tapes and backups</heading>
<sect><heading>* Serial ports</heading>
<sect><heading>* Sound cards</heading>
<chapt><heading>PC Hardware compatibility</heading>
<sect><heading>CORE/PROCESSING</heading>
<sect1><heading>Motherboards</heading>
<sect2><heading>ISA</heading>
<sect2><heading>EISA</heading>
<sect2><heading>VLB</heading>
<sect2><heading>PCI</heading>
<sect1><heading>CPUs/FPUs</heading>
<sect1><heading>Memory</heading>
<sect1><heading>BIOS</heading>
<sect><heading>INPUT/OUTPUT</heading>
<sect1><heading>Video cards</heading>
<sect1><heading>Sound cards</heading>
<sect1><heading>Serial ports (including multiport cards)</heading>
<sect1><heading>Parallel ports</heading>
<sect1><heading>Modems</heading>
<sect1><heading>Etherenet cards</heading>
<sect1><heading>Keyboards</heading>
<sect1><heading>Mice</heading>
<sect1><heading>Other (joysticks? tablets?)</heading>
<sect><heading>STORAGE</heading>
<sect1><heading>Disk/tape controllers</heading>
<sect2><heading>SCSI</heading>
<sect2><heading>IDE</heading>
<sect2><heading>Floppy</heading>
<sect1><heading>Hard drives</heading>
<sect1><heading>Tape drives</heading>
<sect1><heading>CD-ROM drives</heading>
<sect1><heading>Other</heading>
<sect><heading>OTHER</heading>
<sect1><heading>PCMCIA</heading>
<!-- ************************************************************ -->
<part><heading>Network Communications</heading>
<chapt><heading>Basic Networking</heading>
<sect><heading>Ethernet basics</heading>
<sect><heading>Serial basics</heading>
<sect><heading>Hardwired Terminals</heading>
<sect><heading>* Ethernet basics</heading>
<sect><heading>* Serial basics</heading>
<sect><heading>* Hardwired Terminals</heading>
&dialup;
<chapt><heading>PPP and SLIP</heading>
<p>If your connection to the internet is through a modem, or
you wish to provide other people with dialup connections to
the internet using FreeBSD, you have the option of using PPP
or SLIP. Furthermore, two varieties of PPP are provided:
<em>user</em> (sometimes referred to as iijppp) and
<em>kernel</em>. The procedures for configuring both types
of PPP, and for setting up SLIP are described in this
chapter.
&userppp;
&ppp;
&slipc;
&slips;
<chapt><heading>Advanced networking</heading>
<sect><heading>Gateways and routing</heading>
&nfs;
<sect><heading>Yellow Pages/NIS</heading>
&diskless;
<sect><heading>ISDN</heading>
<p>This section is in progress. Please contact
Coranth Gryphon <htmlurl url="mailto:gryphon@healer.com"
name="&lt;gryphon@healer.com&gt;"> for more information.
<chapt><heading>Mail</heading>
&nfs;
<sect><heading>* Yellow Pages/NIS</heading>
&diskless;
<sect><heading>* ISDN</heading>
<chapt><heading>* Mail</heading>
@ -187,7 +141,7 @@ OUTLINE:
&current;
&ctm;
&sup;
<chapt><heading>Kernel debugging</heading>
&kerneldebug;
&submitters;
&booting;
&memoryuse;
@ -195,9 +149,12 @@ OUTLINE:
<!-- ************************************************************ -->
<part><heading>Additional resources</heading>
<part><heading>Appendices</heading>
&mirrors;
&bibliography;
&eresources;
&hw;
&contrib;
&glossary;
</book>

114
handbook/history.sgml
View file

@ -1,44 +1,92 @@
<!-- $Id: history.sgml,v 1.1 1995-05-10 22:12:01 jfieber Exp $ -->
<!-- $Id: history.sgml,v 1.1.4.1 1995-09-17 11:19:31 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>A brief history of FreeBSD</heading>
<sect><heading>A brief history of FreeBSD<label id="history"></heading>
<p><em>Contributed by &a.jkh;</em>.
The FreeBSD project was started somewhere in the early part of 1992 as
an outgrowth of the "Unofficial 386BSD Patchkit" by the patchkit's
last 3 coordinators: Nate Williams, Jordan Hubbard and Rod Grimes.
The FreeBSD project had its genesis in the early part of 1992,
partially as an outgrowth of the "Unofficial 386BSD Patchkit" by the
patchkit's last 3 coordinators: Nate Williams, Rod Grimes and myself.
David Greenman and Julian Elischer were also lurking in the background
around this time, though they didn't come fully into the project until
a month or two after it was more or less officially launched. The
original working title of the project was also "386BSD 0.5" or "386BSD
Interim", a reference to the fact that the original goal was to
produce an intermediate snapshot of 386BSD.
a month or two after it was more or less officially launched. Our
original goal was to produce an intermediate snapshot of 386BSD in
order to fix a number of problems with it that the patchkit mechanism
just wasn't capable of solving. Some of you may remember the early
working title for the project being "386BSD 0.5" or "386BSD Interim"
in reference to that fact.
386BSD was Bill Jolitz's operating system, which had been up to
that point suffering rather severely from neglect, a consequence
of which was to cause the patchkit to swell ever more
uncomfortably with each passing day. The 3 ex-patchkit
coordinators were all in agreement that the patchkit had to die.
It was rapidly outliving its usefulness, and it would be a far
easier thing to simply do another 386BSD release with all patches
applied and a number of its aging utilities updated.
386BSD was Bill Jolitz's operating system, which had been up to that
point suffering rather severely from almost a year's worth of neglect.
As the patchkit swelled ever more uncomfortably with each passing day,
we were in unanimous agreement that something had to be done and
decided to try and assist Bill by providing this interim "cleanup"
snapshot. Those plans came to a rude halt when Bill Jolitz suddenly
decided to withdraw his sanction from the project and without any
clear indication of what would be done instead.
These plans came to a rude halt when Bill Jolitz suddenly decided
to withdraw his sanction from the project. It didn't take the
team members long to decide that the goal remained worthwhile
even without Bill's support, and so they adopted the name
"FreeBSD", which was coined by David Greenman.
It didn't take us long to decide that the goal remained worthwhile
even without Bill's support, and so we adopted the name "FreeBSD",
which was coined by David Greenman. Our initial objectives were set
after consulting with the system's current users and once it became
clear that the project was on the road to perhaps even becoming a
reality, I contacted Walnut Creek CDROM with an eye towards improving
FreeBSD's distribution channels to those many unfortunates without
easy access to the Internet. Walnut Creek CDROM not only supported
the idea of distributing FreeBSD on CD but went so far as to provide
the project with a machine to work on and a fast Internet connection.
Without Walnut Creek CDROM's almost unprecidented degree of faith in
what was, at the time, a completely unknown project, it is in fact
very unlikely that FreeBSD would have gotten as far, as fast, as it
has today.
The first CDROM (and general net-wide) distribution was FreeBSD 1.0,
released in December of '93. This was based on the 4.3 BSD Lite
("Net/2") tape from U.C. Berkeley with many components provided by
386BSD and the Free Software Foundation. It was a fairly reasonable
success for a first offering, and we followed this release with the
highly successful FreeBSD 1.1 version in May of 1994.
Around this time, some rather unexpected storm clouds formed on our
horizon as Novell and U.C. Berkeley settled their long-running lawsuit
over the legal status of the Berkeley Net/2 tape. A condition of that
settlement was U.C. Berkeley's concession that large parts of Net/2
was "encumbered" code and property of Novell, who had in turn aquired
it from AT&amp;T some time previously. What Berkeley got in return was
Novell's "blessing" that the 4.4 Lite release, when it was finally
released, would be declared unencumbered and all existing Net/2 users
would be strongly encouraged to switch. This included us, and we were
given until the end of July 1994 to stop shipping our own Net/2 based
product. Under the terms of that agreement, were were allowed one
last release before the deadline and that became FreeBSD 1.1.5.1, the
culmination of our year's work with Net/2 and generally considered by
many to be a significant project milestone for stability and general
performance..
We then set about the arduous task of literally re-inventing ourselves
with a completely new and rather incomplete set of 4.4 Lite bits. The
"Lite" releases were light in part because Berkeley's CSRG removed
large chunks of code required for actually making a bootable running
system out of it due to various legal requirements and the fact that
the Intel port of 4.4 was highly incomplete. It took us until
December of 1994 to make this transition, and in January of 1995 we
released FreeBSD 2.0 to the net and on CDROM. Despite being still
more than a little rough around the edges, the release was a
significant success and has since been followed by the more robust and
easier to install FreeBSD 2.0.5 release in June of 1995.
Where to from here? Well, we intend to release FreeBSD 2.1 sometime
in October of 1995 and have reasonable expectations that it will
meet or exceed all of the standards for quality we set with FreeBSD
1.1.5.1 back in July of 1994. From there, we'll probably continue our now
two-track scheme of a "stable" branch of FreeBSD and an "experimental"
branch, where development can continue at its usually rapid pace without
penalizing those who just want a working system without too much excitement.
We also intend to focus on any remaining areas of weakness, like documentation
or missing drivers, and steadily increase the overall quality and feature set
of the system well into 1996 and beyond.
Jordan
Once it also became clear that the project was on the road to
perhaps even becoming a reality, Jordan Hubbard contacted Walnut
Creek CDROM with an eye towards improving FreeBSD's distribution
channels to those many unfortunates without easy access to the
Internet. Walnut Creek CDROM not only supported the idea of
distributing FreeBSD on CD, but went so far as to provide the
project with a machine to work on and a fast Internet connection.
Without Walnut Creek CDROM's almost unprecidented degree of faith
in what was, at the time, a completely unknown project, it is
very unlikely that FreeBSD would have gotten as far, as fast, as
it has today.

6
handbook/kerberos.sgml
View file

@ -1,7 +1,7 @@
<!-- $Id: kerberos.sgml,v 1.2 1995-05-11 22:31:28 jfieber Exp $ -->
<!-- $Id: kerberos.sgml,v 1.2.4.1 1995-09-17 11:19:32 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>Kerberos</heading>
<sect><heading>Kerberos<label id="kerberos"></heading>
<p><em>Contributed by &a.mark; (based on contribution by &a.md;).</em>
@ -293,7 +293,7 @@ Master key entered. BEWARE!
Current Kerberos master key version is 1
Local realm: GRONDAR.ZA
grunt# kadmin -n &
grunt# kadmind -n &
grunt# KADM Server KADM0.0A initializing
Please do not use 'kill -9' to kill this job, use a
regular kill instead

4
handbook/memoryuse.sgml
View file

@ -1,7 +1,7 @@
<!-- $Id: memoryuse.sgml,v 1.1 1995-05-18 03:05:11 jfieber Exp $ -->
<!-- $Id: memoryuse.sgml,v 1.1.4.1 1995-09-17 11:19:33 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>PC memory utilization</heading>
<chapt><heading>PC memory utilization<label id="memoryuse"></heading>
<p><em>Contributed by &a.joerg;.<newline>
16 Apr 1995.</em>

4
handbook/nfs.sgml
View file

@ -1,7 +1,7 @@
<!-- $Id: nfs.sgml,v 1.1.1.1 1995-04-28 16:19:59 jfieber Exp $ -->
<!-- $Id: nfs.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:34 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>NFS</heading>
<sect><heading>NFS<label id="nfs"></heading>
<p><em>Contributed by &a.john;.</em>

41
handbook/nutshell.sgml
View file

@ -1,7 +1,7 @@
<!-- $Id: nutshell.sgml,v 1.1 1995-05-11 02:03:38 jfieber Exp $ -->
<!-- $Id: nutshell.sgml,v 1.1.4.1 1995-09-17 11:19:35 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>FreeBSD in a nutshell</heading>
<sect><heading>FreeBSD in a nutshell<label id="nutshell"></heading>
<p>FreeBSD is a state of the art operating system for
personal computers based on the Intel CPU architecture, which
@ -31,12 +31,12 @@
as such from the ground up.</item>
<item>The industry standard <bf>X Window System</bf> (X11R6)
provides a graphical user interface (GUI) for the cost of a
common VGA card and monitor.</item>
common VGA card and monitor and comes with full sources.</item>
<item><bf>Binary compatibility</bf> with many programs built for SCO,
BSDI, NetBSD, and 386BSD.</item>
<item>Hundreds of <bf>ready-to-run</bf> applications are
available from the
FreeBSD <bf>ports and packages</bf>
FreeBSD <bf>ports</bf> and <bf>packages</bf>
collection. Why search the net when you can find it all
right here?</item>
<item>Thousands of additional and <bf>easy-to-port</bf> applications
@ -52,9 +52,8 @@
and memory.</item>
<item>A full compliment of <bf>C</bf>, <bf>C++</bf> and
<bf>Fortran</bf> development tools. Many additional
languages for research and advanced development are
available as well in the ports and packages
collection.</item>
languages for advanced research and development are
also available in the ports and packages collection.</item>
<item><bf>Source code</bf> for the entire system means you have
the greatest degree of control over your environment. Why be
locked into a proprietary solution and at the mercy of your vendor
@ -71,19 +70,19 @@
many thousands of hours in fine tuning the system for
maximum performance and reliability in real-life load
situations. As many of the commercial giants struggle to
field PC operating systems with such features, performance,
field PC operating systems with such features, performance
and reliability, FreeBSD can offer them <bf>now</bf>!
The applications to which FreeBSD can be put are truly
limited only by your own imagination. From software
development to factory automation. Inventory control to
azimuth correction of remote satellite antennae, if it can
be done with a commercial UNIX product, then it's more than
development to factory automation, inventory control to
azimuth correction of remote satellite antennae; if it can
be done with a commercial UNIX product then it's more than
likely that you can do it with FreeBSD, too! FreeBSD also
benefits significantly from the literally thousands of high
quality applications developed by research centers and
universities around the world, and often available at low
(to no) cost. Commercial applications are also available
universities around the world, often available at little
to no cost. Commercial applications are also available
and appearing in greater numbers every day.
Because the source code for FreeBSD itself is generally
@ -112,7 +111,7 @@
<item><bf>Education:</bf> Are you a student of computer science
or a related engineering field? There is no better way
of learning about operating systems, computer
architecture and networks than the hands on, under the
architecture and networking than the hands on, under the
hood experience that FreeBSD can provide. A number of
freely available CAD, mathematical and graphic design
packages also make it highly useful to those who's
@ -124,25 +123,29 @@
computer science. FreeBSD's freely available nature also
makes it possible for remote groups to collaborate on
ideas or shared development without having to worry about
special licensing agreements, or with limitations on what
may be discussed in certain forums.</item>
special licensing agreements or limitations on what
may be discussed in open forums.</item>
<item><bf>Networking:</bf> Need a new router? A name server
(DNS)? A firewall to keep people out of your internal
network? FreeBSD can easily turn that unused 386 or 486 PC
sitting in the corner into an advanced router with
sophisticated packet filtering capabilities. </item>
<item><bf>X Window workstation:</bf> FreeBSD is an excellent
<item><bf>X Window workstation:</bf> FreeBSD is a fine
choice for an inexpensive X terminal solution, either
using the freely available XFree86 server or one
of the excellent commercial servers provided by X Inside.
Unlike an X
terminal, FreeBSD allows many applications to be run
locally, if desired, thus relieving the burden on a
central server. Additionally, FreeBSD can boot
"diskless" making individual workstations even cheaper
central server. FreeBSD can even boot
"diskless", making individual workstations even cheaper
and easier to administer.</item>
<item><bf>Software Development:</bf> The basic FreeBSD system
comes with a full compliment of development tools
included the renowned GNU C/C++ compiler and
debugger. </item>
</itemize>
FreeBSD is available in both source and binary form on CDROM and
via anonymous ftp. See <ref id="mirrors" name="Obtaining FreeBSD">
for more details.

1190
handbook/porting.sgml
View file

File diff suppressed because it is too large Load diff

123
handbook/ports.sgml
View file

@ -1,7 +1,7 @@
<!-- $Id: ports.sgml,v 1.2 1995-05-18 03:05:19 jfieber Exp $ -->
<!-- $Id: ports.sgml,v 1.2.4.1 1995-09-17 11:19:38 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>The Ports collection<label id="ports:"></heading>
<sect><heading>The Ports collection<label id="ports"></heading>
<p><em>Contributed by &a.gpalmer; and &a.jkh;.</em>
@ -16,59 +16,75 @@ back of your computer!).
<sect1><heading>What is the FreeBSD Ports Collection?</heading>
<p> People who (allegedly) know what they are doing have automated the
process of ``porting'' software to FreeBSD, and the result is the
Ports Collection. The general idea is that a combination of various
programming tools available in the base FreeBSD installation will
allow you to fetch the port from a FreeBSD mirror site, type ``make''
and get the fully working program.
<p> When 2.0 was released, the FreeBSD Project decided to attempt to
automate the process of ``porting'' such software to FreeBSD, and the
result is the Ports Collection. The general idea was that a
combination of various programming tools already available in the base
FreeBSD installation would allow you to simply type `make' for a given
port and have the underlying ports mechanism automatically fetch the
port from a FreeBSD mirror site, apply any special configuration
knowledge to it and then build it to result in a fully working version
of the program.
The ports collection itself normally doesn't have any of the
original source code necessary for the compilation in the tree, just
those shell scripts, Makefiles and source code ``diffs'' that are
necessary to compile the program under FreeBSD. This is meant to keep
the entire system down to a manageable size, and the current system
has over 100 ports in the master source tree, and yet a compressed tar
file of that tree is about 2 megabytes (all the source code needed is
over 100Mb's!).
necessary to configure and compile the program under FreeBSD. This
keeps the entire system down to a manageable size, with the current
system having over 300 ports in the master source tree and yet taking
up less than ten megabytes.
<sect1><heading>How does the system compile with no source code?</heading>
<p> A ports' Makefile automatically looks in a central location on
your system (usually /usr/ports/distfiles, though this value can be
<p> The Makefile for a port automatically looks in a central location
on your system (usually /usr/ports/distfiles, though this value can be
customized) for the associated set of original distribution files that
have been ``ported''. These are generally provided at various places
on the Internet, though if you have a CDROM distribution of FreeBSD
then you've already got them available on your CD for ease of use.
See section 3.1 if you have such a CD distribution, otherwise skip to
section 3.2.
have been ``ported''. Those not found locally are searched for
wherever they're generally provided on the Internet. If you have a
CDROM distribution of FreeBSD then you've already got them available
on your CD for ease of use. See <ref id="ports:cd"
name="Compiling ports from CD"> if you have such a CDROM
distribution, otherwise skip to <ref id="ports:inet"
name="Compiling ports using an Internet connection">.
<!--
3.1 Compiling ports from CD
<sect1><heading>Compiling ports from CDROM<label id="ports:cd"></heading>
Type something profound here.
-->
<p>The ports collection is easy to use from CDROM, and all you need to
do is to create a "link tree" to it using the <tt>lndir(1)</tt> command that
comes with the <em>XFree86</em> distribution. Find a location with
some free space and create a directory there, and make a symbolic link
from <tt>/usr/ports</tt> to that directory. Then invoke the <tt>lndir(1)</tt> command with
the full pathname of the ``ports'' directory on the CDROM as an
argument (this might be, for example, something like: <tt>lndir
/cdrom/ports</tt>). Then you can build ports directly off the CDROM by
building them in the link tree you've created.
<sect2><heading>Compiling ports using an Internet connection</heading>
Note that there are some ports for which we can't provide the original
source in the CDROM due to licensing limitations. In that case,
you'll need to look at the next section (<ref id="ports:inet"
name="Compiling ports using an Internet connection">).
<sect1><heading>Compiling ports using an Internet connection<label id="ports:inet"></heading>
<p> The ports collection can also use an auto-fetch system to keep
your ports collection source tree up to date, updating the central
``distfiles'' version for you the next time you compile the port.
Of course, this always assumes you have a permanent network link,
or don't mind heavy usage of your telephone. If you don't want heavy
network usage when you compile your ports tree, you can pre-fetch the
Of course, this assumes you have a permanent network link or don't
mind heavy usage of your telephone. If you don't want heavy network
usage when you compile your ports tree, you can pre-fetch the
necessary tarballs beforehand and put them into /usr/ports/distfiles
(or wherever DISTDIR points) by hand. A good way to see what files a
port is going to need is to cd to that port's directory and do a
``make -n fetch'' to see what it does.
by hand. A good way to see what files a port is going to need is to
cd to that ports' directory and do a <tt>make fetch-list</tt> to see what
it does. The output of <tt>make fetch-list</tt> can also be used as a
shell script to fetch the ports' tarballs at a well-connected machine.
You can also chose to get the source files either from the master
FTP site as defined in the relevant Makefile (in the MASTER_SITES
line), or some FreeBSD mirror site also carrying a set of distfiles,
as does the master FTP site on ftp.FreeBSD.org (aka ftp.cdrom.com) in
the directory /pub/FreeBSD/ports/distfiles. Note that the files in
the directory <tt>/pub/FreeBSD/distfiles</tt>. Note that the files in
that directory are not guarenteed to be kept up to date - this is a
volunteer project! We can't make any guarantees about the mirror
sites either - they are obviously under independant control and don't
@ -83,8 +99,8 @@ going to the top of the tree and typing ``make fetch''.
<p>Oh. You can do one of four (4) things :
<enum>
<item> Fix it yourself. Technical details can be found in the GUIDELINES file,
available from URL ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/GUIDELINES
<item> Fix it yourself. Technical details can be found in
<ref id="porting" name="Porting applications">.
<item> Gripe. This is done by e-mail *ONLY*! The people at Walnut Creek are
in no way responsible for the functionality (or lack thereof) of the
@ -103,7 +119,7 @@ going to the top of the tree and typing ``make fetch''.
bug!
<item> Forget it. This is the easiest for most - very few of the programs in
ports can be classed as `essential'!
ports can be classified as `essential'!
<item> Grab the pre-compiled package from a ftp server. The ``master'' package
collection is in:
@ -112,7 +128,8 @@ going to the top of the tree and typing ``make fetch''.
though check your local mirror first, please!
These are more likely to work (on the whole) than trying to compile from
source, and a lot faster!
source, and a lot faster! Use the <tt>pkg_add(1)</tt> or <tt>pkg_manage(1)</tt> program to
install them to your system.
</enum>
<sect1><heading>I've ported a program and I want to make a port out of it. What now?</heading>
@ -124,35 +141,21 @@ going to the top of the tree and typing ``make fetch''.
<sect1><heading>I've got a good port, what now?</heading>
<p> Upload the fixed version to freefall.cdrom.com /pub/incoming or
ftp.FreeBSD.org /pub/FreeBSD/incoming and send e-mail to
<p>Upload the fixed version to <tt>ftp://freefall.cdrom.com/pub/incoming</tt> or
<tt>ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming</tt> and send e-mail to
ports@FreeBSD.org with the filename and details. Someone on the
all-volunteer `ports committee' will (hopefully) look it over and
commit it to the ports collection if they like the looks of it.
<sect1><heading>Things go funny during the fetch stage of compilation!</heading>
<p> We know. Please don't blame us. There is a program called `ncftp'
which is used instead of the normal ftp as it can do so-called
``background'' or ``batch'' transfers, ideal for this situation.
Unfortunately it can do strange things, and has crashed at least one
machine (during circumstances stranger than most, I'll admit, but it
was still responsible). Hopefully a future release of ncftp will fix
these problems (it is not maintained by the main FreeBSD team, but a
third party, who is I believe aware of its shortcomings)
<sect1><heading>I want to leave the compile going overnight, but some ports don't like this.</heading>
<p> There is a way around this. Before starting the compilation, type:
<verb>
setenv BATCH yes # (if you use csh/tcsh) or
BATCH=yes # (for sh/bash)
BATCH=yes; export BATCH # (for sh/bash)
</verb>
This should miss out ports which need user interaction. Unfortunately,
ncftp doesn't know about this trick, and can often screw up and ask
stupid questions in unattended batch mode. See (7).
This should skip ports which need user interaction to build.
To compile those ports left out by doing the above, using a
different login shell (or unsetting the above BATCH variable), set the
@ -170,7 +173,7 @@ the weirdness can be explained properly in there (most of the current
weirdness is due to the lack of assumptions about anything, which is
necessary due to the generic nature of these files). Also check that
you have an up-to-date copy, as the file can change from minute to
minute. A reasonably up-to-date copy can be found in:
minute. The most up-to-date copy can be found in:
<url url="ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/src/share/mk">
@ -195,15 +198,11 @@ time now! :-)
<sect1><heading>How do I get more information on all the ports?</heading>
<p> One good method is to cd to the top of the ports tree (say /usr/ports)
and type something like:
and type:
<verb>
make describe | sed -e '/===/D' -e 's;/usr/ports/;;' | expand -40
make print-index
</verb>
The ``make describe'' will try to extract the one-line description from
each port, and the ``sed'' will delete the extraneous output. ``expand''
just makes it a little more readable (sort of - you may want to season
the output of this more to taste).
This will print a summary of all ports in the tree.
<sect1><heading>I've heard of a new checksum system. What is this for?</heading>

6
handbook/ppp.sgml
View file

@ -1,7 +1,7 @@
<!-- $Id: ppp.sgml,v 1.1.1.1 1995-04-28 16:19:59 jfieber Exp $ -->
<!-- $Id: ppp.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:39 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>Setting up a PPP link</heading>
<sect><heading>Setting up kernel PPP<label id="ppp"></heading>
<p><em>Contributed by &a.gena;.</em>
@ -50,7 +50,7 @@ To connect:
<enum>
<item> Dial to the remote host using kermit ( or other modem program )
enter your user name and password ( or whatever is needed to enable PPP
ont the remote host )
on the remote host )
<item> Exit kermit. ( without hanging up the line )

205
handbook/scsi.sgml
View file

@ -1,11 +1,11 @@
<!-- $Id: scsi.sgml,v 1.1.1.1 1995-04-28 16:19:59 jfieber Exp $ -->
<!-- $Id: scsi.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:39 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
<title>An introduction to SCSI and its use with FreeBSD</title>
<author>(c) 1995, Wilko Bulte, <tt/wilko@yedi.iaf.nl/
<date>V0.2, Thu Apr 20 22:45:23 MET DST 1995</date>
Copyright 1995, W. C. Bulte, Arnhem, The Netherlands
<date>Sun Sep 3 17:14:48 MET DST 1995</date>
Copyright 1995, Wilko C. Bulte, Arnhem, The Netherlands
<abstract>
This document attempts to describe the background of SCSI, its
@ -13,9 +13,9 @@
</abstract>
-->
<sect><heading>SCSI</heading>
<sect><heading>SCSI<label id="scsi"></heading>
<p><em>&copy; 1995, &a.wilko;.</em>
<p><em>&copy; 1995, &a.wilko;.<newline>3 September 1995.</em>
SCSI is an acronym for Small Computer Systems Interface. It is an
ANSI standard that has become one of the leading I/O buses in the
@ -28,7 +28,7 @@
standard allowing devices from different vendors to work together.
This effort was recognised in the ANSI SCSI-1 standard. The SCSI-1
standard (approx 1985) is now more or less obsolete. The current
standard is SCSI-2 (see <ref id="further-reading" name="Further
standard is SCSI-2 (see <ref id="scsi:further-reading" name="Further
reading">), with SCSI-3 on the drawing boards.
In addition to a physical interconnection standard, SCSI defines a
@ -38,7 +38,7 @@
includes the (revised) CCS as part of the standard itself. The
commands are dependent on the type of device at hand. It does not
make much sense of course to define a Write command for a
scanner...
scanner.
The SCSI bus is a parallel bus, which comes in a number of
variants. The oldest and most used is an 8 bit wide bus, with
@ -87,10 +87,10 @@
QIC tape unit, a SCSI-1 helical scan tape unit and 2 SCSI-1 disks
work together quite happily.
<sect1>Concepts of SCSI
<sect1><heading>Components of SCSI</heading>
<p>
<sect2>A <it>smart</it> interface
<p>
<!-- <sect2><heading>A <it>smart</it> interface</heading>
<p> -->
As said before, SCSI devices are smart. The idea is to put the
knowledge about intimate hardware details onto the SCSI device
itself. In this way, the host system does not have to worry
@ -104,8 +104,8 @@
there is no longer a need to change (and qualify!) drivers for
every odd new device that is introduced.
<sect2>Do's and don't's on interconnections
<p>
<!-- <sect2><heading>Do's and don't's on interconnections</heading>
<p> -->
For cabling and connectors there is a golden rule: get good
stuff. With bus speeds going up all the time you will save
yourself a lot of grief by using good material.
@ -116,9 +116,10 @@
hunting down a problem with a flaky machine only to discover that
shortening the SCSI bus with 1 meter solved the problem. And the
original bus length was well within the SCSI specification.
<sect2>SCSI bus types
<sect2><heading>SCSI bus types</heading>
<p>
From an electrical point of view, there are two Incompatible bus
From an electrical point of view, there are two incompatible bus
types: single-ended and differential. This means that there are
two different main groups of SCSI devices and controllers, which
cannot be mixed on the same bus. It is possible however to use
@ -148,7 +149,7 @@
that on a narrow (8 bit) bus 10 Mbytes/sec are possible instead
of 5 Mbytes/sec for 'slow' SCSI. More on this later.
It should be noted that the datalines > 8 are only used for
It should be noted that the datalines &gt; 8 are only used for
datatransfers and device addressing. The transfers of commands
and status messages etc are only performed on the lowest 8
datalines. The standard allows narrow devices to operate on
@ -156,7 +157,7 @@
between the devices. You have to watch your device addressing
closely when mixing wide and narrow.
<sect3>Single ended buses
<sect3><heading>Single ended buses</heading>
<p>
A single-ended SCSI bus uses signals that are either 5 Volts or
0 Volts (indeed, TTL levels) and are relative to a COMMON
@ -177,7 +178,7 @@
differential SCSI bus was introduced in the SCSI-2 standard.
For connector pinning and connector types please refer to the
SCSI-2 standard (see <ref id="further-reading" name="Further
SCSI-2 standard (see <ref id="scsi:further-reading" name="Further
reading">) itself, connectors etc are listed there in
painstaking detail.
@ -190,7 +191,7 @@
is a bad idea, you better stick to 50 pins cabling
in accordance with the SCSI standard.
<sect3>Differential buses
<sect3><heading>Differential buses</heading>
<p>
A differential SCSI bus has a maximum length of 25
meters. Quite a difference from the 3 meters for a single-ended
@ -216,7 +217,7 @@
AH1740 as a single ended board, whereas the AH1744 was differential.
The software interface to the host is identical for both.
<sect3>Terminators
<sect2><heading>Terminators</heading>
<p>
Terminators in SCSI terminology are resistor networks that are
used to get a correct impedance matching. Impedance matching
@ -277,7 +278,7 @@
for the internal flat cable connectors. This makes
reconfiguration much easier.
<sect3>Terminator power
<sect2><heading>Terminator power</heading>
<p>
The terminators discussed in the previous chapter need power to
operate properly. On the SCSI bus, a line is dedicated to this
@ -317,7 +318,7 @@
configurable, using some sort of setup tool. Consult you
documentation!
<sect3>Device addressing
<sect2><heading>Device addressing</heading>
<p>
Because the SCSI bus is, ehh, a bus there must be a way to
distinguish or address the different devices connected to it.
@ -349,7 +350,7 @@
tapechanger. In this way, the host system can address each of
the parts of the tape unit as desired.
<sect3>Bus layout
<sect2><heading>Bus layout</heading>
<p>
SCSI buses are linear. So, not shaped like Y-junctions, star
topologies, cobwebbs or whatever else people might want to
@ -364,9 +365,9 @@
<bf>Stick to the linear bus rule!</bf>
<sect1>Using SCSI with FreeBSD
<sect1><heading>Using SCSI with FreeBSD</heading>
<p>
<sect2>About translations, BIOSes and magic..
<sect2><heading>About translations, BIOSes and magic...</heading>
<p>
As stated before, you should first make sure that you have a
electrically sound bus.
@ -445,10 +446,10 @@ Feb 9 19:33:46 yedi /386bsd: sd0: 636MB (1303250 total sec), 1632 cyl, 15 head,
the value reported by the drive when inquiring about the geometry
now becomes fake.
<sect2>SCSI subsystem design
<sect2><heading>SCSI subsystem design</heading>
<p>
FreeBSD uses a sort of layered SCSI subsystem. For each different
controller card a so called device driver is written. This driver
FreeBSD uses a layered SCSI subsystem. For each different
controller card a device driver is written. This driver
knows all the intimate details about the hardware it
controls. The driver has a interface to the upper layers of the
SCSI subsystem through which it receives it's commands and
@ -465,20 +466,98 @@ Feb 9 19:33:46 yedi /386bsd: sd0: 636MB (1303250 total sec), 1632 cyl, 15 head,
banging and more high level stuff. Adding support for another
piece of hardware is a much more managable problem.
<sect2>Kernel configuration
<sect2><heading>Kernel configuration</heading>
<p>
Dependent on your hardware, the kernel configuration file must
contain a line which describes your hostadapter. This includes
I/O addresses, interrupts etc. Consult the man page for your
adapter driver to get more info.
contain one or more lines describing your hostadapter(s).
This includes I/O addresses, interrupts etc.
Consult the man page for your
adapter driver to get more info. Apart from that, check out
/sys/i386/conf/LINT for an overview of a kernel config file.
LINT contains every possible option you can dream of. It
does <em>not</em> imply LINT will actually get you to a
working kernel at all.
Although it is probably an obvious remark: the kernel config
Although it is probably stating the obvious: the kernel config
file should reflect your actual hardware setup. So, interrupts,
I/O addresses etc must match the kernel config file.
I/O addresses etc must match the kernel config file. During
system boot messages will be displayed to indicate whether
the configured hardware was actually found.
An example from the kernel config file (they live in
<tt>/sys/i386/conf</tt> BTW), with some added comments (between
&lsqb;&rsqb;):
An example based on the FreeBSD 2.0.5-Release kernel config
file LINT with some added comments (between &lsqb;&rsqb;):
<verb>
# SCSI host adapters: `aha', `ahb', `aic', `bt', `nca'
#
# aha: Adaptec 154x
# ahb: Adaptec 174x
# ahc: Adaptec 274x/284x/294x
# aic: Adaptec 152x and sound cards using the Adaptec AIC-6360 (slow!)
# bt: Most Buslogic controllers
# nca: ProAudioSpectrum cards using the NCR 5380 or Trantor T130
# uha: UltraStore 14F and 34F
# sea: Seagate ST01/02 8 bit controller (slow!)
# wds: Western Digital WD7000 controller (no scatter/gather!).
#
# Note that the order is important in order for Buslogic cards to be
# probed correctly.
#
&lsqb;For a Bustek controller&rsqb;
controller bt0 at isa? port "IO_BT0" bio irq ? vector btintr
&lsqb;For an Adaptec AHA274x, 284x etc controller&rsqb;
controller ahc0 at isa? bio irq ? vector ahcintr # port??? iomem?
&lsqb;For an Adaptec AHA174x controller&rsqb;
controller ahb0 at isa? bio irq ? vector ahbintr
&lsqb;For an Adaptec AHA154x controller&rsqb;
controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr
&lsqb;For an Ultrastor adapter&rsqb;
controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr
controller scbus0 #base SCSI code
disk sd0 at scbus0 target 0 unit 0 [SCSI disk 0 is at scbus 0, LUN 0]
disk sd1 at scbus0 target 1 [implicit LUN 0 if omitted]
disk sd2 at scbus0 target 3
disk sd3 at scbus0 target 4
tape st1 at scbus0 target 6 [SCSI tape at target 6]
device cd0 at scbus? [the first ever CDROM found, no wiring]
</verb>
The example above tells the kernel to look for a bt (Bustek)
controller, then for an Adaptec 274x, 284x etc board, and
so on. The lines following the controller specifications
tell the kernel to configure specific devices but
<em>only</em> attach them when they match the target ID and
LUN specified.
So, if you had a SCSI tape at target ID 2 it would not be
configured, but it will attach when it is at target ID 6.
Below is another example of a kernel config file as used by
FreeBSD version < 2.0.5. The difference with the first example is
that devices are not 'wired down'. 'Wired down' means
that you specify which SCSI target belongs to which device.
A kernel built to the config file below will attach
the first SCSI disk it finds to sd0, the second disk to sd1
etc. If you ever removed or added a disk, all other devices
of the same type (disk in this case) would 'move around'.
This implies you have to change /etc/fstab each time.
Although the old style still works, you
are <em>strongly</em> recommended to use this new feature.
It will save you a lot of grief whenever you shift your
hardware around on the SCSI buses. So, when you re-use
your old trusty config file after upgrading from a
pre-FreeBSD2.0.5.R system check this out.
<verb>
controller ahb0 at isa? bio irq 11 vector ahbintr &lsqb;driver for Adaptec 174x&rsqb;
@ -498,11 +577,7 @@ device st1
device cd0 #Only need one of these, the code dynamically grows &lsqb;for the cdrom&rsqb;
</verb>
So, the ahb driver is used for the Adaptec 1740, the aha driver
for the Adaptec 154x etc. If you have more than one card of the
same type in your system you get an ahb1, ahb2 line etc.
The example above supports 4 SCSI disks. If during boot more
Both examples support 4 SCSI disks. If during boot more
devices of a specific type (e.g. sd disks) are found than are
configured in the booting kernel, the system will complain. You
will have to build and boot a new kernel (after adapting the kernel
@ -514,7 +589,7 @@ device cd0 #Only need one of these, the code dynamically grows &lsq
subsystem. For more detailed info on hostadapter drivers use eg
<tt>man 4 aha</tt> for info on the Adaptec 154x driver.
<sect2>Tuning your SCSI kernel setup
<sect2><heading>Tuning your SCSI kernel setup</heading>
<p>
Experience has shown that some devices are slow to respond to INQUIRY
commands after a SCSI bus reset. An INQUIRY command is sent by the kernel
@ -534,7 +609,7 @@ options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device
with device recognition. If this helps, tune it back until it just stays
working.
<sect2>Rogue SCSI devices
<sect2><heading>Rogue SCSI devices</heading>
<p>
Although the SCSI standard tries to be complete and concise, it is
a complex standard and implementing things correctly is no easy task.
@ -570,7 +645,7 @@ Mar 29 21:16:37 yedi /386bsd: st1: Archive Viper 150 is a known rogue
to connect your bogus Mumbletech SCSI cdrom you might be the one
that has to define which workaround is needed.
<sect2>Busmaster host adapters
<sect2><heading>Busmaster host adapters</heading>
<p>
Most, but not all, SCSI host adapters are bus mastering controllers.
This means that they can do I/O on their own without putting load onto
@ -601,7 +676,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed
Check the man pages for the host adapter that you use. Or better
still, use the ultimate documentation (read: driver source).
<sect1>Tracking down problems
<sect1><heading>Tracking down problems</heading>
<p>
The following list is an attempt to give a guideline for the most
common SCSI problems and their solutions. It is by no means
@ -627,7 +702,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed
If possible, configure your hostadapter to use slow bus speeds.
</itemize>
<sect1><heading>Further reading<label id="further-reading"></>
<sect1><heading>Further reading<label id="scsi:further-reading"></heading>
<p>
If you intend to do some serious SCSI hacking, you might want to
have the official standard at hand:
@ -644,44 +719,46 @@ options "TUNE_1542" #dynamic tune of bus DMA speed
BBS (719-574-0424) and on the ncrinfo.ncr.com anonymous ftp site.
Latest X3T10 committee documents are:
<verb>
AT Attachment (ATA or IDE) &lsqb;X3.221-1994&rsqb; Approved
ATA Extensions (ATA-2) &lsqb;X3T10/948D Rev 2i&rsqb;
Enhanced Small Device Interface (ESDI) &lsqb;X3.170-1990/X3.170a-1991&rsqb; Approved
Small Computer System Interface - 2 (SCSI-2) &lsqb;X3.131-1994&rsqb; Approved
SCSI-2 Common Access Method Transport and SCSI Interface Module (CAM)
<itemize>
<item>AT Attachment (ATA or IDE) &lsqb;X3.221-1994&rsqb; (<em>Approved</em>)
<item>ATA Extensions (ATA-2) &lsqb;X3T10/948D Rev 2i&rsqb;
<item>Enhanced Small Device Interface (ESDI) &lsqb;X3.170-1990/X3.170a-1991&rsqb; (<em>Approved</em>)
<item>Small Computer System Interface - 2 (SCSI-2) &lsqb;X3.131-1994&rsqb; (<em>Approved</em>)
<item>SCSI-2 Common Access Method Transport and SCSI Interface Module (CAM)
&lsqb;X3T10/792D Rev 11&rsqb;
</verb>
</itemize>
Other publications that might provide you with additional information are:
<verb>
"SCSI: Understanding the Small Computer System Interface", written by NCR
<itemize>
<item>"SCSI: Understanding the Small Computer System Interface", written by NCR
Corporation. Available from: Prentice Hall, Englewood Cliffs, NJ, 07632
Phone: (201) 767-5937 ISBN 0-13-796855-8
"Basics of SCSI", a SCSI tutorial written by Ancot Corporation
<item>"Basics of SCSI", a SCSI tutorial written by Ancot Corporation
Contact Ancot for availability information at:
Phone: (415) 322-5322 Fax: (415) 322-0455
"SCSI Interconnection Guide Book", an AMP publication (dated 4/93, Catalog
<item>"SCSI Interconnection Guide Book", an AMP publication (dated 4/93, Catalog
65237) that lists the various SCSI connectors and suggests cabling schemes.
Available from AMP at (800) 522-6752 or (717) 564-0100
"Fast Track to SCSI", A Product Guide written by Fujitsu.
<item>"Fast Track to SCSI", A Product Guide written by Fujitsu.
Available from: Prentice Hall, Englewood Cliffs, NJ, 07632
Phone: (201) 767-5937 ISBN 0-13-307000-X
"The SCSI Bench Reference", "The SCSI Encyclopedia", and the "SCSI Tutor",
<item>"The SCSI Bench Reference", "The SCSI Encyclopedia", and the "SCSI Tutor",
ENDL Publications, 14426 Black Walnut Court, Saratoga CA, 95070
Phone: (408) 867-6642
"Zadian SCSI Navigator" (quick ref. book) and "Discover the Power of SCSI"
<item>"Zadian SCSI Navigator" (quick ref. book) and "Discover the Power of SCSI"
(First book along with a one-hour video and tutorial book), Zadian Software,
Suite 214, 1210 S. Bascom Ave., San Jose, CA 92128, (408) 293-0800
</verb>
</itemize>
On Usenet the newsgroups comp.periphs.scsi and comp.periphs are
noteworthy places to look for more info. You can also find the
SCSI-Faq there, which posted periodically.
On Usenet the newsgroups <htmlurl
url="news:comp.periphs.scsi" name="comp.periphs.scsi">
and <htmlurl url="news:comp.periphs" name="comp.periphs">
are noteworthy places to look for more info. You can also
find the SCSI-Faq there, which is posted periodically.
Most major SCSI device and hostadapter suppliers operate ftp sites
and/or BBS systems. They may be valuable sources of information

129
handbook/slipc.sgml
View file

@ -1,9 +1,9 @@
<!-- $Id: slipc.sgml,v 1.1.1.1.4.1 1995-09-17 11:03:24 davidg Exp $ -->
<!-- $Id: slipc.sgml,v 1.1.1.1.4.2 1995-09-17 11:19:41 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>Setting up a SLIP client</heading>
<sect><heading>Setting up a SLIP client<label id="slipc"></heading>
<p><em>Contributed by &a.asami;.</em>
<p><em>Contributed by &a.asami;<newline>8 Aug 1995.</em>
The following is one way to set up a FreeBSD machine for SLIP on a
static host network. For dynamic hostname assignments (i.e., your
@ -16,37 +16,23 @@ just for your reference, I'm no expert in SLIP nor networking so your
mileage may vary.
-->
Note: for 1.1 systems (not 1.1.5), you need to use /dev/tty01 instead
of /dev/cua01. substitute all the occurences of "cua" in this document
with "tty".
First, determine which serial port your modem is connected to. I have
a symbolic link /dev/modem -> cuaa1, and only use the modem name in my
configuration files. It can become quite cumbersome when you need to
fix a bunch of files in /etc and .kermrc's all over the system! (Note
that /dev/cuaa0 is COM1, cuaa1 is COM2, etc.)
Note: the default 1.1.5(.1) system only comes with cua/ttyd pairs for
the last two ports (2 and 3), so if your modem is at sio0/sio1
(COM1/COM2), you need to make the devices. Try "cd /dev; sh MAKEDEV
cua01" to make the new special files for sio1 (ditto for sio0). This
will delete tty01, but you shouldn't need it anymore...or you can make
a symbolic link /dev/tty01 -> ttyd1 if you don't want to hunt down all
occurences of tty01 in your setup files.
I actually have a symbolic link /dev/modem -> cua01 (and /dev/mouse ->
ttyd0). I use only the modem/mouse names in my configuration files.
This helped a lot when I switched from 1.1 to 1.1.5.1 (tty01 => cua01)
and when I had to move my modem temporarily to sio2 to enable the
RS-232C port on the serial card. It can become quite cumbersome when
you need to fix a bunch of files in /etc and .kermrc's all over the
system!
First, make sure you have
Make sure you have
<verb>
pseudo-device sl 2
pseudo-device sl 1
</verb>
in your kernel's config file. It is included in the GENERIC, GENERICAH
and GENERICBT kernels, so this won't be a problem unless you deleted it.
in your kernel's config file. It is included in the GENERIC kernel,
so this won't be a problem unless you deleted it.
<sect1><heading>Things you have to do only once</heading>
<p><enum>
<item> Add your home machine, the gateway and nameservers to your
<item>Add your home machine, the gateway and nameservers to your
/etc/hosts file. Mine looks like this:
<verb>
127.0.0.1 localhost loghost
@ -59,48 +45,70 @@ and GENERICBT kernels, so this won't be a problem unless you deleted it.
By the way, silvia is the name of the car that I had when I was
back in Japan (it's called 2?0SX here in U.S.).
<item> Make sure you have "hosts" before "bind" in your /etc/host.conf.
<item>Make sure you have "hosts" before "bind" in your /etc/host.conf.
Otherwise, funny things may happen.
<item> Edit the /etc/netstart and add this to the end of the file:
<item>Edit the file /etc/sysconfig.
<enum>
<item>Set your hostname by editing the line that says:
<verb>
# set up slip
gateway=slip-gateway
ifconfig sl0 inet $hostname $gateway netmask 0xffffff00
route add default $gateway
hostname=myname.my.domain
</verb>
Note that because of the "slip-gateway" entry in /etc/hosts, there
is no local dependency in the netstart file. Also, you might want
to un-comment the "<verb>route add $hostname localhost</verb>" line.
You should give it your full Internet hostname.
<item> Make a file /etc/resolv.conf which contains:
<item>Add sl0 to the list of network interfaces by changing the line
that says:
<verb>
network_interfaces="lo0"
</verb>
to:
<verb>
network_interfaces="lo0 sl0"
</verb>
<item>Set the startup flags of sl0 by adding a line:
<verb>
ifconfig_sl0="inet ${hostname} slip-gateway netmask 0xffffff00 up"
</verb>
<item>Designate the default router by changing the line:
<verb>
defaultrouter=NO
</verb>
to:
<verb>
defaultrouter=slip-gateway
</verb>
</enum>
<item>Make a file /etc/resolv.conf which contains:
<verb>
domain HIP.Berkeley.EDU
nameserver 128.32.136.9
nameserver 128.32.136.12
</verb>
As you can see, these set up the nameserver hosts. Of course, the
actual addresses depend on your environment.
actual domain names and addresses depend on your environment.
<item> Set the password for root and toor (and any other accounts that
<item>Set the password for root and toor (and any other accounts that
doesn't have a password). Use passwd, don't edit the passwd or
passwd.master files!
<item> Edit /etc/myname and reboot the machine.
<item>Reboot your machine and make sure it comes up with the correct
hostname.
</enum>
<sect1><heading>Making a SLIP connection</heading>
<p><enum>
<item> Dial up, type "slip" at the prompt, enter your machine name and
<item>Dial up, type "slip" at the prompt, enter your machine name and
password. The things you need to enter depends on your
environment. I use kermit, with a script like this:
<verb>
# kermit setup
set modem hayes
set line /dev/cua01
set speed 57600
set line /dev/modem
set speed 115200
set parity none
set flow rts/cts
set terminal bytesize 8
@ -119,27 +127,21 @@ output ***\x0d, echo \x0aCONNECTED\x0a
filesystem is generally a BAD idea. Do it at your own risk. I'm
just too lazy.
Note: If you have an 1.1 machine, and kermit doesn't give you a
prompt, try "stty -f /dev/tty01 clocal". I put this in
/etc/rc.local so that it works the first time I boot the machine.
This doesn't apply to 1.1.5(.1) systems, as cua0? are already
configured for dialouts.
<item> Leave the kermit there (you can suspend it by "z") and as root,
<item>Leave the kermit there (you can suspend it by "z") and as root,
type
<verb>
slattach -h -c -s 57600 /dev/cua01
slattach -h -c -s 115200 /dev/modem
</verb>
if you are able to "ping" hosts on campus, you are connected!
If it doesn't work, you might want to try "-a" instead of "-c".
if you are able to "ping" hosts on the other side of the router,
you are connected! If it doesn't work, you might want to try "-a"
instead of "-c" as an argument to slattach.
</enum>
<sect1><heading>How to shutdown the connection</heading>
<p>Type "ps gx" (as root) to find out the PID of slattach, and use
"kill -INT" to kill it.
Then go back to kermit ("fg" if you suspended it) and exit from it
("q").
<p>Type "kill -INT `cat /var/run/slattach.modem.pid`" (as root) to
kill slattach. Then go back to kermit ("fg" if you suspended it)
and exit from it ("q").
The slattach man page says you have to use "ifconfig sl0 down" to
mark the interface down, but this doesn't seem to make any
@ -149,24 +151,19 @@ slattach -h -c -s 57600 /dev/cua01
often does). In that case, simply start kermit and quit it again.
It usually goes out on the second try.
When you want to connect again, go back to (XXX). You may have to
watch out for clocal mode. If "stty -f /dev/tty01" doesn't tell
you it's clocal, you need to re-set it before kermitting. Again,
this is only for 1.1 machines.
<sect1><heading>Troubleshooting</heading>
<p>If it doesn't work, feel free to ask me. The things that people
tripped over so far:
<itemize>
<item> Not using "-c" or "-a" in slattach (I have no idea why this can be
<item>Not using "-c" or "-a" in slattach (I have no idea why this can be
fatal, but adding this flag solved the problem for at least one
person)
<item> Using "s10" instead of "sl0" (might be hard to see the difference on
<item>Using "s10" instead of "sl0" (might be hard to see the difference on
some fonts.
<item> Try "ifconfig sl0" to see your interface status. I get:
<item>Try "ifconfig sl0" to see your interface status. I get:
<verb>
silvia# ifconfig sl0
sl0: flags=10<POINTOPOINT>

28
handbook/slips.sgml
View file

@ -11,7 +11,7 @@ Setting up FreeBSD as a SLIP Server
-->
<sect><heading>Setting up a SLIP server</heading>
<sect><heading>Setting up a SLIP server<label id="slips"></heading>
<p><em>Contribudted by &a.ghelmer;.<newline>
v1.0, 15 May 1995.</em>
@ -35,7 +35,7 @@ problem.
For FreeBSD 1.x users, all of the files referenced in the directory
<tt>/etc/sliphome</tt> are actually in the <tt>/etc</tt> directory.
<sect1><heading>Prerequisites<label id="prereqs"></>
<sect1><heading>Prerequisites<label id="slips:prereqs"></>
<p>
This document is very technical in nature, so background knowledge is
@ -64,7 +64,7 @@ modems, and perhaps <tt/stty(1)/ for information on setting serial
port parameters &lsqb;such as <tt/clocal/ for directly-connected
serial interfaces&rsqb;.
<sect1>Quick Overview
<sect1><heading>Quick Overview</heading>
<p>
In its typical configuration, using FreeBSD as a SLIP server works as
@ -76,7 +76,7 @@ the special user, and if it finds a match, connects the serial line to
an available SLIP interface and then runs the shell script
<tt>/etc/sliphome/slip.login</tt> to configure the SLIP interface.
<sect2>An Example of a SLIP Server Login
<sect2><heading>An Example of a SLIP Server Login</heading>
<p>
For example, if a SLIP user ID were <tt>Shelmerg</tt>, <tt/Shelmerg/'s
@ -121,7 +121,7 @@ logging).
OK, enough of the examples -- let's dive into setting up the system.
<sect1>Kernel Configuration
<sect1><heading>Kernel Configuration</heading>
<p>
FreeBSD's default kernels usually come with two SLIP interfaces
defined (<tt>sl0</tt> and <tt>sl1</tt>); you can use <tt>netstat
@ -182,7 +182,7 @@ See the document ``Building Berkeley Kernels with Config'' and the
manual page for <tt>config(8)</tt> to see how to configure and build
kernels.
<sect1>Sliplogin Configuration
<sect1><heading>Sliplogin Configuration</heading>
<p>
@ -196,7 +196,7 @@ and (optionally) <tt>slip.logout</tt>, which undoes
<tt>slip.login</tt>'s effects when the serial connection is
terminated.
<sect2>slip.hosts Configuration
<sect2><heading>slip.hosts Configuration</heading>
<p>
@ -249,7 +249,7 @@ going to use ``proxy ARP'' on your SLIP server (it's not ``true''
proxy ARP, but that is the terminology used in this document to
describe it). If you're not sure which method to select or how to
assign IP addresses, please refer to the TCP/IP books referenced in
the <ref id="prereqs"> section and/or consult your IP network manager.
the <ref id="slips:prereqs"> section and/or consult your IP network manager.
If you are going to use a separate subnet for your SLIP clients, you
will need to allocate the subnet number out of your assigned IP
@ -268,7 +268,7 @@ Ethernet subnet, and you'll also need to adjust your
<tt>/etc/sliphome/slip.logout</tt> scripts to use <tt>arp(8)</tt> to
manage the proxy-ARP entries in the SLIP server's ARP table.
<sect2>slip.login Configuration
<sect2><heading>slip.login Configuration</heading>
<p>
The typical <tt>/etc/sliphome/slip.login</tt> file looks like this:
@ -347,7 +347,7 @@ Note that when you create <tt>/etc/sliphome/slip.login</tt> and
/etc/sliphome/slip.logout</tt>) must be set, or <tt>sliplogin</tt>
will be unable to execute it.
<sect2>slip.logout Configuration
<sect2><heading>slip.logout Configuration</heading>
<p>
@ -400,7 +400,7 @@ It bears repeating: make sure <tt>/etc/sliphome/slip.logout</tt> has
the execute bit set for after you create it (ie, <tt>chmod 755
/etc/sliphome/slip.logout</tt>).
<sect1>Routing Considerations
<sect1><heading>Routing Considerations</heading>
<p>
If you are not using the ``proxy ARP'' method for routing packets
@ -411,7 +411,7 @@ your SLIP server, or you will probably need to install and configure
<tt>gated</tt> on your FreeBSD SLIP server so that it will tell your
routers via appropriate routing protocols about your SLIP subnet.
<sect2>Static Routes
<sect2><heading>Static Routes</heading>
<p>
Adding static routes to your nearest default routers can be
@ -423,7 +423,7 @@ which static routes to tell other routers about, so some expertise and
troubleshooting/tweaking may be necessary to get static-route-based
routing to work.
<sect2>Running gated
<sect2><heading>Running gated</heading>
<p>
An alternative to the headaches of static routes is to install
@ -503,7 +503,7 @@ appropriate for your system. Please see the manual page for
<tt>gated</tt> for information on <tt>gated</tt>'s command-line
parameters.
<sect1>Acknowledgements
<sect1><heading>Acknowledgements</heading>
<p>
Thanks to these people for comments and advice regarding this tutorial:

185
handbook/submitters.sgml
View file

@ -1,28 +1,28 @@
<!-- $Id: submitters.sgml,v 1.2 1995-05-18 03:05:22 jfieber Exp $ -->
<!-- $Id: submitters.sgml,v 1.2.4.1 1995-09-17 11:19:43 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Contributing to FreeBSD</heading>
<chapt><heading>Contributing to FreeBSD<label id="submitters"></heading>
<p><em>Contributed by &a.jkh;.</em>
This guide is intended for those who are moderately familar with FreeBSD
and are now to the point where they have some locally developed
customizations or fixes to the system which they'd like to incorporate
back into the mainstream sources, thus saving the work of having to
re-integrate the changes for each subsequent FreeBSD release. Submitting
something to the FreeBSD project is also an excellent way of getting your
code seriously <em>tested</em>! Many people have developed an original concept
far beyond what they might have envisioned at the start just due to the
flood of feedback and ideas generated by the many thousands of users of
FreeBSD. Contributions are also what FreeBSD lives and grows from,
and so your contributions are very important to the continued survival
of this communal effort of ours---we're very glad to see you reading this
documentation!
This guide is intended for those who are moderately familar with
FreeBSD and have reached a point where they have some locally
developed customizations or fixes to the system which they'd like to
incorporate back into the mainstream sources. Submitting something to
the FreeBSD project ensures that you won't have to continually
reintegrate it with each subsequent release and is also an excellent
way of getting your code seriously <em>tested</em>! Many people have
seen an original concept develop far beyond what they might have
originally envisioned simply due to the flood of feedback and ideas
generated by the many thousands of users of FreeBSD. Contributions
are also what FreeBSD lives and grows from, so your contributions are
very important to the continued survival of this communal effort of
ours---we're very glad to see you reading this document!
Submissions to FreeBSD can generally be classified into four catagories:
<enum>
<item>Ideas, general suggestions, bug reports.
<item>Addition, deletion, renaming or patching of existing sources.
<item>Changes to existing sources.
<item>Significant contribution of a large body of independant work.
<item>Porting of freely available software.
</enum>
@ -41,8 +41,7 @@ are each, in their own way, quite significant to the project.
volume of mail!) may
subscribe to the hackers mailing list by sendimg mail to
<tt>&lt;majordomo@freebsd.org&gt;</tt>.
See <ref id="eresources:mailing-lists"
name="mailing lists">
See <ref id="eresources:mail" name="mailing lists">
for more information about this and other mailing lists.
<item>An actual bug report should be filed by using the
@ -65,28 +64,23 @@ are each, in their own way, quite significant to the project.
<p>An addition or change to the existing source code is a somewhat trickier
affair and depends a lot on how far out of date you are with the current
state of the core FreeBSD development. There is a special on-going release
of FreeBSD known as ``FreeBSD-current'' and made available in a variety of
ways for the convenience of developers who wish to actively work on the
system. See <ref id="current:" name="Staying current with
FreeBSD"> for more information about getting and using FreeBSD-current.
of FreeBSD known as ``FreeBSD-current'' which is made available in
a variety of ways for the convenience of developers working
actively on the system. See <ref id="current" name="Staying
current with FreeBSD"> for more information about getting and using
FreeBSD-current.
Working from older sources unfortunately means that your changes may
sometimes be too obsolete to use, or too divergent to allow for easy
re-integration. This can be minimized somewhat by subscribing to the
<tt>&lt;announce@freebsd.org&gt;</tt> mailing list, among
others, where periodic
announcements concerning the current state of the system are made.
If you see a change being proposed for which you have a better solution,
by all means come forward with your contribution and we
will do our very best to evaluate it fairly and perhaps integrate it if
it is indeed a better solution.
sometimes be too obsolete or too divergent for easy re-integration into
FreeBSD. Chances of this can be minimized somewhat by subscribing to the
<tt>&lt;announce@freebsd.org&gt;</tt> and
<tt>&lt;current@freebsd.org&gt;</tt> mailing lists, where discussions
on the current state of the system take place.
Assuming that you can manage to secure fairly up-to-date sources to base
your changes on, the next step is to produce a set of diffs to send to the
FreeBSD maintainers for evaluation and possible adoption. This is done
with the <tt>diff(1)</tt> command, with the FreeBSD
maintainers preferring to receive
diffs in `context diff' form. For example:
FreeBSD maintainers. This is done with the <tt>diff(1)</tt> command,
with the `context diff' form being preferred. For example:
<tscreen><verb>
diff -c &lt;oldfile&gt &lt;newfile&gt;
</verb></tscreen>
@ -94,39 +88,36 @@ or
<tscreen><verb>
diff -c -r &lt;olddir&gt &lt;newdir&gt;
</verb></tscreen>
See the man page for <tt>diff(1)</tt> for more details
on producing both context and recursive context diffs.
would generate such a set of context diffs for the given source file
or directory hierarchy. See the man page for <tt>diff(1)</tt> for more
details.
Once you have a set of diffs that are capable of taking a copy
of the original code and bringing it to a state identical to
the ``new'' sources (you may test this with the
Once you have a set of diffs (which you may test with the
<tt>patch(1)</tt> command), you should bundle them up in an
email message and send it, along with a brief description of
what the diffs are for, to
<tt>&lt;hackers@freebsd.org&gt;</tt>. Someone will very
likely get back in touch with you in 24 hours or less,
assuming of course that your diffs are interesting!
assuming of course that your diffs are interesting! :-)
If your changes don't express themselves well as diffs alone
(e.g. you've perhaps added, deleted or renamed files as well)
then you may be better off bundling any new files, diffs and
instructions for deleting/renaming any others into a
<tt>tar</tt> file and running the <tt>uuencode(1)</tt> program
on it before sending the output of that to
<tt>&lt;hackers@freebsd.org&gt;</tt>. See the man pages on
<tt>tar(1)</tt> and <tt>uuencode(1)</tt> for more info on
bundling files through the mail this way.
instructions for deleting/renaming others into a <tt>tar</tt>
file and running the <tt>uuencode(1)</tt> program on it before
sending the output of that to <tt>&lt;hackers@freebsd.org&gt;</tt>.
See the man pages on <tt>tar(1)</tt> and <tt>uuencode(1)</tt> for more
information on bundling files this way.
If your change is of a potentially sensitive nature, for
example you're unsure of copyright issues governing its
further distribution, or you're simply not ready to release it
without a tighter review first, then you should send it to
<tt>&lt;core@freebsd.org&gt;</tt> rather than
If your change is of a potentially sensitive nature, e.g.
you're unsure of copyright issues governing its further distribution
or you're simply not ready to release it without a tighter review first,
then you should send it to <tt>&lt;core@freebsd.org&gt;</tt> rather than
<tt>&lt;hackers@freebsd.org&gt;</tt>. The core mailing list
reaches a much smaller group of people who do much of the
day-to-day work on FreeBSD. Note that this group is also
<em>very busy</em> and so you should only mail to them
in cases where mailing to hackers truly is impractical.
<em>very busy</em> and so you should only send mail to them
in cases where mailing to hackers is truly impractical.
<sect><heading>Contributions of new code</heading>
@ -135,42 +126,40 @@ diff -c -r &lt;olddir&gt &lt;newdir&gt;
work, or the addition of an important new feature to FreeBSD,
it becomes almost always necessary to either send changes as
uuencoded tar files or upload them to our ftp site <url
url="ftp://freefall.cdrom.com/pub/FreeBSD/incoming"> where
users may log in anonymously and upload their work or download
the work-in-progress files left by others.
url="ftp://ftp.freebsd.org/pub/FreeBSD/incoming">.
When working with large amounts of code, the touchy subject of
copyrights also invariably comes up. Acceptable copyrights
for code included in FreeBSD are:
<enum>
<item>Contributions under the BSD copyright
are greatly preferred due to its ``no strings attached''
nature and general attractiveness to commercial enterprises
who might then be inclined to invest something of their own
<item>The BSD copyright. This copyright is most preferred
due to its ``no strings attached'' nature and general
attractiveness to commercial enterprises. Far from
discouraging such commercial use, the FreeBSD Project
actively encourages such participation by commercial interests
who might eventually be inclined to invest something of their own
into FreeBSD.
<item>Contributions under the GNU Public License, or ``GPL''. This is
not quite as popular a solution for us, due to
the amount of extra effort demanded of anyone
using the code for commercial purposes. However, given the
sheer quantity of GPL'd code we currently require (compiler,
assembler, text formatter, etc), it would be silly to pretend
that we couldn't deal with the GPL at all and so we have become
more willing to accept code with either the BSD or the GPL
copyright. Code under the GPL also goes into a different part
of the tree, that being <tt>/sys/gnu</tt> or
<tt>/usr/src/gnu</tt>.
<item>Contributions coming under any other type of copyright must be
carefully reviewed before their inclusion into FreeBSD will even
be considered. Contributions for which particularly restrictive
commercial copyrights apply are generally rejected, though the
authors are always free to make the changes available through
their own channels.
<item>The GNU Public License, or ``GPL''. This license isn't quite
as popular with us due to the amount of extra effort demanded
of anyone using the code for commercial purposes, but given
the sheer quantity of GPL'd code we currently require (compiler,
assembler, text formatter, etc) it would be silly to refuse
additional contributions under this license. Code under the GPL
also goes into a different part of the tree, that being
<tt>/sys/gnu</tt> or <tt>/usr/src/gnu</tt>, and is therefore
easily identifable to anyone for whom the GPL presents a problem.
</enum>
To place such a copyright on your work, place the following
<p>Contributions coming under any other type of copyright must be
carefully reviewed before their inclusion into FreeBSD will
be considered. Contributions for which particularly restrictive
commercial copyrights apply are generally rejected, though the
authors are always encouraged to make such changes available
through their own channels.
To place a ``BSD-style'' copyright on your work, include the following
text at the very beginning of every source code file you wish
to protect, replacing the text between the `<tt>%%</tt>' with
the appropriate information.
@ -204,7 +193,7 @@ 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.
$Id: submitters.sgml,v 1.2 1995-05-18 03:05:22 jfieber Exp $
$Id: submitters.sgml,v 1.2.4.1 1995-09-17 11:19:43 davidg Exp $
</verb></tscreen>
For your convenience, a copy of this text can be found in
<tt>/usr/share/examples/etc/bsd-style-copyright</tt>.
@ -213,25 +202,21 @@ For your convenience, a copy of this text can be found in
<sect><heading>Porting of software</heading>
<p>The porting of freely available software, while perhaps not as
gratifying as developing your own package from scratch, is still
a vital part of FreeBSD's growth and of great usefulness to those
who wouldn't otherwise know where to turn for it. All ported
software is organized into a hierarchy know as ``the ports
collection''. This collection enables a new user to get a
complete overview of what's available in a short time, and with a
logical framework. The ports collection also saves
considerable space by not actually containing the the majority of
the sources being ported. See <ref id="ports:" name="The ports
collection"> for more information on using the ports collection
and <ref id="porting:" name="Porting applications"> for
guidelines on creating new ports. You may also send mail to
gratifying as developing your own from scratch, is still a vital part
of FreeBSD's growth and of great usefulness to those who wouldn't
otherwise know where to turn for it. All ported software is organized
into a carefully organized hierarchy know as ``the ports collection''.
The collection enables a new user to get a quick and complete overview
of what's available for FreeBSD in an easy-to-compile form. It also
saves considerable space by not actually containing the the majority
of the sources being ported, but merely those differences required for
running under FreeBSD. See <ref id="ports" name="The ports
collection"> for more information on using the ports collection and
<ref id="porting" name="Porting applications"> for guidelines on
creating new ports. You may also send mail to
<tt>&lt;ports@freebsd.org&gt;</tt>.
Whichever way you decide to contribute, we hope you'll find it an
enjoyable process and also realize how valuable your
contributions are to the project! FreeBSD is one of those great
projects where the more we all put in, the more we all get back
out of it again, and with enough steady contributions it begins
to aquire a momentum of its own. It is through such momentum
that mountains are moved!
enjoyable and rewarding process. Such contributions are also very
valuable to FreeBSD's continued progress, and as a free software
effort, the more we all put in the more we all get back out of it!

18
handbook/sup.sgml
View file

@ -1,8 +1,8 @@
<!-- $Id: sup.sgml,v 1.2.4.1 1995-09-17 11:03:26 davidg Exp $ -->
<!-- $Id: sup.sgml,v 1.2.4.2 1995-09-17 11:19:44 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>SUP</heading>
<sect><heading>SUP<label id="sup"></heading>
<p><em>Contributed by &a.jkh; and &a.gclarkii;.</em>
@ -30,12 +30,12 @@ the two collections; if you don't want ports, you can simply delete all the
ports entries. If you're inside the United States, you may also uncomment
the `secure' collection line to grab the DES code. If you're outside the
U.S., you should NOT sup this code from FreeBSD.ORG as this will
violate U.S. export restrictions. Simply sup everything *but* the secure
collection and then go look on "braae.ru.ac.za", where it's available for
violate U.S. export restrictions. Simply sup everything <em>but</em> the secure
collection and then go look on braae.ru.ac.za, where it's available for
anonymous ftp for those outside the U.S.
Any other distributions you do not wish to receive can be commented out
with a # at the begining of the distribution line.
with a &num; at the begining of the distribution line.
Once this is setup, you're ready to go. To start sup type:
<verb>
@ -48,11 +48,9 @@ like so:
</verb>
Thats all there is to it! Remember that if you're running current,
which is what you will have if you sup, please join the freebsd-current
mailing list. You should also be sure to read:
<verb>
ftp://ftp.FreeBSD.ORG:/pub/FreeBSD/FAQ/current-policy.FAQ
</verb>
For important information on just what we can and cannot do for you as
mailing list. You should also be sure to read <ref id="current"
name="Staying current with FreeBSD">
for important information on just what we can and cannot do for you as
a -current user.
<sect1><heading>Description of FreeBSD SUP distributions</heading>

122
handbook/troubleshooting.sgml
View file

@ -1,7 +1,7 @@
<!-- $Id: troubleshooting.sgml,v 1.1.1.1 1995-04-28 16:19:59 jfieber Exp $ -->
<!-- $Id: troubleshooting.sgml,v 1.1.1.1.4.1 1995-09-17 11:19:45 davidg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Troubleshooting</heading>
<chapt><heading>Troubleshooting<label id="troubleshooting"></heading>
<p>The following tips and tricks may help you turn a
failing (or failed) installation attempt into a success.
@ -41,15 +41,7 @@
address, IO address or a number of other device
configuration parameters. You can also disable a device
entirely if it's causing problems for other devices you'd
much rather have work. Note that this only affects the
kernel being booted temporarily, it does not write out
the information to the kernel so that these settings are
permanantly altered (this would be actually rather hard).
If you reboot, you'll have to make the same changes
again. The goal of the <tt>-c</tt> utility is to get you
up far enough to be able to download the appropriate
sources and configure and rebuild a kernel more specific
to your needs.
much rather have work.
Another solution is, obviously, to remove the offending
hardware or simply strip the system down to the bare
@ -61,17 +53,6 @@
</descrip>
<sect>
<heading>My floppy-tape drive isn't probed</heading>
<p>Cause: Last-minute problems with this driver caused it
to be disabled by default.
Solution: Boot with -c (described above) and set the
flags value of fdc0 to 1. This will re-enable the floppy
tape driver. Sorry, but it was causing problems for
other people!
<sect>
<heading>When I boot for the first time, it still looks for
/386bsd!</heading>
@ -86,100 +67,3 @@
If you're installing for the first time, don't forget to
(W)rite out your new boot blocks! :-)
<sect>
<heading>I want to boot FreeBSD off the second drive. It
doesn't!</heading>
<p>Cause: FreeBSD will actually install just fine on a
drive other than 0 (the first drive), and the boot
manager will even allow you to select it, but the boot
blocks rather pathologically assume 0. This should be
fixed in 2.1.
Solution: Easy - follow these steps:
1. Select the first (0) drive from the (F)disk editor
and write out the boot manager with the (B) option.
This will enable the boot manager that allows you to
actually boot off the other drive.
2. Exit the fdisk editor for the first drive and and
re-enter it again for the drive you wish to install
on. Set up a partition on this drive, or select
(A)ll for the entire drive.
3. Enter the disklabel editor and allocate space on
your second drive as normal. Proceed with the
installation.
4. Once you've installed on the disk and are going to
reboot from the hard disk, enter the following at
the boot prompt:
hd(1,a)/kernel
This will ensure that you really boot from the second
drive. If you've actually installed on a drive other
than 1 (the 3rd or 4th drive?), substitute that number
in for the above. You will need to enter this EVERY
time you reboot from the hard disk. If you're feeling
brave and have a srcdist + the requisite experience,
you can hack the boot blocks in:
/usr/src/sys/i386/boot/biosboot
So that this drive you're booting from is hard-coded.
Recompile the boot blocks and reinstall them on your
drive with `disklabel -B ...' You can then have the
default Do The Right Thing.
<sect>
<heading>Newfs crashes, requesting that blocksize be 32K</heading>
<p>Cause: You have your SCSI controller configured to
translate geometries for disks >1GB in size.
Solution: Turn such translation OFF in your controller's
BIOS setup! FreeBSD has no problems with disks >1GB just
so long as the root partition starts and ends BELOW
cylinder 1024. This is a PC hardware limitation.
<sect>
<heading>FreeBSD won't boot off the hard disk</heading>
<p>Cause: Root partition does not start and end below
cylinder 1024.
Solution: See solution for newfs crashes, or move your
root partition. This limitation holds true for ANY
operating system you wish to boot from your hard drive.
<sect>
<heading>FreeBSD still won't boot off the hard disk</heading>
<p>Cause: No boot code is installed in sector 1.
Solution: Chose the Write MBR (B)oot code in the FDISK
editor.
<sect>
<heading>Nope, FreeBSD's still not booting from the hard
disk</heading>
<p>Cause: BIOS disk geometry different from that used when
installing FreeBSD.
Solution: With IDE drives, pay careful attention to the
geometry information that FreeBSD prints out when it's
first booting off the floppy. Use this geometry in your
BIOS setup or use the BIOS geometry when you install
FreeBSD. Either way, they have to match.
With SCSI drives, the values they report is most often
bogus and cannot be used. In this situation, the SCSI
controller is performing geometry translation and it's
probably wise to assume a default of 64 heads, 32 sectors
and 1MB/cylinder. Use these values when you install
FreeBSD. See above comments concerning newfs failures
for more info.