d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

(This really shouldn't all be on one commit, but I forgot

Browse Source 
I was in the middle of one of these "projects" when I started
on the next, so they wound up all intermixed)

Move the mailing list entities from authors.sgml to the new file
lists.sgml.  Add an entity for majordomo at the same time.

Avoid the use of contractions.  This revealed some grammer problems,
and also has the benefit of helping make things clearer for those people
who do make speak English as a their first language.
This commit is contained in:
Mike Pritchard 1996-05-16 23:18:28 +00:00
parent 63cf8b69f9
commit 09d44b1ef5
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=15798
38 changed files with 772 additions and 765 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
share/doc/handbook/authors.sgml
View File

@ -1,58 +1,12 @@
<!-- $Id: authors.sgml,v 1.21 1996/05/14 20:31:50 rich Exp $ -->
<!-- $Id: authors.sgml,v 1.22 1996/05/16 20:20:54 jkh Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
Names and email address of contributing authors and CVS committers
and some of the common FreeBSD mailing lists. Use these
entities when referencing people or mailing lists. Please
note the use of single
Names and email address of contributing authors and CVS committers.
Use these entities when referencing people. Please note the use of single
and double quotes.
-->
<!ENTITY a.announce "FreeBSD announcments mailing list
<tt><htmlurl url='mailto:freebsd-announce@FreeBSD.ORG'
name='&lt;freebsd-announce@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.doc "FreeBSD documentation project mailing list
<tt><htmlurl url='mailto:freebsd-doc@FreeBSD.ORG'
name='&lt;freebsd-doc@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.bugs "FreeBSD problem reports mailing list
<tt><htmlurl url='mailto:freebsd-doc@FreeBSD.ORG'
name='&lt;freebsd-doc@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.current "FreeBSD-current mailing list
<tt><htmlurl url='mailto:freebsd-current@FreeBSD.ORG'
name='&lt;freebsd-current@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.emulation "FreeBSD-emulation mailing list
<tt><htmlurl url='mailto:freebsd-emulation@FreeBSD.ORG'
name='&lt;freebsd-emulation@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.fs "FreeBSD filesystem project mailing list
<tt><htmlurl url='mailto:freebsd-fs@FreeBSD.ORG'
name='&lt;freebsd-fs@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.hackers "FreeBSD technical discussions mailing list
<tt><htmlurl url='mailto:freebsd-hackers@FreeBSD.ORG'
name='&lt;freebsd-hackers@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.ports "FreeBSD ports mailing list
<tt><htmlurl url='mailto:freebsd-ports@FreeBSD.ORG'
name='&lt;freebsd-ports@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.questions "FreeBSD general questions mailing list
<tt><htmlurl url='mailto:freebsd-questions@FreeBSD.ORG'
name='&lt;freebsd-questions@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.scsi "FreeBSD SCSI subsystem mailing list
<tt><htmlurl url='mailto:freebsd-questions@FreeBSD.ORG'
name='&lt;freebsd-questions@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.stable "FreeBSD-stable mailing list
<tt><htmlurl url='mailto:freebsd-questions@FreeBSD.ORG'
name='&lt;freebsd-questions@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.asami "Satoshi Asami
<tt><htmlurl url='mailto:asami@FreeBSD.ORG'
name='&lt;asami@FreeBSD.ORG&gt;'></tt>">

4
share/doc/handbook/basics.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: basics.sgml,v 1.5 1995/12/11 15:09:02 jkh Exp $ -->
<!-- $Id: basics.sgml,v 1.6 1995/12/14 19:42:34 jfieber Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Unix Basics<label id="basics"></heading>
@ -66,7 +66,7 @@
using the <tt><bf>apropos</bf></tt> command.
<p>So, you are looking at all those fancy commands in <tt>
/usr/bin</tt> but don't even have the faintest idea
/usr/bin</tt> but do not even have the faintest idea
what most of them actually do? Simply do a
<tscreen>
% <bf>cd /usr/bin; man -f *</bf>

8
share/doc/handbook/booting.sgml
View File

@ -3,7 +3,7 @@
This conversion has been made by Ollivier Robert.
$Id: booting.sgml,v 1.9 1996/01/31 14:25:57 mpp Exp $
$Id: booting.sgml,v 1.10 1996/01/31 19:02:55 mpp Exp $
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
@ -51,7 +51,7 @@
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
will not compile under FreeBSD itself because it is written for
Microsoft compilers.
Dosboot will boot the kernel from a MS-DOS file or from a FreeBSD
@ -83,7 +83,7 @@
<tag>MSDOS</tag>
While this is technically possible, it isn't particular useful,
While this is technically possible, it is not particular useful,
because of ``FAT'' filesystems inability to make links, device
nodes and such ``UNIXisms''.
@ -147,7 +147,7 @@
<tt>/nfs</tt>, chroots to <tt>/nfs</tt> and executes
<tt>/sbin/init</tt> there
Now you run FreeBSD diskless, even though you don't control
Now you run FreeBSD diskless, even though you do not control
the NFS server...
<tag/C -- Start an X-server/

4
share/doc/handbook/contrib.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: contrib.sgml,v 1.83 1996/05/13 09:31:34 asami Exp $ -->
<!-- $Id: contrib.sgml,v 1.84 1996/05/15 17:32:46 joerg Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>FreeBSD contributor list<label id="contrib"></heading>
@ -36,7 +36,7 @@
couple of FreeBSD hackers alive and busy. Thanks!
Thanks also to Dermot McDonnell for his donation of a
Toshiba XM3401B CDROM drive. It's been most useful!
Toshiba XM3401B CDROM drive. It has been most useful!
Thanks to Chuck Robey &lt;chuckr@eng.umd.edu&gt; who
contributed his floppy tape streamer for experimental

20
share/doc/handbook/ctm.sgml
View File

@ -3,7 +3,7 @@
#
# Converted by Ollivier Robert <roberto@FreeBSD.ORG>
#
# $Id: ctm.sgml,v 1.7 1996/02/02 05:27:24 wosch Exp $
# $Id: ctm.sgml,v 1.8 1996/05/09 23:04:32 mpp Exp $
#
# ----------------------------------------------------------------------------
# "THE BEER-WARE LICENSE" (Revision 42):
@ -66,7 +66,7 @@
If you only have access to electronic mail or are otherwise blocked
from using FTP then you may wish to get your deltas via email:
Send email to <tt/&lt;majordomo@FreeBSD.ORG&gt;/ to subscribe to
Send email to &a.majordomo to subscribe to
the list ``ctm-src-cur''. (If you do not know how to subscribe
yourself using majordomo, send a message first containing the
word ``help'' - it will send you back usage instructions.)
@ -82,7 +82,7 @@
deltas, you should subscribe to the <tt/ctm-announce@FreeBSD.ORG/
mailing list. In the future, this will be the only place where
announcements concerning the operations of the <tt/CTM/ system will be
posted. Send an email to <tt/majordomo@FreeBSD.ORG/ with a single
posted. Send an email to &a.majordomo with a single
line of ``<tt/subscribe ctm-announce/'' to get added to the list.
<sect1><heading>Starting off with <tt/CTM/ for the first time</heading>
@ -97,7 +97,7 @@
Megabytes of <tt/gzip/'ed data is common for a base delta.
If you do have the 2.0-RELEASE <tt/srcdist/, you can instead
retrieve the <tt/src-cur.0372R20.gz/ file, it's only 4Mb and it
retrieve the <tt/src-cur.0372R20.gz/ file, it is only 4Mb and it
will take you to current from the 2.0-RELEASE sources.
Once you've picked a base delta to start from, you will also need
@ -110,11 +110,11 @@
ctm -v -v /where/you/store/your/deltas/src-cur.*
</verb>
<tt/CTM/ understands deltas which have been put through <tt/gzip/,
so you don't need to gunzip them first, this saves disk space.
so you do not need to gunzip them first, this saves disk space.
Unless it feels very secure about the entire process, <tt/CTM/ will
not touch your tree. To verify a delta you can also use the
``<tt/-c/'' flag and <tt/CTM/ won't actually touch your tree; it will
``<tt/-c/'' flag and <tt/CTM/ will not actually touch your tree; it will
merely verify the integrity of the delta and see if it would apply
cleanly to your current tree.
@ -122,13 +122,13 @@
for more details.
I would also be very happy if somebody could help with the ``user
interface'' portions, as I have realized that I can't make up my
interface'' portions, as I have realized that I cannot make up my
mind on what options should do what, how and when...
That's really all there is to it. Every time you get a new delta,
just run it through <tt/CTM/ to keep your sources up to date.
Don't remove the deltas if they are hard to download again. You
Do not remove the deltas if they are hard to download again. You
just might want to keep them around in case something bad happens.
Even if you only have floppy disks, consider using <tt/fdwrite/ to
make a copy.
@ -157,7 +157,7 @@
</itemize>
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...
be most welcome. And do not forget to tell me what you want also...
<sect1><heading>Miscellaneous stuff</heading>
<p>
@ -174,7 +174,7 @@
There is a sequence of deltas for the <tt/ports/ collection too,
but interest has not been all that high yet. Tell me if you want
an email list for that too and we'll consider setting it up.
an email list for that too and we will consider setting it up.
If you have commit privileges or are similarly authorized by the
FreeBSD core team, you can also get access to the CVS repository

