Some more spelling fixes.
This commit is contained in:
parent
d45d3fa224
commit
739d6a140c
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=13796
@ -4,7 +4,7 @@
|
||||
|
||||
<title>Frequently Asked Questions for FreeBSD 2.X
|
||||
<author>The FreeBSD FAQ Team, <tt/FAQ@FreeBSD.ORG/
|
||||
<date> $Id: freebsd-faq.sgml,v 1.30 1996/01/27 15:57:07 roberto Exp $
|
||||
<date> $Id: freebsd-faq.sgml,v 1.31 1996/01/28 16:59:05 jfieber Exp $
|
||||
<abstract>
|
||||
This is the FAQ for FreeBSD systems version 2.X All entries are
|
||||
assumed to be relevant to FreeBSD 2.0.5+, unless otherwise noted.
|
||||
@ -161,7 +161,7 @@ Any entries with a <XXX> are under construction.
|
||||
domain.
|
||||
<tag/users-groups/ This is the mailing list for the
|
||||
coordinators from each of the local area Users Groups to
|
||||
dicuss matters with each other and a designated individual
|
||||
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
|
||||
@ -184,7 +184,7 @@ Any entries with a <XXX> are under construction.
|
||||
To unsubscribe, it is as easy. Just remember to send your request
|
||||
to
|
||||
<url url="mailto:Majordomo@FreeBSD.ORG" name="The mail administrator">
|
||||
<bf/not/ to the list itself. The last thing the subscribred
|
||||
<bf/not/ to the list itself. The last thing the subscribed
|
||||
users want to see is administrative requests...
|
||||
|
||||
<sect1>
|
||||
@ -320,7 +320,7 @@ Any entries with a <XXX> are under construction.
|
||||
strings attached, though at least on the side of enforced
|
||||
access rather than the usual opposite. Due to the additional
|
||||
complexities that can evolve in the commercial use of GPL software,
|
||||
we do, however, endevor to replace such software with submissions
|
||||
we do, however, endeavor to replace such software with submissions
|
||||
under the more relaxed BSD copyright whenever possible.
|
||||
|
||||
<sect>
|
||||
@ -373,7 +373,7 @@ Any entries with a <XXX> are under construction.
|
||||
with the ``upgrade'' option of the 2.1.0 installation program.
|
||||
|
||||
After the installation, if you build a custom kernel, it will run
|
||||
in 4 MB. Someone has even succeded in booting with 2 MB (the
|
||||
in 4 MB. Someone has even succeeded in booting with 2 MB (the
|
||||
system was almost unusable though :-))
|
||||
|
||||
<sect1>
|
||||
@ -803,7 +803,7 @@ sea32550N|Seagate 32550N:\
|
||||
<itemize>
|
||||
<item>AST/4 in shared IRQ mode,
|
||||
<item>ARNET 8 port in shared IRQ mode,
|
||||
<item>BOCA 4/8/16 port cards inshared IRQ mode,
|
||||
<item>BOCA 4/8/16 port cards in shared IRQ mode,
|
||||
<item>Cyclades 8/16 port <Alpha>,
|
||||
<item>Cronyx/Sigfgma multiport sync/async,
|
||||
<item>RISCom/8 multiport card,
|
||||
@ -813,7 +813,7 @@ sea32550N|Seagate 32550N:\
|
||||
Some unnamed clone cards have also been known to work, especially
|
||||
those that claim to be AST compatible.
|
||||
|
||||
A Dibiboard driver is currently in alpha stage. If you want to
|
||||
A Digiboard driver is currently in alpha stage. If you want to
|
||||
test it, take the file in
|
||||
<url url="ftp://freefall.FreeBSD.ORG/pub/incoming"
|
||||
name="the incoming directory">
|
||||
@ -940,13 +940,13 @@ options PSM_NO_RESET #don't reset mouse hardware (some laptops)
|
||||
Fujitsu MB86960A/MB86965A Ethernet cards
|
||||
</descrip>
|
||||
|
||||
<bf/NOTE/ PCMCIA ethernet cards from IBM and National
|
||||
<bf/NOTE/ PCMCIA Ethernet cards from IBM and National
|
||||
Semiconductor.
|
||||
|
||||
<bf/NOTE/ Drivers marked with (*) are known to have problems.
|
||||
|
||||
<bf/NOTE/ We also support TCP/IP over parallel lines. At this point
|
||||
we are incompatiable with other versions, but we hope to correct
|
||||
we are incompatible with other versions, but we hope to correct
|
||||
this in the near future.
|
||||
|
||||
<sect1>
|
||||
@ -972,7 +972,7 @@ options PSM_NO_RESET #don't reset mouse hardware (some laptops)
|
||||
|
||||
<descrip>
|
||||
<tag><tt/b004.c/</tag>
|
||||
Driver for B004 compatiable Transputer boards <newline>
|
||||
Driver for B004 compatible Transputer boards <newline>
|
||||
<tag>``ctx'' driver</tag>
|
||||
Driver for CORTEX-I Frame grabber <newline>
|
||||
<tag>``gp'' driver</tag>
|
||||
@ -1073,7 +1073,7 @@ options PSM_NO_RESET #don't reset mouse hardware (some laptops)
|
||||
<heading>Are there any Database systems for FreeBSD?</heading>
|
||||
<p>
|
||||
Yes! Conetic Software Systems has ported their C/base and C/books
|
||||
datebase systems to FreeBSD 2.0.5 and higher.
|
||||
database systems to FreeBSD 2.0.5 and higher.
|
||||
|
||||
<descrip>
|
||||
<tag/For more information/
|
||||
@ -1149,7 +1149,7 @@ options PSM_NO_RESET #don't reset mouse hardware (some laptops)
|
||||
Yes. We support the concept of a ``package'', which is
|
||||
essentially a gzipped binary distribution with a little extra
|
||||
intelligence embedded in it for doing any custom installation
|
||||
work required. Packages can also be installed or deinstalled
|
||||
work required. Packages can also be installed or uninstalled
|
||||
again easily without having to know the gory details. CDROM
|
||||
people will have a <tt>packages/</tt> directory on their CD,
|
||||
others can get the currently available packages from:
|
||||
@ -1393,7 +1393,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
|
||||
<p>
|
||||
Read this:
|
||||
<url url="http://www.freebsd.org/How/handbook/current.html"
|
||||
name="Handook's section of FreeBSD-CURRENT">
|
||||
name="Handbook's section of FreeBSD-CURRENT">
|
||||
it will tell you all you need to know.
|
||||
|
||||
<sect1>
|
||||
@ -1404,13 +1404,13 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
|
||||
for keeping their development trees in sync. We use it to keep
|
||||
remote sites in sync with our central development sources.
|
||||
|
||||
Unless you have direct internet connectivity, and don't care too
|
||||
Unless you have direct Internet connectivity, and don't care too
|
||||
much about the cost/duration of the sessions, you shouldn't use
|
||||
sup. For those ``low/expensive-bandwidth'' applications, we have
|
||||
developed <tt/CTM/, see the section <ref id="ctm" name="on CTM">
|
||||
for more about that.
|
||||
|
||||
To use it, you need to have direct internet connectivity (not
|
||||
To use it, you need to have direct Internet connectivity (not
|
||||
just mail or news). First, pick up the <tt/sup.tgz/ package
|
||||
from:
|
||||
|
||||
@ -1433,7 +1433,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
|
||||
which are a set of supfiles for supping from <tt/FreeBSD.ORG/.
|
||||
|
||||
<sect1>
|
||||
<heading>Has anyone done any temperature testing while running FreeBSD? I know linux runs cooler than dos, but have never seen a mention of FreeBSD. It seems to run really hot</heading>
|
||||
<heading>Has anyone done any temperature testing while running FreeBSD? I know Linux runs cooler than dos, but have never seen a mention of FreeBSD. It seems to run really hot</heading>
|
||||
<p>
|
||||
No, but we have done numerous taste tests on blindfolded
|
||||
volunteers who have also had 250 micrograms of LSD-25
|
||||
@ -1448,7 +1448,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
|
||||
funny old business we're in!
|
||||
|
||||
Seriously, Linux use the ``<tt/HALT/'' instruction when the
|
||||
system is idle thus lowering its energy comsumption and therefore
|
||||
system is idle thus lowering its energy consumption and therefore
|
||||
the heat it generates.
|
||||
|
||||
<sect1>
|
||||
@ -1523,7 +1523,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
|
||||
|
||||
<p>
|
||||
Newer BSD based systems have a ``<tt/-b/'' option to split that
|
||||
allows them to split files on arbitary byte bondaries.
|
||||
allows them to split files on arbitrary byte boundaries.
|
||||
|
||||
Here is an example from <tt>/usr/src/Makefile</tt>.
|
||||
|
||||
@ -1542,10 +1542,10 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
|
||||
<sect1>
|
||||
<heading>I've got this neato kernel extension I just know everyone will will want. How do I get it included into the distribution?</heading>
|
||||
<p>
|
||||
Please take a look at the FAQ for submiting code to FreeBSD at:
|
||||
Please take a look at the FAQ for submitting code to FreeBSD at:
|
||||
|
||||
<url url="http://www.FreeBSD.ORG/How/handbook/submitters.html"
|
||||
name="Handbbook's section on how to submit code">.
|
||||
name="Handbook's section on how to submit code">.
|
||||
|
||||
And thanks for the thought.
|
||||
|
||||
@ -1620,11 +1620,11 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx
|
||||
helpful in configuring the new one.
|
||||
|
||||
<sect1>
|
||||
<heading>I don't understand, I have removed <tt/npx0/ from my kernel configuration file as I don't have a mathematic coprocessor but it keeps bombing saying that <tt/_hw_float/ is missing.</heading>
|
||||
<heading>I don't understand, I have removed <tt/npx0/ from my kernel configuration file as I don't have a mathematic co-processor but it keeps bombing saying that <tt/_hw_float/ is missing.</heading>
|
||||
|
||||
<p>
|
||||
The <tt/npx0/ is <bf/MANDATORY/. Even if you don't have a
|
||||
mathematic coprocessor, you <bf/must/ include the <tt/npx0/
|
||||
mathematic co-processor, you <bf/must/ include the <tt/npx0/
|
||||
device.
|
||||
|
||||
<sect1>
|
||||
@ -1675,7 +1675,7 @@ disk fd1 at fdc0 drive 1
|
||||
write to through a special program to manage it called
|
||||
``<tt/ft/'' - see the man page on <tt/ft/ for further details.
|
||||
Versions previous to <tt/-current/ also had some trouble dealing
|
||||
wiht bad tape media; if you have trouble where <tt/ft/ seems to
|
||||
with bad tape media; if you have trouble where <tt/ft/ seems to
|
||||
go back and forth over the same spot, try grabbing the latest
|
||||
version of <tt/ft/ from <tt>/usr/src/sbin/ft</tt> in
|
||||
<tt/-current/ and try that.
|
||||
@ -1725,7 +1725,7 @@ disk fd1 at fdc0 drive 1
|
||||
<p>
|
||||
The panic indicates that the system ran out of virtual memory for
|
||||
network buffers (specifically, mbuf clusters). You can increase
|
||||
the amount of VM avaliable for mbuf clusters by adding:
|
||||
the amount of VM available for mbuf clusters by adding:
|
||||
|
||||
<code>
|
||||
options "NMBCLUSTERS=<n>"
|
||||
@ -1786,7 +1786,7 @@ disk fd1 at fdc0 drive 1
|
||||
put additional services like <tt/INN/ or a <tt/http/ server.
|
||||
|
||||
The <tt>/etc/rc.serial</tt> is for serial port initialization
|
||||
(e.g. locking the port characterictics, and so on.).
|
||||
(e.g. locking the port characteristics, and so on.).
|
||||
|
||||
The <tt>/etc/rc.i386</tt> is for Intel-specifics setting like the
|
||||
iBCS2 emulation.
|
||||
@ -2010,7 +2010,7 @@ disk fd1 at fdc0 drive 1
|
||||
|
||||
<p>
|
||||
Some versions of the Linux NFS code only accept mount requests
|
||||
from a priviledged port; try
|
||||
from a privileged port; try
|
||||
<verb>
|
||||
mount -o -P linuxbox:/blah /mnt
|
||||
</verb>
|
||||
@ -2019,14 +2019,14 @@ disk fd1 at fdc0 drive 1
|
||||
|
||||
<p>
|
||||
Sun workstations running SunOS 4.X only accept mount requests
|
||||
from a priviledged port; try
|
||||
from a privileged port; try
|
||||
<verb>
|
||||
mount -o -P sunbox:/blah /mnt
|
||||
</verb>
|
||||
<sect1><heading>I'm having problems with my NeXTStep machines and other FreeBSD ones accross PPP</heading>
|
||||
<sect1><heading>I'm having problems with my NeXTStep machines and other FreeBSD ones across PPP</heading>
|
||||
|
||||
<p>
|
||||
Try disabling the TCP extentions in <tt>/etc/sysconfig</tt> by
|
||||
Try disabling the TCP extensions in <tt>/etc/sysconfig</tt> by
|
||||
changing the following variable to NO:
|
||||
<verb>
|
||||
tcp_extensions=NO
|
||||
@ -2228,7 +2228,7 @@ Zynx ZX342
|
||||
<heading>How can I enable dialup logins on my modem?</heading>
|
||||
<p>
|
||||
So you want to become an Internet service provider, eh? First,
|
||||
you'll need one or more modems that can autoanswer. Your modem
|
||||
you'll need one or more modems that can auto-answer. Your modem
|
||||
will need to assert carrier-detect when it detects a carrier and
|
||||
not assert it all the time. It will need to hang up the phone
|
||||
and reset itself when the data terminal ready (<tt/DTR/) line
|
||||
|
@ -1,8 +1,8 @@
|
||||
<!-- $Id: authors.sgml,v 1.14 1996/01/03 12:59:37 gclarkii Exp $ -->
|
||||
<!-- $Id: authors.sgml,v 1.15 1996/01/20 16:19:17 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
Names and email address of contributing authors and CVS commiters. Use these
|
||||
Names and email address of contributing authors and CVS committers. Use these
|
||||
entities when referencing people. Please not the use of single
|
||||
and double quotes.
|
||||
-->
|
||||
|
@ -3,7 +3,7 @@
|
||||
|
||||
This conversion has been made by Ollivier Robert.
|
||||
|
||||
$Id: booting.sgml,v 1.7 1995/10/07 04:31:15 jfieber Exp $
|
||||
$Id: booting.sgml,v 1.8 1995/10/22 00:41:56 jfieber Exp $
|
||||
|
||||
|
||||
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
|
||||
@ -52,7 +52,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
|
||||
MicroSoft compilers.
|
||||
Microsoft compilers.
|
||||
|
||||
Dosboot will boot the kernel from a MS-DOS file or from a FreeBSD
|
||||
filesystem partition on the disk. It attempts to negotiate with
|
||||
@ -62,7 +62,7 @@
|
||||
|
||||
<tag>Netboot</tag>
|
||||
|
||||
Netboot will try to find a supported ethernet card, and use
|
||||
Netboot will try to find a supported Ethernet card, and use
|
||||
BOOTP, TFTP and NFS to find a kernel file to boot.
|
||||
</descrip>
|
||||
|
||||
@ -73,13 +73,13 @@
|
||||
will initialize itself, trying to determine what hardware is
|
||||
present and so on, and then it needs to find a root filesystem.
|
||||
|
||||
Presently we support the following types of rootfilesystems:
|
||||
Presently we support the following types of root filesystems:
|
||||
|
||||
<descrip>
|
||||
<tag>UFS</tag>
|
||||
|
||||
This is the most normal type of root filesystem. It can reside on
|
||||
a floppy or on harddisk.
|
||||
a floppy or on hard disk.
|
||||
|
||||
<tag>MSDOS</tag>
|
||||
|
||||
@ -108,7 +108,7 @@
|
||||
<p>
|
||||
To get the user-land going, when the kernel has finished
|
||||
initialization, it will create a process with ``<tt/pid == 1/'' and execute
|
||||
a program on the rootfilesystem, this program is normally
|
||||
a program on the root filesystem, this program is normally
|
||||
``<tt>/sbin/init</tt>''.
|
||||
|
||||
You can substitute any program for /sbin/init, as long as you keep
|
||||
@ -152,7 +152,7 @@
|
||||
|
||||
<tag/C -- Start an X-server/
|
||||
|
||||
Now you have an Xterminal, which is better than that dingy
|
||||
Now you have an X-terminal, which is better than that dingy
|
||||
X-under-windows-so-slow-you-can-see-what-it-does thing that
|
||||
your boss insist is better than forking our money on HW.
|
||||
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: contrib.sgml,v 1.45 1996/01/15 23:57:59 asami Exp $ -->
|
||||
<!-- $Id: contrib.sgml,v 1.46 1996/01/25 05:35:31 asami Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>FreeBSD contributor list<label id="contrib"></heading>
|
||||
@ -8,7 +8,7 @@
|
||||
<p>This software was originally derived from William
|
||||
F. Jolitz's 386BSD release 0.1, though almost none of the
|
||||
original 386BSD specific code remains. This software has
|
||||
been essentially reimplemented from the 4.4 BSD Lite
|
||||
been essentially re-implemented from the 4.4 BSD Lite
|
||||
release provided by the Computer Science Research Group
|
||||
(CSRG) at the University of California, Berkeley and
|
||||
associated academic contributors.
|
||||
@ -31,7 +31,7 @@
|
||||
their support.
|
||||
|
||||
TRW Financial Systems, Inc. provided 130 PCs, three 68 GB
|
||||
fileservers, twelve ethernets, two routers and an ATM
|
||||
fileservers, twelve Ethernets, two routers and an ATM
|
||||
switch for debugging the diskless code. They also keep a
|
||||
couple of FreeBSD hackers alive and busy. Thanks!
|
||||
|
||||
@ -70,7 +70,7 @@
|
||||
|
||||
<sect><heading>The FreeBSD Developers</heading>
|
||||
|
||||
<p>These are the people who have commit privs and do the work on
|
||||
<p>These are the people who have commit privileges and do the work on
|
||||
FreeBSD source tree. All core team members are also developers.
|
||||
|
||||
<itemize>
|
||||
|
@ -1,9 +1,9 @@
|
||||
<!--
|
||||
# This is the sgml version of the ctm.FAQ file.
|
||||
#
|
||||
# Converted by Ollivier RObert <roberto@FreeBSD.ORG>
|
||||
# Converted by Ollivier Robert <roberto@FreeBSD.ORG>
|
||||
#
|
||||
# $Id: ctm.sgml,v 1.4 1995/08/29 01:42:33 jfieber Exp $
|
||||
# $Id: ctm.sgml,v 1.5 1995/10/16 09:11:22 jkh Exp $
|
||||
#
|
||||
# ----------------------------------------------------------------------------
|
||||
# "THE BEER-WARE LICENSE" (Revision 42):
|
||||
@ -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
|
||||
retreive the <tt/src-cur.0372R20.gz/ file, it's only 4Mb and it
|
||||
retrieve the <tt/src-cur.0372R20.gz/ file, it's 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,7 +110,7 @@
|
||||
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 diskspace.
|
||||
so you don't 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
|
||||
@ -125,7 +125,7 @@
|
||||
interface'' portions, as I have realized that I can't make up my
|
||||
mind on what options should do what, how and when...
|
||||
|
||||
That's really all there is to it. Everytime you get a new delta,
|
||||
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
|
||||
@ -176,7 +176,7 @@
|
||||
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.
|
||||
|
||||
If you have commit priviledges or are similary authorized by the
|
||||
If you have commit privileges or are similarly authorized by the
|
||||
FreeBSD core team, you can also get access to the CVS repository
|
||||
tree by the same means. Contact &a.phk;
|
||||
for details.
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: current.sgml,v 1.6 1995/10/16 09:01:52 jkh Exp $ -->
|
||||
<!-- $Id: current.sgml,v 1.7 1995/12/11 15:09:10 jkh Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@
|
||||
|
||||
THE FREEBSD CURRENT POLICY
|
||||
|
||||
Last updated: $Date: 1995/10/16 09:01:52 $
|
||||
Last updated: $Date: 1995/12/11 15:09:10 $
|
||||
|
||||
This document attempts to explain the rationale behind
|
||||
FreeBSD-current, what you should expect should you decide to run it,
|
||||
@ -25,7 +25,7 @@ snapshot of the working sources for FreeBSD. These include work in
|
||||
progress, experimental changes and transitional mechanisms that may or
|
||||
may not be present in the next official release of the software.
|
||||
While many of us compile almost daily from FreeBSD-current sources,
|
||||
there are periods of time when the sources are literally uncompilable.
|
||||
there are periods of time when the sources are literally un-compilable.
|
||||
These problems are generally resolved as expeditiously as possible,
|
||||
but whether or not FreeBSD-current sources bring disaster or greatly
|
||||
desired functionality can literally be a matter of which part of any
|
||||
|
@ -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.3 1995/08/29 01:42:35 jfieber Exp $
|
||||
$Id: dialup.sgml,v 1.4 1995/12/04 17:58:37 jfieber Exp $
|
||||
|
||||
<!DOCTYPE linuxdoc PUBLIC "-//Linux//DTD linuxdoc//EN">
|
||||
|
||||
@ -290,7 +290,7 @@ version 1.1.5 and higher, there are also initialization devices
|
||||
(<tt>/dev/ttyld?</tt> and <tt>/dev/cual0?</tt>). The initialization
|
||||
devices are used to initialize communications port parameters each
|
||||
time a port is opened, such as <tt>crtscts</tt> for modems which use
|
||||
<tt>CTS/RTS</tt> signalling for flow control. The locking devices are
|
||||
<tt>CTS/RTS</tt> signaling for flow control. The locking devices are
|
||||
used to lock flags on ports to prevent users or programs changing
|
||||
certain parameters; see the manual pages <tt/termios(4)/, <tt/sio(4)/,
|
||||
and <tt/stty(1)/ for information on the terminal settings, locking
|
||||
@ -440,7 +440,7 @@ parity; otherwise, the default is 7 bits, even parity.
|
||||
|
||||
The example above starts the communications rate at 19.2 Kbps (for a
|
||||
V.32bis connection), then cycles through 9600 bps (for V.32), 2400
|
||||
bps, 1200 bps, 300 bps, and back to 19.2 Kbps. Communcations rate
|
||||
bps, 1200 bps, 300 bps, and back to 19.2 Kbps. Communications rate
|
||||
cycling is implemented with the <tt/nx=/ (<bf/next table/) capability.
|
||||
Each of the lines uses a <tt/tc=/ (<bf/table continuation/) entry to
|
||||
pick up the rest of the ``standard'' settings for a particular data
|
||||
@ -519,7 +519,7 @@ kill -1 1
|
||||
|
||||
to send the signal. If this is your first time setting up the system,
|
||||
though, you may want to wait until your modem(s) are properly
|
||||
configured and connected before signalling <tt/init/.
|
||||
configured and connected before signaling <tt/init/.
|
||||
|
||||
<sect3><heading>Locked-Speed Config</heading>
|
||||
<p>
|
||||
@ -774,7 +774,7 @@ If you still can't get a <tt/login:/ prompt, check
|
||||
<item> The initial capability name specified in <tt>/etc/ttys</tt> for
|
||||
the line matches a name of a capability in <tt>/etc/gettytab</tt>
|
||||
|
||||
<item> Each <tt/nx=/ entry matches another <tt/gettytab/ capabilty
|
||||
<item> Each <tt/nx=/ entry matches another <tt/gettytab/ capability
|
||||
name
|
||||
|
||||
<item> Each <tt/tc=/ entry matches another <tt/gettytab/ capability
|
||||
@ -795,7 +795,7 @@ url="mailto:questions@freebsd.org" name="questions@FreeBSD.ORG"></tt>
|
||||
describing your modem and your problem, and the good folks on the list will
|
||||
try to help.
|
||||
|
||||
<sect1><heading>Acknowledgements</heading>
|
||||
<sect1><heading>Acknowledgments</heading>
|
||||
<p>
|
||||
|
||||
Thanks to these people for comments and advice:
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: diskless.sgml,v 1.1.1.1 1995/04/28 16:19:59 jfieber Exp $ -->
|
||||
<!-- $Id: diskless.sgml,v 1.2 1995/06/30 17:37:35 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>Diskless operation<label id="diskless"></heading>
|
||||
@ -28,7 +28,7 @@
|
||||
<itemize>
|
||||
<item>HP9000/8xx running HP-UX 9.04 or later (pre
|
||||
9.04 doesn't work)</item>
|
||||
<item>Sun/Solaries 2.3. (you may need to get
|
||||
<item>Sun/Solaris 2.3. (you may need to get
|
||||
bootp)</item>
|
||||
</itemize>
|
||||
|
||||
@ -61,8 +61,8 @@ server <X.X.X.X> - print/set bootp/tftp server address
|
||||
netmask <X.X.X.X> - print/set netmask
|
||||
hostname <name> - print/set hostname
|
||||
kernel <name> - print/set kernel name
|
||||
rootfs <ip:/fs> - print/set rootfilesystem
|
||||
swapfs <ip:/fs> - print/set swapfilesystem
|
||||
rootfs <ip:/fs> - print/set root filesystem
|
||||
swapfs <ip:/fs> - print/set swap filesystem
|
||||
swapsize <size> - set diskless swapsize in Kbytes
|
||||
diskboot - boot from disk
|
||||
autoboot - continue boot process
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: dma.sgml,v 1.1.2.2 1995/11/01 16:40:14 jfieber Exp $ -->
|
||||
<!-- $Id: dma.sgml,v 1.2 1995/11/20 01:10:12 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
@ -386,7 +386,7 @@
|
||||
un-masked. That DMA channel is now considered to be
|
||||
``armed'', and will respond when DRQ is asserted.
|
||||
|
||||
Refer to a hardware databook for precise programming
|
||||
Refer to a hardware data book for precise programming
|
||||
details for the 8237. You will also need to refer to the
|
||||
I/O port map for the PC system. This map describes where
|
||||
the DMA and Page Register ports are located. A complete
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: eresources.sgml,v 1.17 1995/12/11 15:09:12 jkh Exp $ -->
|
||||
<!-- $Id: eresources.sgml,v 1.18 1996/01/16 14:53:09 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt>
|
||||
@ -244,7 +244,7 @@ development for the future releases.
|
||||
|
||||
<tag/FREEBSD-ISP/ <em>Issues for Internet Service Providers</em><newline>
|
||||
This mailing list is for discussing topics relevant to Internet
|
||||
Serivce Providers (ISPs) using FreeBSD.
|
||||
Service Providers (ISPs) using FreeBSD.
|
||||
|
||||
<tag/FREEBSD-MULTIMEDIA/ <em>Multimedia discussions</em><newline>
|
||||
This is a forum about multimedia applications using FreeBSD.
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: esdi.sgml,v 1.3 1995/11/25 20:00:45 jkh Exp $ -->
|
||||
<!-- $Id: esdi.sgml,v 1.4 1995/12/04 17:58:38 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
@ -12,7 +12,7 @@
|
||||
This document describes the use of ESDI disks in combination
|
||||
with the FreeBSD operating system. Contrary to popular
|
||||
belief, this is possible and people are using ESDI based
|
||||
systems succesfully! This document tries to explain you
|
||||
systems successfully! This document tries to explain you
|
||||
how to do this.
|
||||
|
||||
If you find something missing, plain wrong or have useful
|
||||
@ -36,7 +36,7 @@
|
||||
Secondly some higher level commands are added, making the ESDI
|
||||
interface somewhat 'smarter' to the operating system driver
|
||||
writers. It is by no means as smart as SCSI by the way. ESDI
|
||||
is standardised by ANSI.
|
||||
is standardized by ANSI.
|
||||
|
||||
Capacities of the drives are boosted by putting more sectors
|
||||
on each track. Typical is 35 sectors per track, high capacity
|
||||
@ -51,13 +51,13 @@
|
||||
<sect3><heading>Physical connections</heading>
|
||||
<p>
|
||||
The ESDI interface uses two cables connected to each drive.
|
||||
One cable is a 34 pin flatcable edge connector that carries
|
||||
One cable is a 34 pin flat cable edge connector that carries
|
||||
the command and status signals from the controller to the
|
||||
drive and viceversa. The command cable is daisy chained
|
||||
drive and vice-versa. The command cable is daisy chained
|
||||
between all the drives. So, it forms a bus onto which all
|
||||
drives are connected.
|
||||
|
||||
The second cable is a a 20 pin flatcable edge connector that
|
||||
The second cable is a a 20 pin flat cable edge connector that
|
||||
carries the data to and from the drive. This cable is radially
|
||||
connected, so each drive has it's own direct connection to the
|
||||
controller.
|
||||
@ -89,7 +89,7 @@
|
||||
is not used.
|
||||
|
||||
So, one and <it>only</it> one drive, the one at
|
||||
the fartest end of the command
|
||||
the farthest end of the command
|
||||
cable has it's terminator installed/enabled. The controller
|
||||
automatically terminates the other end of the cable.
|
||||
Please note that this implies that the controller must be
|
||||
@ -111,7 +111,7 @@
|
||||
|
||||
<sect3><heading>ESDI speed variants</heading>
|
||||
<p>
|
||||
As briefly mentioned before, ESDI comes in two speed flavours.
|
||||
As briefly mentioned before, ESDI comes in two speed flavors.
|
||||
The older drives and controllers use a 10 Mbits/second
|
||||
data transfer rate. Newer stuff uses 15 Mbits/second.
|
||||
|
||||
@ -132,7 +132,7 @@
|
||||
In my case, the controller could not handle this number
|
||||
of sectors. It proved to work well except that it only
|
||||
used 35 sectors on each track. This meant losing a
|
||||
lot of diskspace.
|
||||
lot of disk space.
|
||||
|
||||
Once again, check the documentation of your hardware for
|
||||
more info. Going out-of-spec like in the example might
|
||||
@ -195,7 +195,7 @@
|
||||
<p>
|
||||
Translations, although not exclusively a ESDI-only problem,
|
||||
might give you real trouble.
|
||||
Translations come in multiple flavours. Most of them
|
||||
Translations come in multiple flavors. Most of them
|
||||
have in common that they attempt to work around the
|
||||
limitations posed upon disk geometries by the original
|
||||
IBM PC/AT design (thanks IBM!).
|
||||
@ -236,7 +236,7 @@
|
||||
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
|
||||
controller wrote this info onto the disk. On powerup it
|
||||
controller wrote this info onto the disk. On power-up it
|
||||
read the info and presented itself to the system based on
|
||||
the info from the disk.
|
||||
|
||||
@ -248,7 +248,7 @@
|
||||
(logically of course) of the bad one.
|
||||
|
||||
In most cases the remapping is done by using N-1 sectors on
|
||||
each track for actual datastorage, and sector N itself is
|
||||
each track for actual data storage, and sector N itself is
|
||||
the spare sector. N is the total number of sectors physically
|
||||
available on the track.
|
||||
The idea behind this is that the operating system sees
|
||||
@ -277,7 +277,7 @@
|
||||
numbers to the end of the FreeBSD slice.
|
||||
|
||||
When the disk is in operation, the disk accesses are checked
|
||||
against the table read from the disk. Whenever a blocknumber
|
||||
against the table read from the disk. Whenever a block number
|
||||
is requested that is in the bad144 list, a replacement block
|
||||
(also from the end of the FreeBSD slice) is used.
|
||||
In this way, the bad144 replacement scheme presents 'perfect'
|
||||
@ -340,7 +340,7 @@ disk wd3 at wdc1 drive 1
|
||||
<p>
|
||||
<sect3><heading>Adaptec 2320 controllers</heading>
|
||||
<p>
|
||||
I succesfully installed FreeBSD onto a ESDI disk controlled by a
|
||||
I successfully installed FreeBSD onto a ESDI disk controlled by a
|
||||
ACB-2320. No other operating system was present on the disk.
|
||||
|
||||
To do so I low level formatted the disk using NEFMT.EXE
|
||||
@ -351,7 +351,7 @@ disk wd3 at wdc1 drive 1
|
||||
BIOS to allow the BIOS to boot it.
|
||||
|
||||
Before using NEFMT.EXE I tried to format the disk using the
|
||||
ACB-2320 BIOS builtin formatter. This proved to be a showstopper,
|
||||
ACB-2320 BIOS builtin formatter. This proved to be a show stopper,
|
||||
because it didn't give me an option to disable spare sectoring.
|
||||
With spare sectoring enabled the FreeBSD installation
|
||||
process broke down on the bad144 run.
|
||||
@ -372,7 +372,7 @@ disk wd3 at wdc1 drive 1
|
||||
|
||||
<sect3><heading>Western Digital WD1007 controllers</heading>
|
||||
<p>
|
||||
I succesfully installed FreeBSD onto a ESDI disk controlled by a
|
||||
I successfully installed FreeBSD onto a ESDI disk controlled by a
|
||||
WD1007 controller. To be precise, it was a WD1007-WA2. Other
|
||||
variations of the WD1007 do exist.
|
||||
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: firewalls.sgml,v 1.1 1995/10/14 21:49:45 jfieber Exp $ -->
|
||||
<!-- $Id: firewalls.sgml,v 1.2 1995/11/01 00:42:17 gpalmer Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>Firewalls<label id="firewalls"></heading>
|
||||
@ -9,7 +9,7 @@ Firewalls are an area of increasing interest for people who are
|
||||
connected to the Internet, and are even finding applications on
|
||||
private networks to provide enhanced security. This section will
|
||||
hopefully explain what firewalls are, how to use them, and how to use
|
||||
the facilities provided in the FreeBSD kernel to impliment them.
|
||||
the facilities provided in the FreeBSD kernel to implement them.
|
||||
|
||||
<quote><bf>Note</bf>: People often think that having a firewall between
|
||||
your companies internal network and the ``Big Bad Internet'' will
|
||||
@ -41,7 +41,7 @@ generally more secure than normal authentication mechanisms.
|
||||
<p>FreeBSD comes with a kernel packet filter (known as <tt>IPFW</tt>),
|
||||
which is what the rest of this section will concentrate on. Proxy
|
||||
servers can be built on FreeBSD from third party software, but there
|
||||
is such a vareity of proxy servers available that it would be
|
||||
is such a variety of proxy servers available that it would be
|
||||
impossible to cover them in this document.
|
||||
|
||||
<sect2><heading>Packet filtering routers<label id="firewalls:packet_filters"></heading>
|
||||
@ -234,12 +234,12 @@ For the accounting chain, valid <em>actions</em> are:
|
||||
<tag/single/Count packets matching the address specifier.
|
||||
|
||||
<tag/bidirectional/Count packets matching the address specifier, and
|
||||
also packets travelling in the opposite direction (i.e. those going
|
||||
also packets traveling in the opposite direction (i.e. those going
|
||||
from ``destination'' to ``source'').
|
||||
|
||||
</descrip>
|
||||
|
||||
<p>Each <em>action</em> will be recognized by the shortest unambigious
|
||||
<p>Each <em>action</em> will be recognized by the shortest unambiguous
|
||||
prefix.
|
||||
|
||||
The <em>protocols</em> which can be specified are:
|
||||
@ -341,7 +341,7 @@ form. The valid <em>commands</em> are:
|
||||
<descrip>
|
||||
|
||||
<tag/list/List the chain rule entries. Unless the <bf>-s</bf> flag is
|
||||
given, the format is compatable with the command line syntax.
|
||||
given, the format is compatible with the command line syntax.
|
||||
|
||||
<tag/flush/Flush the chain rule entries.
|
||||
|
||||
@ -436,7 +436,7 @@ possible attacks and also modification of the firewall rules if your
|
||||
requirements alter.
|
||||
|
||||
<quote><bf>Note:</BF> If you use the logging versions of the
|
||||
<bf>accept</bf> command, it can generate <em>large</em> ammounts
|
||||
<bf>accept</bf> command, it can generate <em>large</em> amounts
|
||||
of log data as one log line will be generated for every packet
|
||||
that passes through the firewall, so large ftp/http transfers,
|
||||
etc, will really slow the system down. It also increases the
|
||||
@ -469,14 +469,14 @@ will allow the script to be fed into /bin/sh and reload the rules into
|
||||
the kernel. Perhaps not the most efficient way, but it works.
|
||||
|
||||
<p>The next problem is what your firewall should actually <bf>DO</bf>!
|
||||
This is largely dependant on what access to your network you want to
|
||||
This is largely dependent on what access to your network you want to
|
||||
allow from the outside, and how much access to the outside world you
|
||||
want to allow from the inside. Some general rules are:
|
||||
|
||||
<itemize>
|
||||
|
||||
<item>Block all incoming access to ports below 1000 for TCP. This is
|
||||
where most of the security sensitive services are, like finger, smtp
|
||||
where most of the security sensitive services are, like finger, SMTP
|
||||
(mail) and telnet.
|
||||
|
||||
<item>Block incoming SYN connections to ports between 1001 and 1024
|
||||
@ -488,7 +488,7 @@ outside, then extend the above suggestion to cover ports 1-1024.
|
||||
useful services that travel over UDP, and what useful traffic there is
|
||||
is normally a security threat (e.g. Suns RPC and NFS protocols). This
|
||||
has its disadvantages also, since UDP is a connectionless protocol,
|
||||
denying incoming UDP traffic also blocks the replies to outoing UDP
|
||||
denying incoming UDP traffic also blocks the replies to outgoing UDP
|
||||
traffic. This can cause a problem for people (on the inside)
|
||||
using external archie (prospero) servers. If you want to allow access
|
||||
to archie, you'll have to allow packets coming from ports 191 and 1525
|
||||
@ -497,7 +497,7 @@ you may consider allowing through, which comes from port 123.
|
||||
|
||||
<item>Block traffic to port 6000 from the outside. Port 6000 is the
|
||||
port used for access to X11 servers, and can be a security threat
|
||||
(especially if people are in the habbit of doing <tt>xhost +</tt> on
|
||||
(especially if people are in the habit of doing <tt>xhost +</tt> on
|
||||
their workstations). X11 can actually use a range of ports starting at
|
||||
6000, the upper limit being how many X displays you can run on the
|
||||
machine. The upper limit as defined by RFC 1700 (Assigned Numbers) is
|
||||
@ -509,7 +509,7 @@ normally fall outside the 1-1024 range specified above.
|
||||
|
||||
</itemize>
|
||||
|
||||
<p>Of course, if you want to make sure that no un-authorised traffic
|
||||
<p>Of course, if you want to make sure that no un-authorized traffic
|
||||
gets through the firewall, change the default policy to ``deny''. This
|
||||
will mean that any traffic which is allowed through has to be
|
||||
specified explicitly in an ``accept'' or ``allow'' filter rule. Which
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: handbook.sgml,v 1.37 1995/12/07 13:22:14 jkh Exp $ -->
|
||||
<!-- $Id: handbook.sgml,v 1.38 1995/12/21 17:16:29 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN" [
|
||||
@ -103,9 +103,9 @@ Web server">.
|
||||
|
||||
<chapt><heading>PPP and SLIP</heading>
|
||||
|
||||
<p>If your connection to the internet is through a modem, or
|
||||
<p>If your connection to the Internet is through a modem, or
|
||||
you wish to provide other people with dialup connections to
|
||||
the internet using FreeBSD, you have the option of using PPP
|
||||
the Internet using FreeBSD, you have the option of using PPP
|
||||
or SLIP. Furthermore, two varieties of PPP are provided:
|
||||
<em>user</em> (sometimes referred to as iijppp) and
|
||||
<em>kernel</em>. The procedures for configuring both types
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: history.sgml,v 1.11 1995/11/24 07:55:26 jkh Exp $ -->
|
||||
<!-- $Id: history.sgml,v 1.12 1995/12/29 01:27:38 jkh Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>A brief history of FreeBSD<label id="history"></heading>
|
||||
@ -105,7 +105,7 @@ contrary, and anyone is free to contribute code or ideas. Once a contributor
|
||||
has established a reasonable track record for reliability, we generally, in
|
||||
fact, give them write access to the project's CVS repository, where their
|
||||
changes can propagate automatically to other users of FreeBSD. Our
|
||||
centralised development model is designed for the convenience of the
|
||||
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
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: hw.sgml,v 1.10 1995/12/03 00:17:57 jkh Exp $ -->
|
||||
<!-- $Id: hw.sgml,v 1.11 1995/12/11 15:09:13 jkh Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
@ -10,7 +10,7 @@
|
||||
<p>Issues of hardware compatibility are among the most
|
||||
troublesome in the computer industry today and FreeBSD is by
|
||||
no means immune to trouble. In this respect, FreeBSD's
|
||||
advantage of being able to run on inexpensive commidity PC
|
||||
advantage of being able to run on inexpensive commodity PC
|
||||
hardware is also its liability when it comes to support for
|
||||
the amazing variety of components on the market. While it
|
||||
would be impossible to provide a exhaustive listing of
|
||||
@ -77,7 +77,7 @@ Slippery when wet. Beware of dog.
|
||||
but would welcome any reports on its performance.
|
||||
|
||||
<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'll 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 migrate drives from server to desktop as falling drive
|
||||
@ -113,7 +113,7 @@ Slippery when wet. Beware of dog.
|
||||
<p>I can recommend the <htmlurl url="http://www.smc.com/" name="SMC">
|
||||
Ultra 16 controller for any ISA application and the SMC EtherPower
|
||||
or Compex ENET32 cards for any serious PCI based networking. Both of
|
||||
the PCI cards are based around DEC's DC21041 ethernet controller
|
||||
the PCI cards are based around DEC's DC21041 Ethernet controller
|
||||
chip and other cards using it, such as the Zynx ZX342 or DEC DE435,
|
||||
will generally work as well.
|
||||
|
||||
@ -238,7 +238,7 @@ device sio11 at isa? port 0x138 tty flags 0xb05 irq 9 vector siointr
|
||||
1995.</em>
|
||||
|
||||
The procedures to make a Boca 16 pord board with
|
||||
FreeBSD are pretty straighforward, but you will need
|
||||
FreeBSD are pretty straightforward, but you will need
|
||||
a couple things to make it work:
|
||||
|
||||
<enum>
|
||||
@ -264,7 +264,7 @@ device sio11 at isa? port 0x138 tty flags 0xb05 irq 9 vector siointr
|
||||
If you do not already have a custom kernel
|
||||
configuration file set up, refer to <ref
|
||||
id="kernelconfig" name="Kernel Configuration"> for
|
||||
general procedurs. The following are the specifics
|
||||
general procedures. The following are the specifics
|
||||
for the Boca 16 board and assume you are using the
|
||||
kernel name MYKERNEL and editing with vi.
|
||||
|
||||
@ -285,7 +285,7 @@ to the config file.
|
||||
|
||||
The following example is for a Boca Board with an
|
||||
interrupt of 3, and a base IO address 100h. The
|
||||
IO address for Each port is +8 hexidecimal from
|
||||
IO address for Each port is +8 hexadecimal from
|
||||
the previous port, thus the 100h, 108h, 110h...
|
||||
addresses.
|
||||
|
||||
@ -370,7 +370,7 @@ sio16: type 16550A (multiport master)
|
||||
> more</tt> will show you the boot
|
||||
messages.</item>
|
||||
|
||||
<item>Next, apprepriate entries in <tt>/dev</tt> for the devices
|
||||
<item>Next, appropriate entries in <tt>/dev</tt> for the devices
|
||||
must be made using the <tt>/dev/MAKEDEV</tt>
|
||||
script. After becoming root:
|
||||
<tscreen>
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: install.sgml,v 1.20 1995/12/04 17:58:40 jfieber Exp $ -->
|
||||
<!-- $Id: install.sgml,v 1.21 1995/12/21 16:10:22 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
@ -35,7 +35,7 @@
|
||||
configurations"> section of this installation guide to
|
||||
be sure that your hardware is supported by FreeBSD. It
|
||||
may be helpful to make a list of any special cards you
|
||||
have installed, such as SCSI controllers, ethernet
|
||||
have installed, such as SCSI controllers, Ethernet
|
||||
adapters or sound cards. This list should include
|
||||
relevant configuration parameters such as interrupts
|
||||
(IRQ) and IO port addresses. </item>
|
||||
@ -160,7 +160,7 @@ Boot:
|
||||
To run the X-window system, eight megabytes of RAM is the
|
||||
recommended minimum.
|
||||
|
||||
Following is a list of all disk controllers and ethernet
|
||||
Following is a list of all disk controllers and Ethernet
|
||||
cards currently known to work with FreeBSD. Other
|
||||
configurations may very well work, and we have simply not
|
||||
received any indication of this.
|
||||
@ -230,7 +230,7 @@ Boot:
|
||||
time:
|
||||
|
||||
<itemize>
|
||||
<item>Soundblaster SCSI and ProAudio Spectrum SCSI (<tt>cd</tt>)
|
||||
<item>SoundBlaster SCSI and ProAudio Spectrum SCSI (<tt>cd</tt>)
|
||||
<item>Mitsumi (all models) proprietary interface (<tt>mcd</tt>)
|
||||
<item>Matsushita/Panasonic (Creative)
|
||||
CR-562/CR-563 proprietary interface (<tt>matcd</tt>)
|
||||
@ -247,7 +247,7 @@ Boot:
|
||||
|
||||
<item>Allied-Telesis AT1700 and RE2000 cards
|
||||
|
||||
<item>SMC Elite 16 WD8013 ethernet interface, and
|
||||
<item>SMC Elite 16 WD8013 Ethernet interface, and
|
||||
most other WD8003E, WD8003EBT, WD8003W, WD8013W,
|
||||
WD8003S, WD8003SBT and WD8013EBT based clones. SMC
|
||||
Elite Ultra is also supported.
|
||||
@ -297,7 +297,7 @@ Boot:
|
||||
Semiconductor are also supported.
|
||||
</itemize>
|
||||
|
||||
<p><em>Note:</em> FreeBSD does not currently suppport
|
||||
<p><em>Note:</em> FreeBSD does not currently support
|
||||
PnP (plug-n-play) features present on some ethernet
|
||||
cards. If your card has PnP and is giving you problems,
|
||||
try disabling its PnP features.
|
||||
@ -717,11 +717,11 @@ ftp://foo.bar.com:1234/pub/FreeBSD
|
||||
<item>Select a Custom or Express install, depending on
|
||||
whether or not you would like the installation to give
|
||||
you a high degree of control over each step of the
|
||||
installation or simply lead you through it, chosing
|
||||
installation or simply lead you through it, choosing
|
||||
reasonable defaults when possible. See details on
|
||||
both installation types below.
|
||||
|
||||
<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 important
|
||||
@ -771,7 +771,7 @@ ftp://foo.bar.com:1234/pub/FreeBSD
|
||||
your disk so far, nor will it until you give the
|
||||
final confirmation). All new or changed partition
|
||||
information will be written out, file systems will
|
||||
be created and/or non-destructively labelled
|
||||
be created and/or non-destructively labeled
|
||||
(depending on how you set their newfs flags in the
|
||||
Label Editor) and all selected distributions will
|
||||
be extracted.
|
||||
@ -796,7 +796,7 @@ ftp://foo.bar.com:1234/pub/FreeBSD
|
||||
altering your system <em>except</em> for ``Commit'',
|
||||
which will perform any requests to alter your system
|
||||
you may have made. Some of the menu options will also
|
||||
have direct `Write' commands available for commiting an
|
||||
have direct `Write' commands available for committing an
|
||||
operation immediately, but they should only be used if
|
||||
you are absolutely sure it is necessary. It is generally
|
||||
better to make your changes and then commit them all at
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: kernelconfig.sgml,v 1.6 1996/01/20 06:11:35 nate Exp $ -->
|
||||
<!-- $Id: kernelconfig.sgml,v 1.7 1996/01/20 06:28:11 nate Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
<!-- <!DOCTYPE linuxdoc PUBLIC '-//FreeBSD//DTD linuxdoc//EN'> -->
|
||||
<chapt><heading>Configuring the FreeBSD Kernel<label id="kernelconfig"></heading>
|
||||
@ -274,15 +274,15 @@
|
||||
<tag>options MATH_EMULATE</tag>
|
||||
|
||||
<p>This line allows the kernel to simulate a math
|
||||
coprocessor if your computer does not have one (386
|
||||
co-processor if your computer does not have one (386
|
||||
or 486SX). If you have a Pentium, a 486DX, or a
|
||||
386 or 486SX with a separate 387 or 487 chip, you
|
||||
can comment this line out.
|
||||
|
||||
<quote><em>Note:</em> The normal math coprocessor
|
||||
<quote><em>Note:</em> The normal math co-processor
|
||||
emulation routines that come with FreeBSD are
|
||||
<em>not</em> very accurate. If you do not have a
|
||||
math coprocessor, and you need the best accuracy,
|
||||
math co-processor, and you need the best accuracy,
|
||||
I recommend that you change this option to
|
||||
<tt>GPL_MATH_EMULATE</tt> to use the superior GNU
|
||||
math support, which is not included by default
|
||||
@ -297,7 +297,7 @@
|
||||
<tag>options BOUNCE_BUFFERS</tag>
|
||||
|
||||
<p>ISA devices and EISA devices operating in an ISA
|
||||
compatibilty mode can only perform DMA (Direct
|
||||
compatibility mode can only perform DMA (Direct
|
||||
Memory Access) to memory below 16 megabytes. This
|
||||
option enables such devices to work in systems with
|
||||
more than 16 megabytes of memory.
|
||||
@ -517,7 +517,7 @@
|
||||
drivers are for the so-called <em>proprietary</em>
|
||||
CD-ROM drives. These drives have their own
|
||||
controller card or might plug into a sound card
|
||||
such as the Soundblaster 16. They are <em>not</em>
|
||||
such as the SoundBlaster 16. They are <em>not</em>
|
||||
IDE or SCSI. Most older single-speed and
|
||||
double-speed CD-ROMs use these interfaces, while
|
||||
newer quad-speeds are likely to be <ref
|
||||
@ -538,7 +538,7 @@
|
||||
<tag>controller matcd0 at isa? port ? bio</tag>
|
||||
|
||||
<p>Matsushita/Panasonic CD-ROM (sold by Creative
|
||||
Labs for Soundblaster).
|
||||
Labs for SoundBlaster).
|
||||
|
||||
</descrip>
|
||||
|
||||
@ -949,7 +949,7 @@
|
||||
|
||||
<p>SoundBlaster digital audio.
|
||||
|
||||
<quote><em/Note:/ If your Soundblaster is on a
|
||||
<quote><em/Note:/ If your SoundBlaster is on a
|
||||
different IRQ (such as 5), change <tt>irq 7</tt>
|
||||
to, for example, <tt>irq 5</tt> and remove the
|
||||
<tt>conflicts</tt> keyword. Also, you must add
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: kerneldebug.sgml,v 1.5 1995/10/22 00:42:10 jfieber Exp $ -->
|
||||
<!-- $Id: kerneldebug.sgml,v 1.6 1996/01/03 11:10:30 gclarkii Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>Kernel Debugging<label id="kerneldebug"></heading>
|
||||
@ -330,7 +330,7 @@
|
||||
<tscreen><verb>
|
||||
x ,10
|
||||
</verb></tscreen>
|
||||
Similiarly, use
|
||||
Similarly, use
|
||||
<tscreen><verb>
|
||||
x/ia foofunc,10
|
||||
</verb></tscreen>
|
||||
@ -401,7 +401,7 @@
|
||||
is the final way out of disaster and almost the same as hitting
|
||||
the Big Red Button.
|
||||
|
||||
If you nead a short command summary, simply type
|
||||
If you need a short command summary, simply type
|
||||
<tscreen><verb>
|
||||
help
|
||||
</verb></tscreen>
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: nutshell.sgml,v 1.6 1995/09/17 10:56:37 davidg Exp $ -->
|
||||
<!-- $Id: nutshell.sgml,v 1.7 1995/12/19 09:22:23 gclarkii Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>FreeBSD in a nutshell<label id="nutshell"></heading>
|
||||
@ -20,7 +20,7 @@
|
||||
SHARED BETWEEN ALL users on the system.</item>
|
||||
<item>Complete <bf>TCP/IP networking</bf> including SLIP, PPP, NFS
|
||||
and NIS support. This means that your FreeBSD machine can
|
||||
interoperate easily with other systems as well act as an enterprise
|
||||
inter-operate easily with other systems as well act as an enterprise
|
||||
server, providing vital functions such as NFS (remote file access) and
|
||||
e-mail services or putting your organization on the Internet
|
||||
with WWW, ftp, routing and firewall (security) services.</item>
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: porting.sgml,v 1.11 1995/12/07 13:22:15 jkh Exp $ -->
|
||||
<!-- $Id: porting.sgml,v 1.12 1996/01/28 16:36:24 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect1><heading>Porting an existing piece of free software<label id="porting"></heading>
|
||||
@ -19,7 +19,7 @@ running under FreeBSD.
|
||||
|
||||
<p>What follows are some guidelines for creating a new port for
|
||||
FreeBSD 2.x . The <tt>${..}</tt> variable names you will
|
||||
see in this document all refer to various user-overridable defaults
|
||||
see in this document all refer to various user-overrideable defaults
|
||||
used (and documented) by <tt>/usr/share/mk/bsd.port.mk</tt>.
|
||||
Please refer to that file for more details on the inner workings of
|
||||
the ports collection.
|
||||
@ -27,7 +27,7 @@ the ports collection.
|
||||
<sect2>
|
||||
<heading>Before Starting the Port<label id="porting:starting"></heading>
|
||||
|
||||
<p>Note: Only a fraction of the overridable variables are
|
||||
<p>Note: Only a fraction of the overrideable variables are
|
||||
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
|
||||
@ -99,7 +99,7 @@ the ports collection.
|
||||
OK to use <tt>__FreeBSD__</tt> and `<tt>#if __FreeBSD__ >
|
||||
1</tt>' to detect a FreeBSD 2.x system.
|
||||
|
||||
If you need more granduarity in detecting FreeBSD systems since
|
||||
If you need more granularity in detecting FreeBSD systems since
|
||||
2.0-RELEASE you can use the following:
|
||||
|
||||
<tscreen><verb>
|
||||
@ -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.11 1995/12/07 13:22:15 jkh Exp $
|
||||
# $Id: porting.sgml,v 1.12 1996/01/28 16:36:24 jfieber Exp $
|
||||
#
|
||||
|
||||
DISTNAME= oneko-1.1b
|
||||
@ -911,7 +911,7 @@ lib/libtcl.so.7.3
|
||||
person who wrote this Makefile]
|
||||
# Whom: Satoshi Asami <asami@FreeBSD.ORG>
|
||||
#
|
||||
# $Id: porting.sgml,v 1.11 1995/12/07 13:22:15 jkh Exp $
|
||||
# $Id: porting.sgml,v 1.12 1996/01/28 16:36:24 jfieber Exp $
|
||||
[ ^^^^ don't worry about this...it will be automatically filled in by CVS when
|
||||
it is committed to our repository]
|
||||
#
|
||||
|
@ -1,7 +1,7 @@
|
||||
<!-- This is an SGML document in the linuxdoc DTD describing
|
||||
Printing with FreeBSD. By Sean Kelly, 1995.
|
||||
|
||||
$Id: printing.sgml,v 1.2 1995/10/01 22:16:19 jfieber Exp $
|
||||
$Id: printing.sgml,v 1.3 1995/12/04 17:58:47 jfieber Exp $
|
||||
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
@ -399,7 +399,7 @@ cd /dev
|
||||
<item>The <em/interrupt-driven/ method is the default
|
||||
with the GENERIC kernel. With this method, the
|
||||
operating system uses an IRQ line to determine when
|
||||
the printer's ready for data.
|
||||
the printer is ready for data.
|
||||
|
||||
<item>The <em/polled/ method directs the operating
|
||||
system to repeatedly ask the printer if it's ready
|
||||
@ -424,7 +424,7 @@ cd /dev
|
||||
<tt/lpt2/ for the third port, and so on.
|
||||
<itemize>
|
||||
<item>If you want interrupt-driven mode, add the <tt/irq/
|
||||
specifer:
|
||||
specifier:
|
||||
<tscreen>
|
||||
<tt>device lpt0 at isa? port? tty irq <it/N/ vector lptintr</tt>
|
||||
</tscreen>
|
||||
@ -495,7 +495,7 @@ showpage
|
||||
functionality, you can intermingle plain text with its
|
||||
escape sequences. PostScript cannot directly print
|
||||
plain text, and that's the kind of printer language for
|
||||
which we must make special accomodations.
|
||||
which we must make special accommodations.
|
||||
|
||||
<sect4><heading>Checking a Parallel Printer<label
|
||||
id="printing:checking:parallel"></heading>
|
||||
@ -657,7 +657,7 @@ tip printer
|
||||
printer, and note it in <tt>/etc/printcap</tt> with
|
||||
the <tt/lp/ capability; see <ref id="printing:device"
|
||||
name="Identifying the Printer Device">. Also, if the
|
||||
printer's on a serial port, set up the communication
|
||||
printer is on a serial port, set up the communication
|
||||
parameters with the <tt/fs/, <tt/fc/, <tt/xs/, and
|
||||
<tt/xc/ capabilities; see <ref id="printing:commparam"
|
||||
name="Configuring Spooler Communications Parameters">.
|
||||
@ -687,7 +687,7 @@ tip printer
|
||||
add an additional step to the simple setup outlined above:
|
||||
install an automatic plain-text--to--PostScript (or other
|
||||
printer language) conversion program. Section <ref
|
||||
id="printing:advanced:if-conversion" name="Accomodating
|
||||
id="printing:advanced:if-conversion" name="Accommodating
|
||||
Plain Text Jobs on PostScript Printers"> tells how to do
|
||||
this.
|
||||
|
||||
@ -960,7 +960,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
|
||||
input to the job to print, and its standard output to
|
||||
the printer device specified with the <tt/lp/
|
||||
capability. The filter is expected to read the job from
|
||||
standard input, peform any necessary translation for the
|
||||
standard input, perform any necessary translation for the
|
||||
printer, and write the results to standard output, which
|
||||
will get printed. For more information on the text
|
||||
filter, see section <ref id="printing:advanced:filters"
|
||||
@ -1069,13 +1069,13 @@ $%&ero;'()*+,-./01234567
|
||||
id="printing:troubleshooting"></heading>
|
||||
|
||||
<p> After performing the simple test with <tt/lptest/, you
|
||||
might've gotten one of the following results instead of
|
||||
might have gotten one of the following results instead of
|
||||
the correct printout:
|
||||
<descrip>
|
||||
<tag/It worked, after awhile; or, it didn't eject a full sheet./
|
||||
|
||||
The printer printed the above, but it sat for awhile
|
||||
and did nothing. In fact, you might've needed to
|
||||
and did nothing. In fact, you might have needed to
|
||||
press a PRINT REMAINING or FORM FEED button on the
|
||||
printer to get any results to appear.
|
||||
|
||||
@ -1231,7 +1231,7 @@ Printer received LF Printer prints CR + LF
|
||||
<tag/The printer lost characters./
|
||||
|
||||
While printing, the printer didn't print a few
|
||||
characters in each line. The problem might've
|
||||
characters in each line. The problem might have
|
||||
gotten worse as the printer ran, losing more and
|
||||
more characters.
|
||||
|
||||
@ -1552,7 +1552,7 @@ lpr -P bamboo -d fish-report.dvi
|
||||
|
||||
Print literal text data, including control characters.
|
||||
|
||||
<tag/<tt/-n// Print ditroff (device indepdendent troff) data.
|
||||
<tag/<tt/-n// Print ditroff (device independent troff) data.
|
||||
|
||||
<tag/-p/
|
||||
|
||||
@ -1743,7 +1743,7 @@ lpr -#3 parser.c parser.h
|
||||
This command is useful while you're testing a new
|
||||
printer or filter installation: disable the queue and
|
||||
submit jobs as root. Other users won't be able to
|
||||
submit jobs until you complete your testing and reenable
|
||||
submit jobs until you complete your testing and re-enable
|
||||
the queue with the <tt/enable/ command.
|
||||
|
||||
<tag/<tt/down <it/printer-name/ <it/message...///
|
||||
@ -1856,7 +1856,7 @@ lpr -#3 parser.c parser.h
|
||||
text by default. This presents a problem for PostScript
|
||||
(or other language-based printers) which can't directly
|
||||
print plain text. Section <ref
|
||||
id="printing:advanced:if-conversion" name="Accomodating
|
||||
id="printing:advanced:if-conversion" name="Accommodating
|
||||
Plain Text Jobs on PostScript Printers"> tells you what
|
||||
you should do to overcome this problem. I recommend
|
||||
reading this section if you have a PostScript printer.
|
||||
@ -2099,7 +2099,7 @@ lpr -#3 parser.c parser.h
|
||||
You should also specify the <tt/rw/ capability; that tells
|
||||
LPD to open the printer in read-write mode.
|
||||
|
||||
If you have a parralel PostScript printer (and therefore
|
||||
If you have a parallel PostScript printer (and therefore
|
||||
can't use two-way communication with the printer, which
|
||||
<tt/lprps/ needs), you can use the following shell script
|
||||
as the text filter:
|
||||
@ -2142,7 +2142,7 @@ fi
|
||||
<p> PostScript is the <it/de facto/ standard for high
|
||||
quality typesetting and printing. PostScript is, however,
|
||||
an <em/expensive/ standard. Thankfully, Alladin
|
||||
Enterprises has a free PostScript workalike called
|
||||
Enterprises has a free PostScript work-alike called
|
||||
<it/Ghostscript/ that runs with FreeBSD. Ghostscript can
|
||||
read most PostScript files and can render their pages onto
|
||||
a variety of devices, including many brands of
|
||||
@ -2343,7 +2343,7 @@ exec /usr/local/bin/dvips -f | /usr/local/libexec/lprps "$@"
|
||||
argument) on standard input, which is the job to print.
|
||||
It then starts the PostScript printer filter <tt/lprps/
|
||||
(see section <ref id="printing:advanced:if-conversion"
|
||||
name="Accomodating Plain Text Jobs on PostScript
|
||||
name="Accommodating Plain Text Jobs on PostScript
|
||||
Printers">) with the arguments LPD passed to this script.
|
||||
<tt/lprps/ will use those arguments to account for the
|
||||
pages printed.
|
||||
@ -2633,12 +2633,12 @@ exit 0
|
||||
this is probably <em/not/ what you want. In almost all
|
||||
cases, you need a text filter.
|
||||
|
||||
The program <tt/lpf/, whch we introduced earlier as a text
|
||||
The program <tt/lpf/, which we introduced earlier as a text
|
||||
filter, can also run as an output filter. If you need a
|
||||
quick-and-dirty output filter but don't want to write the
|
||||
byte detection and signal sending code, try <tt/lpf/. You
|
||||
can also wrap <tt/lpf/ in a shell script to handle any
|
||||
intialization codes the printer might require.
|
||||
initialization codes the printer might require.
|
||||
|
||||
<sect2><heading><tt/lpf/: a Text Filter<label
|
||||
id="printing:advanced:lpf"></heading>
|
||||
@ -3349,7 +3349,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
|
||||
By using the <tt/sc/ capability, we prevent the use of
|
||||
<tt/lpr -#/, but that still doesn't prevent users from
|
||||
running <tt/lpr/ multiple times, or from submitting the
|
||||
same file mutliple times in one job like this:
|
||||
same file multiple times in one job like this:
|
||||
<tscreen><verb>
|
||||
lpr forsale.sign forsale.sign forsale.sign forsale.sign forsale.sign
|
||||
</verb></tscreen>
|
||||
@ -3696,7 +3696,7 @@ total 337.00 154 $ 6.74
|
||||
|
||||
Compute charges with <it/price/ dollars per page or
|
||||
per foot instead of the price from the <tt/pc/
|
||||
capabilty in <tt>/etc/printcap</tt>, or two cents (the
|
||||
capability in <tt>/etc/printcap</tt>, or two cents (the
|
||||
default). You can specify <it/price/ as a floating
|
||||
point number.
|
||||
|
||||
@ -3737,7 +3737,7 @@ total 337.00 154 $ 6.74
|
||||
want to charge for printouts in this capability. You can
|
||||
override this value when you run <tt/pac/ with the <tt/-p/
|
||||
option. The units for the <tt/-p/ option are in dollars,
|
||||
though, not hundreths of cents. For example,
|
||||
though, not hundredths of cents. For example,
|
||||
<tscreen><verb>
|
||||
pac -p1.50
|
||||
</verb></tscreen>
|
||||
@ -3857,7 +3857,7 @@ pac -p1.50
|
||||
|
||||
<sect><heading>Acknowledgments</heading>
|
||||
|
||||
<p> I'd like to thank the following people who've assisted in
|
||||
<p> I'd like to thank the following people who have assisted in
|
||||
the development of this document:
|
||||
|
||||
<descrip>
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: relnotes.sgml,v 1.7 1995/11/20 01:10:28 jfieber Exp $ -->
|
||||
<!-- $Id: relnotes.sgml,v 1.8 1995/12/07 13:22:16 jkh Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
@ -534,7 +534,7 @@
|
||||
emulator is in its early stages and has not been
|
||||
extensively tested, but it is functional. Most of
|
||||
SCO's 3.2.2 binaries work, as does an old
|
||||
INFORMIX-2.10 for SCO. Further testing is nessesary
|
||||
INFORMIX-2.10 for SCO. Further testing is necessary
|
||||
to complete this project. There is also work under
|
||||
way for ELF and XOUT loaders, and most of the svr4
|
||||
syscall wrappers are written.
|
||||
@ -554,9 +554,9 @@
|
||||
you can!).
|
||||
|
||||
The preferred method to submit bug reports from a machine
|
||||
with internet mail connectivity is to use the send-pr
|
||||
with Internet mail connectivity is to use the send-pr
|
||||
command. Bug reports will be dutifully filed by our
|
||||
faithful bugfiler program and you can be sure that we'll
|
||||
faithful bug-filer program and you can be sure that we'll
|
||||
do our best to respond to all reported bugs as soon as
|
||||
possible.
|
||||
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id$ -->
|
||||
<!-- $Id: routing.sgml,v 1.1 1995/10/07 04:31:41 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
<!-- <!DOCTYPE linuxdoc PUBLIC '-//FreeBSD//DTD linuxdoc//EN'> -->
|
||||
|
||||
@ -161,7 +161,7 @@ host2.foobar.com link#1 UC 0 0
|
||||
ISP's Terminal Server. Your ISP has a local network at
|
||||
their site, which has, among other things, the server
|
||||
where you connect and a hardware device (T1-GW) attached
|
||||
to the ISP's internet feed.
|
||||
to the ISP's Internet feed.
|
||||
|
||||
The default routes for each of your machines will be:
|
||||
|
||||
@ -206,12 +206,12 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
||||
networks.
|
||||
|
||||
In one case, the machine as two ethernet cards, each
|
||||
having an address on the seperate subnets. Alternately,
|
||||
having an address on the separate subnets. Alternately,
|
||||
the machine may only have one ethernet card, and be using
|
||||
ifconfig aliasing. The former is used if two physically
|
||||
separate ethernet networks are in use, the latter if
|
||||
there is one physical network segment, but two logically
|
||||
seperate subnets.
|
||||
separate subnets.
|
||||
|
||||
Either way, routing tables are set up so that each subnet
|
||||
knows that this machine is the defined gateway (inbound
|
||||
@ -220,7 +220,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
||||
often used when we need to implement packet filtering or
|
||||
firewall security in either or both directions.
|
||||
|
||||
<sect1><heading>Routing propogation</heading>
|
||||
<sect1><heading>Routing propagation</heading>
|
||||
|
||||
<p>We have already talked about how we define our routes to
|
||||
the outside world, but not about how the outside world
|
||||
@ -242,7 +242,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
||||
information) that keeps track of all assigned
|
||||
address-spaces, and defines their point of connection to
|
||||
the Internet Backbone. The ``Backbone'' are the main
|
||||
trunk lines that carry internet traffic across the
|
||||
trunk lines that carry Internet traffic across the
|
||||
country, and around the world. Each backbone machine has
|
||||
a copy of a master set of tables, which direct traffic
|
||||
for a particular network to a specific backbone carrier,
|
||||
@ -252,7 +252,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
||||
It is the task of your service provider to advertise to
|
||||
the backbone sites that they are the point of connection
|
||||
(and thus the path inward) for your site. This is known
|
||||
as route propogation.
|
||||
as route propagation.
|
||||
|
||||
<!--
|
||||
<sect1><heading>Multicast Routing</heading>
|
||||
@ -260,7 +260,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
||||
|
||||
<sect1><heading>Troubleshooting</heading>
|
||||
|
||||
<p>Sometimes, there is a problem with routing propogation,
|
||||
<p>Sometimes, there is a problem with routing propagation,
|
||||
and some sites are unable to connect to you. Perhaps the
|
||||
most useful command for trying to figure out where a
|
||||
routing is breaking down is the <tt>traceroute(8)</tt>
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: scsi.sgml,v 1.9 1995/11/25 20:00:49 jkh Exp $ -->
|
||||
<!-- $Id: scsi.sgml,v 1.10 1995/12/04 17:58:50 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
@ -224,7 +224,7 @@
|
||||
is important to get clean signals on the bus, without
|
||||
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 travelling over your SCSI bus, you
|
||||
are. With 20Mbytes/sec traveling over your SCSI bus, you
|
||||
don't want signals echoing back.
|
||||
|
||||
Terminators come in various incarnations, with more or less
|
||||
@ -259,7 +259,7 @@
|
||||
by far the most misunderstood part of SCSI. And it is by far
|
||||
the simplest.. The rule is: <bf>every SCSI bus has 2 (two)
|
||||
terminators, one at each end of the bus.</bf> So, two and not
|
||||
one or three or whatever. Do yourself a favour and stick to
|
||||
one or three or whatever. Do yourself a favor and stick to
|
||||
this rule. It will save you endless grief, because wrong
|
||||
termination has the potential to introduce highly mysterious
|
||||
bugs.
|
||||
@ -456,7 +456,7 @@
|
||||
asked for a geometry , it is nearly always better to supply the
|
||||
geometry used by the BIOS, or <em>if the BIOS is never going to know
|
||||
about this disk</em>, (e.g. it is not a booting disk) to supply a
|
||||
ficticious geometry that is convenient.
|
||||
fictitious geometry that is convenient.
|
||||
|
||||
<sect3><heading>SCSI subsystem design</heading>
|
||||
<p>
|
||||
@ -476,7 +476,7 @@
|
||||
|
||||
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.
|
||||
|
||||
<sect3><heading>Kernel configuration</heading>
|
||||
<p>
|
||||
@ -554,7 +554,7 @@ device cd0 at scbus? [the first ever CDROM found, no wiring]
|
||||
to unit number 1. Note that <em>wired down devices need not
|
||||
be found</em>
|
||||
to get their unit number. The unit number for a wired down device
|
||||
is reserved for thet device, even if it is turned off at boot
|
||||
is reserved for that device, even if it is turned off at boot
|
||||
time. This allows the device to be turned on and brought
|
||||
on-line at a later time, without rebooting. Notice that a device's
|
||||
unit number has <em>no</em> relationship with it's target ID on
|
||||
@ -706,7 +706,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed
|
||||
<item>
|
||||
Check for loose connectors and cables.
|
||||
<item>
|
||||
Check and doublecheck the location and number of your terminators.
|
||||
Check and double check the location and number of your terminators.
|
||||
<item>
|
||||
Check if your bus has at least one supplier of terminator power
|
||||
(especially with external terminators.
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: skey.sgml,v 1.2 1995/09/26 19:12:28 wollman Exp $ -->
|
||||
<!-- $Id: skey.sgml,v 1.3 1995/10/07 04:31:56 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
<!--
|
||||
Copyright 1995 Massachusetts Institute of Technology
|
||||
@ -146,7 +146,7 @@ command:
|
||||
$ keyinit -s
|
||||
Updating wollman:
|
||||
Old key: kh94741
|
||||
Reminder you need the 6 english words from the skey command.
|
||||
Reminder you need the 6 English words from the skey command.
|
||||
Enter sequence count from 1 to 9999: 100 ) I typed this
|
||||
Enter new key [default kh94742]:
|
||||
s/key 100 kh94742
|
||||
@ -294,7 +294,7 @@ authentication.
|
||||
<p>The second line (`<tt/permit user/') allows the specified user to
|
||||
use UNIX passwords at any time. Generally speaking, this should only
|
||||
be used for people who are either unable to use the `<tt/key/'
|
||||
program, like those with dumb terminls, or those who are uneducable.
|
||||
program, like those with dumb terminals, or those who are uneducable.
|
||||
|
||||
<p>The third line (`<tt/permit port/') allows all users logging in on
|
||||
the specified terminal line to use UNIX passwords; this would be used
|
||||
|
@ -12,7 +12,7 @@ Setting up FreeBSD as a SLIP Server
|
||||
-->
|
||||
|
||||
<sect><heading>Setting up a SLIP server<label id="slips"></heading>
|
||||
<p><em>Contribudted by &a.ghelmer;.<newline>
|
||||
<p><em>Contributed by &a.ghelmer;.<newline>
|
||||
v1.0, 15 May 1995.</em>
|
||||
|
||||
This document provides suggestions for setting up SLIP Server services
|
||||
@ -489,7 +489,7 @@ appropriate for your system. Please see the manual page for
|
||||
<tt>gated</tt> for information on <tt>gated</tt>'s command-line
|
||||
parameters.
|
||||
|
||||
<sect1><heading>Acknowledgements</heading>
|
||||
<sect1><heading>Acknowledgments</heading>
|
||||
|
||||
<p>
|
||||
Thanks to these people for comments and advice regarding this tutorial:
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: submitters.sgml,v 1.13 1996/01/05 08:36:27 jkh Exp $ -->
|
||||
<!-- $Id: submitters.sgml,v 1.14 1996/01/05 08:47:37 jkh Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt><heading>Contributing to FreeBSD<label id="submitters"></heading>
|
||||
@ -27,8 +27,8 @@ highly specialized types of kernel development. No matter what your
|
||||
skill level, there's almost certainly something you can do to help the
|
||||
project!
|
||||
|
||||
<p>Commmercial entities engaged in FreeBSD-related enterprises are
|
||||
also encouraged to contact us. Need a special extention to make your
|
||||
<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
|
||||
let us know! We may be able to work cooperatively on some aspect of
|
||||
@ -87,7 +87,7 @@ for V86 machines by the protected mode kernel.
|
||||
text areas in the default kernel executable so that that portion
|
||||
of the kernel address space may be recovered at a later time,
|
||||
after hardware specific protected mode drivers have been loaded
|
||||
and activated. This includes seperation of BIOS based drivers
|
||||
and activated. This includes separation of BIOS based drivers
|
||||
from each other, since it is better to run with a BIOS based
|
||||
driver in all cases than to not run at all.
|
||||
|
||||
@ -107,9 +107,9 @@ device space resource usage by fixed devices.
|
||||
Specifically, a device centric registration mechanism for timer
|
||||
and sound and other system critical service providers. Consider
|
||||
Timer2 and Timer0 and speaker services as one example of a single
|
||||
monithic service provider.
|
||||
monolithic service provider.
|
||||
|
||||
<item>A kernel exported symbol space in the kernel data space acessable
|
||||
<item>A kernel exported symbol space in the kernel data space accessible
|
||||
by an LKM loader mechanism that does relocation and symbol space
|
||||
manipulation. The intent of this interface is to support the
|
||||
ability to demand load and unload kernel modules.
|
||||
@ -145,7 +145,7 @@ preemption).
|
||||
somewhat handled by changing PCMCIA bridging rules and power
|
||||
management event handling. But there are things like detecting
|
||||
internal vs. external display and picking a different screen
|
||||
resoloution based on that fact, not spinning down the disk if
|
||||
resolution based on that fact, not spinning down the disk if
|
||||
the machine is in dock, and allowing dock-based cards to disappear
|
||||
without affecting the machines ability to boot (same issue for
|
||||
PCMCIA).
|
||||
@ -155,7 +155,7 @@ PCMCIA).
|
||||
<item>A "make world" that "makes the world" (rename the current one
|
||||
to "make regress" if that's all it is good for).
|
||||
|
||||
<item>A 4M (preferrably smaller!) memory footprint.
|
||||
<item>A 4M (preferably smaller!) memory footprint.
|
||||
|
||||
</enum>
|
||||
|
||||
@ -340,7 +340,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.13 1996/01/05 08:36:27 jkh Exp $
|
||||
$Id: submitters.sgml,v 1.14 1996/01/05 08:47:37 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>.
|
||||
@ -392,7 +392,7 @@ this in a note accompanying your donation. Thanks!
|
||||
|
||||
<sect2><heading>Donating hardware</heading>
|
||||
|
||||
<p>Donations of hardware in any of the 3 following catagories are also gladly
|
||||
<p>Donations of hardware in any of the 3 following categories are also gladly
|
||||
accepted by the FreeBSD Project:
|
||||
|
||||
<itemize>
|
||||
@ -414,7 +414,7 @@ such items as we'll 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>
|
||||
<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
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: userppp.sgml,v 1.4 1995/12/04 17:58:52 jfieber Exp $ -->
|
||||
<!-- $Id: userppp.sgml,v 1.5 1995/12/06 22:01:50 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect>Setting up user PPP<label id="userppp">
|
||||
@ -14,13 +14,13 @@
|
||||
because I am not really much of an authority on PPP. I've 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
|
||||
details, so I hope that by writing this and haveing others
|
||||
details, so I hope that by writing this and having others
|
||||
flesh out some of the information I'm going to learn something
|
||||
as well.
|
||||
-->
|
||||
|
||||
<p>User PPP was intruduced to FreeBSD in release 2.0.5 as an
|
||||
addition to the exisiting kernel implementation of PPP. So,
|
||||
<p>User PPP was introduced to FreeBSD in release 2.0.5 as an
|
||||
addition to the existing kernel implementation of PPP. So,
|
||||
what is different about this new PPP that warrants its
|
||||
addition? To quote from the manual page:
|
||||
|
||||
@ -63,7 +63,7 @@
|
||||
|
||||
<item>Your ISP's netmask setting
|
||||
|
||||
<item>IP adresses of one or more nameservers
|
||||
<item>IP addresses of one or more nameservers
|
||||
|
||||
<item>If your ISP allocates you a static IP address and/or hostname then
|
||||
you will need that as well. If not, you will need to know from what
|
||||
@ -262,7 +262,7 @@ protocol: ppp
|
||||
written in the <tt>chat(8)</tt> language.
|
||||
|
||||
<tag/Line 10:/ Sets the default timeout (in seconds) for the connection. So
|
||||
the connectioned will be closed automatically after 120 seconds
|
||||
the connection will be closed automatically after 120 seconds
|
||||
of inactivity.
|
||||
|
||||
<tag/Line 11:/ Sets the interface addresses. The string x.x.x.x should be
|
||||
|
Loading…
Reference in New Issue
Block a user