Fix typos.
Reviewed by: /usr/local/bin/ispell
This commit is contained in:
Jean-Marc Zucconi
parent
e0ecc0226a
commit
d745bece54
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=11027
@ -1,10 +1,10 @@
|
||||
<!-- $Id: bibliography.sgml,v 1.2 1995/06/30 17:37:30 jfieber Exp $ -->
|
||||
<!-- $Id: bibliography.sgml,v 1.3 1995/06/30 18:41:08 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt>
|
||||
<heading>Bibliography<label id="bibliography"></heading>
|
||||
|
||||
<p>While the manual pages provide the definative reference
|
||||
<p>While the manual pages provide the definitive reference
|
||||
for individual pieces of the FreeBSD operating system,
|
||||
they are notorious for not illustrating how to put the
|
||||
pieces together to make the whole operating system run
|
||||
@ -119,12 +119,12 @@
|
||||
<p><itemize>
|
||||
|
||||
<item>Stanley, Tom. <em>ISA System
|
||||
Architechure</em>. 3rd ed. Reading, Mass. :
|
||||
Architecture</em>. 3rd ed. Reading, Mass. :
|
||||
Addison-Wesley, 1995.
|
||||
<newline>ISBN 0201409968</item>
|
||||
|
||||
<item>Stanley, Tom. <em>PCI System
|
||||
Architechure</em>. 3rd ed. Reading, Mass. :
|
||||
Architecture</em>. 3rd ed. Reading, Mass. :
|
||||
Addison-Wesley, 1995. <newline>ISBN
|
||||
0201409933</item>
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: contrib.sgml,v 1.18 1995/09/26 10:16:23 asami Exp $ -->
|
||||
<!-- $Id: contrib.sgml,v 1.19 1995/09/26 19:19:26 wollman Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>FreeBSD contributor list<label id="contrib"></heading>
|
||||
@ -19,7 +19,7 @@
|
||||
some occasionally rocky moments in relations between the
|
||||
two groups, we both want essentially the same thing: More
|
||||
BSD based operating systems on people's computers! We wish
|
||||
the NetBSD group every success in their endevors.
|
||||
the NetBSD group every success in their endeavors.
|
||||
|
||||
<sect><heading>Hardware contributors</heading>
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: current.sgml,v 1.3 1995/06/30 17:37:33 jfieber Exp $ -->
|
||||
<!-- $Id: current.sgml,v 1.4 1995/09/25 09:38:59 jkh Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@
|
||||
|
||||
THE FREEBSD CURRENT POLICY
|
||||
|
||||
Last updated: $Date: 1995/06/30 17:37:33 $
|
||||
Last updated: $Date: 1995/09/25 09:38:59 $
|
||||
|
||||
This document attempts to explain the rationale behind FreeBSD-current,
|
||||
what you should expect should you decide to run it, and states some
|
||||
@ -67,7 +67,7 @@ too much time to do this as a general task.
|
||||
<item> In any way ``officially supported'' by us.
|
||||
|
||||
We do our best to help people genuinely in one of the 3
|
||||
``legitimate'' FreeBSD-current catagories, but we simply <em>do not
|
||||
``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
|
||||
@ -104,14 +104,14 @@ too much time to do this as a general task.
|
||||
subscribe cvs-all
|
||||
</verb>
|
||||
In the body of your message. Optionally, you can also say `help'
|
||||
and MajorDomo will send you full help on how to subscribe and
|
||||
and Majordomo will send you full help on how to subscribe and
|
||||
unsubscribe to the various other mailing lists we support.
|
||||
|
||||
<item> Grab the sources from ftp.FreeBSD.ORG. You can do this in
|
||||
three ways:
|
||||
|
||||
<enum>
|
||||
<item> Using the CTM facility desribed below. Unless you
|
||||
<item> Using the CTM facility described below. Unless you
|
||||
have a good TCP/IP connection at a flat rate, this is
|
||||
the way to do it.
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: eresources.sgml,v 1.9 1995/07/27 16:15:32 jfieber Exp $ -->
|
||||
<!-- $Id: eresources.sgml,v 1.10 1995/09/01 04:54:11 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt>
|
||||
@ -280,7 +280,7 @@ fixes, etc).
|
||||
|
||||
<tag/FREEBSD-USER-GROUPS/ <em>User Group Coordination List</em><newline>
|
||||
This is the mailing list for the coordinators from each of the
|
||||
local area Users Groups to dicuss matters with each other and a
|
||||
local area Users Groups to discuss matters with each other and a
|
||||
designated individual from the Core Team. This mail list should
|
||||
be limited to meeting synopsis and coordination of projects that span
|
||||
User Groups.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: handbook.sgml,v 1.28 1995/09/25 04:53:31 jfieber Exp $ -->
|
||||
<!-- $Id: handbook.sgml,v 1.29 1995/09/25 18:23:03 wollman Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN" [
|
||||
@ -31,7 +31,7 @@ installation and day to day use of <bf>FreeBSD Release
|
||||
2.0.5</bf>.
|
||||
|
||||
This manual is a <bf>work in progress</bf> and is the
|
||||
work of many individials. Many sections do not yet exist
|
||||
work of many individuals. Many sections do not yet exist
|
||||
and some of those that do exist need to be updated. If
|
||||
you are interested in helping with this project, send
|
||||
email to &a.jfieber; or to the FreeBSD Documentation
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: history.sgml,v 1.5 1995/08/26 12:07:06 jkh Exp $ -->
|
||||
<!-- $Id: history.sgml,v 1.6 1995/09/14 21:57:08 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>A brief history of FreeBSD<label id="history"></heading>
|
||||
@ -36,7 +36,7 @@ FreeBSD's distribution channels to those many unfortunates without
|
||||
easy access to the Internet. Walnut Creek CDROM not only supported
|
||||
the idea of distributing FreeBSD on CD but went so far as to provide
|
||||
the project with a machine to work on and a fast Internet connection.
|
||||
Without Walnut Creek CDROM's almost unprecidented degree of faith in
|
||||
Without Walnut Creek CDROM's almost unprecedented degree of faith in
|
||||
what was, at the time, a completely unknown project, it is in fact
|
||||
very unlikely that FreeBSD would have gotten as far, as fast, as it
|
||||
has today.
|
||||
@ -52,7 +52,7 @@ Around this time, some rather unexpected storm clouds formed on our
|
||||
horizon as Novell and U.C. Berkeley settled their long-running lawsuit
|
||||
over the legal status of the Berkeley Net/2 tape. A condition of that
|
||||
settlement was U.C. Berkeley's concession that large parts of Net/2
|
||||
was "encumbered" code and property of Novell, who had in turn aquired
|
||||
was "encumbered" code and property of Novell, who had in turn acquired
|
||||
it from AT&T some time previously. What Berkeley got in return was
|
||||
Novell's "blessing" that the 4.4 Lite release, when it was finally
|
||||
released, would be declared unencumbered and all existing Net/2 users
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: install.sgml,v 1.10 1995/09/25 04:53:32 jfieber Exp $ -->
|
||||
<!-- $Id: install.sgml,v 1.11 1995/09/26 17:47:02 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
@ -499,7 +499,7 @@ C> MD C:\FREEBSD
|
||||
C> XCOPY /S E:\FLOPPIES C:\FREEBSD\FLOPPIES\
|
||||
C> XCOPY /S E:\DISTS\BIN C:\FREEBSD\BIN\
|
||||
</verb></tscreen>
|
||||
asssuming that <tt>C:</tt> is where you have free space
|
||||
assuming that <tt>C:</tt> is where you have free space
|
||||
and <tt>E:</tt> is where your CDROM is mounted. Note
|
||||
that you need the <tt>FLOPPIES</tt> directory because
|
||||
the <tt>root.flp</tt> image is needed during an MS-DOS
|
||||
@ -521,7 +521,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
|
||||
|
||||
<p>Installing from tape is probably the easiest method,
|
||||
short of an on-line install using FTP or a CDROM
|
||||
instal. The installation program expects the files to
|
||||
install. The installation program expects the files to
|
||||
be simply tar'ed onto the tape, so after getting all of
|
||||
the files for distribution you're interested in, simply
|
||||
tar them onto the tape with a command like:
|
||||
@ -714,7 +714,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
|
||||
wish to proceed directly to the Language option and
|
||||
set your preferred language. This will bring up some
|
||||
of the documentation in that language instead of
|
||||
english.
|
||||
English.
|
||||
|
||||
<item>Select the Options item and set any special
|
||||
preferences you may have.
|
||||
@ -769,7 +769,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
|
||||
flags in the Label editor) and all selected
|
||||
distributions will be extracted.
|
||||
|
||||
<item>The Configure menu choice allows you to furthur
|
||||
<item>The Configure menu choice allows you to further
|
||||
configure your FreeBSD installation by giving you
|
||||
menu-driven access to various system defaults.
|
||||
Some items, like networking, may be especially
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: kerberos.sgml,v 1.3 1995/06/30 17:37:40 jfieber Exp $ -->
|
||||
<!-- $Id: kerberos.sgml,v 1.4 1995/07/10 20:14:08 markm Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>Kerberos<label id="kerberos"></heading>
|
||||
@ -226,7 +226,7 @@ grunt# mv grunt-new-srvtab srvtab
|
||||
|
||||
<p>If the file is for a client system, and the network is not
|
||||
deemed safe, then copy the <tt><client>-new-srvtab</tt> to
|
||||
removeable media and transport it by secure physical means. Be
|
||||
removable media and transport it by secure physical means. Be
|
||||
sure to rename it to <tt>srvtab</tt> in the client's
|
||||
<tt>/etc/kerberosIV</tt> directory, and make sure it is mode 600:
|
||||
|
||||
@ -325,7 +325,7 @@ Apr 30 11:23:22 Apr 30 19:23:22 krbtgt.GRONDAR.ZA@GRONDAR.ZA
|
||||
</verb></tscreen>
|
||||
|
||||
<p>Now try changing the password using <tt>passwd</tt> to check if the
|
||||
kpasswd daemon can get authorisation to the Kerberos database:
|
||||
kpasswd daemon can get authorization to the Kerberos database:
|
||||
|
||||
<tscreen><verb>
|
||||
grunt$ passwd
|
||||
@ -342,7 +342,7 @@ Password changed.
|
||||
|
||||
<p>Kerberos allows us to give <it>each</it> user who needs root
|
||||
privileges their own <it>separate</it> <tt>su</tt>password. We
|
||||
could now add an id which is authorised to <tt>su</tt> to <it>root</it>.
|
||||
could now add an id which is authorized to <tt>su</tt> to <it>root</it>.
|
||||
This is controlled by having an instance of <it>root</it> associated
|
||||
with a principal. Using <tt>kdb_edit</tt> we can create the entry
|
||||
<it>jane.root</it> in the Kerberos database:
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: kerneldebug.sgml,v 1.2 1995/06/30 17:37:41 jfieber Exp $ -->
|
||||
<!-- $Id: kerneldebug.sgml,v 1.3 1995/07/31 01:18:46 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>Kernel Debugging<label id="kerneldebug"></heading>
|
||||
@ -44,7 +44,7 @@
|
||||
programs will drastically increase, and since
|
||||
the whole kernel is loaded entirely at boot time and cannot be
|
||||
swapped out later, several megabytes of
|
||||
physical RAM willl be wasted.
|
||||
physical RAM will be wasted.
|
||||
|
||||
If you are testing a new kernel, for example by typing the new
|
||||
kernel's name at the boot prompt, but need to boot a different
|
||||
@ -218,7 +218,7 @@
|
||||
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 similiar code to
|
||||
code, so you'll 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.
|
||||
@ -243,7 +243,7 @@
|
||||
If you need to do low-level debugging on your kernel, there's
|
||||
an on- line debugger available called DDB. It allows to
|
||||
setting breakpoints, single-steping kernel functions, examining
|
||||
and changeing kernel variables, etc. However, it cannot not
|
||||
and changing kernel variables, etc. However, it cannot not
|
||||
access kernel source files, and only has access to the global
|
||||
and static symbols, not to the full debug information like
|
||||
<tt>kgdb</tt>.
|
||||
@ -354,7 +354,7 @@
|
||||
w/w 0xf0010030 0 0
|
||||
</verb></tscreen>
|
||||
The command modifier (<tt>b</tt>/<tt>h</tt>/<tt>w</tt>)
|
||||
specifies the size of the data to be writtten, the first
|
||||
specifies the size of the data to be written, the first
|
||||
following expression is the address to write to, the remainder
|
||||
is interpreted as data to write to successive memory locations.
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: nfs.sgml,v 1.1.1.1 1995/04/28 16:19:59 jfieber Exp $ -->
|
||||
<!-- $Id: nfs.sgml,v 1.2 1995/06/30 17:37:43 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>NFS<label id="nfs"></heading>
|
||||
@ -36,7 +36,7 @@ a FreeBSD system with a lower-performance Ethernet adapter. Also,
|
||||
"/sharedfs" will be the exported NFS filesystem (see "man exports"), and
|
||||
"/project" will be the mount point on the client for the exported file
|
||||
system. In all cases, note that additional options, such as "hard" or
|
||||
"soft" and "bg" may be desireable in your application.
|
||||
"soft" and "bg" may be desirable in your application.
|
||||
|
||||
Examples for the FreeBSD system ("freebox") as the client:
|
||||
in /etc/fstab on freebox:
|
||||
@ -74,6 +74,6 @@ individually, avoiding the deadlock situation.
|
||||
|
||||
Overruns may still occur when a high-performance workstations is slamming
|
||||
data out to a PC system, but with the better cards, such overruns are
|
||||
not guarranteed on NFS "units". When an overrun occurs, the units affected
|
||||
not guaranteed on NFS "units". When an overrun occurs, the units affected
|
||||
will be retransmitted, and there will be a fair chance that they will be
|
||||
received, assembled, and acknowledged.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: porting.sgml,v 1.3 1995/06/30 17:37:44 jfieber Exp $ -->
|
||||
<!-- $Id: porting.sgml,v 1.4 1995/08/19 15:38:25 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>Porting applications<label id="porting"></heading>
|
||||
@ -22,7 +22,7 @@
|
||||
mentioned in this document. Most (if not all) are documented
|
||||
at the start of the <tt>bsd.port.mk</tt> file which can be
|
||||
found in <tt>/usr/share/mk</tt>. This file uses a non-standard tab
|
||||
setting. <tt>Emacs</tt> should recognise the setting on
|
||||
setting. <tt>Emacs</tt> should recognize the setting on
|
||||
loading the file. <tt>vi</tt> or <tt>ex</tt> can be set to
|
||||
using the correct value by typing `<tt>:set tabstop=4</tt>'
|
||||
once the file has been loaded.
|
||||
@ -125,7 +125,7 @@
|
||||
# Date created: 5 December 1994
|
||||
# Whom: asami
|
||||
#
|
||||
# $Id: Makefile,v 1.5 1995/04/11 00:20:20 asami Exp $
|
||||
# $Id: porting.sgml,v 1.4 1995/08/19 15:38:25 jfieber Exp $
|
||||
#
|
||||
|
||||
DISTNAME= oneko-1.1b
|
||||
@ -653,7 +653,7 @@ EXEC_DEPENDS= wish:${PORTSDIR}/x11/tk
|
||||
<p>Note: The GNU General Public License (GPL), both version 1
|
||||
and 2, shouldn't be a problem for ports.
|
||||
|
||||
<p>Note: If you are a commiter, make sure you update the
|
||||
<p>Note: If you are a committer, make sure you update the
|
||||
<tt>ports/LEGAL</tt> file too.
|
||||
|
||||
<sect1>
|
||||
@ -848,7 +848,7 @@ lib/libtcl.so.7.3
|
||||
person who wrote this Makefile]
|
||||
# Whom: Satoshi Asami <asami@FreeBSD.ORG>
|
||||
#
|
||||
# $Id$
|
||||
# $Id: porting.sgml,v 1.4 1995/08/19 15:38:25 jfieber Exp $
|
||||
[ ^^^^ don't worry about this...it will be automatically filled in by CVS when
|
||||
it is committed to our repository]
|
||||
#
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: ports.sgml,v 1.5 1995/07/07 22:25:52 jfieber Exp $ -->
|
||||
<!-- $Id: ports.sgml,v 1.6 1995/07/12 15:01:38 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>The Ports collection<label id="ports"></heading>
|
||||
@ -85,12 +85,12 @@ FTP site as defined in the relevant Makefile (in the MASTER_SITES
|
||||
line), or some FreeBSD mirror site also carrying a set of distfiles,
|
||||
as does the master FTP site on ftp.FreeBSD.org (aka ftp.cdrom.com) in
|
||||
the directory <tt>/pub/FreeBSD/distfiles</tt>. Note that the files in
|
||||
that directory are not guarenteed to be kept up to date - this is a
|
||||
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 independant control and don't
|
||||
sites either - they are obviously under independent control and don't
|
||||
even have to mirror the distfiles directory.
|
||||
|
||||
If you have a non-permanant link, you can fetch all the distfiles by
|
||||
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''.
|
||||
|
||||
|
||||
@ -180,7 +180,7 @@ minute. The most up-to-date copy can be found in:
|
||||
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
|
||||
remember that any changes must respect backwards-compatability with
|
||||
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
|
||||
not be warmly welcomed unless all the existing makefiles work without
|
||||
@ -208,7 +208,7 @@ This will print a summary of all ports in the tree.
|
||||
|
||||
<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
|
||||
that the origional porter worked from, and this can lead to problems.
|
||||
that the original porter worked from, and this can lead to problems.
|
||||
So a simple checksumming system has been employed to try and highlight
|
||||
problems in this area.
|
||||
|
||||
@ -225,7 +225,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 recognise the ``checksum''
|
||||
Some older versions of the system don't recognize the ``checksum''
|
||||
target. In that case, try the command
|
||||
<verb>
|
||||
make check-md5
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: ppp.sgml,v 1.3 1995/06/30 17:37:46 jfieber Exp $ -->
|
||||
<!-- $Id: ppp.sgml,v 1.4 1995/07/29 13:08:01 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>Setting up kernel PPP<label id="ppp"></heading>
|
||||
@ -92,7 +92,7 @@ pppd /dev/tty01 19200
|
||||
necessary authorization on the remote host.
|
||||
( Example of such script is attached to the end of this document )
|
||||
|
||||
Use the follwing /etc/ppp/pppdown script to disconnect the PPP line:
|
||||
Use the following /etc/ppp/pppdown script to disconnect the PPP line:
|
||||
<verb>
|
||||
#!/bin/sh
|
||||
pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
|
||||
@ -246,7 +246,7 @@ exit
|
||||
This /etc/ppp/kermit.dial 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
|
||||
to change input statement depending on responces from your modem
|
||||
to change input statement depending on responses from your modem
|
||||
and remote host.
|
||||
<verb>
|
||||
;
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: scsi.sgml,v 1.3 1995/08/29 01:42:45 jfieber Exp $ -->
|
||||
<!-- $Id: scsi.sgml,v 1.4 1995/09/05 21:07:15 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
@ -26,7 +26,7 @@
|
||||
|
||||
After some time an industry effort was started to come to a more strict
|
||||
standard allowing devices from different vendors to work together.
|
||||
This effort was recognised in the ANSI SCSI-1 standard. The SCSI-1
|
||||
This effort was recognized in the ANSI SCSI-1 standard. The SCSI-1
|
||||
standard (approx 1985) is now more or less obsolete. The current
|
||||
standard is SCSI-2 (see <ref id="scsi:further-reading" name="Further
|
||||
reading">), with SCSI-3 on the drawing boards.
|
||||
@ -44,27 +44,27 @@
|
||||
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
|
||||
about.) Modern designs also use 16 bit wides buses, with
|
||||
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
|
||||
allows a maximum buswidth of 32 bits, using an additional cable.
|
||||
allows a maximum bus width of 32 bits, using an additional cable.
|
||||
|
||||
Of course the SCSI bus not only has data lines, but also a number
|
||||
of control signals. A very elaborate protocol is part of the
|
||||
standard to allow multiple devices to share the bus in an efficient
|
||||
manner. In SCSI-2, the data is always checked using a seperate
|
||||
manner. In SCSI-2, the data is always checked using a separate
|
||||
parity line. In pre-SCSI-2 designs parity was optional.
|
||||
|
||||
In SCSI-3 even faster bustypes are introduced, along with a serial
|
||||
In SCSI-3 even faster bus types are introduced, along with a serial
|
||||
SCSI bus that reduces the cabling overhead and allows a higher
|
||||
maximum buslength.
|
||||
maximum bus length.
|
||||
|
||||
As you could have guessed from the description above, SCSI devices
|
||||
are intelligent. They have to be to adhere to the SCSI standard
|
||||
(which is over 2 inches thick BTW). So, for a hard disk drive for
|
||||
instance you do not specify a head/cylinder/sector to address a
|
||||
particular block, but simply the number of the block you want.
|
||||
Elaborate caching schemes, automatic badblock replacement etc
|
||||
Elaborate caching schemes, automatic bad block replacement etc
|
||||
are all made possible by this 'intelligent device' approach.
|
||||
|
||||
On a SCSI bus, each possible pair of devices can communicate. If
|
||||
@ -78,7 +78,7 @@
|
||||
because it is not absolutely sure that the implementation of an old
|
||||
device follows the (old) standard closely enough to be acceptable
|
||||
on a new bus. Modern devices are usually more well-behaved,
|
||||
because the standardisation has become more strict and is better
|
||||
because the standardization has become more strict and is better
|
||||
adhered to by the device manufacturers. Generally speaking, the
|
||||
chances of getting a working set of devices on a single bus is
|
||||
better when all the devices are SCSI-2 or newer. This does not
|
||||
@ -149,11 +149,11 @@
|
||||
that on a narrow (8 bit) bus 10 Mbytes/sec are possible instead
|
||||
of 5 Mbytes/sec for 'slow' SCSI. More on this later.
|
||||
|
||||
It should be noted that the datalines > 8 are only used for
|
||||
datatransfers and device addressing. The transfers of commands
|
||||
It should be noted that the data lines > 8 are only used for
|
||||
data transfers and device addressing. The transfers of commands
|
||||
and status messages etc are only performed on the lowest 8
|
||||
datalines. The standard allows narrow devices to operate on
|
||||
a wide bus. The usable buswidth is negotiated
|
||||
data lines. The standard allows narrow devices to operate on
|
||||
a wide bus. The usable bus width is negotiated
|
||||
between the devices. You have to watch your device addressing
|
||||
closely when mixing wide and narrow.
|
||||
|
||||
@ -174,7 +174,7 @@
|
||||
bus must adhere to the length restrictions for fast buses!
|
||||
|
||||
It is obvious that with the newer fast-SCSI devices the
|
||||
buslength can become a real bottleneck. This is why the
|
||||
bus length can become a real bottleneck. This is why the
|
||||
differential SCSI bus was introduced in the SCSI-2 standard.
|
||||
|
||||
For connector pinning and connector types please refer to the
|
||||
@ -236,8 +236,8 @@
|
||||
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
|
||||
a single jumper to enable or disable a builtin terminator.
|
||||
There are special terminators you can stick onto a flatcable
|
||||
a single jumper to enable or disable a built-in terminator.
|
||||
There are special terminators you can stick onto a flat cable
|
||||
bus. Others look like external connectors, so a connector hood
|
||||
without a cable. So, lots of choice as you can see.
|
||||
|
||||
@ -245,7 +245,7 @@
|
||||
from simple resistor (passive) terminators to active
|
||||
terminators. Active terminators contain more or less elaborate
|
||||
circuits to give more clean bus signals. The general consensus
|
||||
seems to be that the usefullnes of active termination increases
|
||||
seems to be that the usefulness of active termination increases
|
||||
when you have long buses and/or fast devices. If you ever have
|
||||
problems with your SCSI buses you might consider trying an
|
||||
active terminator. Try to borrow one first, they reputedly are
|
||||
@ -325,7 +325,7 @@
|
||||
|
||||
This is done by means of the SCSI or target ID. Each device has
|
||||
a unique target ID. You can select the ID to which a device
|
||||
must respond using a set of jumpers, or a dipswitch, or
|
||||
must respond using a set of jumpers, or a dip switch, or
|
||||
something similar. Consult the documentation of your device for
|
||||
more information.
|
||||
|
||||
@ -334,26 +334,26 @@
|
||||
|
||||
For an 8 bit bus, a maximum of 8 targets is possible. The
|
||||
maximum is 8 because the selection is done bitwise using the 8
|
||||
datalines on the bus. For wide this increases to the number of
|
||||
datalines.
|
||||
data lines on the bus. For wide this increases to the number of
|
||||
data lines.
|
||||
|
||||
The higher the SCSI target ID, the higher the priority the
|
||||
devices has. When it comes to arbitration between devices that
|
||||
want to use the bus at the same time, the device that has the
|
||||
highest SCSI ID will win. This also means that the SCSI
|
||||
hostadapter usually uses target ID 7 (for narrow buses).
|
||||
host adapter usually uses target ID 7 (for narrow buses).
|
||||
|
||||
For a further subdivision, the standard allows for Logical
|
||||
Units or LUNs for short. A single target ID may have multiple
|
||||
LUNs. For example, a tape device including a tape changer may
|
||||
have LUN 0 for the tape device itself, and LUN 1 for the
|
||||
tapechanger. In this way, the host system can address each of
|
||||
tape changer. In this way, the host system can address each of
|
||||
the parts of the tape unit as desired.
|
||||
|
||||
<sect2><heading>Bus layout</heading>
|
||||
<p>
|
||||
SCSI buses are linear. So, not shaped like Y-junctions, star
|
||||
topologies, cobwebbs or whatever else people might want to
|
||||
topologies, cobwebs or whatever else people might want to
|
||||
invent.
|
||||
|
||||
You might notice that the terminator issue discussed earlier
|
||||
@ -375,8 +375,8 @@
|
||||
When you want to use a SCSI disk on your PC as boot disk, you
|
||||
must aware of some quirks related to PC BIOSes. The PC BIOS in
|
||||
it's first incarnation used a low level physical interface to the
|
||||
harddisk. So, you had to tell the BIOS (using a setup tool or a
|
||||
BIOS builtin setup) how your disk physically looked like. This
|
||||
hard disk. So, you had to tell the BIOS (using a setup tool or a
|
||||
BIOS built-in setup) how your disk physically looked like. This
|
||||
involved stating number of heads, number of cylinders, number of
|
||||
sectors per track, obscure things like precompensation and
|
||||
reduced write current cylinder etc.
|
||||
@ -388,9 +388,9 @@
|
||||
|
||||
The SCSI host adapter or SCSI controller you have put in your
|
||||
AT/EISA/PCI/whatever bus to connect your disk therefore has it's
|
||||
own onboard BIOS. During system startup, the SCSI BIOS takes over
|
||||
the harddisk interface routines from the system BIOS. To fool the
|
||||
system BIOS, the system setup is normally set to No harddisk
|
||||
own on-board BIOS. During system startup, the SCSI BIOS takes over
|
||||
the hard disk interface routines from the system BIOS. To fool the
|
||||
system BIOS, the system setup is normally set to No hard disk
|
||||
present. Obvious, isn't it?
|
||||
|
||||
The SCSI BIOS itself presents to the system a so called
|
||||
@ -405,8 +405,8 @@
|
||||
|
||||
Right.. All is well now?! No, it isn't. The system BIOS has
|
||||
another quirk you might run into. The number of cylinders of a
|
||||
bootable harddisk cannot be greater than 1024. Using the
|
||||
translation above, this is a showstopper for disks greater than
|
||||
bootable hard disk cannot be greater than 1024. Using the
|
||||
translation above, this is a show-stopper for disks greater than
|
||||
1 Gb. With disk capacities going up all the time this is causing
|
||||
problems.
|
||||
|
||||
@ -424,7 +424,7 @@
|
||||
translated values your host adapter uses.
|
||||
|
||||
Failing to observe the translation issue might be un-bootable systems or
|
||||
operating systems overwriting eachothers partitions. Using fdisk
|
||||
operating systems overwriting each others partitions. Using fdisk
|
||||
you should be able to see all partitions.
|
||||
|
||||
As promised earlier: what is this talk about 'lying' devices? As
|
||||
@ -464,12 +464,12 @@ Feb 9 19:33:46 yedi /386bsd: sd0: 636MB (1303250 total sec), 1632 cyl, 15 head,
|
||||
|
||||
The multi level design allows a decoupling of low-level bit
|
||||
banging and more high level stuff. Adding support for another
|
||||
piece of hardware is a much more managable problem.
|
||||
piece of hardware is a much more manageable problem.
|
||||
|
||||
<sect2><heading>Kernel configuration</heading>
|
||||
<p>
|
||||
Dependent on your hardware, the kernel configuration file must
|
||||
contain one or more lines describing your hostadapter(s).
|
||||
contain one or more lines describing your host adapter(s).
|
||||
This includes I/O addresses, interrupts etc.
|
||||
Consult the man page for your
|
||||
adapter driver to get more info. Apart from that, check out
|
||||
@ -586,7 +586,7 @@ device cd0 #Only need one of these, the code dynamically grows &lsq
|
||||
above will work fine when you have only 2 SCSI disks.
|
||||
|
||||
Use <tt>man 4 scsi</tt> to check for the latest info on the SCSI
|
||||
subsystem. For more detailed info on hostadapter drivers use eg
|
||||
subsystem. For more detailed info on host adapter drivers use eg
|
||||
<tt>man 4 aha</tt> for info on the Adaptec 154x driver.
|
||||
|
||||
<sect2><heading>Tuning your SCSI kernel setup</heading>
|
||||
@ -598,13 +598,13 @@ device cd0 #Only need one of these, the code dynamically grows &lsq
|
||||
|
||||
To work around this problem, FreeBSD allows a tunable delay time before
|
||||
the SCSI devices are probed following a SCSI bus reset. You can set this
|
||||
delaytime in your kernel configuration file using a line like:
|
||||
delay time in your kernel configuration file using a line like:
|
||||
|
||||
<verb>
|
||||
options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device
|
||||
</verb>
|
||||
This line sets the delay time to 15 seconds. On my own system I had to
|
||||
use 3 seconds minimum to get my trusty old CDROM drive to be recognised.
|
||||
use 3 seconds minimum to get my trusty old CDROM drive to be recognized.
|
||||
Start with a high value (say 30 seconds or so) when you have problems
|
||||
with device recognition. If this helps, tune it back until it just stays
|
||||
working.
|
||||
@ -616,7 +616,7 @@ options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device
|
||||
Some vendors do a better job then others.
|
||||
|
||||
This is exactly where the 'rogue' devices come into view. Rogues are
|
||||
devices that are recognised by the FreeBSD kernel as behaving slightly
|
||||
devices that are recognized by the FreeBSD kernel as behaving slightly
|
||||
(...) non-standard. Rogue devices are reported by the kernel when
|
||||
booting. An example for two of my cartridge tape units:
|
||||
|
||||
@ -634,7 +634,7 @@ Mar 29 21:16:37 yedi /386bsd: st1: Archive Viper 150 is a known rogue
|
||||
believing that there are 8 LUNs at that particular target ID. The
|
||||
confusion this causes is left as an exercise to the user.
|
||||
|
||||
The SCSI subsystem of FreeBSD recognises devices with bad habits by
|
||||
The SCSI subsystem of FreeBSD recognizes devices with bad habits by
|
||||
looking at the INQUIRY response they send when probed. Because the
|
||||
INQUIRY response also includes the version number of the device
|
||||
firmware, it is even possible that for different firmware versions
|
||||
@ -655,7 +655,7 @@ Mar 29 21:16:37 yedi /386bsd: st1: Archive Viper 150 is a known rogue
|
||||
FreeBSD. It must be noted however that there might be some rough edges.
|
||||
|
||||
For instance an Adaptec 1542 controller can be set to use different
|
||||
transferspeeds on the host bus (ISA or AT in this case). The controller
|
||||
transfer speeds on the host bus (ISA or AT in this case). The controller
|
||||
is settable to different rates because not all motherboards can handle
|
||||
the higher speeds. Problems like hangups, bad data etc might be the
|
||||
result of using a higher data transfer rate then your motherboard
|
||||
@ -699,7 +699,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed
|
||||
<item>
|
||||
Make a minimal bus config with as little devices as possible.
|
||||
<item>
|
||||
If possible, configure your hostadapter to use slow bus speeds.
|
||||
If possible, configure your host adapter to use slow bus speeds.
|
||||
</itemize>
|
||||
|
||||
<sect1><heading>Further reading<label id="scsi:further-reading"></heading>
|
||||
@ -760,6 +760,6 @@ Suite 214, 1210 S. Bascom Ave., San Jose, CA 92128, (408) 293-0800
|
||||
are noteworthy places to look for more info. You can also
|
||||
find the SCSI-Faq there, which is posted periodically.
|
||||
|
||||
Most major SCSI device and hostadapter suppliers operate ftp sites
|
||||
Most major SCSI device and host adapter suppliers operate ftp sites
|
||||
and/or BBS systems. They may be valuable sources of information
|
||||
about the devices you own.
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
<!-- $Id: submitters.sgml,v 1.5 1995/07/07 22:25:54 jfieber Exp $ -->
|
||||
<!-- $Id: submitters.sgml,v 1.6 1995/08/12 21:33:24 jkh Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>Contributing to FreeBSD<label id="submitters"></heading>
|
||||
|
||||
<p><em>Contributed by &a.jkh;.</em>
|
||||
|
||||
This guide is intended for those who are moderately familar with
|
||||
This guide is intended for those who are moderately familiar with
|
||||
FreeBSD and have reached a point where they have some locally
|
||||
developed customizations or fixes to the system which they'd like to
|
||||
incorporate back into the mainstream sources. Submitting something to
|
||||
@ -19,14 +19,14 @@ are also what FreeBSD lives and grows from, so your contributions are
|
||||
very important to the continued survival of this communal effort of
|
||||
ours---we're very glad to see you reading this document!
|
||||
|
||||
Submissions to FreeBSD can generally be classified into four catagories:
|
||||
Submissions to FreeBSD can generally be classified into four categories:
|
||||
<enum>
|
||||
<item>Ideas, general suggestions, bug reports.
|
||||
<item>Changes to existing sources.
|
||||
<item>Significant contribution of a large body of independant work.
|
||||
<item>Significant contribution of a large body of independent work.
|
||||
<item>Porting of freely available software.
|
||||
</enum>
|
||||
A submission in <em>any</em> of these catagories is highly welcomed as they
|
||||
A submission in <em>any</em> of these categories is highly welcomed as they
|
||||
are each, in their own way, quite significant to the project.
|
||||
|
||||
|
||||
@ -39,7 +39,7 @@ are each, in their own way, quite significant to the project.
|
||||
Likewise, people with an interest
|
||||
in such things (and a tolerance for a <em>high</em>
|
||||
volume of mail!) may
|
||||
subscribe to the hackers mailing list by sendimg mail to
|
||||
subscribe to the hackers mailing list by sending mail to
|
||||
<tt><majordomo@freebsd.org></tt>.
|
||||
See <ref id="eresources:mail" name="mailing lists">
|
||||
for more information about this and other mailing lists.
|
||||
@ -149,7 +149,7 @@ diff -c -r <olddir> <newdir>
|
||||
additional contributions under this license. Code under the GPL
|
||||
also goes into a different part of the tree, that being
|
||||
<tt>/sys/gnu</tt> or <tt>/usr/src/gnu</tt>, and is therefore
|
||||
easily identifable to anyone for whom the GPL presents a problem.
|
||||
easily identifiable to anyone for whom the GPL presents a problem.
|
||||
</enum>
|
||||
|
||||
<p>Contributions coming under any other type of copyright must be
|
||||
@ -193,7 +193,7 @@ THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
||||
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
||||
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
|
||||
$Id: submitters.sgml,v 1.5 1995/07/07 22:25:54 jfieber Exp $
|
||||
$Id: submitters.sgml,v 1.6 1995/08/12 21:33:24 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>.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: sup.sgml,v 1.5 1995/07/07 22:25:54 jfieber Exp $ -->
|
||||
<!-- $Id: sup.sgml,v 1.6 1995/09/01 04:54:14 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
|
||||
@ -25,7 +25,7 @@ your /etc/services file:
|
||||
SUP gets the information it needs to run from a configuration file
|
||||
called a supfile. This file tells sup what collections it will be updating
|
||||
and/or installing and where they go. The supfile in this directory will
|
||||
sup both the source and ports collection - look for the blank line seperating
|
||||
sup both the source and ports collection - look for the blank line separating
|
||||
the two collections; if you don't want ports, you can simply delete all the
|
||||
ports entries. If you're inside the United States, you may also uncomment
|
||||
the `secure' collection line to grab the DES code. If you're outside the
|
||||
@ -35,7 +35,7 @@ collection and then go look on braae.ru.ac.za, where it's available for
|
||||
anonymous ftp for those outside the U.S.
|
||||
|
||||
Any other distributions you do not wish to receive can be commented out
|
||||
with a # at the begining of the distribution line.
|
||||
with a # at the beginning of the distribution line.
|
||||
|
||||
Once this is setup, you're ready to go. To start sup type:
|
||||
<verb>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user