36
share/doc/handbook/current.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: current.sgml,v 1.9 1996/02/11 00:16:12 jkh Exp $ -->
<!-- $Id: current.sgml,v 1.10 1996/05/09 23:04:33 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
@ -10,7 +10,7 @@
THE FREEBSD CURRENT POLICY
Last updated: $Date: 1996/02/11 00:16:12 $
Last updated: $Date: 1996/05/09 23:04:33 $
This document attempts to explain the rationale behind
FreeBSD-current, what you should expect should you decide to run it,
@ -32,9 +32,9 @@ desired functionality can literally be a matter of which part of any
given 24 hour period you grabbed them in!
Under certain circumstances we will sometimes make binaries for parts
of FreeBSD-current available, but only because we're interested in
getting something tested, not because we're in the business of
providing binary releases of current. If we don't offer, please don't
of FreeBSD-current available, but only because we are interested in
getting something tested, not because we are in the business of
providing binary releases of current. If we do not offer, please do not
ask! It takes far too much time to do this as a general task.
<sect><heading>Who needs FreeBSD-current?</heading>
@ -72,10 +72,10 @@ ask! It takes far too much time to do this as a general task.
``legitimate'' FreeBSD-current categories, but we simply <em>do not
have the time</em> to help every person who jumps into FreeBSD-current
with more enthusiasm than knowledge of how to deal with
experimental system software. This is not because we're mean and
nasty people who don't like helping people out (we wouldn't even be
doing FreeBSD if we were), it's literally because we can't answer
400 messages a day <em>and</em> actually work on FreeBSD! I'm sure
experimental system software. This is not because we are mean and
nasty people who do not like helping people out (we would not even be
doing FreeBSD if we were), it is literally because we cannot answer
400 messages a day <em>and</em> actually work on FreeBSD! I am sure
that, if given the choice between having us answer lots of questions or
continuing to improve FreeBSD, most of you would vote for us
improving it.
@ -84,9 +84,9 @@ ask! It takes far too much time to do this as a general task.
<sect><heading>Using FreeBSD-current</heading>
<p><enum> <item> Join the freebsd-current and cvs-all
mailing lists. This is not just a good idea, it's
<em>essential</em>. If you aren't on the &a.current, you
won't see the comments that people are making about the
mailing lists. This is not just a good idea, it is
<em>essential</em>. If you are not on the &a.current, you
will not see the comments that people are making about the
current state of the system and thus will probably end up stumbling
over a lot of problems that others have already found and
solved. Even more importantly, you will miss out on
@ -95,12 +95,10 @@ ask! It takes far too much time to do this as a general task.
rebuild the kernel or your system will crash horribly!").
The cvs-all mailing list will allow you to see the commit log
entry for each change as it's made along with any pertinent
entry for each change as it is made along with any pertinent
information on possible side-effects.
To join these lists, send mail to
<htmlurl url="mailto:majordomo@FreeBSD.ORG"
name="majordomo@FreeBSD.ORG"> and say:
To join these lists, send mail to &a.majordomo and specify:
<verb>
subscribe current
subscribe cvs-all
@ -120,7 +118,7 @@ ask! It takes far too much time to do this as a general task.
<item> Use the CMU `sup' program (Software Update
Protocol), also described below.
This is the second most recommended method, since it allows
you to grab the entire collection once and then only what's
you to grab the entire collection once and then only what has
changed from then on. Many people run sup from cron
and keep their sources up-to-date automatically.
@ -146,7 +144,7 @@ ask! It takes far too much time to do this as a general task.
communications bandwidth is not a consideration, use sup or ftp.
Otherwise, use CTM.
<item> If you're grabbing the sources to run, and not just look at,
<item> If you are grabbing the sources to run, and not just look at,
then grab <em>all</em> of current, not just selected portions. The
reason for this is that various parts of the source depend on
updates elsewhere, and trying to compile just a subset is almost
@ -159,7 +157,7 @@ ask! It takes far too much time to do this as a general task.
bootstrapping procedures that sometimes become necessary as we move
towards the next release.
<item> Be active! If you're running FreeBSD-current, we want to know
<item> Be active! If you are running FreeBSD-current, we want to know
what you have to say about it, especially if you have suggestions
for enhancements or bug fixes. Suggestions with accompanying code
are received most enthusiastically!

82
share/doc/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.7 1996/03/31 18:01:53 joerg Exp $
$Id: dialup.sgml,v 1.8 1996/05/09 23:04:35 mpp Exp $
<!DOCTYPE linuxdoc PUBLIC "-//Linux//DTD linuxdoc//EN">
@ -68,10 +68,10 @@ If you need more information about these terms and data communications
in general, the author remembers reading that <em/The RS-232 Bible/
(anybody have an ISBN?) is a good reference.
When talking about communications data rates, the author doesn't use
When talking about communications data rates, the author does notuse
the term <bf/baud/. Baud refers to the number of electrical state
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
per second) is the ``correct'' term to use (at least it does not seem
to bother the curmudgeons quite a much).
<sect2><heading>External vs. Internal Modems</heading>
@ -97,7 +97,7 @@ A background knowledge of these items is assumed
<itemize>
<item> You know how to connect your modem to your computer so that the
two can communicate (unless you have an internal modem, which doesn't
two can communicate (unless you have an internal modem, which does not
need such a cable)
<item> You are familiar with your modem's command set, or know where
@ -134,7 +134,7 @@ without all of the needed signals, so if you have problems, such as
a login session not going away when the line hangs up, you may have a
problem with your cable.
The second prerequisite depends on the modem(s) you use. If you don't
The second prerequisite depends on the modem(s) you use. If you do not
know your modem's command set by heart, you will need to have the
modem's reference book or user's guide handy. Sample commands for USR
Sportster 14,400 external modems will be given, which you may be able
@ -228,7 +228,7 @@ sio3 at 0x2e8-0x2ef irq 9 on isa
sio3: type 16550A
</verb></tscreen>
If your kernel doesn't recognize all of your serial ports, you'll
If your kernel does not recognize all of your serial ports, you will
probably need to configure a custom FreeBSD kernel for your system.
Please see the BSD System Manager's Manual chapter on ``Building
@ -238,13 +238,13 @@ Options'' &lsqb;in <tt>/sys/conf/options</tt> and in
<tt>/sys/<em>arch</em>/conf/options.<em>arch</em></tt>, with
<em>arch</em> for example being <tt>i386</tt>&rsqb; for more
information on configuring and building kernels. You may have to
unpack the kernel source distribution if haven't installed the system
unpack the kernel source distribution if have not installed the system
sources already (<tt>srcdist/srcsys.??</tt> in FreeBSD 1.1,
<tt>srcdist/sys.??</tt> in FreeBSD 1.1.5.1, or the entire source
distribution in FreeBSD 2.0) to be able to configure and build
kernels.
Create a kernel configuration file for your system (if you haven't
Create a kernel configuration file for your system (if you have not
already) by <tt/cd/ing to <tt>/sys/i386/conf</tt>. Then, if you are
creating a new custom configuration file, copy the file GENERICAH (or
GENERICBT, if you have a BusTek SCSI controller on FreeBSD 1.x) to
@ -258,7 +258,7 @@ device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr
device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr
</verb></tscreen>
You can comment-out or completely remove lines for devices you don't
You can comment-out or completely remove lines for devices you do not
have. If you have a multiport serial board, such as the Boca Board
BB2016, please see the <tt/sio(4)/ man page for complete information
on how to write configuration lines for multiport boards. Be careful
@ -271,7 +271,7 @@ Note that <tt/port "IO_COM1"/ is a substitution for <tt/port 0x3f8/,
<tt/IO_COM4/ is <tt/0x2e8/, which are fairly common port addresses for
their respective serial ports; interrupts 4, 3, 5, and 9 are fairly
common interrupt request lines. Also note that regular serial ports
<bf>can't</bf> share interrupts on ISA-bus PCs (multiport boards have
<bf>cannot</bf> share interrupts on ISA-bus PCs (multiport boards have
on-board electronics that allow all the 16550A's on the board to share
one or two interrupt request lines).
@ -319,7 +319,7 @@ exists.
After making new device special files, be sure to check the
permissions on the files (especially the <tt>/dev/cua*</tt> files) to
make sure that only users who should have access to those device
special files can read &amp; write on them - you probably don't want
special files can read &amp; write on them - you probably do not want
to allow your average user to use your modems to dialout. The default
permissions on the <tt>/dev/cua*</tt> files should be sufficient:
@ -336,7 +336,7 @@ These permissions allow the user <tt/uucp/ and users in the group
<p>
There are three system configuration files in the <tt>/etc</tt>
directory that you'll probably need to edit to allow dialup access to
directory that yo will probably need to edit to allow dialup access to
your FreeBSD system. The first, <tt>/etc/gettytab</tt>, contains
configuration information for the <tt>/usr/libexec/getty</tt> daemon.
Second, <tt>/etc/ttys</tt> holds information that tells
@ -351,8 +351,8 @@ group likes to configure their modems and system so that no matter at
what speed a remote user dials in, the local computer-to-modem RS-232
interface runs at a locked speed. The benefit of this configuration
is that the remote user always sees a system login prompt immediately.
The downside is that the system doesn't know what a user's true data
rate is, so full-screen programs like Emacs won't adjust their
The downside is that the system does not know what a user's true data
rate is, so full-screen programs like Emacs will not adjust their
screen-painting methods to make their response better for slower
connections.
@ -360,17 +360,17 @@ The other school configures their modems' RS-232 interface to vary its
speed based on the remote user's connection speed. For example,
V.32bis (14.4 Kbps) connections to the modem might make the modem run
its RS-232 interface at 19.2 Kbps, while 2400 bps connections make the
modem's RS-232 interface run at 2400 bps. Because <tt/getty/ doesn't
modem's RS-232 interface run at 2400 bps. Because <tt/getty/ does not
understand any particular modem's connection speed reporting,
<tt/getty/ gives a <tt/login:/ message at an initial speed and watches
the characters that come back in response. If the user sees junk,
it's assumed that they know they should press the
it is assumed that they know they should press the
<tt>&lt;Enter&gt;</tt> key until they see a recognizable prompt. If
the data rates don't match, <tt/getty/ sees anything the user types as
the data rates do not match, <tt/getty/ sees anything the user types as
``junk'', tries going to the next speed and gives the <tt/login:/
prompt again. This procedure can continue ad nauseum, but normally
only takes a keystroke or two before the user sees a good prompt.
Obviously, this login sequence doesn't look as clean as the former
Obviously, this login sequence does not look as clean as the former
``locked-speed'' method, but a user on a low-speed connection should
receive better interactive response from full-screen programs.
@ -390,17 +390,17 @@ the file and the list of capabilities.
<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
particular speed, you probably will not need to make any changes to
<tt>/etc/gettytab</tt>.
<sect3><heading>Matching-Speed Config</heading>
<p>
You'll need to setup an entry in <tt>/etc/gettytab</tt> to give
You will need to setup an entry in <tt>/etc/gettytab</tt> to give
<tt/getty/ information about the speeds you wish to use for your
modem. If you have a 2400 bps modem, you can probably use the
existing <tt/D2400/ entry. This entry already exists in the FreeBSD
1.1.5.1 <tt/gettytab/ file, so you don't need to add it unless it is
1.1.5.1 <tt/gettytab/ file, so you do not need to add it unless it is
missing under your version of FreeBSD:
<tscreen><verb>
@ -415,8 +415,8 @@ D2400|d2400|Fast-Dial-2400:\
:nx=D2400:tc=300-baud:
</verb></tscreen>
If you have a higher speed modem, you'll probably need to add an entry
in <tt>/etc/gettytab</tt>; here's an entry you could use for a 14.4
If you have a higher speed modem, you will probably need to add an entry
in <tt>/etc/gettytab</tt>; here is an entry you could use for a 14.4
Kbps modem with a top interface speed of 19.2 Kpbs:
<tscreen><verb>
@ -450,7 +450,7 @@ rate.
If you have a 28.8 Kbps modem and/or you want to take advantage of
compression on a 14.4 Kbps modem, you need to use a higher
communications rate than 19.2 Kbps. Here's an example of a
communications rate than 19.2 Kbps. Here is an example of a
<tt/gettytab/ entry starting a 57.6 Kpbs:
<tscreen><verb>
@ -470,7 +470,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
:nx=VH9600:tc=std.57600:
</verb></tscreen>
If you have a slow CPU or a heavily loaded system and you don't have
If you have a slow CPU or a heavily loaded system and you dobnot have
16550A-based serial ports, you may receive sio ``silo'' errors at 57.6
Kbps.
@ -482,7 +482,7 @@ Kbps.
(user <tt/root/ may only login on ttys marked <tt/secure/). See the
manual page for <tt/ttys(5)/ for more information.
You'll need to either modify existing lines in <tt>/etc/ttys</tt> or
You will need to either modify existing lines in <tt>/etc/ttys</tt> or
add new lines to make <tt/init/ run <tt/getty/ processes automatically
on your new dialup ports. The general format of the line will be the
same, whether you are using a locked-speed or matching-speed
@ -588,7 +588,7 @@ stty -f /dev/ttyd2 crtscts
stty -f /dev/ttyd3 crtscts
</verb></tscreen>
Since there isn't an initialization device special file on FreeBSD
Since there is no 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.
@ -596,7 +596,7 @@ hope the flags aren't cleared by a miscreant.
<p>
If you have a modem whose parameters may be permanently set in
non-volatile RAM, you'll need to use a terminal program (such as Telix
non-volatile RAM, you will need to use a terminal program (such as Telix
under PC-DOS or <tt/tip/ under FreeBSD) to set the parameters.
Connect to the modem using the same communications speed as the
initial speed <tt/getty/ will use and configure the modem's
@ -644,7 +644,7 @@ settings as an example:
<item> Switch 1: UP - DTR Normal
<item> Switch 2: Don't care (Verbal Result Codes/Numeric Result Codes)
<item> Switch 2: Do not care (Verbal Result Codes/Numeric Result Codes)
<item> Switch 3: UP - Suppress Result Codes
@ -656,20 +656,20 @@ settings as an example:
<item> Switch 7: UP - Load NVRAM Defaults
<item> Switch 8: Don't care (Smart Mode/Dumb Mode)
<item> Switch 8: Do not care (Smart Mode/Dumb Mode)
</itemize>
Result codes should be disabled/suppressed for dialup modems to avoid
problems that can occur if <tt/getty/ mistakenly gives a <tt/login:/
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
command or returns a result code. I have heard this sequence can result
in a extended, silly conversation between <tt/getty/ and the modem.
<sect2><heading>Locked-speed Config</heading>
<p>
For a locked-speed configuration, you'll need to configure the modem
For a locked-speed configuration, you will need to configure the modem
to maintain a constant modem-to-computer data rate independent of the
communications rate. On a USR Sportster 14,400 external modem, these
commands will lock the modem-to-computer data rate at the speed used
@ -683,7 +683,7 @@ AT&amp;B1&amp;W
<sect2><heading>Matching-speed Config</heading>
<p>
For a variable-speed configuration, you'll need to configure your
For a variable-speed configuration, you will need to configure your
modem to adjust its serial port data rate to match the incoming call
rate. On a USR Sportster 14,400 external modem, these commands will
lock the modem's error-corrected data rate to the speed used to issue
@ -741,13 +741,13 @@ If you see something different, like this:
^^
</verb></tscreen>
and the modem hasn't accepted a call yet, this means that <tt/getty/
and the modem has not accepted a call yet, this means that <tt/getty/
has completed its open on the communications port. This could
indicate a problem with the cabling or a mis-configured modem, because
<tt/getty/ should not be able to open the communications port until
<tt/CD/ (carrier detect) has been asserted by the modem.
If you don't see any <tt/getty/ processes waiting to open the desired
If you do not see any <tt/getty/ processes waiting to open the desired
<tt/ttyd?/ port, double-check your entries in <tt>/etc/ttys</tt> to
see if there are any mistakes there. Also, check the log file
<tt>/var/log/messages</tt> to see if there are any log messages from
@ -761,15 +761,15 @@ missing device special files.
<p>
Try dialing into the system; be sure to use 8 bits, no parity, 1 stop
bit on the remote system. If you don't get a prompt right away, or
bit on the remote system. If you do not get a prompt right away, or
get garbage, try pressing <tt>&lt;Enter&gt;</tt> about once per
second. If you still don't see a <tt/login:/ prompt after a while,
second. If you still do not see a <tt/login:/ prompt after a while,
try sending a <tt>BREAK</tt>. If you are using a high-speed modem to
do the dialing, try dialing again after locking the dialing modem's
interface speed (via <tt>AT&amp;B1</tt> on a USR Sportster, for
example).
If you still can't get a <tt/login:/ prompt, check
If you still cannot get a <tt/login:/ prompt, check
<tt>/etc/gettytab</tt> again and double-check that
<itemize>
@ -784,14 +784,14 @@ name
</itemize>
If you dial but the modem on the FreeBSD system won't answer, make
If you dial but the modem on the FreeBSD system will not answer, make
sure that the modem is configured to answer the phone when <tt/DTR/ is
asserted. If the modem seems to be configured correctly, verify that
the <tt/DTR/ line is asserted by checking the modem's indicator lights
(if it has any).
If you've gone over everything several times and it still doesn't work,
take a break and come back to it later. If it still doesn't work,
If you have gone over everything several times and it still does not work,
take a break and come back to it later. If it still does not work,
perhaps you can send an electronic mail message to the &a.questions
describing your modem and youer problem, and the good folks on the list will
try to help.

4
share/doc/handbook/diskless.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: diskless.sgml,v 1.2 1995/06/30 17:37:35 jfieber Exp $ -->
<!-- $Id: diskless.sgml,v 1.3 1996/01/31 14:26:03 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>Diskless operation<label id="diskless"></heading>
@ -117,7 +117,7 @@ hostname myclient.mydomain
<item> On HP-UX systems: The server should be
running HP-UX 9.04 or later for HP9000/800 series
machines. Prior versions don't allow the
machines. Prior versions do not allow the
creation of device files over NFS.
<item> When extracting <tt>/dev</tt> in

6
share/doc/handbook/dma.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: dma.sgml,v 1.2 1995/11/20 01:10:12 jfieber Exp $ -->
<!-- $Id: dma.sgml,v 1.3 1996/01/31 14:26:03 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
@ -156,7 +156,7 @@
If a peripheral wants to generate an interrupt when the
transfer of a buffer is complete, it can test for its
-DACK signal and the EOP signal both being asserted at
the same time. When that happens, it means the DMA won't
the same time. When that happens, it means the DMA will not
transfer any more information for that peripheral without
intervention by the CPU. The peripheral can then assert
one of the interrupt signals to get the processors'
@ -223,7 +223,7 @@
PC-compatible DMA cannot access locations above 16Meg.
To get around this restriction, operating systems will
reserve a buffer in an area below 16Meg that also doesn't
reserve a buffer in an area below 16Meg that also does not
span a physical 64K boundary. Then the DMA will be
programmed to read data to that buffer. Once the DMA has
moved the data into this buffer, the operating system

16
share/doc/handbook/eresources.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: eresources.sgml,v 1.21 1996/05/09 23:04:37 mpp Exp $ -->
<!-- $Id: eresources.sgml,v 1.22 1996/05/11 09:24:45 jkh Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt>
@ -23,7 +23,7 @@
<heading>Mailing lists<label id="eresources:mail"></heading>
<p>Though many of the FreeBSD development members read USENET, we cannot
always guarantee that we'll get to your questions in a timely fashion
always guarantee that we will get to your questions in a timely fashion
(or at all) if you post them only to one of the comp.unix.bsd.freebsd.*
groups. By addressing your questions to the appropriate mailing list
you will reach both us and a concentrated FreeBSD audience, invariably
@ -118,11 +118,7 @@ cvs-usrsbin /usr/src/usr.sbin System binaries
given list you simply mail to <em>listname</em><tt>@FreeBSD.ORG</tt>. It
will then be redistributed to mailing list members world-wide.
To subscribe to a list, send mail to:
<tscreen><verb>
majordomo@FreeBSD.ORG
</verb></tscreen>
And include the keyword
To subscribe to a list, send mail to &a.majordomo and include
<tscreen><verb>
subscribe <listname> [<optional address>]
</verb></tscreen>
@ -151,9 +147,9 @@ list of available commands, do this:
help
^D
</verb></tscreen>
Again, we'd like to request that you keep discussion in the technical mailing
lists on a technical track. If you're only interested in the "high points"
then it's suggested that you join freebsd-announce, which is intended only
Again, we would like to request that you keep discussion in the technical mailing
lists on a technical track. If you are only interested in the "high points"
then it is suggested that you join freebsd-announce, which is intended only
for infrequent traffic.
<sect1><heading>List charters</heading>

8
share/doc/handbook/esdi.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: esdi.sgml,v 1.5 1996/01/31 14:26:05 mpp Exp $ -->
<!-- $Id: esdi.sgml,v 1.6 1996/01/31 19:02:56 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
@ -40,7 +40,7 @@
Capacities of the drives are boosted by putting more sectors
on each track. Typical is 35 sectors per track, high capacity
drives I've seen were up to 54 sectors/track.
drives I have seen were up to 54 sectors/track.
Although ESDI has been largely obsoleted by IDE and SCSI interfaces,
the availability of free or cheap surplus drives makes them
@ -232,7 +232,7 @@
keep in mind that if you have multiple operating systems on the
same disk, all must use the same translation</em>
While on the subject of translations, I've seen one controller
While on the subject of translations, I have seen one controller
type (but there are probably more like this) offer the option
to logically split a drive in multiple partitions as a BIOS
option. I had select 1 drive == 1 partition because this
@ -352,7 +352,7 @@ disk wd3 at wdc1 drive 1
Before using NEFMT.EXE I tried to format the disk using the
ACB-2320 BIOS builtin formatter. This proved to be a show stopper,
because it didn't give me an option to disable spare sectoring.
because it did not give me an option to disable spare sectoring.
With spare sectoring enabled the FreeBSD installation
process broke down on the bad144 run.

6
share/doc/handbook/handbook.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: handbook.sgml,v 1.46 1996/05/14 20:31:51 rich Exp $ -->
<!-- $Id: handbook.sgml,v 1.47 1996/05/15 15:17:25 jfieber Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN" [
@ -11,6 +11,10 @@
<!ENTITY % authors SYSTEM "authors.sgml">
%authors;
<!-- Entity shorthand for mailing list email addresses -->
<!ENTITY % lists SYSTEM "lists.sgml">
%lists;
<!-- Entity definitions for all the parts -->
<!ENTITY % sections SYSTEM "sections.sgml">
%sections;

14
share/doc/handbook/history.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: history.sgml,v 1.12 1995/12/29 01:27:38 jkh Exp $ -->
<!-- $Id: history.sgml,v 1.13 1996/01/31 14:26:07 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>A brief history of FreeBSD<label id="history"></heading>
@ -9,11 +9,11 @@ The FreeBSD project had its genesis in the early part of 1993,
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
around this time, though they did not come fully into the project until
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
just was not 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.
@ -26,7 +26,7 @@ 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.
It didn't take us long to decide that the goal remained worthwhile
It did not 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
@ -79,7 +79,7 @@ easier to install FreeBSD 2.0.5 release in June of 1995.
<em>Where to from here?</em>
We just released FreeBSD 2.1.0 on November 19th, 1995 and, by all
accounts, people are pretty happy with it. We'll therefore continue
accounts, people are pretty happy with it. We will therefore continue
with the 2.1-STABLE branch of FreeBSD (which actually began with 2.0.5)
well into Q1 of 1996 with at least one additional release:
FreeBSD 2.1.1.
@ -90,7 +90,7 @@ where long term projects for everything from NFS v3 to PCCARD support
are currently taking place. Preliminary timelines suggest that development
in 2.2 will begin slowing down and early release engineering simulations
(2.2 SNAPshots) started in Q1 of 1996. Given a favorable prognosis for 2.2's
general health, a migration to 2.2 will then begin in early Q2 of '96 and
general health, a migration to 2.2 will then begin in early Q2 of 1996 and
a new 2.3 branch created for next-generation development. Around the
time that 2.2-RELEASE is produced (late Q2 1996), the 2.1.x lineage will
also be phased out.
@ -108,7 +108,7 @@ changes can propagate automatically to other users of FreeBSD. Our
centralized development model is designed for the convenience of the
<em>users</em> of FreeBSD, who are thereby provided with an easy way of
tracking one central code base, not to keep potential contributors out!
Individuals who've shown a consistent and significant dedication to the project
Individuals who hae shown a consistent and significant dedication to the project
are even often asked to join the FreeBSD core team to help in setting
the project's overall directions and goals, so truly no part of the project
is closed to additional members. All we ask of those wishing for closer

42
share/doc/handbook/hw.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: hw.sgml,v 1.19 1996/04/08 15:01:04 jfieber Exp $ -->
<!-- $Id: hw.sgml,v 1.20 1996/05/09 23:04:43 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
@ -42,7 +42,7 @@ Slippery when wet. Beware of dog.
<sect1><heading>Jordan's Picks</heading>
<p>I have had fairly good luck building workstation and server
configurations with the following components. I can't guarantee that
configurations with the following components. I cannot guarantee that
you will too, nor that any of the companies here will remain "best buys"
forever. I will try, when I can, to keep this list up-to-date but
cannot obviously guarantee that it will be at any given time.
@ -52,9 +52,9 @@ Slippery when wet. Beware of dog.
<htmlurl url="http://asustek.asus.com.tw/FTP/ASUS/Info/Spec/pi-p55tp4xe.txt"
name="P55TP4XE">
motherboard appears to be a good choice for mid-to-high range Pentium
server and workstation systems. If you're really looking for performance,
be also sure to get the <htmlurl url="http://asustek.asus.com.tw/Products/TB/mem-0002.html" name="pipelined burst cache module">. I feel that it's worth
the extra cost. If you're looking for a 486 class motherboard, you might
server and workstation systems. If you are really looking for performance,
be also sure to get the <htmlurl url="http://asustek.asus.com.tw/Products/TB/mem-0002.html" name="pipelined burst cache module">. I feel that it is worth
the extra cost. If you are looking for a 486 class motherboard, you might
also investigate ASUS's <htmlurl url="http://asustek.asus.com.tw/FTP/ASUS/Info/Spec/pvi-486sp3.txt" name="486SP3G"> offering.
NOTE: The Intel <htmlurl url="http://asustek.asus.com.tw/Products/TB/triton-intro.html" name="Triton"> chipset based motherboards do not offer memory
@ -63,8 +63,8 @@ Slippery when wet. Beware of dog.
therefore want to wait for Intel's newest generation of motherboards
based on the Orion chipset or investigate ASUS's SiS chipset based
motherboard, the <htmlurl url="http://asustek.asus.com.tw/FTP/ASUS/Info/Spec/pi-p55sp4.txt" name="P55SP4">. I have no personal experience with this
motherboard and have heard mixed reports - some say it's a fine MB, others
say that it's measurably slower than the Triton. The only undisputed
motherboard and have heard mixed reports - some say it is a fine MB, others
say that it is measurably slower than the Triton. The only undisputed
advantage it offers is being available <em>now</em>.
<sect2><heading>Disk Controllers</heading>
@ -75,7 +75,7 @@ Slippery when wet. Beware of dog.
1542CF for ISA, Buslogic Bt747c for EISA and Adaptec 2940 for PCI.
<sect2><heading>Disk drives</heading>
<p>In this particular game of Russian roulette, I'll make few specific
<p>In this particular game of Russian roulette, I will make few specific
recommendations except to say "SCSI over IDE whenever you can afford it."
Even in small desktop configurations, SCSI often makes more sense since it
allows you to easily migrate drives from server to desktop as falling drive
@ -84,17 +84,17 @@ Slippery when wet. Beware of dog.
food chain!
<p>I do not currently see SCSI WIDE drives as a necessary expense unless
you're putting together an NFS or NEWS server that will be doing a lot
you are putting together an NFS or NEWS server that will be doing a lot
of multiuser disk I/O.
<sect2><heading>CDROM drives</heading>
<p>My SCSI preferences extend to SCSI CDROM drives as well, and the
<htmlurl url="http://www.toshiba.com" name="Toshiba"> XM-3501B (now
released in a caddy-less model called the XM-5401B) drive has always
performed well for me. Generally speaking, most SCSI CDROM drives I've
seen have been of pretty solid construction (probably because they don't
performed well for me. Generally speaking, most SCSI CDROM drives I have
seen have been of pretty solid construction (probably because they do not
occupy the lower end of the market, due to their higher price) and you
probably won't go wrong with an HP or NEC SCSI CDROM drive either.
probably will not go wrong with an HP or NEC SCSI CDROM drive either.
<sect2><heading>Tape drives</heading>
<p>I've had pretty good luck with both
@ -104,7 +104,7 @@ Slippery when wet. Beware of dog.
<htmlurl url="http://www-dmo.external.hp.com:80/tape/_cpb0001.htm"
name="4mm (DAT)"> drives from <htmlurl url="http://www.hp.com" name="HP">.
<p>For backup purposes, I'd have to give the higher recommendation to the
<p>For backup purposes, I would have to give the higher recommendation to the
Exabyte due to the more robust nature (and higher storage capacity) of
8mm tape.
@ -114,7 +114,7 @@ Slippery when wet. Beware of dog.
can heartily recommend the <htmlurl url="http://www.matrox.com/"
name="Matrox"> <htmlurl url="http://www.matrox.com/mgaweb/brochure.htm"
name="Millenium"> card. If free X servers are more to your
liking, you certainly can't go wrong with one of <htmlurl url="http://www.nine.com/" name="Number 9's"> cards - their S3 Vision 868 and 968 based cards
liking, you certainly cannot go wrong with one of <htmlurl url="http://www.nine.com/" name="Number 9's"> cards - their S3 Vision 868 and 968 based cards
(the 9FX series) are pretty fast cards as well, and are supported by
<htmlurl url="http://www.xfree86.org" name="XFree86">'s S3 server.
@ -123,7 +123,7 @@ Slippery when wet. Beware of dog.
name="Sony Multiscan 17SE monitors">, as have I with
the Viewsonic offering in the same (trinitron) tube. For larger than
17", all I can recommend at the time of this writing is to not spend
any less than U.S. &dollar;2,500 for a 21" monitor if that's what you really
any less than U.S. &dollar;2,500 for a 21" monitor if that is what you really
need. There are good monitors available in the >=20" range and there
are also cheap monitors in the >=20" range. Unfortunately, none are
both cheap and good!
@ -137,7 +137,7 @@ Slippery when wet. Beware of dog.
will generally work as well.
<sect2><heading>Serial</heading>
<p>If you're looking for high-speed serial networking solutions, then
<p>If you are looking for high-speed serial networking solutions, then
<htmlurl url="http://www.dgii.com/" name="Digi International">
makes the <htmlurl url="http://www.dgii.com/prodprofiles/profiles-prices/digiprofiles/digispecs/sync570.html" name="SYNC/570"> series, with drivers now in
FreeBSD-current. <htmlurl url="http://www.etinc.com"
@ -148,9 +148,9 @@ Slippery when wet. Beware of dog.
said that FreeBSD's support for <htmlurl url="http://www.cyclades.com/"
name="Cyclades">'s products is probably the tightest, primarily as a result
of that company's committment to making sure that we are adequately supplied
with evaluation boards and technical specs. I've heard that the Cyclom-16Ye
offers the best price/performance, though I've not checked the prices lately.
Other multiport cards I've heard good things about are the BOCA and AST
with evaluation boards and technical specs. I have heard that the Cyclom-16Ye
offers the best price/performance, though I have not checked the prices lately.
Other multiport cards I have heard good things about are the BOCA and AST
cards, and <htmlurl url="http://www.stallion.com/" name="Stallion
Technologies"> apparently offers an unofficial driver for their
cards at <htmlurl url="ftp://ftp.stallion.com/drivers/unsupported/freebsd/stalbsd-0.0.4.tar.gz" name="this"> location.
@ -159,12 +159,12 @@ Slippery when wet. Beware of dog.
<p>I currently use the <htmlurl url="http://www.gravis.com/" name="Gravis">
Ultrasound MAX due to its high sound quality and full-duplex audio
capabilities (dual DMA channels). Support for Windows NT and OS/2 is
fairly anemic, however, so I'm not sure that I can recommend it as an
fairly anemic, however, so I am not sure that I can recommend it as an
all-around card for a machine that will be running both FreeBSD and NT
or OS/2. In such a scenario, I might recommend the <htmlurl url="http://www.creaf.com/" name="Creative Labs"> AWE32 instead.
<sect2><heading>Video</heading>
<p>For video capture, there's really only once choice - the
<p>For video capture, there is really only once choice - the
<htmlurl url="http://www.matrox.com/" name="Matrox">
<htmlurl url="http://www.matrox.com/imgweb/meteor.htm" name="Meteor">
card. FreeBSD also supports the older video spigot card from

24
share/doc/handbook/install.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: install.sgml,v 1.27 1996/05/16 20:01:26 jkh Exp $ -->
<!-- $Id: install.sgml,v 1.28 1996/05/16 20:20:57 jkh Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
@ -351,10 +351,10 @@ Boot:
There is not a lot of preparatory work that needs to be done to
successfully install from one of Walnut Creek's FreeBSD CDROMs (other
CDROM distributions may work as well, though we cannot say for certain
as we have no hand or say in how they're created). You can either
as we have no hand or say in how they are created). You can either
boot into the CD installation directly from DOS using Walnut Creek's
supplied ``install.bat'' batch file or you can make a boot floppy with
the ``makeflp.bat'' command. [NOTE: If you're running
the ``makeflp.bat'' command. [NOTE: If you are running
FreeBSD 2.1-RELEASE and have an IDE CDROM, use the
inst&lowbar;ide.bat or atapiflp.bat batch files instead].
@ -375,8 +375,8 @@ Boot:
from the hard disk, you can mount the cdrom at any time by
typing: <tt>mount /cdrom</tt>
Before removing the CD again, also note that it's necessary to first
type: <tt>umount /cdrom</tt>. Don't just remove it from the drive!
Before removing the CD again, also note that it is necessary to first
type: <tt>umount /cdrom</tt>. Do not just remove it from the drive!
<quote><bf>Special note:</bf> Before invoking the
installation, be sure that the CDROM is in the drive
@ -413,29 +413,29 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent
The first floppy that you will need in addition to the boot.flp
image is ``floppies/root.flp'', which is somewhat special in that
it's not a DOS filesystem floppy at all, but rather a floppy "image"
it is not a DOS filesystem floppy at all, but rather a floppy "image"
(it's actually a gzip'd cpio file). You can create this floppy in
the same way that you created the boot floppy <ref id="install"
name="the beginning of this guide">. Once this floppy is
made, you can go on to make the distribution set floppies
using ordinary DOS or UFS (if you're preparing the floppies on
using ordinary DOS or UFS (if you are preparing the floppies on
another FreeBSD machine) formatted diskettes.
You will need, at minimum, as many 1.44MB or 1.2MB floppies as
it takes to hold all files in the bin (binary distribution)
directory. If you're preparing these floppies under DOS, then
directory. If you are preparing these floppies under DOS, then
THESE floppies *must* be formatted using the MS-DOS FORMAT
command. If you're using Windows, use the Windows File
command. If you are using Windows, use the Windows File
Manager format command.
Do <em>not</em> trust Factory Preformatted floppies! Format
them again yourself, just to make sure. Many problems
reported by our users in the past have resulted from the use
of improperly formatted media, which is why I'm taking such
of improperly formatted media, which is why I am taking such
special care to mention it here!
If you're creating the floppies from another FreeBSD machine,
a format is still not a bad idea though you don't need to put
If you are creating the floppies from another FreeBSD machine,
a format is still not a bad idea though you do nott need to put
a DOS filesystem on each floppy. You can use the `disklabel'
and `newfs' commands to put a UFS filesystem on them instead,
as the following sequence of commands (for a 3.5" 1.44MB floppy

6
share/doc/handbook/kerberos.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: kerberos.sgml,v 1.5 1995/09/27 00:46:21 jmz Exp $ -->
<!-- $Id: kerberos.sgml,v 1.6 1996/01/03 13:13:16 gclarkii Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>Kerberos<label id="kerberos"></heading>
@ -30,7 +30,7 @@
<heading>Creating the initial database</heading>
<p>This is done on the Kerberos server only. First make sure that your
don't have any old Kerberos databases around. You should change to the
do not have any old Kerberos databases around. You should change to the
directory <tt>/etc/kerberosIV</tt> and check that only the following
files are present:
@ -98,7 +98,7 @@ ARC.NASA.GOV trident.arc.nasa.gov
realm. The rest of the lines show how to default systems of a
particular subdomain to a named realm.
Now we're ready to create the database. This only needs to run on
Now we are ready to create the database. This only needs to run on
the Kerberos server (or Key Distribution Centre). Issue the
<tt>kdb_init</tt> command to do this:

48
share/doc/handbook/kernelconfig.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: kernelconfig.sgml,v 1.10 1996/05/09 23:04:46 mpp Exp $ -->
<!-- $Id: kernelconfig.sgml,v 1.11 1996/05/15 15:17:26 jfieber Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!-- <!DOCTYPE linuxdoc PUBLIC '-//FreeBSD//DTD linuxdoc//EN'> -->
<chapt><heading>Configuring the FreeBSD Kernel<label id="kernelconfig"></heading>
@ -77,7 +77,7 @@
</verb></tscreen>
Traditionally, this name is in all capital letters and,
if you are maintaining multiple FreeBSD machines with
different hardware, it's a good idea to name it after
different hardware, it is a good idea to name it after
your machine's hostname. We will call it MYKERNEL for
the purpose of this example.
@ -91,11 +91,11 @@
here, but is covered well in many books in the <ref
id="bibliography" name="bibliography">. Feel free to change the
comment lines at the top to reflect your configuration or the
changes you've made to differentiate it from GENERIC.
changes you have made to differentiate it from GENERIC.
If you've build a kernel under SunOS or some other BSD
If you have build a kernel under SunOS or some other BSD
operating system, much of this file will be very familiar
to you. If you're coming from some other operating
to you. If you are coming from some other operating
system such as DOS, on the other hand, the GENERIC
configuration file might seem overwhelming to you, so
follow the descriptions in the <ref
@ -106,10 +106,10 @@
older version of FreeBSD, you will probably have to get a new
version of <tt>config(8)</tt> from the same place you got the new
kernel sources. It is located in <tt>/usr/src/usr.sbin</tt>, so
you'll need to download those sources as well. Re-build and install
you will need to download those sources as well. Re-build and install
it before running the next commands.</quote>
When you're finished, type the following to compile and
When you are finished, type the following to compile and
install your kernel:
<tscreen><verb>
# /usr/sbin/config MYKERNEL
@ -128,7 +128,7 @@
to recover in case your new kernel <ref
id="kernelconfig:noboot" name="does not boot">.
<quote><em/Note:/ If you've added any new devices (such
<quote><em/Note:/ If you have added any new devices (such
as sound cards) you may have to add some <ref
id="kernelconfig:nodes" name="device nodes"> to your
<tt>/dev</tt> directory before you can use them.</quote>
@ -160,7 +160,7 @@
be dependant upon an option gets this option out of an
<tt>opt_<em>foo</em>.h</tt> declaration file created in the
compile directory by <tt>config</tt>. The list of valid options
for <tt>config</tt> lives in two files: options that don't
for <tt>config</tt> lives in two files: options that do nott
depend on the architecture are listed in
<tt>/sys/conf/options</tt>, architecture-dependant ones
in <tt>/sys/<em>arch</em>/conf/options.<em>arch</em></tt>,
@ -210,7 +210,7 @@
this from GENERIC to whatever you named your
kernel, in this example, MYKERNEL. The value you
put in <tt>ident</tt> will print when you boot up
the kernel, so it's useful to give a kernel a
the kernel, so it is useful to give a kernel a
different name if you want to keep it separate from
your usual kernel (if you want to build an
experimental kernel, for example). Note that, as
@ -219,7 +219,7 @@
contains any numbers.
Since this name is passed to the C compiler as a
<tt>-D</tt> switch, don't use names like <tt>
<tt>-D</tt> switch, do not use names like <tt>
DEBUG</tt>, or something that could be confused
with another machine or CPU name, like <tt>vax</tt>.
@ -231,7 +231,7 @@
you expect to have on your machine. However, under
normal circumstances, you will want to set
<tt>maxusers</tt> to at least four, especially if
you're using X Windows or compiling software. The
you are using X Windows or compiling software. The
reason is that the most important table set by
<tt>maxusers</tt> is the maximum number of
processes, which is set to <bf><tt>20 + 16 *
@ -336,7 +336,7 @@
Windows, which many graphics-intensive programs
(such as the movie player XAnim, and Linux DOOM)
will automatically take advantage of for extra
speed. If you use X Windows, you'll definitely
speed. If you use X Windows, you will definitely
want to include this.
<tag>options SYSVSEM</tag>
@ -505,7 +505,7 @@
<tt>wdc1</tt> is a secondary IDE controller where
you might have a third or fourth hard drive, or an
IDE CD-ROM. Comment out the lines which do not
apply (if you have a SCSI hard drive, you'll
apply (if you have a SCSI hard drive, you will
probably want to comment out all six lines, for
example).
@ -625,11 +625,11 @@
<p>This causes the
kernel to pause 15 seconds before probing each SCSI
device in your system. If you only have IDE hard
drives, you can ignore this, otherwise you'll
drives, you can ignore this, otherwise you will
probably want to lower this number, perhaps to 5
seconds, to speed up booting. Of course if you do
this, and FreeBSD has trouble recognizing your SCSI
devices, you'll have to raise it back up.
devices, you will have to raise it back up.
<tag>controller scbus0</tag>
@ -797,7 +797,7 @@
<p>The next lines enable support for various Ethernet
cards. If you do not have a network card, you can
comment out all of these lines. Otherwise, you'll
comment out all of these lines. Otherwise, you will
want to leave in support for your particular
Ethernet card(s):
@ -869,7 +869,7 @@
</descrip>
<quote><em/Note:/ With certain cards (notably the
NE2000) you'll have to change the port and/or IRQ
NE2000) you will have to change the port and/or IRQ
since there is no ``standard'' location for these
cards.</quote>
@ -946,7 +946,7 @@
<p>This is the first section containing lines that are
not in the GENERIC kernel. To include sound card
support, you'll have to copy the appropriate lines from
support, you will have to copy the appropriate lines from
the LINT kernel (which contains support for
<em>every</em> device) as follows:
@ -1054,7 +1054,7 @@
<tag>pseudo-device pty <em>number</em><label id="kernelconfig:ptys"></tag>
<p><tt>pty</tt> is a ``pseudo-terminal'' or simulated
login port. It's used by incoming <bf>telnet</bf>
login port. It is used by incoming <bf>telnet</bf>
and <bf>rlogin</bf> sessions, xterm, and some other
applications such as emacs. The <em>number</em>
indicates the number of <tt>pty</tt>s to create.
@ -1088,7 +1088,7 @@
<p>This section describes some miscellaneous hardware
devices supported by FreeBSD. Note that none of these
lines are included in the GENERIC kernel, you'll have
lines are included in the GENERIC kernel, you will have
to copy them from this handbook or the LINT kernel
(which contains support for <em>every</em> device):
@ -1106,7 +1106,7 @@
script that plays some simple songs, and
<tt>/usr/games/piano</tt> which lets you play songs
using the keyboard as a simple piano (this file
only exists if you've installed the <em>games</em>
only exists if you have installed the <em>games</em>
package). Also, the excellent text role-playing
game NetHack (in the ports collection) can be
configured to use this device to play songs when
@ -1174,7 +1174,7 @@ controller wcd0
<p>If the <tt>config</tt>
command fails when you give it your kernel
description, you've probably made a simple error
description, you have probably made a simple error
somewhere. Fortunately, <tt>config</tt> will print
the line number that it had trouble with, so you can
quickly skip to it with <tt>vi</tt>. For example, if
@ -1244,7 +1244,7 @@ config: line 17: syntax error
<tag>Kernel works, but <tt>ps</tt> does not work any more!</tag>
<p>If you've installed a different version
<p>If you have installed a different version
of the kernel from the one that the system utilities
have been built with, for example, an experimental
``2.2.0'' kernel on a 2.1.0-RELEASE system, many

36
share/doc/handbook/kerneldebug.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: kerneldebug.sgml,v 1.8 1996/01/31 19:02:59 mpp Exp $ -->
<!-- $Id: kerneldebug.sgml,v 1.9 1996/03/14 02:52:06 adam Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Kernel Debugging<label id="kerneldebug"></heading>
@ -70,10 +70,10 @@
and voila, you can debug the crash dump using the kernel sources
just like you can for any other program.
Here's a script log of a <tt>kgdb</tt> session illustrating the
Here is a script log of a <tt>kgdb</tt> session illustrating the
procedure. Long
lines have been folded to improve readability, and the lines are
numbered for reference. Despite this, it's a real-world error
numbered for reference. Despite this, it is a real-world error
trace taken during the development of the pcvt console driver.
<tscreen><verb>
1:Script started on Fri Dec 30 23:15:22 1994
@ -169,10 +169,10 @@
<tag/line 36:/ Force usage of a new stack frame; this is no longer
necessary now. The stack frames are supposed to point to
the right locations now, even in case of a trap.
(I don't have a new core dump handy &lt;g&gt;, my kernel
didn't panic for rather long.)
(I do not have a new core dump handy &lt;g&gt;, my kernel
did not panic for ia rather long time.)
From looking at the code in source line 403,
there's a high probability that either the pointer
there is a high probability that either the pointer
access for ``tp'' was messed up, or the array access was
out of bounds.
<tag/line 52:/ The pointer looks suspicious, but happens to be a valid
@ -188,23 +188,23 @@
<sect><heading>Post-mortem analysis of a dump</heading>
<p>What do you do if a kernel dumped core but you did not expect
it, and it's therefore not compiled using <tt>config -g</tt>?
Not everything is lost here. Don't panic!
it, and it is therefore not compiled using <tt>config -g</tt>?
Not everything is lost here. Do not panic!
Of course, you still need to enable crash dumps. See above
on the options you've got in order to do this.
on the options you have to specify in order to do this.
Go to your kernel compile directory, and edit the line
containing <tt>COPTFLAGS?=-O</tt>. Add the <tt>-g</tt> option
there (but <em>don't</em> change anything on the level of
there (but <em>do not</em> change anything on the level of
optimization). If you do already know roughly the probable
location of the failing piece of code (e.g., the <tt>pcvt</tt>
driver in the example above), remove all the object files for
this code. Rebuild the kernel. Due to the time stamp change on
the Makefile, there will be some other object files rebuild,
for example <tt>trap.o</tt>. With a bit of luck, the added
<tt>-g</tt> option won't change anything for the generated
code, so you'll finally get a new kernel with similar code to
<tt>-g</tt> option will not change anything for the generated
code, so you will finally get a new kernel with similar code to
the faulting one but some debugging symbols. You should at
least verify the old and new sizes with the <tt>size(1)</tt> command. If
there is a mismatch, you probably need to give up here.
@ -226,8 +226,8 @@
The most important ones being breakpointing and single-stepping
kernel code.
If you need to do low-level debugging on your kernel, there's
an on- line debugger available called DDB. It allows to
If you need to do low-level debugging on your kernel, there is
an on-line debugger available called DDB. It allows to
setting breakpoints, single-steping kernel functions, examining
and changing kernel variables, etc. However, it cannot not
access kernel source files, and only has access to the global
@ -255,7 +255,7 @@
The second scenario is a hot-key on the keyboard, usually
Ctrl-Alt-ESC. For syscons, this can be remapped, and some of
the distributed maps do this, so watch out.
There's an option
There is an option
available for serial consoles
that allows the use of a serial line BREAK on the console line to
enter DDB (``<tt>options BREAK_TO_DEBUGGER</tt>''
@ -314,7 +314,7 @@
<tscreen><verb>
n
</verb></tscreen>
<bf>Note:</bf> this is different from <tt>gdb</tt>'s `next' statement, it's like
<bf>Note:</bf> this is different from <tt>gdb</tt>'s `next' statement, it is like
<tt>gdb</tt>'s `finish'.
To examine data from memory, use (for example):
@ -405,9 +405,9 @@
<tscreen><verb>
help
</verb></tscreen>
However, it's highly recommended to have a printed copy of the
However, it is highly recommended to have a printed copy of the
<tt>ddb(4)</tt> manual page ready for a debugging session.
Remember that it's hard to read the on-line manual while
Remember that it is hard to read the on-line manual while
single-stepping the kernel.

44
share/doc/handbook/linuxemu.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: linuxemu.sgml,v 1.2 1996/05/15 15:17:28 jfieber Exp $ -->
<!-- $Id: linuxemu.sgml,v 1.3 1996/05/16 22:50:29 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Linux Emulation<label id="linuxemu"></heading>
@ -7,7 +7,7 @@
<sect><heading>How to install the Linux emulator</heading>
<p>Linux emulation in FreeBSD has reached a point where it's possible
<p>Linux emulation in FreeBSD has reached a point where it is possible
to run a large fraction of Linux binaries in both a.out and ELF
format. The linux emulation in the -STABLE branch is capable of
running Linux DOOM and Mathematica; the version present in
@ -126,7 +126,7 @@ linux
<p>In -current it is no longer necessary to specify options "LINUX"
or options "COMPAT_LINUX". Linux emulation is done with an LKM
(``Loadable Kernel Module'') so it can be installed on the fly without
having to reboot. You'll need the following things in your startup files,
having to reboot. You will need the following things in your startup files,
however:
<enum>
<item> In <tt>/etc/sysconfig</tt>, you need the following line:
@ -143,7 +143,7 @@ fi
</verb>
</enum>
<p>If you want to verify it's running, <tt>modstat</tt> will do that:
<p>If you want to verify it is running, <tt>modstat</tt> will do that:
<tscreen>
<verb>
% modstat
@ -168,9 +168,9 @@ and Installing a Custom Kernel">.
<sect2><heading>Installing using the linux_lib port</heading>
<p>Most linux applications use shared libraries, so you're still not
done untill you install the shared libraries. It's possible to do
this by hand, however, it's vastly simpler to just grab the
<p>Most linux applications use shared libraries, so you are still not
done untill you install the shared libraries. It is possible to do
this by hand, however, it is vastly simpler to just grab the
<tt>linux_lib</tt> port:
<tscreen>
<verb>
@ -186,12 +186,12 @@ linux binaries linked against the ZMAGIC libraries; QMAGIC libraries
Linuxulator heartburn. As of this writing (March 1996) ELF emulation
is still in the formulative stages but seems to work pretty well. Also,
expect some programs to complain about incorrect minor versions. In
general this doesn't seem to be a problem.
general this does not seem to be a problem.
<sect2><heading>Installing libraries manually</heading>
<p>If you don't have the ``ports'' distribution, you can install the
libraries by hand instead. You'll need the Linux shared libraries
libraries by hand instead. You will need the Linux shared libraries
that the program depends on and the runtime linker. Also, you will
need to create a "shadow root" directory, /compat/linux, for Linux
libraries on your FreeBSD system. Any shared libraries opened by
@ -250,7 +250,7 @@ these files on your FreeBSD system:
<p>Note that if you already have a Linux shared library with a
matching major revision number to the first column of the 'ldd'
output, you won't need to copy the file named in the last column to
output, you will not need to copy the file named in the last column to
your system, the one you already have should work. It is advisable to
copy the shared library anyway if it is a newer version, though. You
can remove the old one, as long as you make the symbolic link point to
@ -266,8 +266,8 @@ according to the output of ldd:
libc.so.4 (DLL Jump 4.5pl26) -> libc.so.4.6.29
</verb>
If it's only one or two versions out of date in the in the trailing
digit then don't worry about copying /lib/libc.so.4.6.29 too, because
If it is only one or two versions out of date in the in the trailing
digit then do not worry about copying /lib/libc.so.4.6.29 too, because
the program should work fine with the slightly older version.
However, if you like you can decide to replace the libc.so anyway, and
that should leave you with:
@ -278,7 +278,7 @@ that should leave you with:
<p>Please note that the symbolic link mechanism is <em>only</em>
needed for Linux binaries, the FreeBSD runtime linker takes care of
looking for matching major revision numbers itself, you don't need to
looking for matching major revision numbers itself, you do not need to
worry about that.
<sect2><heading>Configuring the ld.so -- for FreeBSD-current
@ -296,9 +296,9 @@ place on your FreeBSD system (to the /compat/linux tree):
/compat/linux/etc/ld.so.config
</verb>
<p>If you don't have access to a Linux system, you should get the
<p>If you do nott have access to a Linux system, you should get the
extra files you need from various ftp sites. Information on where to
look for the various files is appended below. For now, let's assume
look for the various files is appended below. For now, let us assume
you know where to get the files.
<p>
@ -312,9 +312,9 @@ version mismatches), and install them under /compat/linux
/lib/ld.so
</verb>
<p>ldconfig and ldd don't necessarily need to be under /compat/linux,
<p>ldconfig and ldd do not necessarily need to be under /compat/linux,
you can install them elsewhere in the system too. Just make sure they
don't conflict with their FreeBSD counterparts. A good idea would be
do not conflict with their FreeBSD counterparts. A good idea would be
to install them in /usr/local/bin as ldconfig-linux and ldd-linux.
<p>
Create the file /compat/linux/etc/ld.so.conf, containing the
@ -339,7 +339,7 @@ in order for the emulator to find them.
% /compat/linux/sbin/ldconfig
</verb>
<p>Ldconfig is statically linked, so it doesn't need any shared
<p>Ldconfig is statically linked, so it does not need any shared
libraries to run. It creates the file /compat/linux/etc/ld.so.cache
which contains the names of all the shared libraries. It should rerun
to recreate this file whenever you install additional shared
@ -347,7 +347,7 @@ libraries.
On FreeBSD-stable do not install /compat/linux/etc/ld.so.cache or run
ldconfig becuase in FreeBSD-stable the syscalls are implemented
differently and ldconfig isn't needed or used.
differently and ldconfig is not needed or used.
<p>You should now be set up for Linux binaries which only need a
shared libc. You can test this by running the Linux ldd on
@ -394,7 +394,7 @@ multi on
</tscreen>
where the order here specifies that /etc/hosts is searched first and
DNS is searched second. When /compat/linux/etc/host.conf isn't
DNS is searched second. When /compat/linux/etc/host.conf is not
installed linux applications find FreeBSD's /etc/host.conf and
complain about the incompatible FreeBSD syntax. You should remove
`bind,' if you have not configured a name-server using the
@ -441,9 +441,9 @@ ftp.demon.co.uk:/pub/linux/distributions
src.doc.ic.ac.uk:/packages/linux/distributions
</verb>
<p>For simplicity, let's concentrate on Slackware here. This
<p>For simplicity, let us concentrate on Slackware here. This
distribution consists of a number of subdirectories, containing
separate packages. Normally, they're controlled by an install
separate packages. Normally, they are controlled by an install
program, but you can retrieve files "by hand" too. First of all, you
will need to look in the "contents" subdir of the distribution. You
will find a lot of small text files here describing the contents of the

57
share/doc/handbook/lists.sgml Normal file
View File

@ -0,0 +1,57 @@
<!-- $Id: authors.sgml,v 1.20 1996/05/09 23:04:30 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
Names and email address of contributing authors and CVS committers
and some of the common FreeBSD mailing lists. Use these
entities when referencing people or mailing lists. Please
note the use of single
and double quotes.
-->
<!ENTITY a.announce "FreeBSD announcments mailing list
<tt><htmlurl url='mailto:freebsd-announce@FreeBSD.ORG'
name='&lt;freebsd-announce@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.doc "FreeBSD documentation project mailing list
<tt><htmlurl url='mailto:freebsd-doc@FreeBSD.ORG'
name='&lt;freebsd-doc@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.bugs "FreeBSD problem reports mailing list
<tt><htmlurl url='mailto:freebsd-doc@FreeBSD.ORG'
name='&lt;freebsd-doc@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.current "FreeBSD-current mailing list
<tt><htmlurl url='mailto:freebsd-current@FreeBSD.ORG'
name='&lt;freebsd-current@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.emulation "FreeBSD-emulation mailing list
<tt><htmlurl url='mailto:freebsd-emulation@FreeBSD.ORG'
name='&lt;freebsd-emulation@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.fs "FreeBSD filesystem project mailing list
<tt><htmlurl url='mailto:freebsd-fs@FreeBSD.ORG'
name='&lt;freebsd-fs@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.hackers "FreeBSD technical discussions mailing list
<tt><htmlurl url='mailto:freebsd-hackers@FreeBSD.ORG'
name='&lt;freebsd-hackers@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.ports "FreeBSD ports mailing list
<tt><htmlurl url='mailto:freebsd-ports@FreeBSD.ORG'
name='&lt;freebsd-ports@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.questions "FreeBSD general questions mailing list
<tt><htmlurl url='mailto:freebsd-questions@FreeBSD.ORG'
name='&lt;freebsd-questions@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.scsi "FreeBSD SCSI subsystem mailing list
<tt><htmlurl url='mailto:freebsd-questions@FreeBSD.ORG'
name='&lt;freebsd-questions@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.stable "FreeBSD-stable mailing list
<tt><htmlurl url='mailto:freebsd-questions@FreeBSD.ORG'
name='&lt;freebsd-questions@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.majordomo "<tt><htmlurl url='mailto:majordomo@FreeBSD.ORG'
name='&lt;majordomo@FreeBSD.ORG&gt;'></tt>">

4
share/doc/handbook/memoryuse.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: memoryuse.sgml,v 1.5 1995/12/19 10:21:07 gclarkii Exp $ -->
<!-- $Id: memoryuse.sgml,v 1.6 1996/01/31 19:02:59 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>PC memory utilization<label id="memoryuse"></heading>
@ -16,7 +16,7 @@ for the <tt>%cs</tt> selector, done by an <tt>ljmp</tt>.)
It then loads the first 15 sectors at <tt>0x10000</tt> (segment BOOTSEG in the
biosboot Makefile), and sets up the stack to work below <tt>0x1fff0</tt>.
After this, it jumps to the entry of boot2 within that code. I.e., it
jumps over itself and the (dummy) partition table, and it's going to
jumps over itself and the (dummy) partition table, and it is going to
adjust the %cs selector---we are still in 16-bit mode there.
boot2 asks for the boot file, and examines the <tt>a.out</tt> header. It masks

4
share/doc/handbook/nfs.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: nfs.sgml,v 1.4 1995/12/04 17:58:42 jfieber Exp $ -->
<!-- $Id: nfs.sgml,v 1.5 1996/01/22 17:44:30 roberto Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>NFS<label id="nfs"></heading>
@ -34,7 +34,7 @@ It should be noted that there is a different problem,
sometimes mistaken for this one,
when the NFS servers and clients are on different networks.
If that is the case, make CERTAIN that your routers are routing the
necessary UDP information, or you won't get anywhere, no matter
necessary UDP information, or you will not get anywhere, no matter
what else you are doing.
In the following examples, "fastws" is the host (interface) name of a

4
share/doc/handbook/nutshell.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: nutshell.sgml,v 1.7 1995/12/19 09:22:23 gclarkii Exp $ -->
<!-- $Id: nutshell.sgml,v 1.8 1996/01/31 14:26:12 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>FreeBSD in a nutshell<label id="nutshell"></heading>
@ -77,7 +77,7 @@
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
be done with a commercial UNIX product then it is 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

120
share/doc/handbook/porting.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: porting.sgml,v 1.18 1996/04/10 06:32:42 asami Exp $ -->
<!-- $Id: porting.sgml,v 1.19 1996/05/09 23:04:48 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect1><heading>Porting an existing piece of free software<label id="porting"></heading>
@ -8,11 +8,11 @@
<p>The porting of freely available software, while perhaps not as
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
of FreeBSD's growth and of great usefulness to those who would not
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
of what is 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.
@ -37,7 +37,7 @@ the ports collection.
once the file has been loaded.
<p>You may come across code that needs modifications or
conditional compilation based upon what version of UNIX it's
conditional compilation based upon what version of UNIX it is
running under. If you need to make such changes to the code
for conditional compilation, make sure you make the changes as
general as possible so that we can back-port code to FreeBSD
@ -89,13 +89,13 @@ the ports collection.
Berkeleyisms, not FreeBSD changes.
<item>In FreeBSD 2.x, <tt>__FreeBSD__</tt> is defined to be
<tt>2</tt>. In earlier versions, it's <tt>1</tt>.
<tt>2</tt>. In earlier versions, it is <tt>1</tt>.
<item>If you need to tell the difference between a FreeBSD 1.x
system and a FreeBSD 2.x system, usually the right answer is
to use the <tt>BSD</tt> macros described above. If there
actually is a FreeBSD specific change (such as special
shared library options when using `<tt>ld</tt>') then it's
shared library options when using `<tt>ld</tt>') then it is
OK to use <tt>__FreeBSD__</tt> and `<tt>#if __FreeBSD__ &gt;
1</tt>' to detect a FreeBSD 2.x system.
@ -126,14 +126,14 @@ The pattern is the year followed by the month.
<p>In the dozens of ports that have been done, there have
only been one or two cases where <tt>__FreeBSD__</tt>
should have been used. Just because an earlier port
screwed up and used it in the wrong place doesn't mean
screwed up and used it in the wrong place does not mean
you should do so too.
<sect2>
<heading>Quick Porting</heading>
<p>This section tells you how to do a quick port. In many
cases, it is not enough, but we'll see.
cases, it is not enough, but we will see.
<p>First, get the original tarball and put it into
<tt>&dollar;{DISTDIR}</tt>, which defaults to
@ -142,7 +142,7 @@ The pattern is the year followed by the month.
<p>Note: The following assumes that the software compiled
out-of-the-box, i.e., there was absolutely no change required
for the port to work on your FreeBSD box. If you needed to
change something, you'll have to refer to the next section
change something, you will have to refer to the next section
too.
<sect3>
@ -156,7 +156,7 @@ The pattern is the year followed by the month.
# Date created: 5 December 1994
# Whom: asami
#
# $Id: porting.sgml,v 1.18 1996/04/10 06:32:42 asami Exp $
# $Id: porting.sgml,v 1.19 1996/05/09 23:04:48 mpp Exp $
#
DISTNAME= oneko-1.1b
@ -170,7 +170,7 @@ The pattern is the year followed by the month.
.include <bsd.port.mk>
</verb></tscreen>
<p>See if you can figure it out. Don't worry about the contents
<p>See if you can figure it out. Do not worry about the contents
of the <tt>&dollar;Id&dollar;</tt> line, it will be filled in
automatically by CVS when the port is imported to our main
ports tree.
@ -201,7 +201,7 @@ A cat chasing a mouse all over the screen
sufficient. Note: This is <em>not</em> a manual nor an
in-depth description on how to use or compile the port.
In particular, please do not just copy the <tt>README</tt>
file here, unless, of course, it's a concise description
file here, unless, of course, it is a concise description
of the port.
<p>It is recommended that you sign the name at the end of
@ -257,7 +257,7 @@ lib/X11/oneko/mouse.xpm
<sect3>
<heading>Submitting the port</heading>
<p>Now that you're happy with your port, the only thing
<p>Now that you are happy with your port, the only thing
remaining is to put it in the main FreeBSD ports tree and
make everybody else happy about it too. To accomplish this,
pack the necessary files (everything described in this
@ -276,8 +276,8 @@ ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/
<sect2>
<heading>Slow Porting</heading>
<p>Ok, so it wasn't that simple, and the port required some
modifications to get it to work. In this section, we'll
<p>Ok, so it was not that simple, and the port required some
modifications to get it to work. In this section, we will
explain, step by step, how to modify it to get it to work with
the ports paradigm.
@ -289,7 +289,7 @@ ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/
and you may find that having <tt>bsd.port.mk</tt> in another
window while you read this really helps to understand it.
<p>But don't worry if you don't really understand what
<p>But do not worry if you do not really understand what
<tt>bsd.port.mk</tt> is doing, not many people
do... <tt>:&gt;</tt>
@ -364,7 +364,7 @@ ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/
targets `<tt>do-&lt;something&gt;</tt>'. For example, the
commands to extract a port are in the target
`<tt>do-extract</tt>'. If you are not happy with the
default target, and you can't fix it by redefining the
default target, and you cannot fix it by redefining the
`<tt>do-&lt;something&gt;</tt>' target in your Makefile.
<p>Note that the `main' targets (e.g., <tt>extract</tt>,
@ -375,7 +375,7 @@ ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/
<tt>do-extract</tt>, but never ever touch <tt>extract</tt>!
<p>Now that you understand what goes on when the user types
`<tt>make</tt>', let's go through the recommended steps to
`<tt>make</tt>', let us go through the recommended steps to
create the perfect port.
<sect3>
@ -386,7 +386,7 @@ ftp://ftp.FreeBSD.ORG/pub/FreeBSD/incoming/
and copy it into <tt>&dollar;{DISTDIR}</tt>. Always use
<em>mainstream</em> sources when and where you can.
<p>If you can't find a ftp site that is well-connected to the
<p>If you cannot find a ftp site that is well-connected to the
net, or can only find sites that have irritatingly
non-standard formats, we can `house' it ourselves by putting
it on
@ -398,7 +398,7 @@ ftp://freefall.FreeBSD.ORG/pub/FreeBSD/LOCAL_PORTS/
<p>If your port requires some additional `patches' that are
available on the Internet, fetch them too and put them in
<tt>&dollar;{DISTDIR}</tt>. Don't worry if they come from
<tt>&dollar;{DISTDIR}</tt>. Do not worry if they come from
site other than where you got the the main source tarball,
we have a way to handle these situations (see the
description of <tt>&dollar;{PATCHFILES}</tt> below).
@ -429,7 +429,7 @@ ftp://freefall.FreeBSD.ORG/pub/FreeBSD/LOCAL_PORTS/
<p>In the preparation of the port, files that have been added
or changed can be picked up with a recursive diff for later
feeding to patch. This is the easiest kind of change to
make as it doesn't involve any mucking around with
make as it does not involve any mucking around with
configuration files. Each set of patches you wish to apply
should be collected into a file named
`<tt>patch-&lt;xx&gt;</tt>' where <tt>&lt;xx&gt;</tt>
@ -499,7 +499,7 @@ ftp://freefall.FreeBSD.ORG/pub/FreeBSD/LOCAL_PORTS/
distribution file list (<tt>&dollar;{DISTFILES}</tt>) to be
named
<tt>&dollar;{DISTNAME}&dollar;{EXTRACT_SUFX}</tt>
by default which, if it's a normal tarball, is going to be
by default which, if it is a normal tarball, is going to be
something like:
<tscreen><verb>
foozolix-1.0.tar.gz
@ -544,11 +544,11 @@ work/foozolix-1.0/
record the directory containing the tarball in
<tt>&dollar;{MASTER_SITES}</tt>. This will provide a backup
site, as well as a direct pointer to the original source
location. Don't forget the trailing slash (<tt>/</tt>)!
location. Do not forget the trailing slash (<tt>/</tt>)!
<p>The make macros will try to use this specification for
grabbing the distribution file with <tt>&dollar;{NCFTP}</tt>
if they can't find it already on the system.
if they cannot find it already on the system.
<p>It is recommended that you put multiple sites on this list,
preferably from different continents. This will safeguard
@ -571,7 +571,7 @@ work/foozolix-1.0/
patch has an extra `<tt>foozolix-1.0/</tt>' in front of the
filenames, then set `<tt>PATCH_DIST_STRIP=-p1</tt>'.
<p>Don't worry if the patches are compressed, they will be
<p>Do not worry if the patches are compressed, they will be
decompressed automatically if the filenames end with
`<tt>.gz</tt>' or `<tt>.Z</tt>'.
@ -590,13 +590,13 @@ work/foozolix-1.0/
depends on. It is a list of `<tt>lib:dir</tt>' pairs
where <tt>lib</tt> is the name of the shared library, and
<tt>dir</tt> is the directory in which to find it in case
it's not available. For example,
it is not available. For example,
<tscreen><verb>
LIB_DEPENDS= tcl\\.7\\.:${PORTSDIR}/lang/tcl
</verb></tscreen>
will check for a shared tcl library with major version 7,
and descend into the <tt>lang/tcl</tt> subdirectory of
your ports tree to build and install it if it's not found.
your ports tree to build and install it if it is not found.
Note that the <tt>lib</tt> part is just an argument given
to `<tt>ldconfig -r | grep</tt>', so periods should be
@ -607,13 +607,13 @@ LIB_DEPENDS= tcl\\.7\\.:${PORTSDIR}/lang/tcl
during run-time. It is a list of `<tt>exec:dir</tt>'
pairs where <tt>exec</tt> is the name of the executable,
and <tt>dir</tt> is the directory in which to find it in
case it's not available. For example,
case it is not available. For example,
<tscreen><verb>
RUN_DEPENDS= wish:${PORTSDIR}/x11/tk
</verb></tscreen>
will check for an executable called `<tt>wish</tt>', and
descend into the <tt>x11/tk</tt> subdirectory of your
ports tree to build and install it if it's not found.
ports tree to build and install it if it is not found.
The dependency is checked from within the <tt>install</tt>
target. Also, the name of the dependency is put in to the
@ -629,7 +629,7 @@ BUILD_DEPENDS= unzip:${PORTSDIR}/archivers/unzip
</verb></tscreen>
will check for an executable called `<tt>unzip</tt>', and
descend into the <tt>archivers/unzip</tt> subdirectory of
your ports tree to build and install it if it's not found.
your ports tree to build and install it if it is not found.
Note that `build' here means everything from extracting to
compilation. The dependency is checked from within the
@ -644,13 +644,13 @@ FETCH_DEPENDS= ncftp2:${PORTSDIR}/net/ncftp2
</verb></tscreen>
will check for an executable called `<tt>ncftp2</tt>', and
descend into the <tt>net/ncftp2</tt> subdirectory of
your ports tree to build and install it if it's not found.
your ports tree to build and install it if it is not found.
The dependency is checked from within the <tt>fetch</tt>
target.
<sect4>
<heading>DEPENDS</heading>
<p>If there is a dependency that doesn't fall into either of
<p>If there is a dependency that does not fall into either of
the above four categories, or your port requires to have
the source of the other port extracted (i.e., having them
installed is not enough), then use this variable. This is
@ -681,7 +681,7 @@ FETCH_DEPENDS= ncftp2:${PORTSDIR}/net/ncftp2
<sect3>
<heading>NO_INSTALL_MANPAGES</heading>
<p>If the port uses imake but doesn't understand the
<p>If the port uses imake but does not understand the
`<tt>install.man</tt>' target,
`<tt>NO_INSTALL_MANPAGES=yes</tt>' should be set. In
addition, the author of the original port should be shot.
@ -696,18 +696,18 @@ FETCH_DEPENDS= ncftp2:${PORTSDIR}/net/ncftp2
<p>Note that it is your responsibility as a porter to read the
licensing terms of the software and make sure that the FreeBSD
project won't held accountable of violating them by
project will not be held accountable of violating them by
redistributing the source or compiled binaries either via ftp
or CD-ROM. If in doubt, please contact the &a.ports;.
<p>We usually get around this problem by setting
<tt>&dollar;{NO_PACKAGE}</tt> in the Makefile, and not putting
the distfile up for ftp. However, for most cases, you should
at least be able to make a port, so don't let the license
at least be able to make a port, so do not let the license
scare you away!
<p>Note: The GNU General Public License (GPL), both version 1
and 2, shouldn't be a problem for ports.
and 2, should not be a problem for ports.
<p>Note: If you are a committer, make sure you update the
<tt>ports/LEGAL</tt> file too.
@ -719,15 +719,15 @@ FETCH_DEPENDS= ncftp2:${PORTSDIR}/net/ncftp2
<sect2>
<heading>Do's and Dont's</heading>
<p>Here's a list of common do's and dont's that you encounter
<p>Here is a list of common do's and dont's that you encounter
during the porting process.
<sect3>
<heading>WRKDIR</heading>
<p>Don't leave anything valuable lying around in the
<p>Do not leave anything valuable lying around in the
`<tt>work</tt>' subdirectory, `<tt>make clean</tt>' will
<em>nuke</em> it completely! If you need auxiliary files
that aren't scripts or patches, put them in the subdirectory
that are not scripts or patches, put them in the subdirectory
`<tt>files</tt>' and use the <tt>post-extract</tt> target to
copy them to the `<tt>work</tt>' subdirectory.
@ -745,7 +745,7 @@ FETCH_DEPENDS= ncftp2:${PORTSDIR}/net/ncftp2
<tt>post-install</tt> rule to do it yourself. Make sure
that you check the variable <tt>NOMANCOMPRESS</tt> that the
user can set in <tt>/etc/make.conf</tt> to disable man page
compression. Here's an example:
compression. Here is an example:
<tscreen><verb>
post-install:
strip ${PREFIX}/bin/xdl
@ -756,7 +756,7 @@ FETCH_DEPENDS= ncftp2:${PORTSDIR}/net/ncftp2
<p>Use the <tt>file</tt> command on the installed executable
to check whether the binary is stripped or not. If it
doesn't say `not stripped', it is stripped.
does not say `not stripped', it is stripped.
<sect3>
<heading>Install additional documentation</heading>
@ -784,14 +784,14 @@ FETCH_DEPENDS= ncftp2:${PORTSDIR}/net/ncftp2
.endif
</verb></tscreen>
<p>Don't forget to add them to <tt>pkg/PLIST</tt> too! (Don't
<p>Do not forget to add them to <tt>pkg/PLIST</tt> too! (Do not
worry about <tt>NOPORTDOCS</tt> here; there is currently no
way for the packages to read variables from
<tt>/etc/make.conf</tt>.)
<sect3>
<heading>DIST_SUBDIR</heading>
<p>Don't let your port clutter <tt>/usr/ports/distfiles</tt>. If
<p>Do not let your port clutter <tt>/usr/ports/distfiles</tt>. If
your port requires a lot of files (including patchfiles) to be
fetched, or contains a file that has a name that might conflict
with other ports (e.g., `Makefile'), set
@ -813,12 +813,12 @@ FETCH_DEPENDS= ncftp2:${PORTSDIR}/net/ncftp2
<sect3>
<heading>Custom utilities</heading>
<p>Don't rely on custom utilities in your local configure
<p>Do not rely on custom utilities in your local configure
script or anything -- they may not be there on the user's
system! If you really need something else to be installed
before you can work, detect this from your configure script,
print a helpful message and exit with a non-zero status! At
least you'll have given the user some idea of what's needed.
least you will have given the user some idea of what is needed.
If the custom utility or package is actually part of the
ports tree, this should be dealt by the dependency mechanism
of ports.
@ -841,7 +841,7 @@ FETCH_DEPENDS= ncftp2:${PORTSDIR}/net/ncftp2
<sect3>
<heading>RCS strings</heading>
<p>Don't put RCS strings in patches. CVS will mangle them
<p>Do not put RCS strings in patches. CVS will mangle them
when we put the files into the ports tree, and when we check
them out again, they will come out different and the patch
will fail. RCS strings are surrounded by dollar
@ -874,7 +874,7 @@ FETCH_DEPENDS= ncftp2:${PORTSDIR}/net/ncftp2
able to cater to the needs of other sites. For X ports that use
imake, this is automatic; otherwise, this can often be done by
simply replacing the occurrences of `<tt>/usr/local</tt>' (or
`<tt>/usr/X11R6</tt>' for X ports that don't use imake) in the
`<tt>/usr/X11R6</tt>' for X ports that do not use imake) in the
various scripts/Makefiles in the port to read
`<tt>&dollar;{PREFIX}</tt>', as this variable is automatically
passed down to every stage of the build and install processes.
@ -882,7 +882,7 @@ FETCH_DEPENDS= ncftp2:${PORTSDIR}/net/ncftp2
<p>The variable <tt>&dollar;{PREFIX}</tt> can be reassigned in your
Makefile or in the user's environment. However, it is strongly
discouraged for individual ports to set this variable explicitly
in the Makefiles. (If your port is an X port but doesn't use
in the Makefiles. (If your port is an X port but does not use
imake, set <tt>USE_X11=yes</tt>; this is quite different from
setting <tt>PREFIX=/usr/X11R6</tt>.)
@ -933,14 +933,14 @@ lib/libtcl.so.7.3
</verb></tscreen>
<p>Note: the `-m' option is new since 2.0.5 and
2.1.0-950726-SNAP, so don't be alarmed if it doesn't work on
2.1.0-950726-SNAP, so do not be alarmed if it does not work on
your machine.
<p>Never, ever, <em>ever</em> add a line that says
`<tt>ldconfig</tt>' without any arguments to your Makefile
or pkg/PLIST. This will reset the shared library cache to
the contents of <tt>/usr/lib</tt> only, and will royally
screw up the user's machine ("Help, xinit doesn't run
screw up the user's machine ("Help, xinit does not run
anymore after I install this port!"). Anybody who does this
will be shot and cut into 65,536 pieces by a rusty knife and
have his liver chopped out by a bunch of crows and will
@ -952,7 +952,7 @@ lib/libtcl.so.7.3
<p>Do look at existing examples and the <tt>bsd.port.mk</tt>
file before asking us questions! <tt>;)</tt>
<p>Do ask us questions if you have any trouble! Don't just
<p>Do ask us questions if you have any trouble! Do not just
beat your head against a wall! <tt>:)</tt>
<sect2>
@ -976,9 +976,9 @@ lib/libtcl.so.7.3
person who wrote this Makefile]
# Whom: Satoshi Asami <asami@FreeBSD.ORG>
#
# $Id: porting.sgml,v 1.18 1996/04/10 06:32:42 asami Exp $
[ ^^^^ don't worry about this...it will be automatically filled in by CVS when
it is committed to our repository]
# $Id: porting.sgml,v 1.19 1996/05/09 23:04:48 mpp Exp $
[ ^^^^ do not worry about this...it will be automatically filled in by CVS
when it is committed to our repository]
#
[section to describe the package itself and main ftp site - DISTNAME
@ -987,7 +987,7 @@ lib/libtcl.so.7.3
DISTNAME= xdvi
PKGNAME= xdvi-pl18
CATEGORIES+= printing
[don't forget the trailing slash ("/")!]
[do not forget the trailing slash ("/")!]
MASTER_SITES= ftp://crl.dec.com/pub/X11/contrib/applications/
[set this if the source is not in the standard ".tar.gz" form]
EXTRACT_SUFX= .tar.Z
@ -999,7 +999,7 @@ lib/libtcl.so.7.3
[maintainer; *mandatory*! This is the person (preferably with commit
privileges) who a user can contact for questions and bug reports - this
person should be the porter or someone who can forward questions to the
original porter reasonably promptly. If you really don't want to have your
original porter reasonably promptly. If you really do not want to have your
address here, set it to "ports@FreeBSD.ORG".]
MAINTAINER= asami@FreeBSD.ORG
@ -1007,8 +1007,8 @@ lib/libtcl.so.7.3
RUN_DEPENDS= gs:${PORTSDIR}/print/ghostscript
LIB_DEPENDS= Xpm\\.4\\.:${PORTSDIR}/graphics/xpm
[this section is for other standard bsd.port.mk variables that don't belong to
any of the above]
[this section is for other standard bsd.port.mk variables that do not belong
to any of the above]
[If it extracts to a directory other than ${DISTNAME}...]
WRKSRC= ${WRKDIR}/xdvi-new
[If it asks questions during configure, build, install...]
@ -1094,12 +1094,12 @@ xvgr-2.10pl1 xvgr-2.10.1 `pl' allowed only when no maj/minor numbers
version.
<sect2>
<heading>That's It, Folks!</heading>
<heading>That is It, Folks!</heading>
<p>Boy, this sure was a long tutorial, wasn't it? Thanks for
following us to here, really.
<p>Well, now that you know how to do a port, let's go at it and
<p>Well, now that you know how to do a port, let us go at it and
convert everything in the world into ports! That is the
easiest way to start contributing to the FreeBSD Project!
<tt>:)</tt>

46
share/doc/handbook/ports.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: ports.sgml,v 1.8 1995/12/04 17:58:45 jfieber Exp $ -->
<!-- $Id: ports.sgml,v 1.9 1996/05/09 23:04:49 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>The Ports collection<label id="ports"></heading>
@ -41,8 +41,8 @@ up less than twenty megabytes.
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''. 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
wherever they are generally provided on the Internet. If you have a
CDROM distribution of FreeBSD then you already have 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"
@ -58,11 +58,11 @@ from <tt>/usr/ports</tt> to that directory. Then invoke the <tt>lndir(1)</tt> c
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.
building them in the link tree you have created.
Note that there are some ports for which we can't provide the original
Note that there are some ports for which we cannot 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"
you will 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>
@ -71,8 +71,8 @@ name="Compiling ports using an Internet connection">).
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 assumes you have a permanent network link or don't
mind heavy usage of your telephone. If you don't want heavy network
Of course, this assumes you have a permanent network link or do not
mind heavy usage of your telephone. If you do not 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
by hand. A good way to see what files a port is going to need is to
@ -86,15 +86,15 @@ 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 <tt>/pub/FreeBSD/distfiles</tt>. Note that the files in
that directory are not guaranteed 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 independent control and don't
volunteer project! We canno make any guarantees about the mirror
sites either - they are obviously under independent control and do not
even have to mirror the distfiles directory.
If you have a non-permanent link, you can fetch all the distfiles by
going to the top of the tree and typing ``make fetch''.
<sect1><heading>It doesn't work?!</heading>
<sect1><heading>It does not work?!</heading>
<p>Oh. You can do one of four (4) things :
<enum>
@ -105,17 +105,17 @@ going to the top of the tree and typing ``make fetch''.
<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
FreeBSD system as a whole, and especially the ports system, which
is mainly contributed by 3rd parties. (If you don't believe me, check
is mainly contributed by 3rd parties. (If you do not believe me, check
the catalogue, especially the line saying "We cannot offer tech-support
on this product")
The e-mail address is Ports@FreeBSD.org. Please include details of
The e-mail address is the &a.ports;. Please include details of
the port, where you got both the port source &amp; distfile(s) from, and
what the error was.
Note: At time of writing, lang/Sather doesn't seem to work on Pentium
Note: At time of writing, lang/Sather does not seem to work on Pentium
machines due to the Intel Curse (aka the Floating Point Division Bug).
Please don't tell us about this - gripe to Intel instead - it's their
Please do not tell us about this - gripe to Intel instead - it is their
bug!
<item> Forget it. This is the easiest for most - very few of the programs in
@ -132,12 +132,12 @@ going to the top of the tree and typing ``make fetch''.
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>
<sect1><heading>I have ported a program and I want to make a port out of it. What now?</heading>
<p> See the <ref id="porting:starting" name="guidelines"> that
contain details of the procedure and structure involved.
<sect1><heading>I've got a good port, what now?</heading>
<sect1><heading>I have got a good port, what now?</heading>
<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
@ -146,7 +146,7 @@ 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>I want to leave the compile going overnight, but some ports don't like this.</heading>
<sect1><heading>I want to leave the compile going overnight, but some ports do not like this.</heading>
<p> There is a way around this. Before starting the compilation, type:
<verb>
@ -176,8 +176,8 @@ minute. The most up-to-date copy can be found in:
<url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current/src/share/mk">
If you find that you still need to go in there and alter things,
by all means do so, and then send the diffs to ports@FreeBSD.org if
you'd like them to be a part of the default distribution. Please also
by all means do so, and then send the diffs to the &a.ports if
you would like them to be a part of the default distribution. Please also
remember that any changes must respect backwards-compatibility with
any and all older Makefiles, unless you want a real nightmare of
/usr/ports munging ahead of you! Large scale changes will generally
@ -187,7 +187,7 @@ alteration. Sorry!
<sect1><heading>This FAQ is weak. What can I do?</heading>
<p> Send changes to ports@FreeBSD.org. Changes are most welcome!
<p> Send changes to the &a.ports;. Changes are most welcome!
This FAQ is also very green and should be considered no more than
a `good start' for now. Authors? You can come out of hiding any
time now! :-)
@ -202,7 +202,7 @@ and type:
</verb>
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>
<sect1><heading>I have heard of a new checksum system. What is this for?</heading>
<p> For various reasons, when using FTP over the Internet to obtain the
source code, you may not always end up with the same copy of the code
@ -223,7 +223,7 @@ checksum routine. The same technique can be applied to a single port.
for that port. Not all ports currently have checksums, but this should be
cured soon.
Some older versions of the system don't recognize the ``checksum''
Some older versions of the system do not recognize the ``checksum''
target. In that case, try the command
<verb>
make check-md5

4
share/doc/handbook/ppp.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: ppp.sgml,v 1.5 1995/09/27 00:46:27 jmz Exp $ -->
<!-- $Id: ppp.sgml,v 1.6 1995/12/04 17:58:46 jfieber Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>Setting up kernel PPP<label id="ppp"></heading>
@ -246,7 +246,7 @@ exit
This <tt>/etc/ppp/kermit.dial</tt> script is used for dialing and authorizing
on remote host. You will need to customize it for your needs.
Put your login and password in this script , also you'll need
Put your login and password in this script , also you will need
to change input statement depending on responses from your modem
and remote host.
<verb>

590
share/doc/handbook/printing.sgml
View File

File diff suppressed because it is too large Load Diff

16
share/doc/handbook/relnotes.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: relnotes.sgml,v 1.9 1996/01/31 14:26:15 mpp Exp $ -->
<!-- $Id: relnotes.sgml,v 1.10 1996/02/02 05:27:27 wosch Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
@ -28,7 +28,7 @@
the Adaptec 2940 (WIDE and narrow) and many hundreds of
bug fixes.
We've also taken the comments and suggestions of many
We have also taken the comments and suggestions of many
of our users to heart and have attempted to provide
what we hope is a more sane and easily understood
installation process. Your feedback on this
@ -92,7 +92,7 @@
security may be all you require! We feel that our
default security model is more than a match for DES,
and without any messy export issues to deal with. If
you're outside (or even inside) the U.S., give it a
you are outside (or even inside) the U.S., give it a
try!
<![ IGNORE [
@ -119,7 +119,7 @@
Ethernet adapters, improved support for the Adaptec
2940 and hundreds of bug fixes.
We've also taken the comments and suggestions of many
We have also taken the comments and suggestions of many
of our users to heart and have attempted to provide
what we hope is a more sane and easily understood
installation process. Your feedback on this constantly
@ -523,7 +523,7 @@
<tag>UNIONFS and LFS</tag> The unionfs and LFS file
systems are known to be severely broken in FreeBSD
2.0.5. This is in part due to old bugs that we
haven't had time to resolve yet and the need to
have not had time to resolve yet and the need to
update these file systems to deal with the new VM
system. We hope to address these issues in a later
release of FreeBSD.
@ -556,7 +556,7 @@
The preferred method to submit bug reports from a machine
with Internet mail connectivity is to use the send-pr
command. Bug reports will be dutifully filed by our
faithful bug-filer program and you can be sure that we'll
faithful bug-filer program and you can be sure that we will
do our best to respond to all reported bugs as soon as
possible.
@ -580,8 +580,8 @@
subscribe to: <tscreen>announce@FreeBSD.org</tscreen>
All but the freebsd-bugs groups can be freely joined by
anyone wishing to do so. Send mail to
MajorDomo@FreeBSD.org and include the keyword `help' on a
anyone wishing to do so. Send mail to &a.majordomo
and include the keyword `help' on a
line by itself somewhere in the body of the message.
This will give you more information on joining the
various lists, accessing archives, etc. There are a

6
share/doc/handbook/routing.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: routing.sgml,v 1.1 1995/10/07 04:31:41 jfieber Exp $ -->
<!-- $Id: routing.sgml,v 1.2 1996/01/31 14:26:16 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!-- <!DOCTYPE linuxdoc PUBLIC '-//FreeBSD//DTD linuxdoc//EN'> -->
@ -68,7 +68,7 @@ host2.foobar.com link#1 UC 0 0
(<tt>10.20.30.255</tt> is the broadcast address for the subnet
<tt>10.20.30</tt>, and <tt>foobar.com</tt> is the domain name
associated with that subnet). The designation <tt>link&num;1</tt>
refers to the first ethernet card in the machine. You'll
refers to the first ethernet card in the machine. You will
notice no additional interface is specified for those.
Both of these groups (local network hosts and local
@ -150,7 +150,7 @@ host2.foobar.com link#1 UC 0 0
world, then the default route will be the gateway machine
at your Internet Service Provider's (ISP) site.
Let's look at an example of default routes. This is a
Let us look at an example of default routes. This is a
common configuration:
<tscreen><verb>
[Local2] <--ether--> [Local1] <--PPP--> [ISP-Serv] <--ether--> [T1-GW]

22
share/doc/handbook/scsi.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: scsi.sgml,v 1.12 1996/01/31 19:03:02 mpp Exp $ -->
<!-- $Id: scsi.sgml,v 1.13 1996/04/19 21:50:32 asami Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
@ -42,8 +42,8 @@
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
single-ended signals, carried on 50 wires. (If you don't know what
single-ended means, don't worry, that is what this document is all
single-ended signals, carried on 50 wires. (If you do not know what
single-ended means, do not worry, that is what this document is all
about.) Modern designs also use 16 bit wide buses, with
differential signals. This allows transfer speeds of
20Mbytes/second, on cables lengths of up to 25 meters. SCSI-2
@ -112,7 +112,7 @@
So, gold plated connectors, shielded cabling, sturdy connector
hoods with strain reliefs etc are the way to go. Second golden
rule: don't use cables longer than necessary. I once spent 3 days
rule: do no use cables longer than necessary. I once spent 3 days
hunting down a problem with a flaky machine only to discover that
shortening the SCSI bus by 1 meter solved the problem. And the
original bus length was well within the SCSI specification.
@ -201,7 +201,7 @@
difference between these two wires determines whether the
signal is asserted or de-asserted. To a certain extent the
voltage difference between ground and the signal wire pair is
not relevant (don't try 10 kVolts though..).
not relevant (do not try 10 kVolts though..).
It is beyond the scope of this document to explain why this
differential idea is so much better. Just accept that
@ -225,14 +225,14 @@
reflections or ringing. If you once made a long distance
telephone call on a bad line you probably know what reflections
are. With 20Mbytes/sec traveling over your SCSI bus, you
don't want signals echoing back.
do not want signals echoing back.
Terminators come in various incarnations, with more or less
sophisticated designs. Of course, there are internal and
external variants. Almost every SCSI device comes with a
number of sockets in which a number of resistor networks can
(must be!) installed. If you remove terminators from a device,
carefully store 'm. You will need them when you ever decide to
carefully store them. You will need them when you ever decide to
reconfigure your SCSI bus. There is enough variation in even
these simple tiny things to make finding the exact replacement
a frustrating business. There are also SCSI devices that have
@ -404,7 +404,7 @@
megabytes. The division by 2 is to get from disk blocks that are
normally 512 bytes in size to Kbytes.
Right.. All is well now?! No, it isn't. The system BIOS has
Right.. All is well now?! No, it is not. The system BIOS has
another quirk you might run into. The number of cylinders of a
bootable hard disk cannot be greater than 1024. Using the
translation above, this is a show-stopper for disks greater than
@ -437,7 +437,7 @@
aha0 targ 0 lun 0: <MICROP 1588-15MB1057404HSP4>
sd0: 636MB (1303250 total sec), 1632 cyl, 15 head, 53 sec, bytes/sec 512
</verb>
Newer kernels usually don't report this information.. e.g.
Newer kernels usually do not report this information.. e.g.
<verb>
(bt0:0:0): "SEAGATE ST41651 7574" type 0 fixed SCSI 2
sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors)
@ -721,11 +721,11 @@ options "TUNE_1542" #dynamic tune of bus DMA speed
<item>
If you can compile a kernel, make one with the SCSIDEBUG option,
and try accessing the device with debugging turned on for
that device. If your device doesn't even probe at startup,
that device. If your device does not even probe at startup,
you may have to define the address of the device that
is failing, and the desired debug level in
<tt>/sys/scsi/scsidebug.h</tt>.
If it probes but just doesn't work, you can use the
If it probes but just does not work, you can use the
<tt>scsi(8)</tt> command to dynamically set a debug level to
it in a running kernel (if SCSIDEBUG is defined).
This will give you COPIOUS debugging output with which to confuse

16
share/doc/handbook/skey.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: skey.sgml,v 1.3 1995/10/07 04:31:56 jfieber Exp $ -->
<!-- $Id: skey.sgml,v 1.4 1996/01/31 14:26:18 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
Copyright 1995 Massachusetts Institute of Technology
@ -43,12 +43,12 @@ of Bell Communications Research, Inc.
<!-- XXX - is there a better word to use than UNIX? -->
<p>There are three different sorts of passwords which we will talk about
in the discussion below. The first is your usual UNIX-style or Kerberos
password; we'll call this a ``UNIX password''. The second sort is the
password; we will call this a ``UNIX password''. The second sort is the
one-time password which is generated by the S/Key `<tt/key/' program and
accepted by the `<tt/keyinit/' program and the login prompt; we'll call
accepted by the `<tt/keyinit/' program and the login prompt; we will call
this a ``one-time password''. The final sort of password is the
secret password which you give to the `<tt/key/' program (and sometimes the
`<tt/keyinit/' program) which it uses to generate one-time passwords; we'll
`<tt/keyinit/' program) which it uses to generate one-time passwords; we will
call it a ``secret password'' or just unqualified ``password''.
<p>The secret password does not necessarily have anything to do with your
@ -73,7 +73,7 @@ one-way hash function is used, it is not possible to generate future
one-time passwords having overheard one which was successfully used;
the iteration count is decremented after each successful login to keep
the user and login program in sync. (When you get the iteration count
down to 1, it's time to reinitialize S/Key.)
down to 1, it is time to reinitialize S/Key.)
<p>There are four programs involved in the S/Key system which we will
discuss below. The `<tt/key/' program accepts an iteration count, a
@ -125,7 +125,7 @@ minimum seven words) which will be needed to generate login keys. The
line starting `ID' gives the parameters of your particular S/Key
instance: your login name, the iteration count, and seed. When
logging in with S/Key, the system will remember these parameters and
present them back to you so you don't have to remember them. The last
present them back to you so you do not have to remember them. The last
line gives the particular one-time password which corresponds to those
parameters and your secret password; if you were to re-login
immediately, this one-time password is the one you would use.
@ -136,7 +136,7 @@ immediately, this one-time password is the one you would use.
connection, you will need to already have a secure connection to some
place where you can run the `<tt/key/' program; this might be in the form
of a desk accessory on a Macintosh, or a shell prompt on a machine you
trust (we'll show the latter). You will also need to make up an
trust (we will show the latter). You will also need to make up an
iteration count (100 is probably a good value), and you may make up
your own seed or use a randomly-generated one. Over on the insecure
connection (to the machine you are initializing), use the `<tt/keyinit -s/'
@ -253,7 +253,7 @@ Enter secret password:
The `<tt/-n 25/' requests twenty-five keys in sequence; the `<tt/57/' indicates
the <em/ending/ iteration number; and the rest is as before. Note that
these are printed out in <em/reverse/ order of eventual use. If you're
these are printed out in <em/reverse/ order of eventual use. If you are
really paranoid, you might want to write the results down by hand;
otherwise you can cut-and-paste into `<tt/lpr/'. Note that each line shows
both the iteration count and the one-time password; you may still find

20
share/doc/handbook/slipc.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: slipc.sgml,v 1.4 1995/10/07 04:31:59 jfieber Exp $ -->
<!-- $Id: slipc.sgml,v 1.5 1995/12/04 17:58:51 jfieber Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>Setting up a SLIP client<label id="slipc"></heading>
@ -11,8 +11,8 @@ address changes each time you dial up), you probably need to do
something much fancier.
<!--
This is just "what I did, and it worked for me". I'm sharing this
just for your reference, I'm no expert in SLIP nor networking so your
This is just "what I did, and it worked for me". I am sharing this
just for your reference, I am no expert in SLIP nor networking so your
mileage may vary.
-->
@ -27,7 +27,7 @@ Make sure you have
pseudo-device sl 1
</verb>
in your kernel's config file. It is included in the GENERIC kernel,
so this won't be a problem unless you deleted it.
so this will not be a problem unless you deleted it.
<sect1><heading>Things you have to do only once</heading>
@ -43,7 +43,7 @@ so this won't be a problem unless you deleted it.
128.32.136.12 ns2.Berkeley.edu ns2
</verb>
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.).
back in Japan (it is called 2?0SX here in U.S.).
<item>Make sure you have "hosts" before "bind" in your <tt>/etc/host.conf</tt>.
Otherwise, funny things may happen.
@ -91,7 +91,7 @@ nameserver 128.32.136.12
actual domain names and addresses depend on your environment.
<item>Set the password for root and toor (and any other accounts that
doesn't have a password). Use passwd, don't edit the <tt>/etc/passwd</tt>
does not have a password). Use passwd, do not edit the <tt>/etc/passwd</tt>
or <tt>/etc/master.passwd</tt> files!
<item>Reboot your machine and make sure it comes up with the correct
@ -124,7 +124,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a
get connected.
<bf>Note</bf>: leaving your password in plain text anywhere in the
filesystem is generally a BAD idea. Do it at your own risk. I'm
filesystem is generally a BAD idea. Do it at your own risk. I am
just too lazy.
<item>Leave the kermit there (you can suspend it by "z") and as root,
@ -133,7 +133,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a
slattach -h -c -s 115200 /dev/modem
</verb>
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"
you are connected! If it does not work, you might want to try "-a"
instead of "-c" as an argument to slattach.
</enum>
@ -144,7 +144,7 @@ slattach -h -c -s 115200 /dev/modem
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
mark the interface down, but this does not seem to make any
difference for me. ("ifconfig sl0" reports the same thing.)
Some times, your modem might refuse to drop the carrier (mine
@ -153,7 +153,7 @@ slattach -h -c -s 115200 /dev/modem
<sect1><heading>Troubleshooting</heading>
<p>If it doesn't work, feel free to ask me. The things that people
<p>If it does not 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

30
share/doc/handbook/slips.sgml
View File

@ -46,9 +46,9 @@ Administration</em> published by O'Reilly &amp; Associates, Inc. (ISBN
Number 0-937175-82-X), or Douglas Comer's books on the TCP/IP
protocol.
It's further assumed that you have already setup your modem(s) and
It is further assumed that you have already setup your modem(s) and
configured the appropriate system files to allow logins through your
modems. If you haven't prepared your system for this yet, please see
modems. If you have not prepared your system for this yet, please see
the tutorial for configuring dialup services; if you have a World-Wide
Web browser available, browse the list of tutorials at
<tt>http://www.freebsd.org/</tt>; otherwise, check the place
@ -116,7 +116,7 @@ goes into <tt>/var/log/messages</tt> (see the manual pages for
<tt>/etc/syslog.conf</tt> to see to which files <tt>syslogd</tt> is
logging).
OK, enough of the examples -- let's dive into setting up the system.
OK, enough of the examples -- let us dive into setting up the system.
<sect1><heading>Kernel Configuration</heading>
<p>
@ -148,13 +148,13 @@ Internet RFC requirements for Internet hosts (see RFC's 1009
&lsqb;Requirements for Internet Hosts -- Communication Layers&rsqb;,
and perhaps 1127 &lsqb;A Perspective on the Host Requirements
RFCs&rsqb;), so if you want your FreeBSD SLIP Server to act as a
router, you'll have to add the line
router, you will have to add the line
<verb>
sysctl -w net.inet.ip.forwarding = 0
</verb>
to your rc.local file.
You'll notice that near the end of the default kernel configuration
You will notice that near the end of the default kernel configuration
file (<tt>/sys/i386/conf/GENERIC</tt>) is a line that reads:
<tscreen><verb>
@ -231,9 +231,9 @@ included code to make use of the flags).
Your choice of local and remote addresses for your SLIP links depends
on whether you are going to dedicate a TCP/IP subnet or if you are
going to use ``proxy ARP'' on your SLIP server (it's not ``true''
going to use ``proxy ARP'' on your SLIP server (it is 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
describe it). If you are not sure which method to select or how to
assign IP addresses, please refer to the TCP/IP books referenced in
the <ref id="slips:prereqs"> section and/or consult your IP network manager.
@ -249,7 +249,7 @@ subnet.
Otherwise, if you will use the ``proxy ARP'' method, you will need to
assign your SLIP client's IP addresses out of your SLIP server's
Ethernet subnet, and you'll also need to adjust your
Ethernet subnet, and you will also need to adjust your
<tt>/etc/sliphome/slip.login</tt> and
<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.
@ -337,7 +337,7 @@ will be unable to execute it.
<p>
<tt>/etc/sliphome/slip.logout</tt> isn't strictly needed (unless you
<tt>/etc/sliphome/slip.logout</tt> is not strictly needed (unless you
are implementing ``proxy ARP''), but if you decide to create it, this
is an example of a basic <tt>slip.logout</tt> script:
@ -357,7 +357,7 @@ is an example of a basic <tt>slip.logout</tt> script:
----- end /etc/sliphome/slip.logout -----
</verb></tscreen>
If you are using ``proxy ARP'', you'll want to have
If you are using ``proxy ARP'', you will want to have
<tt>/etc/sliphome/slip.logout</tt> remove the ARP entry for the SLIP
client:
@ -401,7 +401,7 @@ routers via appropriate routing protocols about your SLIP subnet.
<p>
Adding static routes to your nearest default routers can be
troublesome (or impossible, if you don't have authority to do so...).
troublesome (or impossible, if you do not have authority to do so...).
If you have a multiple-router network in your organization, some
routers, such as Cisco and Proteon, may not only need to be configured
with the static route to the SLIP subnet, but also need to be told
@ -423,7 +423,7 @@ FreeBSD ``out-of-the-box''. Complete information and documentation on
<tt>gated</tt> is available on the Web starting at
<tt>http://www.gated.cornell.edu/</tt>. Compile and install it, and
then write a <tt>/etc/gated.conf</tt> file to configure your gated;
here's a sample, similar to what the author used on a FreeBSD SLIP
here is a sample, similar to what the author used on a FreeBSD SLIP
server:
<tscreen><verb>
@ -472,17 +472,17 @@ import proto rip interface ed {
The above sample <tt>gated.conf</tt> file broadcasts routing
information regarding the SLIP subnet <tt>xxx.xxx.yy</tt> via RIP onto
the Ethernet; if you are using a different Ethernet driver than the
<tt/ed/ driver, you'll need to change the references to the <tt/ed/
<tt/ed/ driver, you will need to change the references to the <tt/ed/
interface appropriately. This sample file also sets up tracing to
<tt>/var/tmp/gated.output</tt> for debugging <tt>gated</tt>'s
activity; you can certainly turn off the tracing options if
<tt>gated</tt> works OK for you. You'll need to change the
<tt>gated</tt> works OK for you. You will need to change the
<tt>xxx.xxx.yy</tt>'s into the network address of your own SLIP subnet
(be sure to change the net mask in the <tt>proto direct</tt> clause as
well).
When you get <tt>gated</tt> built and installed and create a
configuration file for it, you'll need to run <tt>gated</tt> in place
configuration file for it, you will need to run <tt>gated</tt> in place
of <tt>routed</tt> on your FreeBSD system; change the
<tt>routed/gated</tt> startup parameters in <tt>/etc/netstart</tt> as
appropriate for your system. Please see the manual page for

13
share/doc/handbook/stable.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: current.sgml,v 1.8 1996/01/31 14:26:01 mpp Exp $ -->
<!-- $Id: stable.sgml,v 1.1 1996/02/11 00:16:17 jkh Exp $ -->
<!-- The FreeBSD Documentation Project -->
@ -10,7 +10,7 @@
THE FREEBSD STABLE POLICY
Last updated: $Date: 1996/01/31 14:26:01 $
Last updated: $Date: 1996/02/11 00:16:17 $
This document attempts to explain the rationale behind
FreeBSD-stable, what you should expect should you decide to run it,
@ -27,9 +27,9 @@ branch (see <ref id="current" name="FreeBSD-current">).
<sect><heading>Who needs FreeBSD-stable?</heading>
<p>If you're a commercial user or someone who puts maximum stability of
<p>If you are a commercial user or someone who puts maximum stability of
their FreeBSD system before all other concerns, you should consider tracking
<em>stable</em>. This is especially true if you've installed the most
<em>stable</em>. This is especially true if you have installed the most
recent release (<htmlurl url="ftp://ftp.freebsd.org/pub/FreeBSD/2.1.0-RELEASE"
name="2.1.0-RELEASE"> at the time of this writing) since the <em>stable</em>
branch is effectively a bug-fix stream relative to the previous release.
@ -53,8 +53,7 @@ next section).
the users a chance to respond if they have any issues to raise concerning
the proposed change.
To join this list, send mail to <htmlurl url="mailto:majordomo@FreeBSD.ORG"
name="majordomo@FreeBSD.ORG"> and say:
To join this list, send mail to &a.majordomo and say:
<verb>
subscribe freebsd-stable
</verb>
@ -73,7 +72,7 @@ next section).
<item> Use the CMU `sup' program (Software Update
Protocol), also described below.
This is the second most recommended method, since it allows
you to grab the entire collection once and then only what's
you to grab the entire collection once and then only what has
changed from then on. Many people run sup from cron
and keep their sources up-to-date automatically.

57
share/doc/handbook/submitters.sgml
View File

@ -1,17 +1,17 @@
<!-- $Id: submitters.sgml,v 1.25 1996/05/09 23:04:50 mpp Exp $ -->
<!-- $Id: submitters.sgml,v 1.26 1996/05/09 23:32:44 jkh Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Contributing to FreeBSD<label id="submitters"></heading>
<p><em>Contributed by &a.jkh;.</em>
<p>So you want to contribute something to FreeBSD? That's great!
<p>So you want to contribute something to FreeBSD? That is great!
We can always use the help, and FreeBSD is one of those systems
that <em>relies</em> on the contributions of its user base in order
to survive. Your contributions are not only appreciated, they're
to survive. Your contributions are not only appreciated, they are
vital to FreeBSD's continued growth!
<p>Contrary to what some people might also have you believe, you don't
<p>Contrary to what some people might also have you believe, you do not
need to be a hot-shot programmer or a close personal friend of the
FreeBSD core team in order to have your contributions accepted. The
FreeBSD Project's development is done by a large and growing number of
@ -24,28 +24,28 @@ system environment (and its installation) rather than just a kernel or
a few scattered utilities, our "TODO" list also spans a very wide
range of tasks, from documentation, beta testing and presentation to
highly specialized types of kernel development. No matter what your
skill level, there's almost certainly something you can do to help the
skill level, there is almost certainly something you can do to help the
project!
<p>Commercial entities engaged in FreeBSD-related enterprises are
also encouraged to contact us. Need a special extension to make your
product work? You'll find us receptive to your requests, given that
they aren't too outlandish. Working on a value-added product? Please
product work? You will find us receptive to your requests, given that
they are not too outlandish. Working on a value-added product? Please
let us know! We may be able to work cooperatively on some aspect of
it. The free software world is challenging a lot of existing
assumptions about how software is developed, sold, and maintained
throughout its life cycle, and we urge you to at least give it a
second look.
<sect><heading>What's needed</heading>
<sect><heading>What is needed</heading>
<p>The following list of tasks and sub-projects represents something
of an amalgam of the various core team TODO lists and user requests
we've collected over the last couple of months. Where possible, tasks
have been ranked by degree of urgency. If you're interested in
we have collected over the last couple of months. Where possible, tasks
have been ranked by degree of urgency. If you are interested in
working on one of the tasks you see here, send mail to the coordinator
listed by clicking on their names. If no coordinator has been
appointed, maybe you'd like to volunteer?
appointed, maybe you would like to volunteer?
<sect1><heading>High priority tasks</heading>
<p>The following tasks are considered to be urgent, usually because
@ -133,7 +133,7 @@ your hardware, etc.
<sect1><heading>Low priority tasks</heading>
<p>The following tasks are purely cosmetic or represent such an
investment of work that it's not likely that anyone will get them done
investment of work that it is not likely that anyone will get them done
anytime soon:
<p>The first 20 items are from Terry Lambert &lt;terry@lambert.org&gt
@ -198,7 +198,7 @@ as opportunity permits. SCO and Solaris are good candidates,
followed by UnixWare, etc.
<item>Processor emulation environments for execution of foreign binaries.
This is easier than it sounds if the system call interface doesn't
This is easier than it sounds if the system call interface does not
change much.
<item>Streams to allow the use of commercial streams drivers.
@ -220,7 +220,7 @@ PCMCIA).
<item>Reorganization of the source tree for multiple platform ports.
<item>A "make world" that "makes the world" (rename the current one
to "make regress" if that's all it is good for).
to "make regress" if that is all it is good for).
<item>A 4M (preferably smaller!) memory footprint.
@ -241,8 +241,7 @@ the following 6 categories:
in such things (and a tolerance for a <em>high</em>
volume of mail!) may
subscribe to the hackers mailing list by sending mail to
<tt><htmlurl url="mailto:majordomo@FreeBSD.ORG"
name="&lt;majordomo@FreeBSD.ORG&gt;"></tt>.
&a.majordomo;.
See <ref id="eresources:mail" name="mailing lists">
for more information about this and other mailing lists.
@ -251,7 +250,7 @@ the following 6 categories:
you for various fields to fill in. Simply go to the fields
surrounded by <tt>&lt;&gt;</tt>'s and fill in your own
information in place of
what's suggested there. You should receive confirmation of your
what is suggested there. You should receive confirmation of your
bug report and a tracking number. Keep this tracking number and use
it in any subsequent correspondence.
If you do not receive confirmation in a timely fashion (3 days to
@ -307,8 +306,8 @@ diff -c -r olddir newdir
likely get back in touch with you in 24 hours or less,
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)
If your changes do not express themselves well as diffs alone
(e.g. you have perhaps added, deleted or renamed files as well)
then you may be better off bundling any new files, diffs and
instructions for deleting/renaming others into a <tt>tar</tt>
file and running the <tt>uuencode(1)</tt> program on it before
@ -317,8 +316,8 @@ diff -c -r olddir newdir
information on bundling files this way.
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,
you are unsure of copyright issues governing its further distribution
or you are simply not ready to release it without a tighter review first,
then you should send it to <tt><htmlurl url="mailto:core@FreeBSD.ORG"
name="&lt;core@FreeBSD.ORG&gt;"></tt> rather than the &a.hackers
The core mailing list
@ -348,7 +347,7 @@ diff -c -r olddir newdir
who might eventually be inclined to invest something of their own
into FreeBSD.
<item>The GNU Public License, or ``GPL''. This license isn't quite
<item>The GNU Public License, or ``GPL''. This license is not 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,
@ -400,7 +399,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.25 1996/05/09 23:04:50 mpp Exp $
$Id: submitters.sgml,v 1.26 1996/05/09 23:32:44 jkh Exp $
</verb></tscreen>
For your convenience, a copy of this text can be found in
<tt>/usr/share/examples/etc/bsd-style-copyright</tt>.
@ -408,7 +407,7 @@ For your convenience, a copy of this text can be found in
&porting;
<sect1><heading>Money, Hardware or Internet access</heading>
<p>We're always very happy to accept donations to further the cause of
<p>We are always very happy to accept donations to further the cause of
the FreeBSD Project and, in a volunteer effort like ours, a little can go
a long way! Donations of hardware are also very important to expanding
our list of supported peripherals since we generally lack the funds to
@ -464,20 +463,20 @@ systems should be sent to the FreeBSD, Inc. address listed in the
We are currently trying to put together a testing lab of all components
that FreeBSD supports so that proper regression testing can be done with
each new release. We are still lacking many important pieces (network cards,
motherboards, etc) and if you'd like to make such a donation, please contact
motherboards, etc) and if you would like to make such a donation, please contact
&a.davidg for information on which items are still required.
<item>Hardware currently unsupported by FreeBSD for which you'd like to
<item>Hardware currently unsupported by FreeBSD for which you would like to
see such support added. Please contact the <htmlurl
url="mailto:core@FreeBSD.ORG" name="FreeBSD Core Team"> before sending
such items as we'll need to find a developer willing to take on the task
such items as we will need to find a developer willing to take on the task
before we can accept delivery of them.
</itemize>
<sect2><heading>Donating Internet access</heading>
<p>We can always use new mirror sites for FTP, WWW or sup.
If you'd like to be such a mirror, please contact
If you would like to be such a mirror, please contact
<htmlurl url="mailto:admin@FreeBSD.ORG" name="the FreeBSD project
administrators"> for more information.
@ -502,7 +501,7 @@ like to publically thank them here!
<item><htmlurl url="http://www.cdrom.com" name="Walnut Creek CDROM">
has donated almost more than we can say (see the
<ref id="history" name="history"> document for more details).
In particular, we'd like to thank them for the hardware used for
In particular, we would like to thank them for the hardware used for
<em>freefall.FreeBSD.ORG</em>, our primary development machine,
and for <em>thud.FreeBSD.ORG</em>, our testing and build box.
We are also indebted to them for funding various contributors over

12
share/doc/handbook/sup.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: sup.sgml,v 1.13 1996/02/11 00:16:18 jkh Exp $ -->
<!-- $Id: sup.sgml,v 1.14 1996/05/09 23:04:53 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
@ -28,9 +28,9 @@ track changes to the -stable release, refer to
<tt>/usr/share/examples/sup/stable-supfile</tt>
instead.
If you're inside the United States, you may also uncomment
If you are inside the United States, you may also uncomment
the `secure' and `eBones' collection lines to grab the DES code.
If you're outside the
If you are outside the
U.S., you should NOT sup this code from sup.FreeBSD.ORG as this will
violate U.S. export restrictions. Instead you should use the
<tt>secure-supfile</tt> found within the above directory. This will
@ -45,7 +45,7 @@ listed in the above example files is currently overloaded and any traffic
that can be transfered to a different host will help relieve some of
the strain.
Once this is setup, you're ready to go. To start sup type:
Once this is setup, you are ready to go. To start sup type:
<verb>
sup supfile
</verb>
@ -54,7 +54,7 @@ like so:
<verb>
sup -v supfile
</verb>
Thats all there is to it! Remember that if you're running current,
Thats all there is to it! Remember that if you are running current,
which is what you will have if you sup with the standard-supfile, please
join the &a.current mailing list. You should also be sure to read
<ref id="current" name="Staying current with FreeBSD">
@ -125,7 +125,7 @@ ports-x11: /usr/ports/x11 X11 software
<p>If you want to keep updated on the original source of the ports,
you can also add this to your supfile. But note that this collection
is <em>enormous</em>, and unless you are an ftp site mirroring the
entire FreeBSD tree (but can't use ``mirror'' for some reason), you
entire FreeBSD tree (but cannot use ``mirror'' for some reason), you
(and us) are much better off not using sup to collect these:
<verb>
ports-distfiles: /usr/ports/distfiles original tarballs

20
share/doc/handbook/troubleshooting.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: troubleshooting.sgml,v 1.2 1995/06/30 17:37:53 jfieber Exp $ -->
<!-- $Id: troubleshooting.sgml,v 1.3 1995/07/07 22:25:55 jfieber Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Troubleshooting<label id="troubleshooting"></heading>
@ -13,16 +13,16 @@
<p><descrip>
<tag>Problem:</tag> A device is conflicting with
another or doesn't match the kernel's compiled-in IRQ or
another or does not match the kernel's compiled-in IRQ or
address.
<tag>Cause:</tag> While most device drivers in
FreeBSD are now smart enough to match themselves to your
hardware settings dynamically, there are a few that still
require fairly rigid configuration parameters to be
compiled in (and matched by the hardware) before they'll
work. We're working hard to eliminate as many of these
last hold-outs as we can, but it's not always as easy as
compiled in (and matched by the hardware) before they will
work. We are working hard to eliminate as many of these
last hold-outs as we can, but it is not always as easy as
it looks.
<tag>Solution:</tag> There are several possible
@ -40,16 +40,16 @@
You can use this utility to reset the IRQ, memory
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
entirely if it is causing problems for other devices you would
much rather have work.
Another solution is, obviously, to remove the offending
hardware or simply strip the system down to the bare
essentials until the problem (hopefully) goes away. Once
you're up, you can do the same thing mentioned
you are up, you can do the same thing mentioned
above---compile a kernel more suited to your hardware, or
incrementally try to figure out what it was about your
original hardware configuration that didn't work.
original hardware configuration that did not work.
</descrip>
@ -62,8 +62,8 @@
Solution: You should re-enter the installation process,
invoke the (F)disk editor and chose the (W)rite option.
This won't hurt an existing installation and will make
This will not hurt an existing installation and will make
sure that the new boot blocks get written to the drive.
If you're installing for the first time, don't forget to
If you are installing for the first time, do not forget to
(W)rite out your new boot blocks! :-)

36
share/doc/handbook/userppp.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: userppp.sgml,v 1.5 1995/12/06 22:01:50 jfieber Exp $ -->
<!-- $Id: userppp.sgml,v 1.6 1996/01/31 14:26:20 mpp Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect>Setting up user PPP<label id="userppp">
@ -11,11 +11,11 @@
(and above).
I hope this document turns into a collaborative effort, largely
because I am not really much of an authority on PPP. I've got
because I am not really much of an authority on PPP. I have got
it working, and want to pass on details of what I did so that
other people can get it working. But I'm not 100% clear on some
other people can get it working. But I am not 100% clear on some
details, so I hope that by writing this and having others
flesh out some of the information I'm going to learn something
flesh out some of the information I am going to learn something
as well.
-->
@ -27,7 +27,7 @@
<quote>
This is a user process PPP software package. Normally, PPP is
implemented as a part of the kernel (e.g. as managed by pppd) and
it's thus somewhat hard to debug and/or modify its behavior. However,
it is thus somewhat hard to debug and/or modify its behavior. However,
in this implementation PPP is done as a user process with the help of
the tunnel device driver (tun).
</quote>
@ -50,7 +50,7 @@
<sect1><heading>Before you start</heading>
<p>This document assumes you're in roughly this position:
<p>This document assumes you are in roughly this position:
You have an account with an Internet Service Provider (ISP) which lets you
use PPP. Further, you have a modem (or other device) connected and
@ -77,7 +77,7 @@
your kernel. Check <ref id="kernelconfig" name="Kernel
Configuration"> for more information on how to acquire these.
In addition, I've assumed that because your connection to the Internet is
In addition, I have assumed that because your connection to the Internet is
not full time you are not running a name server (<tt>named(8)</tt>).
<sect1><heading>Building a ppp ready kernel</heading>
@ -92,7 +92,7 @@
pseudo-device tun 1
</verb></tscreen>
in it somewhere. The stock GENERIC kernel has this as standard, so if you
have not installed a custom kernel you don't have to change anything.
have not installed a custom kernel you do not have to change anything.
If your kernel configuration file does not have this line in it then you
should add the line, re-compile and then re-install the kernel. Boot from
this new kernel.
@ -159,7 +159,7 @@ bind
and then to consult the DNS if the name was not found in the
<tt>/etc/hosts</tt> file.
It's probably a good idea to make sure you are not running the ``named''
It is probably a good idea to make sure you are not running the ``named''
service. Check your <tt>/etc/sysconfig</tt> file for the line that refers
to ``namedflags'', and make sure the line reads
<tscreen><verb>
@ -170,7 +170,7 @@ namedflags="NO"
<p>This file should contain the IP addresses and names of machines on your
network. At a bare minimum it should contain entries for the machine
which will be running ppp. Assuming that you're machine is called
which will be running ppp. Assuming that your machine is called
foo.bar.com with the IP address 10.0.0.1, <tt>/etc/hosts</tt> should
contain:
<tscreen><verb>
@ -228,7 +228,7 @@ nameserver 158.152.1.65
10 set timeout 120
11 set ifaddr x.x.x.x y.y.y.y
</verb></tscreen>
Don't include the line numbers, they're just for this discussion.
Do not include the line numbers, they are just for this discussion.
<descrip>
<tag/Line 1:/ Identifies the default entry. Commands in this entry are
@ -239,7 +239,7 @@ nameserver 158.152.1.65
<tag/Line 3:/ Sets the speed you want to connect at.
<tag/* Lines 4 and 5:/ Don't know exactly what effect these lines have
<tag/* Lines 4 and 5:/ Do not know exactly what effect these lines have
<tag/Line 6:/ Dial string commands. user ppp uses the <tt>chat(8)</tt>
language. Check the manual page for information on the features
@ -247,10 +247,10 @@ nameserver 158.152.1.65
<tag/Line 7:/ Identifies an entry for a provider called ``provider''.
<tag/Line 8:/ Sets the phone number for this provider. Don't include any
<tag/Line 8:/ Sets the phone number for this provider. Do not include any
spaces in the phone number.
<tag/Line 9:/ Set's the login string sequence. In this example, the string is
<tag/Line 9:/ Sets the login string sequence. In this example, the string is
for a service who's login session looks like
<tscreen><verb>
J. Random Provider
@ -298,8 +298,8 @@ set ifaddr 0 0
<sect1><heading>Final system configuration</heading>
<p>You now have PPP configured, but there's a few more things to do before
it's ready to work. They all involve editing the <tt>/etc/sysconfig</tt>
<p>You now have PPP configured, but there are a few more things to do before
it is ready to work. They all involve editing the <tt>/etc/sysconfig</tt>
file.
Working from the top down in this file, make sure the ``hostname='' line
@ -330,7 +330,7 @@ ifconfig_tun0="inet foo.bar.com y.y.y.y netmask 0xffffffff"
<tscreen><verb>
routedflags=-s
</verb></tscreen>
It's probably worth your while ensuring that the ``sendmail_flags'' line
It is probably worth your while ensuring that the ``sendmail_flags'' line
does not include the ``-q'' option, otherwise sendmail will attempt to do
a network lookup every now and then, possibly causing your machine to dial
out. My sendmail line looks like
@ -343,7 +343,7 @@ sendmail_flags="-bd"
# /usr/sbin/sendmail -q
</verb></tscreen>
That should be about all you need to do to get PPP working with a static
IP address. All that's left is to reboot the machine. During startup the
IP address. All that is left is to reboot the machine. During startup the
tun0 device should be detected, and two lines like the following should be
printed,
<tscreen><verb>