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

Rid blank lines of whitespace.

Browse source 
(Translation teams:  You can ignore this commit.)
This commit is contained in:
Chris Costello 1999-11-07 01:54:56 +00:00
parent b822a1769d
commit 7cfb0ff20b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=6023
51 changed files with 2206 additions and 2206 deletions
Download patch file Download diff file Expand all files Collapse all files

74
en_US.ISO8859-1/articles/contributing/article.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.125 1999/10/31 05:02:06 jdp Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.126 1999/11/02 23:45:01 jim Exp $
-->
<chapter id="contrib">
@ -50,7 +50,7 @@
interested in working on one of the tasks you see here, send mail to the
coordinator listed by clicking on their names. If no coordinator has
been appointed, maybe you would like to volunteer?</para>
<sect2>
<title>High priority tasks</title>
@ -69,7 +69,7 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Filesystem problems. Overall coordination: &a.fs;</para>
@ -88,7 +88,7 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Implement Int13 vm86 disk driver. Coordinator:
&a.hackers;</para>
@ -129,11 +129,11 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Kernel issues. Overall coordination: &a.hackers;</para>
</listitem>
<listitem>
<para>Add more pro-active security infrastructure. Overall
coordination: &a.security;</para>
@ -214,7 +214,7 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>PCMCIA/PCCARD. Coordinators: &a.msmith; and &a.phk;</para>
@ -248,7 +248,7 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Advanced Power Management. Coordinators: &a.msmith; and
&a.phk;</para>
@ -292,17 +292,17 @@
network cards. The same thing for NDIS drivers and NetWare SCSI
drivers.</para>
</listitem>
<listitem>
<para>An "upgrade system" option that works on Linux boxes instead
of just previous rev FreeBSD boxes.</para>
</listitem>
<listitem>
<para>Symmetric Multiprocessing with kernel preemption (requires
kernel preemption).</para>
</listitem>
<listitem>
<para>A concerted effort at support for portable computers. This is
somewhat handled by changing PCMCIA bridging rules and power
@ -334,21 +334,21 @@
the latest release from it and report any failures in the
process.</para>
</listitem>
<listitem>
<para>Read the freebsd-bugs mailing list. There might be a
problem you can comment constructively on or with patches you
can test. Or you could even try to fix one of the problems
yourself.</para>
</listitem>
<listitem>
<para>Read through the FAQ and Handbook periodically. If anything
is badly explained, out of date or even just completely wrong, let
us know. Even better, send us a fix (SGML is not difficult to
learn, but there is no objection to ASCII submissions).</para>
</listitem>
<listitem>
<para>Help translate FreeBSD documentation into your native language
(if not already available) &mdash; just send an email to &a.doc;
@ -357,7 +357,7 @@
by doing this &mdash; in fact, the documentation most in need of
translation is the installation instructions.</para>
</listitem>
<listitem>
<para>Read the freebsd-questions mailing list and &ng.misc
occasionally (or even regularly). It can be very satisfying to
@ -365,19 +365,19 @@
sometimes you may even learn something new yourself! These forums
can also be a source of ideas for things to work on.</para>
</listitem>
<listitem>
<para>If you know of any bugfixes which have been successfully
applied to -current but have not been merged into -stable after a
decent interval (normally a couple of weeks), send the committer a
polite reminder.</para>
</listitem>
<listitem>
<para>Move contributed software to <filename>src/contrib</filename>
in the source tree.</para>
</listitem>
<listitem>
<para>Make sure code in <filename>src/contrib</filename> is up to
date.</para>
@ -386,23 +386,23 @@
<listitem>
<para>Look for year 2000 bugs (and fix any you find!)</para>
</listitem>
<listitem>
<para>Build the source tree (or just part of it) with extra warnings
enabled and clean up the warnings.</para>
</listitem>
<listitem>
<para>Fix warnings for ports which do deprecated things like using
gets() or including malloc.h.</para>
</listitem>
<listitem>
<para>If you have contributed any ports, send your patches back to
the original author (this will make your life easier when they
bring out the next version)</para>
</listitem>
<listitem>
<para>Suggest further tasks for this list!</para>
</listitem>
@ -434,7 +434,7 @@
<para>Contributions to the system generally fall into one or more of the
following 6 categories:</para>
<sect2 id="contrib-general">
<title>Bug reports and general commentary</title>
@ -508,7 +508,7 @@
<screen>&prompt.user; <userinput>diff -c oldfile newfile</userinput></screen>
or
<screen>&prompt.user; <userinput>diff -c -r olddir newdir</userinput></screen>
would generate such a set of context diffs for the given source file
@ -567,7 +567,7 @@
participation by commercial interests who might eventually be
inclined to invest something of their own into FreeBSD.</para>
</listitem>
<listitem>
<para>The GNU Public License, or &ldquo;GPL&rdquo;. This license is
not quite as popular with us due to the amount of extra effort
@ -637,7 +637,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<sect3>
<title><anchor id="donations">Donating funds</title>
<para>While the FreeBSD Project is not a 501(c)(3) (charitable)
corporation and hence cannot offer special tax incentives for any
donations made, any such donations will be gratefully accepted on
@ -660,12 +660,12 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<city>Concord</city>
<state>CA</state>, <postcode>94520</postcode>
</address>
<para>(currently using the Walnut Creek CDROM address until a PO box
can be opened)</para>
<para>Wire transfers may also be sent directly to:</para>
<address>
<otheraddr>Bank Of America</otheraddr>
<otheraddr>Concord Main Office</otheraddr>
@ -676,7 +676,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<otheraddr>Routing #: 121-000-358</otheraddr>
<otheraddr>Account #: 01411-07441 (FreeBSD, Inc.)</otheraddr>
</address>
<para>Any correspondence related to donations should be sent to &a.jkh,
either via email or to the FreeBSD, Inc. postal address given above.
</para>
@ -688,7 +688,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<sect3>
<title>Donating hardware</title>
<para>Donations of hardware in any of the 3 following categories are
also gladly accepted by the FreeBSD Project:</para>
@ -722,7 +722,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<sect3>
<title>Donating Internet access</title>
<para>We can always use new mirror sites for FTP, WWW or
<command>cvsup</command>. If you would like to be such a mirror,
please contact the FreeBSD project administrators
@ -783,7 +783,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<listitem>
<para><emphasis>Direct funding:</emphasis></para>
<para>The following individuals and businesses have generously
contributed direct funding to the project:</para>
@ -897,11 +897,11 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<listitem>
<para><emphasis>Hardware contributors:</emphasis></para>
<para>The following individuals and businesses have generously
contributed hardware for testing and device driver
development/support:</para>
<itemizedlist>
<listitem>
<para>Walnut Creek CDROM for providing the Pentium P5-90 and
@ -968,7 +968,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<listitem>
<para><emphasis>Special contributors:</emphasis></para>
<itemizedlist>
<listitem>
<para><ulink url="http://www.cdrom.com/">Walnut Creek CDROM</ulink>
@ -1069,7 +1069,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
4.4BSD-Lite release provided by the Computer Science Research Group
(CSRG) at the University of California, Berkeley and associated academic
contributors.</para>
<para>There are also portions of NetBSD and OpenBSD that have been
integrated into FreeBSD as well, and we would therefore like to thank
all the contributors to NetBSD and OpenBSD for their work.</para>

40
en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml,v 1.18 1999/09/06 06:52:59 peter Exp $
-->
<chapter id="kerneldebug">
@ -55,7 +55,7 @@
some 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 memory will be wasted.</para>
<para>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 one in
order to get your system up and running again, boot it only into single
@ -186,7 +186,7 @@
<varlistentry>
<term>line 20:</term>
<listitem>
<para>This is the location of function <function>trap()</function>
in the stack trace.</para>
@ -195,7 +195,7 @@
<varlistentry>
<term>line 36:</term>
<listitem>
<para>Force usage of a new stack frame; this is no longer necessary
now. The stack frames are supposed to point to the right
@ -210,7 +210,7 @@
<varlistentry>
<term>line 52:</term>
<listitem>
<para>The pointer looks suspicious, but happens to be a valid
address.</para>
@ -219,7 +219,7 @@
<varlistentry>
<term>line 56:</term>
<listitem>
<para>However, it obviously points to garbage, so we have found our
error! (For those unfamiliar with that particular piece of code:
@ -251,7 +251,7 @@
<para>What do you do if a kernel dumped core but you did not expect it,
and it is therefore not compiled using <command>config -g</command>? Not
everything is lost here. Do not panic!</para>
<para>Of course, you still need to enable crash dumps. See above on the
options you have to specify in order to do this.</para>
@ -271,14 +271,14 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols</
faulting one but some debugging symbols. You should at least verify the
old and new sizes with the &man.size.1; command. If there is a
mismatch, you probably need to give up here.</para>
<para>Go and examine the dump as described above. The debugging symbols
might be incomplete for some places, as can be seen in the stack trace
in the example above where some functions are displayed without line
numbers and argument lists. If you need more debugging symbols, remove
the appropriate object files and repeat the <command>kgdb</command>
session until you know enough.</para>
<para>All this is not guaranteed to work, but it will do it fine in most
cases.</para>
</sect1>
@ -290,14 +290,14 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols</
high level of user interface, there are some things it cannot do. The
most important ones being breakpointing and single-stepping kernel
code.</para>
<para>If you need to do low-level debugging on your kernel, there is an
on-line debugger available called DDB. It allows to setting
breakpoints, single-stepping kernel functions, examining and changing
kernel variables, etc. However, it cannot access kernel source files,
and only has access to the global and static symbols, not to the full
debug information like <command>kgdb</command>.</para>
<para>To configure your kernel to include DDB, add the option line
<programlisting>
@ -318,7 +318,7 @@ options DDB</programlisting>
<option>-d</option> right at the boot prompt. The kernel will start up
in debug mode and enter DDB prior to any device probing. Hence you can
even debug the device probe/attach functions.</para>
<para>The second scenario is a hot-key on the keyboard, usually
Ctrl-Alt-ESC. For syscons, this can be remapped; some of the
distributed maps do this, so watch out. There is an option available
@ -327,11 +327,11 @@ options DDB</programlisting>
in the kernel config file). It is not the default since there are a lot
of crappy serial adapters around that gratuitously generate a BREAK
condition, for example when pulling the cable.</para>
<para>The third way is that any panic condition will branch to DDB if the
kernel is configured to use it. For this reason, it is not wise to
configure a kernel with DDB for a machine running unattended.</para>
<para>The DDB commands roughly resemble some <command>gdb</command>
commands. The first thing you probably need to do is to set a
breakpoint:</para>
@ -344,7 +344,7 @@ options DDB</programlisting>
<literal>a-f</literal> need to be preceded with <literal>0x</literal>
(this is optional for other numbers). Simple expressions are allowed,
for example: <literal>function-name + 0x103</literal>.</para>
<para>To continue the operation of an interrupted kernel, simply
type:</para>
@ -419,11 +419,11 @@ options DDB</programlisting>
specifies the size of the data to be written, the first following
expression is the address to write to and the remainder is interpreted
as data to write to successive memory locations.</para>
<para>If you need to know the current registers, use:</para>
<screen><userinput>show reg</userinput></screen>
<para>Alternatively, you can display a single register value by e.g.
<screen><userinput>p $eax</userinput></screen>
@ -468,7 +468,7 @@ options DDB</programlisting>
<para>is the final way out of disaster and almost the same as hitting the
Big Red Button.</para>
<para>If you need a short command summary, simply type:</para>
<screen><userinput>help</userinput></screen>
@ -493,7 +493,7 @@ options DDB</programlisting>
with all the symbols in it, and the other one is the target machine that
simply runs a similar copy of the very same kernel (but stripped of the
debugging information).</para>
<para>You should configure the kernel in question with <command>config
-g</command>, include <option>DDB</option> into the configuration, and
compile it as usual. This gives a large blurb of a binary, due to the
@ -573,7 +573,7 @@ text_addr = 0xf5109020? (y or n) <userinput>y</userinput>
<sect1>
<title>Debugging a Console Driver</title>
<para>Since you need a console driver to run DDB on, things are more
complicated if the console driver itself is failing. You might remember
the use of a serial console (either with modified boot blocks, or by

38
en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.11 1999/09/06 06:53:02 peter Exp $
-->
<chapter id="policies">
@ -20,27 +20,27 @@
<para>If a particular portion of the FreeBSD distribution is being
maintained by a person or group of persons, they can communicate this
fact to the world by adding a
<programlisting>
MAINTAINER= email-addresses</programlisting>
line to the <filename>Makefile</filename>s covering this portion of the
source tree.</para>
<para>The semantics of this are as follows:</para>
<para>The maintainer owns and is responsible for that code. This means
that he is responsible for fixing bugs and answer problem reports
pertaining to that piece of the code, and in the case of contributed
software, for tracking new versions, as appropriate.</para>
<para>Changes to directories which have a maintainer defined shall be sent
to the maintainer for review before being committed. Only if the
maintainer does not respond for an unacceptable period of time, to
several emails, will it be acceptable to commit changes without review
by the maintainer. However, it is suggested that you try and have the
changes reviewed by someone else if at all possible.</para>
<para>It is of course not acceptable to add a person or group as
maintainer unless they agree to assume this duty. On the other hand it
doesn't have to be a committer and it can easily be a group of
@ -58,11 +58,11 @@ MAINTAINER= email-addresses</programlisting>
actively being maintained outside the FreeBSD project. For historical
reasons, we call this <emphasis>contributed</emphasis> software. Some
examples are perl, gcc and patch.</para>
<para>Over the last couple of years, various methods have been used in
dealing with this type of software and all have some number of
advantages and drawbacks. No clear winner has emerged.</para>
<para>Since this is the case, after some debate one of these methods has
been selected as the &ldquo;official&rdquo; method and will be required
for future imports of software of this kind. Furthermore, it is
@ -72,7 +72,7 @@ MAINTAINER= email-addresses</programlisting>
&ldquo;official&rdquo; versions of the source by everyone (even without
cvs access). This will make it significantly easier to return changes
to the primary developers of the contributed software.</para>
<para>Ultimately, however, it comes down to the people actually doing the
work. If using this model is particularly unsuited to the package being
dealt with, exceptions to these rules may be granted only with the
@ -93,28 +93,28 @@ MAINTAINER= email-addresses</programlisting>
<para>The <application>Tcl</application> embedded programming
language will be used as example of how this model works:</para>
<para><filename>src/contrib/tcl</filename> contains the source as
distributed by the maintainers of this package. Parts that are entirely
not applicable for FreeBSD can be removed. In the case of Tcl, the
<filename>mac</filename>, <filename>win</filename> and
<filename>compat</filename> subdirectories were eliminated before the
import</para>
<para><filename>src/lib/libtcl</filename> contains only a "bmake style"
<filename>Makefile</filename> that uses the standard
<filename>bsd.lib.mk</filename> makefile rules to produce the library
and install the documentation.</para>
<para><filename>src/usr.bin/tclsh</filename> contains only a bmake style
<filename>Makefile</filename> which will produce and install the
<command>tclsh</command> program and its associated man-pages using the
standard <filename>bsd.prog.mk</filename> rules.</para>
<para><filename>src/tools/tools/tcl_bmake</filename> contains a couple of
shell-scripts that can be of help when the tcl software needs updating.
These are not part of the built or installed software.</para>
<para>The important thing here is that the
<filename>src/contrib/tcl</filename> directory is created according to
the rules: It is supposed to contain the sources as distributed (on a
@ -133,7 +133,7 @@ MAINTAINER= email-addresses</programlisting>
be patched into the FreeBSD checked out version and "committed", as this
destroys the vendor branch coherency and makes importing future versions
rather difficult as there will be conflicts.</para>
<para>Since many packages contain files that are meant for compatibility
with other architectures and environments that FreeBSD, it is
permissible to remove parts of the distribution tree that are of no
@ -148,7 +148,7 @@ MAINTAINER= email-addresses</programlisting>
check in such utilities (as necessary) in the
<filename>src/tools</filename> directory along with the port itself so
that it is available to future maintainers.</para>
<para>In the <filename>src/contrib/tcl</filename> level directory, a file
called <filename>FREEBSD-upgrade</filename> should be added and it
should states things like:</para>
@ -177,7 +177,7 @@ MAINTAINER= email-addresses</programlisting>
with the contributed source. Rather you should <command>cvs add
FREEBSD-upgrade ; cvs ci</command> after the initial import. Example
wording from <filename>src/contrib/cpio</filename> is below:</para>
<programlisting>
This directory contains virgin sources of the original distribution files
on a "vendor" branch. Do not, under any circumstances, attempt to upgrade
@ -316,12 +316,12 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
<para><emphasis>Contributed by &a.asami;, &a.peter;, and &a.obrien; 9
December 1996.</emphasis></para>
<para>If you are adding shared library support to a port or other piece of
software that doesn't have one, the version numbers should follow these
rules. Generally, the resulting numbers will have nothing to do with
the release version of the software.</para>
<para>The three principles of shared library building are:</para>
<itemizedlist>

44
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.15 1999/09/06 06:52:53 peter Exp $
-->
<chapter id="advanced-networking">
@ -12,7 +12,7 @@
<para><emphasis>Contributed by &a.gryphon;. 6 October
1995.</emphasis></para>
<para>For one machine to be able to find another, there must be a
mechanism in place to describe how to get from one to the other. This is
called Routing. A &ldquo;route&rdquo; is a defined pair of addresses: a
@ -25,7 +25,7 @@
We will talk a little bit more about default routes later on. There are
also three types of gateways: individual hosts, interfaces (also called
&ldquo;links&rdquo;), and ethernet hardware addresses.</para>
<sect2>
<title>An example</title>
@ -325,7 +325,7 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
can lead to serious network problems, particularly with NFS. This
difficulty is not specific to FreeBSD, but FreeBSD systems are affected
by it.</para>
<para>The problem nearly always occurs when (FreeBSD) PC systems are
networked with high-performance workstations, such as those made by
Silicon Graphics, Inc., and Sun Microsystems, Inc. The NFS mount will
@ -336,7 +336,7 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
many systems, there is no way to shut down the client gracefully once
this problem has manifested itself. The only solution is often to reset
the client, because the NFS situation cannot be resolved.</para>
<para>Though the &ldquo;correct&rdquo; solution is to get a higher
performance and capacity Ethernet adapter for the FreeBSD system, there
is a simple workaround that will allow satisfactory operation. If the
@ -347,13 +347,13 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
specified using the fourth field of the <filename>fstab</filename> entry
on the client for automatic mounts, or by using the <option>-o</option>
parameter of the mount command for manual mounts.</para>
<para>It should be noted that there is a different problem, sometimes
mistaken for this one, when the NFS servers and clients are on different
networks. If that is the case, make <emphasis>certain</emphasis> that
your routers are routing the necessary UDP information, or you will not
get anywhere, no matter what else you are doing.</para>
<para>In the following examples, <hostid>fastws</hostid> is the host
(interface) name of a high-performance workstation, and
<hostid>freebox</hostid> is the host (interface) name of a FreeBSD
@ -364,7 +364,7 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
cases, note that additional options, such as <option>hard</option> or
<option>soft</option> and <option>bg</option> may be desirable in your
application.</para>
<para>Examples for the FreeBSD system (<hostid>freebox</hostid>) as the
client: in <filename>/etc/fstab</filename> on freebox:</para>
@ -387,7 +387,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0</programlisting>
<para>Nearly any 16-bit Ethernet adapter will allow operation without the
above restrictions on the read or write size.</para>
<para>For anyone who cares, here is what happens when the failure occurs,
which also explains why it is unrecoverable. NFS typically works with a
&ldquo;block&rdquo; size of 8k (though it may do fragments of smaller
@ -407,7 +407,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0</programlisting>
<para>By keeping the unit size below the Ethernet packet size limitation,
we ensure that any complete Ethernet packet received can be acknowledged
individually, avoiding the deadlock situation.</para>
<para>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 guaranteed on NFS &ldquo;units&rdquo;. When an overrun
@ -425,7 +425,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0</programlisting>
allow you to boot your FreeBSD machine over the network and run FreeBSD
without having a disk on your client. Under 2.0 it is now possible to
have local swap. Swapping over NFS is also still supported.</para>
<para>Supported Ethernet cards include: Western Digital/SMC 8003, 8013,
8216 and compatibles; NE1000/NE2000 and compatibles (requires
recompile)</para>
@ -451,7 +451,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0</programlisting>
</listitem>
</itemizedlist>
</step>
<step>
<para>Set up a bootp server to provide the client with IP, gateway,
netmask.</para>
@ -467,7 +467,7 @@ diskless:\
:gw=192.1.2.5:\
:vm=rfc1048:</programlisting>
</step>
<step>
<para>Set up a TFTP server (on same machine as bootp server) to
provide booting information to client. The name of this file is
@ -572,7 +572,7 @@ hostname myclient.mydomain</programlisting>
rootfs 192.1.2.3:/rootfs/myclient
hostname myclient.mydomain</programlisting>
</step>
<step>
<para>Ensure that your NFS server has exported the root (and swap if
applicable) filesystems to your client, and that the client has
@ -610,7 +610,7 @@ hostname myclient.mydomain</programlisting>
<screen>&prompt.root; <userinput>chmod 0600 /swapfs/swap.192.1.2.4</userinput></screen>
</step>
<step>
<para>Unpack the root filesystem in the directory the client will
use for its root filesystem (<filename>/rootfs/myclient</filename>
@ -634,7 +634,7 @@ hostname myclient.mydomain</programlisting>
</listitem>
</itemizedlist>
</step>
<step>
<para>Run <command>netboot.com</command> on the client or make an
EPROM from the <filename>netboot.rom</filename> file</para>
@ -671,7 +671,7 @@ hostname myclient.mydomain</programlisting>
<para>A good resource for information on ISDN technology and hardware is
<ulink url="http://alumni.caltech.edu/~dank/isdn/">Dan Kegel's ISDN
Page</ulink>.</para>
<para>A quick simple roadmap to ISDN follows:</para>
<itemizedlist>
@ -734,7 +734,7 @@ hostname myclient.mydomain</programlisting>
<para>In case you are interested in adding support for a different ISDN
protocol, a currently unsupported ISDN PC card or otherwise enhancing
isdn4bsd, please get in touch with <email>hm@kts.org</email>.</para>
<para>A majordomo maintained mailing list is available. To join the
list, send mail to <email>majordomo@FreeBSD.org</email> and
specify:</para>
@ -782,7 +782,7 @@ subscribe freebsd-isdn</programlisting>
<listitem>
<para>Motorola BitSurfer and Bitsurfer Pro</para>
</listitem>
<listitem>
<para>Adtran</para>
</listitem>
@ -857,7 +857,7 @@ subscribe freebsd-isdn</programlisting>
<example>
<title>Branch office or Home network</title>
<para>Network is 10 Base T Ethernet. Connect router to network cable
with AUI/10BT transceiver, if necessary.</para>
@ -880,9 +880,9 @@ ISDN BRI line</programlisting>
<example>
<title>Head office or other lan</title>
<para>Network is Twisted Pair Ethernet.</para>
<!-- This should be a graphic -->
<programlisting>
-------Novell Server

22
en_US.ISO8859-1/books/handbook/backups/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml,v 1.12 1999/09/10 00:56:44 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml,v 1.13 1999/10/26 21:39:59 nik Exp $
-->
<chapter id="backups">
@ -337,7 +337,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
most widely used backup strategy. There are no initial costs. There
is no backup schedule to follow. Just say no. If something happens
to your data, grin and bear it!</para>
<para>If your time and your data is worth little to nothing, then
&ldquo;Do nothing&rdquo; is the most suitable backup program for your
computer. But beware, Unix is a useful tool, you may find that within
@ -377,7 +377,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<sect3>
<title>Before the Disaster</title>
<para>There are only four steps that you need to perform in
preparation for any disaster that may occur.</para>
@ -581,14 +581,14 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
<sect3>
<title>After the Disaster</title>
<para>The key question is: did your hardware survive? You have been
doing regular backups so there is no need to worry about the
software.</para>
<para>If the hardware has been damaged. First, replace those parts
that have been damaged.</para>
<para>If your hardware is okay, check your floppies. If you are using
a custom boot floppy, boot single-user (type <literal>-s</literal>
at the <prompt>boot:</prompt> prompt). Skip the following
@ -605,7 +605,7 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
located in <filename>/mnt2/stand</filename>.</para>
<para>Recover each filesystem separately.</para>
<para>Try to &man.mount.8; (e.g. <command>mount /dev/da0a
/mnt</command>) the root partition of your first disk. If the
disklabel was damaged, use &man.disklabel.8; to re-partition and
@ -617,7 +617,7 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
/dev/sa0</command>). Unmount the filesystem (e.g. <command>umount
/mnt</command>) Repeat for each filesystem that was
damaged.</para>
<para>Once your system is running, backup your data onto new tapes.
Whatever caused the crash or data loss may strike again. An another
hour spent now, may save you from further distress later.</para>
@ -625,7 +625,7 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
<sect3>
<title>* I did not prepare for the Disaster, What Now?</title>
<para></para>
</sect3>
</sect2>
@ -645,11 +645,11 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
<para>The media is unreliable, especially over long periods of
time</para>
</listitem>
<listitem>
<para>Backing up and restoring is very slow</para>
</listitem>
<listitem>
<para>They have a very limited capacity (the days of backing up
an entire hard disk onto a dozen or so floppies has long since

8
en_US.ISO8859-1/books/handbook/basics/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml,v 1.11 1999/09/06 06:52:54 peter Exp $
-->
<chapter id="basics">
@ -79,7 +79,7 @@
documentation, so &man.chmod.1; refers to the
<command>chmod</command> user command and &man.chmod.2; refers to the
system call.</para>
<para>This is fine if you know the name of the command and simply wish to
know how to use it, but what if you cannot recall the command name? You
can use <command>man</command> to search for keywords in the command
@ -92,7 +92,7 @@
have the keyword &ldquo;mail&rdquo; in their descriptions. This is
actually functionally equivalent to using the <command>apropos</command>
command.</para>
<para>So, you are looking at all those fancy commands in
<filename>/usr/bin</filename> but do not even have the faintest idea
what most of them actually do? Simply do a
@ -116,7 +116,7 @@
<command>info</command> command or, if you installed
<command>emacs</command>, the info mode of
<command>emacs</command>.</para>
<para>To use the &man.info.1; command, simply type:</para>
<screen>&prompt.user; <userinput>info</userinput></screen>

74
en_US.ISO8859-1/books/handbook/contrib/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.125 1999/10/31 05:02:06 jdp Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.126 1999/11/02 23:45:01 jim Exp $
-->
<chapter id="contrib">
@ -50,7 +50,7 @@
interested in working on one of the tasks you see here, send mail to the
coordinator listed by clicking on their names. If no coordinator has
been appointed, maybe you would like to volunteer?</para>
<sect2>
<title>High priority tasks</title>
@ -69,7 +69,7 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Filesystem problems. Overall coordination: &a.fs;</para>
@ -88,7 +88,7 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Implement Int13 vm86 disk driver. Coordinator:
&a.hackers;</para>
@ -129,11 +129,11 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Kernel issues. Overall coordination: &a.hackers;</para>
</listitem>
<listitem>
<para>Add more pro-active security infrastructure. Overall
coordination: &a.security;</para>
@ -214,7 +214,7 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>PCMCIA/PCCARD. Coordinators: &a.msmith; and &a.phk;</para>
@ -248,7 +248,7 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Advanced Power Management. Coordinators: &a.msmith; and
&a.phk;</para>
@ -292,17 +292,17 @@
network cards. The same thing for NDIS drivers and NetWare SCSI
drivers.</para>
</listitem>
<listitem>
<para>An "upgrade system" option that works on Linux boxes instead
of just previous rev FreeBSD boxes.</para>
</listitem>
<listitem>
<para>Symmetric Multiprocessing with kernel preemption (requires
kernel preemption).</para>
</listitem>
<listitem>
<para>A concerted effort at support for portable computers. This is
somewhat handled by changing PCMCIA bridging rules and power
@ -334,21 +334,21 @@
the latest release from it and report any failures in the
process.</para>
</listitem>
<listitem>
<para>Read the freebsd-bugs mailing list. There might be a
problem you can comment constructively on or with patches you
can test. Or you could even try to fix one of the problems
yourself.</para>
</listitem>
<listitem>
<para>Read through the FAQ and Handbook periodically. If anything
is badly explained, out of date or even just completely wrong, let
us know. Even better, send us a fix (SGML is not difficult to
learn, but there is no objection to ASCII submissions).</para>
</listitem>
<listitem>
<para>Help translate FreeBSD documentation into your native language
(if not already available) &mdash; just send an email to &a.doc;
@ -357,7 +357,7 @@
by doing this &mdash; in fact, the documentation most in need of
translation is the installation instructions.</para>
</listitem>
<listitem>
<para>Read the freebsd-questions mailing list and &ng.misc
occasionally (or even regularly). It can be very satisfying to
@ -365,19 +365,19 @@
sometimes you may even learn something new yourself! These forums
can also be a source of ideas for things to work on.</para>
</listitem>
<listitem>
<para>If you know of any bugfixes which have been successfully
applied to -current but have not been merged into -stable after a
decent interval (normally a couple of weeks), send the committer a
polite reminder.</para>
</listitem>
<listitem>
<para>Move contributed software to <filename>src/contrib</filename>
in the source tree.</para>
</listitem>
<listitem>
<para>Make sure code in <filename>src/contrib</filename> is up to
date.</para>
@ -386,23 +386,23 @@
<listitem>
<para>Look for year 2000 bugs (and fix any you find!)</para>
</listitem>
<listitem>
<para>Build the source tree (or just part of it) with extra warnings
enabled and clean up the warnings.</para>
</listitem>
<listitem>
<para>Fix warnings for ports which do deprecated things like using
gets() or including malloc.h.</para>
</listitem>
<listitem>
<para>If you have contributed any ports, send your patches back to
the original author (this will make your life easier when they
bring out the next version)</para>
</listitem>
<listitem>
<para>Suggest further tasks for this list!</para>
</listitem>
@ -434,7 +434,7 @@
<para>Contributions to the system generally fall into one or more of the
following 6 categories:</para>
<sect2 id="contrib-general">
<title>Bug reports and general commentary</title>
@ -508,7 +508,7 @@
<screen>&prompt.user; <userinput>diff -c oldfile newfile</userinput></screen>
or
<screen>&prompt.user; <userinput>diff -c -r olddir newdir</userinput></screen>
would generate such a set of context diffs for the given source file
@ -567,7 +567,7 @@
participation by commercial interests who might eventually be
inclined to invest something of their own into FreeBSD.</para>
</listitem>
<listitem>
<para>The GNU Public License, or &ldquo;GPL&rdquo;. This license is
not quite as popular with us due to the amount of extra effort
@ -637,7 +637,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<sect3>
<title><anchor id="donations">Donating funds</title>
<para>While the FreeBSD Project is not a 501(c)(3) (charitable)
corporation and hence cannot offer special tax incentives for any
donations made, any such donations will be gratefully accepted on
@ -660,12 +660,12 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<city>Concord</city>
<state>CA</state>, <postcode>94520</postcode>
</address>
<para>(currently using the Walnut Creek CDROM address until a PO box
can be opened)</para>
<para>Wire transfers may also be sent directly to:</para>
<address>
<otheraddr>Bank Of America</otheraddr>
<otheraddr>Concord Main Office</otheraddr>
@ -676,7 +676,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<otheraddr>Routing #: 121-000-358</otheraddr>
<otheraddr>Account #: 01411-07441 (FreeBSD, Inc.)</otheraddr>
</address>
<para>Any correspondence related to donations should be sent to &a.jkh,
either via email or to the FreeBSD, Inc. postal address given above.
</para>
@ -688,7 +688,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<sect3>
<title>Donating hardware</title>
<para>Donations of hardware in any of the 3 following categories are
also gladly accepted by the FreeBSD Project:</para>
@ -722,7 +722,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<sect3>
<title>Donating Internet access</title>
<para>We can always use new mirror sites for FTP, WWW or
<command>cvsup</command>. If you would like to be such a mirror,
please contact the FreeBSD project administrators
@ -783,7 +783,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<listitem>
<para><emphasis>Direct funding:</emphasis></para>
<para>The following individuals and businesses have generously
contributed direct funding to the project:</para>
@ -897,11 +897,11 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<listitem>
<para><emphasis>Hardware contributors:</emphasis></para>
<para>The following individuals and businesses have generously
contributed hardware for testing and device driver
development/support:</para>
<itemizedlist>
<listitem>
<para>Walnut Creek CDROM for providing the Pentium P5-90 and
@ -968,7 +968,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<listitem>
<para><emphasis>Special contributors:</emphasis></para>
<itemizedlist>
<listitem>
<para><ulink url="http://www.cdrom.com/">Walnut Creek CDROM</ulink>
@ -1069,7 +1069,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
4.4BSD-Lite release provided by the Computer Science Research Group
(CSRG) at the University of California, Berkeley and associated academic
contributors.</para>
<para>There are also portions of NetBSD and OpenBSD that have been
integrated into FreeBSD as well, and we would therefore like to thank
all the contributors to NetBSD and OpenBSD for their work.</para>

190
en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.31 1999/09/26 18:41:18 nik Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.32 1999/10/29 09:29:15 jkh Exp $
-->
<chapter id="cutting-edge">
@ -46,7 +46,7 @@
part of the source tree and for whom keeping &ldquo;current&rdquo;
is an absolute requirement.</para>
</listitem>
<listitem>
<para>Members of the FreeBSD group who are active testers, willing
to spend time working through problems in order to ensure that
@ -54,7 +54,7 @@
who wish to make topical suggestions on changes and the general
direction of FreeBSD.</para>
</listitem>
<listitem>
<para>Peripheral members of the FreeBSD (or some other) group who
merely wish to keep an eye on things and use the current sources
@ -74,11 +74,11 @@
there is some cool new feature in there and you want to be the
first on your block to have it.</para>
</listitem>
<listitem>
<para>A quick way of getting bug fixes.</para>
</listitem>
<listitem>
<para>In any way &ldquo;officially supported&rdquo; by us. We do
our best to help people genuinely in one of the 3
@ -125,7 +125,7 @@ subscribe cvs-all</programlisting>
how to subscribe and unsubscribe to the various other mailing
lists we support.</para>
</listitem>
<listitem>
<para>Grab the sources from <hostid
role="fqdn">ftp.FreeBSD.org</hostid>. You can do this in three
@ -174,7 +174,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
</listitem>
</orderedlist>
</listitem>
<listitem>
<para>Essentially, if you need rapid on-demand access to the source
and communications bandwidth is not a consideration, use
@ -249,7 +249,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<title>Using FreeBSD-stable</title>
<orderedlist>
<listitem>
<para>Join the &a.stable;. This will keep you informed of
build-dependencies that may appear in <emphasis>stable</emphasis>
@ -274,7 +274,7 @@ subscribe cvs-all</programlisting>
how to subscribe and unsubscribe to the various other mailing
lists we support.</para>
</listitem>
<listitem>
<para>If you are installing a new system and want it to be as stable
as possible, you can simply grab the latest dated branch snapshot
@ -331,14 +331,14 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
</listitem>
</orderedlist>
</listitem>
<listitem>
<para>Essentially, if you need rapid on-demand access to the source
and communications bandwidth is not a consideration, use
<command>cvsup</command> or <command>ftp</command>. Otherwise,
use <application>CTM</application>.</para>
</listitem>
<listitem>
<para>Before compiling stable, read the Makefile in
<filename>/usr/src</filename> carefully. You should at least run
@ -356,14 +356,14 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<title>Synchronizing Source Trees over the Internet</title>
<para><emphasis>Contributed by &a.jkh;.</emphasis></para>
<para>There are various ways of using an Internet (or email) connection to
stay up-to-date with any given area of the FreeBSD project sources, or
all areas, depending on what interests you. The primary services we
offer are <link linkend="anoncvs">Anonymous CVS</link>, <link
linkend="cvsup">CVSup</link>, and <link
linkend="ctm">CTM</link>.</para>
<para><application>Anonymous CVS</application> and
<application>CVSup</application> use the <emphasis>pull</emphasis> model
of updating sources. In the case of <application>CVSup</application>
@ -380,7 +380,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
from a remote CVS repository. <application>CVSup</application> can do
this far more efficiently, but <application>Anonymous CVS</application>
is easier to use.</para>
<para><application>CTM</application>, on the other hand, does not
interactively compare the sources you have with those on the master
archive or otherwise pull them across.. Instead, a script which
@ -404,7 +404,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
will have to start from scratch (from the most recent CVS &ldquo;base
delta&rdquo;) and rebuild it all with CTM or, with anoncvs, simply
delete the bad bits and resync.</para>
<para>For more information on <application>Anonymous CVS</application>,
<application>CTM</application>, and <application>CVSup</application>,
please see one of the following sections:</para>
@ -416,7 +416,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title><anchor id="anoncvs-intro">Introduction</title>
<para>Anonymous CVS (or, as it is otherwise known,
<emphasis>anoncvs</emphasis>) is a feature provided by the CVS
utilities bundled with FreeBSD for synchronizing with a remote CVS
@ -454,7 +454,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title><anchor id="anoncvs-usage">Using Anonymous CVS</title>
<para>Configuring &man.cvs.1; to use an Anonymous CVS repository is a
simple matter of setting the <envar>CVSROOT</envar> environment
variable to point to one of the FreeBSD project's
@ -467,7 +467,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
anoncvs@anoncvs.FreeBSD.org:/cvs</para>
</listitem>
</itemizedlist>
<para>Since CVS allows one to &ldquo;check out&rdquo; virtually any
version of the FreeBSD sources that ever existed (or, in some cases,
will exist <!-- smiley -->:), you need to be familiar with the
@ -481,7 +481,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
the latest revision on a given line of development, at any given
time. Because a branch tag does not refer to a specific revision,
it may mean something different tomorrow than it means today.</para>
<para>Here are the branch tags that users might be interested
in:</para>
@ -523,10 +523,10 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
</listitem>
</varlistentry>
</variablelist>
<para>Here are the revision tags that users might be interested
in:</para>
<variablelist>
<varlistentry>
<term>RELENG_3_3_0_RELEASE</term>
@ -659,7 +659,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
</listitem>
</varlistentry>
</variablelist>
<para>When you specify a branch tag, you normally receive the latest
versions of the files on that line of development. If you wish to
receive some past version, you can do so by specifying a date with
@ -669,7 +669,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Examples</title>
<para>While it really is recommended that you read the manual page for
&man.cvs.1; thoroughly before doing anything, here are some
quick examples which essentially show how to use Anonymous
@ -684,7 +684,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
&prompt.user; <userinput>cvs co ls</userinput>
&prompt.user; <userinput>cvs release -d ls</userinput></screen>
</example>
<example>
<title>Checking out the version of ls(1) in the 2.2-stable
branch:</title>
@ -694,7 +694,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
&prompt.user; <userinput>cvs co -rRELENG_2_2 ls</userinput>
&prompt.user; <userinput>cvs release -d ls</userinput></screen>
</example>
<example>
<title>Creating a list of changes (as unidiffs) to &man.ls.1;</title>
@ -716,10 +716,10 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Other Resources</title>
<para>The following additional resources may be helpful in learning
CVS:</para>
<itemizedlist>
<listitem>
<para><ulink
@ -756,7 +756,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Why should I use <application>CTM</application>?</title>
<para><application>CTM</application> will give you a local copy of the
FreeBSD source trees. There are a number of &ldquo;flavors&rdquo;
of the tree available. Whether you wish to track the entire cvs
@ -781,7 +781,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>What do I need to use <application>CTM</application>?</title>
<para>You will need two things: The <application>CTM</application>
program and the initial deltas to feed it (to get up to
&ldquo;current&rdquo; levels).</para>
@ -807,7 +807,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/">ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/</ulink></para>
<para>or see section <link linkend="mirrors-ctm">mirrors</link>.</para>
<para>FTP the relevant directory and fetch the
<filename>README</filename> file, starting from there.</para>
@ -880,9 +880,9 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Using <application>CTM</application> in your daily life</title>
<para>To apply the deltas, simply say:</para>
<screen>&prompt.root; <userinput>cd /where/ever/you/want/the/stuff</userinput>
&prompt.root; <userinput>ctm -v -v /where/you/store/your/deltas/src-xxx.*</userinput></screen>
@ -918,7 +918,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Keeping your local changes</title>
<para>As a developer one would like to experiment with and change
files in the source tree. <application>CTM</application> supports
local modifications in a limited way: before checking for the
@ -935,7 +935,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Other interesting <application>CTM</application> options</title>
<sect4>
<title>Finding out exactly what would be touched by an
update</title>
@ -949,7 +949,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
pre- or post- process the modified files in any manner, or just
are feeling a tad paranoid <!-- smiley -->:-).</para>
</sect4>
<sect4>
<title>Making backups before updating</title>
@ -961,7 +961,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
touched by a given <application>CTM</application> delta to
<filename>backup-file</filename>.</para>
</sect4>
<sect4>
<title>Restricting the files touched by an update</title>
@ -993,9 +993,9 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Future plans for <application>CTM</application></title>
<para>Tons of them:</para>
<itemizedlist>
<listitem>
<para>Use some kind of authentication into the CTM system, so as
@ -1007,7 +1007,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
became confusing and counter intuitive.</para>
</listitem>
</itemizedlist>
<para>The bad news is that I am very busy, so any help in doing this
will be most welcome. And do not forget to tell me what you want
also...</para>
@ -1015,7 +1015,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Miscellaneous stuff</title>
<para>All the &ldquo;DES infected&rdquo; (e.g. export controlled)
source is not included. You will get the
&ldquo;international&rdquo; version only. If sufficient interest
@ -1028,7 +1028,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Thanks!</title>
<variablelist>
<varlistentry>
<term>&a.bde;</term>
@ -1081,7 +1081,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3 id="cvsup-intro">
<title>Introduction</title>
<para><application>CVSup</application> is a software package for
distributing and updating source trees from a master CVS repository
on a remote server host. The FreeBSD sources are maintained in a
@ -1119,7 +1119,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3 id="cvsup-install">
<title>Installation</title>
<para>The easiest way to install <application>CVSup</application> if
you are running FreeBSD 2.2 or later is to use either <ulink
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ports-current/net/cvsup.tar">the
@ -1178,16 +1178,16 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupd-bin-16.0.tar.gz">ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupd-bin-16.0.tar.gz</ulink> (server).</para>
</listitem>
</itemizedlist>
<para>as well as from the many FreeBSD <link linkend="mirrors-ftp">FTP
mirror sites</link> around the world.</para>
<para>Most users will need only the client. These executables are
entirely self-contained, and they will run on any version of FreeBSD
from FreeBSD-2.1.0 to FreeBSD-current.</para>
<para>In summary, your options for installing CVSup are:</para>
<itemizedlist>
<listitem>
<para>FreeBSD-2.2 or later: static binary, port, or
@ -1206,7 +1206,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3 id="cvsup-config">
<title>CVSup Configuration</title>
<para><application>CVSup</application>'s operation is controlled by a
configuration file called the <filename>supfile</filename>.
Beginning with FreeBSD-2.2, there are some sample
@ -1214,7 +1214,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
url="file:/usr/share/examples/cvsup/">/usr/share/examples/cvsup/</ulink>.
These examples are also available from <ulink
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/">ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/</ulink> if you are on a pre-2.2 system.</para>
<para>The information in a <filename>supfile</filename> answers the
following questions for cvsup:</para>
@ -1244,7 +1244,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
your status files?</link></para>
</listitem>
</itemizedlist>
<para>In the following sections, we will construct a typical
<filename>supfile</filename> by answering each of these questions in
turn. First, we describe the overall structure of a
@ -1290,7 +1290,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<filename>supfile</filename> for receiving and updating the main
source tree of <link
linkend="current">FreeBSD-current</link>.</para>
<itemizedlist>
<listitem>
<para>Which files do you want to receive?<anchor
@ -1695,7 +1695,7 @@ cvs-crypto</programlisting>
<sect3>
<title>Running <application>CVSup</application></title>
<para>You are now ready to try an update. The command line for doing
this is quite simple:</para>
@ -1716,7 +1716,7 @@ cvs-crypto</programlisting>
trial run without touching your precious files. Just create an
empty directory somewhere convenient, and name it as an extra
argument on the command line:</para>
<screen>&prompt.root; <userinput>mkdir /var/tmp/dest</userinput>
&prompt.root; <userinput>cvsup supfile /var/tmp/dest</userinput></screen>
@ -1750,7 +1750,7 @@ cvs-crypto</programlisting>
<para>There are plenty of other options available. For a brief list
of them, type <command>cvsup -H</command>. For more detailed
descriptions, see the manual page.</para>
<para>Once you are satisfied with the way updates are working, you can
arrange for regular runs of cvsup using &man.cron.8;.
Obviously, you should not let cvsup use its GUI when running it from
@ -1773,7 +1773,7 @@ cvs-crypto</programlisting>
<literal>ports-all</literal>. The other collections are used only
by small groups of people for specialized purposes, and some mirror
sites may not carry all of them.</para>
<variablelist>
<varlistentry>
<term><literal>cvs-all release=cvs</literal></term>
@ -2459,7 +2459,7 @@ cvs-crypto</programlisting>
<sect3>
<title>For more information</title>
<para>For the CVSup FAQ and other information about CVSup, see <ulink
url="http://www.polstra.com/projects/freeware/CVSup/">The CVSup
Home Page</ulink>.</para>
@ -2477,14 +2477,14 @@ cvs-crypto</programlisting>
<sect1 id="makeworld">
<title>Using <command>make world</command> to rebuild your system</title>
<para><emphasis>Contributed by &a.nik;.</emphasis></para>
<para>Once you have synchronised your local source tree against a
particular version of FreeBSD (<literal>stable</literal>,
<literal>current</literal> and so on) you must then use the source tree
to rebuild the system.</para>
<warning>
<title>Take a backup</title>
@ -2539,7 +2539,7 @@ cvs-crypto</programlisting>
<note>
<title/Version 2.1.7 and below/
<para>If your machine has a floating point unit (386DX, 486DX, Pentium
and up class machines) then you can also uncomment the HAVE_FPU
line.</para>
@ -2587,9 +2587,9 @@ cvs-crypto</programlisting>
<para>If you are feeling particularly paranoid, you can check your
system to see which files are owned by the group you are renaming or
deleting.</para>
<screen>&prompt.root; <userinput>find / -group <replaceable>GID</replaceable> -print</userinput></screen>
<para>will show all files owned by group <replaceable>GID</replaceable>
(which can be either a group name or a numeric group ID).</para>
</tip>
@ -2609,7 +2609,7 @@ cvs-crypto</programlisting>
<note>
<title>Version 2.2.5 and above</title>
<para>As described in more detail below, versions 2.2.5 and above of
FreeBSD have separated the building process from the installing
process. You can therefore <emphasis>build</emphasis> the new
@ -2618,9 +2618,9 @@ cvs-crypto</programlisting>
</note>
<para>As the superuser, you can execute
<screen>&prompt.root; <userinput/shutdown now/</screen>
from a running system, which will drop it to single user mode.</para>
<para>Alternatively, reboot the system, and at the boot prompt, enter
@ -2662,9 +2662,9 @@ cvs-crypto</programlisting>
<sect3>
<title>All versions</title>
<para>You must be in the <filename>/usr/src</filename> directory, so
<screen>&prompt.root; <userinput>cd /usr/src</userinput></screen>
(unless, of course, your source code is elsewhere, in which case
@ -2674,7 +2674,7 @@ cvs-crypto</programlisting>
command reads instructions from the <filename>Makefile</filename>
which describes how the programs that comprise FreeBSD should be
rebuilt, the order they should be built in, and so on.</para>
<para>The general format of the command line you will type is as
follows;</para>
@ -2695,7 +2695,7 @@ cvs-crypto</programlisting>
<para>is another way of specifying that profiled libaries should not be
built, and corresponds with the
<programlisting>NOPROFILE= true
# Avoid compiling profiled libraries</programlisting>
@ -2719,7 +2719,7 @@ cvs-crypto</programlisting>
<sect3>
<title>Saving the output</title>
<para>It's a good idea to save the output you get from running
&man.make.1; to another file. If something goes wrong you will
have a copy of the error message, and a complete list of where the
@ -2749,11 +2749,11 @@ Script done, &hellip;</screen>
<sect3>
<title>Version 2.2.2 and below</title>
<para><filename>/usr/src/Makefile</filename> contains the
<maketarget>world</maketarget> target, which will rebuild the entire
system and then install it.</para>
<para>Use it like this.</para>
<screen>&prompt.root; <userinput>make world</userinput></screen>
@ -2761,7 +2761,7 @@ Script done, &hellip;</screen>
<sect3>
<title>Version 2.2.5 and above</title>
<para>Beginning with version 2.2.5 of FreeBSD (actually, it was first
created on the -current branch, and then retrofitted to -stable
midway between 2.2.2 and 2.2.5) the <maketarget>world</maketarget>
@ -2817,7 +2817,7 @@ Script done, &hellip;</screen>
<sect3>
<title>-current and above</title>
<para>If you are tracking -current you can also pass the
<option>-j</option> option to <command>make</command>. This lets
<command>make</command> spawn several simultaneous processes.</para>
@ -2837,7 +2837,7 @@ Script done, &hellip;</screen>
<para>If you have a multi-CPU machine and you are using an SMP
configured kernel try values between 6 and 10 and see how they speed
things up.</para>
<para>Be aware that (at the time of writing) this is still
experimental, and commits to the source tree may occasionally break
this feature. If the world fails to compile using this parameter
@ -2849,7 +2849,7 @@ Script done, &hellip;</screen>
<para>Assuming everything goes well you have anywhere between an hour
and a half and a day or so to wait.</para>
<para>As a general rule of thumb, a 200MHz P6 with more than 32MB of
RAM and reasonable SCSI disks will complete <command>make
world</command> in about an hour and a half. A 32MB P133 will
@ -2881,14 +2881,14 @@ Script done, &hellip;</screen>
<warning>
<title>Backup your existing <filename>/etc</filename></title>
<para>Although, in theory, nothing is going to touch this directory
automatically, it is always better to be sure. So copy your
existing <filename>/etc</filename> directory somewhere safe.
Something like:</para>
<screen>&prompt.root; <userinput>cp -Rp /etc /etc.old</userinput></screen>
<para><option>-R</option> does a recursive copy, <option>-p</option>
preserves times, ownerships on files and suchlike.</para>
</warning>
@ -2898,11 +2898,11 @@ Script done, &hellip;</screen>
put this dummy directory in <filename>/var/tmp/root</filename>, and
there are a number of subdirectories required under this as
well.</para>
<screen>&prompt.root; <userinput>mkdir /var/tmp/root</userinput>
&prompt.root; <userinput>cd /usr/src/etc</userinput>
&prompt.root; <userinput>make DESTDIR=/var/tmp/root distrib-dirs distribution</userinput></screen>
<para>This will build the necessary directory structure and install the
files. A lot of the subdirectories that have been created under
<filename>/var/tmp/root</filename> are empty and should be deleted.
@ -2945,15 +2945,15 @@ Script done, &hellip;</screen>
<title>Name the new root directory
(<filename>/var/tmp/root</filename>)with a timestamp, so you can
easily compare differences between versions</title>
<para>Frequently remaking the world means that you have to update
<filename>/etc</filename> frequently as well, which can be a bit of
a chore.</para>
<para>You can speed this process up by keeping a copy of the last set
of changed files that you merged into <filename>/etc</filename>.
The following procedure gives one idea of how to do this.</para>
<procedure>
<step>
<para>Make the world as normal. When you want to update
@ -3013,7 +3013,7 @@ Script done, &hellip;</screen>
to <filename>/etc</filename>.</para>
</step>
</procedure>
<para>You can use &man.date.1; to automate the generation of the
directory names.</para>
@ -3026,7 +3026,7 @@ Script done, &hellip;</screen>
<note>
<title>DEVFS</title>
<para>If you are using DEVFS then this is probably unnecessary.</para>
</note>
@ -3036,7 +3036,7 @@ Script done, &hellip;</screen>
<step>
<para>Copy <filename>/var/tmp/root/dev/MAKEDEV</filename> to
<filename>/dev</filename>.</para>
<screen>&prompt.root; <userinput>cp /var/tmp/root/dev/MAKEDEV /dev</userinput></screen>
</step>
@ -3097,7 +3097,7 @@ Script done, &hellip;</screen>
<note>
<title>Source older than 2 April 1998</title>
<para>If your source code is older than 2nd April 1998, or the
<filename>Makefile</filename> version is not 1.68 or higher (for
FreeBSD current and 3.x systems) or 1.48.2.21 or higher (for 2.2.x
@ -3545,27 +3545,27 @@ Antonio</screen>
<listitem>
<para>Sue Blake, <email>sue@welearn.com.au</email></para>
</listitem>
<listitem>
<para>Brian Haskin, <email>haskin@ptway.com</email></para>
</listitem>
<listitem>
<para>Kees Jan Koster, <email>kjk1@ukc.ac.uk</email></para>
</listitem>
<listitem>
<para>A Joseph Kosy, <email>koshy@india.hp.com</email></para>
</listitem>
<listitem>
<para>Greg Lehey, <email>grog@lemis.com</email></para>
</listitem>
<listitem>
<para>Wes Peters, <email>softweyr@xmission.com</email></para>
</listitem>
<listitem>
<para>Joseph Stein, <email>joes@wstein.com</email></para>
</listitem>
@ -3573,12 +3573,12 @@ Antonio</screen>
<listitem>
<para>Studded, <email>studded@dal.net</email></para>
</listitem>
<listitem>
<para>Axel Thimm,
<email>Axel.Thimm@physik.fu-berlin.de</email></para>
</listitem>
<listitem>
<para>Matthew Thyer,
<email>Matthew.Thyer@dsto.defence.gov.au</email></para>

106
en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.34 1999/10/13 13:02:46 jdp Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.35 1999/10/13 13:08:21 jdp Exp $
-->
<chapter id="eresources">
@ -32,7 +32,7 @@
questions to the appropriate mailing list you will reach both us and a
concentrated FreeBSD audience, invariably assuring a better (or at least
faster) response.</para>
<para>The charters for the various lists are given at the bottom of this
document. <emphasis>Please read the charter before joining or sending
mail to any list</emphasis>. Most of our list subscribers now receive
@ -41,7 +41,7 @@
signal-to-noise ratio of the lists high. To do less would see the
mailing lists ultimately fail as an effective communications medium for
the project.</para>
<para>Archives are kept for all of the mailing lists and can be searched
using the <ulink url="http://www.FreeBSD.org/search.html">FreeBSD World
Wide Web server</ulink>. The keyword searchable archive offers an
@ -354,7 +354,7 @@
be redistributed to mailing list members world-wide.</para>
<para>To subscribe to a list, send mail to &a.majordomo; and include
<programlisting>
subscribe &lt;listname&gt; [&lt;optional address&gt;]</programlisting>
@ -416,7 +416,7 @@ help
<email>freebsd-chat@FreeBSD.org</email> mailing list is freely
available and should be used instead.</para>
</listitem>
<listitem>
<para>No posting should be made to more than 2 mailing lists, and
only to 2 when a clear and obvious need to post to both lists
@ -442,7 +442,7 @@ help
therefore probably rate a warning (or ban) on that basis
alone.</para>
</listitem>
<listitem>
<para>Advertising of non-FreeBSD related products or services is
strictly prohibited and will result in an immediate ban if it is
@ -463,7 +463,7 @@ help
CMU/Transarc</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-ANNOUNCE</term>
@ -478,7 +478,7 @@ help
moderated mailing list.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-ARCH</term>
@ -521,7 +521,7 @@ help
discussion has been resolved.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-BUGS</term>
@ -536,7 +536,7 @@ help
interface</ulink> to it.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-CHAT</term>
@ -555,7 +555,7 @@ help
this -chat list.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-CORE</term>
@ -568,7 +568,7 @@ help
scrutiny.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-CURRENT</term>
@ -584,7 +584,7 @@ help
for which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-CURRENT-DIGEST</term>
@ -600,7 +600,7 @@ help
to.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-DOC</term>
@ -614,7 +614,7 @@ help
list; feel free to join and contribute!</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-FS</term>
@ -639,7 +639,7 @@ help
expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-ISDN</term>
@ -650,7 +650,7 @@ help
development of ISDN support for FreeBSD.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-JAVA</term>
@ -662,7 +662,7 @@ help
porting and maintenance of JDKs.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-HACKERS</term>
@ -678,7 +678,7 @@ help
expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-HACKERS-DIGEST</term>
@ -717,7 +717,7 @@ help
mirror sites.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-INSTALL</term>
@ -728,7 +728,7 @@ help
development for the future releases.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-ISP</term>
@ -742,7 +742,7 @@ help
expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-NEWBIES</term>
@ -761,7 +761,7 @@ help
newbies.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-PLATFORMS</term>
@ -785,7 +785,7 @@ help
Core Team Policy decisions.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-PORTS</term>
@ -800,7 +800,7 @@ help
for which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-QUESTIONS</term>
@ -813,7 +813,7 @@ help
technical.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-QUESTIONS-DIGEST</term>
@ -826,7 +826,7 @@ help
message. The average digest size is about 40kB.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-SCSI</term>
@ -838,7 +838,7 @@ help
which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-SECURITY</term>
@ -850,7 +850,7 @@ help
list for which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-SECURITY-NOTIFICATIONS</term>
@ -861,7 +861,7 @@ help
FreeBSD-security.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-SMALL</term>
@ -871,7 +871,7 @@ help
list for which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-STABLE</term>
@ -887,7 +887,7 @@ help
for which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-USER-GROUPS</term>
@ -923,7 +923,7 @@ help
<para><ulink
url="news:comp.unix.bsd.freebsd.announce">comp.unix.bsd.freebsd.announce</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.bsd.freebsd.misc">comp.unix.bsd.freebsd.misc</ulink></para>
@ -938,62 +938,62 @@ help
<listitem>
<para><ulink url="news:comp.unix">comp.unix</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.questions">comp.unix.questions</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.admin">comp.unix.admin</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.programmer">comp.unix.programmer</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.shell">comp.unix.shell</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.user-friendly">comp.unix.user-friendly</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.security.unix">comp.security.unix</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.sources.unix">comp.sources.unix</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.advocacy">comp.unix.advocacy</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.misc">comp.unix.misc</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.bugs.4bsd">comp.bugs.4bsd</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.bugs.4bsd.ucb-fixes">comp.bugs.4bsd.ucb-fixes</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.bsd">comp.unix.bsd</ulink></para>
@ -1009,37 +1009,37 @@ help
<para><ulink
url="news:comp.windows.x.i386unix">comp.windows.x.i386unix</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x">comp.windows.x</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.apps">comp.windows.x.apps</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.announce">comp.windows.x.announce</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.intrinsics">comp.windows.x.intrinsics</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.motif">comp.windows.x.motif</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.pex">comp.windows.x.pex</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.emulators.ms-windows.wine">comp.emulators.ms-windows.wine</ulink></para>
@ -1332,7 +1332,7 @@ help
<entry>Read-only cvs, personal webspace, email</entry>
<entry>&a.brian</entry>
</row>
<row>
<entry>dogma.freebsd-uk.eu.org</entry>
<entry>Telnet/FTP/SSH</entry>

262
en_US.ISO8859-1/books/handbook/hw/chapter.sgml
View file

File diff suppressed because it is too large Load diff

162
en_US.ISO8859-1/books/handbook/install/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/install/chapter.sgml,v 1.25 1999/09/21 16:43:15 chris Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/install/chapter.sgml,v 1.26 1999/09/23 21:12:05 chris Exp $
-->
<chapter id="install">
@ -111,7 +111,7 @@
live in the <filename>floppies</filename> subdirectory, as is
typically the case).</para>
</listitem>
<listitem>
<para>If you are using a UNIX system to create the floppy
images:</para>
@ -199,7 +199,7 @@
<para>After adjusting the kernel to match how you have your hardware
configured, type <command>Q</command> to continue booting with the new
settings.</para>
<para>After FreeBSD has been installed, changes made in the configuration
mode will be permanent so you do not have to reconfigure every time you
boot. Even so, it is likely that you will want to build a custom kernel
@ -215,16 +215,16 @@
386sx is not recommended). Support for generic IDE or ESDI drive
configurations, various SCSI controller, network and serial cards is
also provided.</para>
<para>A minimum of four megabytes of RAM is required to run FreeBSD. To
run the X Window System, eight megabytes of RAM is the recommended
minimum.</para>
<para>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.</para>
<sect2>
<title>Disk Controllers</title>
@ -232,15 +232,15 @@
<listitem>
<para>WD1003 (any generic MFM/RLL)</para>
</listitem>
<listitem>
<para>WD1007 (any generic IDE/ESDI)</para>
</listitem>
<listitem>
<para>IDE</para>
</listitem>
<listitem>
<para>ATA</para>
</listitem>
@ -403,7 +403,7 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE
IV and SmartRAID IV SCSI/RAID controllers are supported. The DPT
@ -415,7 +415,7 @@
SMART, SMART-2/E, Smart-2/P, SMART-2SL, Smart Array 3200,
Smart Array 3100ES and Smart Array 221.</para>
</listitem>
<listitem>
<para>SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820,
53C825a, 53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI
@ -451,12 +451,12 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>QLogic 1020, 1040, 1040B, 1080, 1240 and 2100 SCSI and Fibre
Channel Adapters</para>
</listitem>
<listitem>
<para>DTC 3290 EISA SCSI controller in 1542 emulation mode.</para>
</listitem>
@ -478,21 +478,21 @@
<para>SoundBlaster SCSI and ProAudio Spectrum SCSI
(<literal>cd</literal>)</para>
</listitem>
<listitem>
<para>Mitsumi (all models) proprietary interface
(<literal>mcd</literal>)</para>
</listitem>
<listitem>
<para>Matsushita/Panasonic (Creative) CR-562/CR-563 proprietary
interface (<literal>matcd</literal>)</para>
</listitem>
<listitem>
<para>Sony proprietary interface (<literal>scd</literal>)</para>
</listitem>
<listitem>
<para>ATAPI IDE interface (<literal>wcd</literal>)</para>
</listitem>
@ -506,15 +506,15 @@
<para>Tekram DC390 and DC390T controllers (maybe other cards based
on the AMD 53c974 as well).</para>
</listitem>
<listitem>
<para>NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.</para>
</listitem>
<listitem>
<para>UltraStor 14F, 24F and 34F SCSI controllers.</para>
</listitem>
<listitem>
<para>Seagate ST01/02 SCSI controllers.</para>
</listitem>
@ -522,7 +522,7 @@
<listitem>
<para>Future Domain 8xx/950 series SCSI controllers.</para>
</listitem>
<listitem>
<para>WD7000 SCSI controller.</para>
</listitem>
@ -531,11 +531,11 @@
<para>Adaptec 1510 series ISA SCSI controllers (not for bootable
devices)</para>
</listitem>
<listitem>
<para>Adaptec 152x series ISA SCSI controllers</para>
</listitem>
<listitem>
<para>Adaptec AIC-6260 and AIC-6360 based boards, which includes the
AHA-152x and SoundBlaster SCSI cards.</para>
@ -550,22 +550,22 @@
<listitem>
<para>Allied-Telesis AT1700 and RE2000 cards</para>
</listitem>
<listitem>
<para>SMC Elite 16 WD8013 Ethernet interface, and most other
WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and
WD8013EBT based clones. SMC Elite Ultra and 9432TX based cards
are also supported.</para>
</listitem>
<listitem>
<para>DEC EtherWORKS III NICs (DE203, DE204, and DE205)</para>
</listitem>
<listitem>
<para>DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)</para>
</listitem>
<listitem>
<para>DEC DC21040/DC21041/DC21140 based NICs:</para>
@ -643,75 +643,75 @@
<listitem>
<para>DEC FDDI (DEFPA/DEFEA) NICs</para>
</listitem>
<listitem>
<para>Fujitsu FMV-181 and FMV-182</para>
</listitem>
<listitem>
<para>Fujitsu MB86960A/MB86965A</para>
</listitem>
<listitem>
<para>Intel EtherExpress</para>
</listitem>
<listitem>
<para>Intel EtherExpress Pro/100B 100Mbit.</para>
</listitem>
<listitem>
<para>Isolan AT 4141-0 (16 bit)</para>
</listitem>
<listitem>
<para>Isolink 4110 (8 bit)</para>
</listitem>
<listitem>
<para>Lucent WaveLAN wireless networking interface.</para>
</listitem>
<listitem>
<para>Novell NE1000, NE2000, and NE2100 ethernet interface.</para>
</listitem>
<listitem>
<para>3Com 3C501 cards</para>
</listitem>
<listitem>
<para>3Com 3C503 Etherlink II</para>
</listitem>
<listitem>
<para>3Com 3c505 Etherlink/+</para>
</listitem>
<listitem>
<para>3Com 3C507 Etherlink 16/TP</para>
</listitem>
<listitem>
<para>3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III</para>
</listitem>
<listitem>
<para>3Com 3C590, 3C595 Etherlink III</para>
</listitem>
<listitem>
<para>3Com 3C90x cards.</para>
</listitem>
<listitem>
<para>HP PC Lan Plus (27247B and 27252A)</para>
</listitem>
<listitem>
<para>Toshiba ethernet cards</para>
</listitem>
<listitem>
<para>PCMCIA ethernet cards from IBM and National Semiconductor are
also supported.</para>
@ -732,71 +732,71 @@
<listitem>
<para>AST 4 port serial card using shared IRQ.</para>
</listitem>
<listitem>
<para>ARNET 8 port serial card using shared IRQ.</para>
</listitem>
<listitem>
<para>BOCA IOAT66 6 port serial card using shared IRQ.</para>
</listitem>
<listitem>
<para>BOCA 2016 16 port serial card using shared IRQ.</para>
</listitem>
<listitem>
<para>Cyclades Cyclom-y Serial Board.</para>
</listitem>
<listitem>
<para>STB 4 port card using shared IRQ.</para>
</listitem>
<listitem>
<para>SDL Communications Riscom/8 Serial Board.</para>
</listitem>
<listitem>
<para>SDL Communications RISCom/N2 and N2pci sync serial
cards.</para>
</listitem>
<listitem>
<para>Digiboard Sync/570i high-speed sync serial card.</para>
</listitem>
<listitem>
<para>Decision-Computer Intl. &ldquo;Eight-Serial&rdquo; 8 port
serial cards using shared IRQ.</para>
</listitem>
<listitem>
<para>Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum,
Gravis UltraSound, Gravis UltraSound MAX and Roland MPU-401 sound
cards.</para>
</listitem>
<listitem>
<para>Matrox Meteor video frame grabber.</para>
</listitem>
<listitem>
<para>Creative Labs Video spigot frame grabber.</para>
</listitem>
<listitem>
<para>Omnimedia Talisman frame grabber.</para>
</listitem>
<listitem>
<para>Brooktree BT848 chip based frame grabbers.</para>
</listitem>
<listitem>
<para>X-10 power controllers.</para>
</listitem>
<listitem>
<para>PC joystick and speaker.</para>
</listitem>
@ -947,7 +947,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<filename>c:\freebsd</filename> &mdash; the <literal>BIN</literal> dist
is only the minimal requirement.</para>
</sect2>
<sect2>
<title>Before installing from QIC/SCSI Tape</title>
@ -974,7 +974,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
installation probe may otherwise fail to find it.</para>
</note>
</sect2>
<sect2>
<title>Before installing over a network</title>
@ -989,7 +989,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<para>SLIP or PPP</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Parallel port</term>
@ -997,7 +997,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<para>PLIP (laplink cable)</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Ethernet</term>
@ -1062,7 +1062,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<sect3>
<title>Preparing for NFS installation</title>
<para>NFS installation is fairly straight-forward: Simply copy the
FreeBSD distribution files you want onto a server somewhere and then
point the NFS media selection at it.</para>
@ -1094,7 +1094,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<sect3>
<title>Preparing for FTP Installation</title>
<para>FTP installation may be done from any mirror site containing a
reasonably up-to-date version of FreeBSD &rel.current;. A full menu
of reasonable choices from almost anywhere in the world is provided
@ -1134,13 +1134,13 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
</listitem>
</varlistentry>
</variablelist>
<note>
<para>Active and passive modes are not the same as a
&ldquo;proxy&rdquo; connection, where a proxy FTP server is
listening and forwarding FTP requests!</para>
</note>
<para>For a proxy FTP server, you should usually give name of the
server you really want as a part of the username, after an @-sign.
The proxy server then 'fakes' the real server. An example: Say you
@ -1170,14 +1170,14 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<para>Once you have taken note of the appropriate preinstallation steps,
you should be able to install FreeBSD without any further
trouble.</para>
<para>Should this not be true, then you may wish to go back and re-read
the relevant preparation section above for the installation media type
you are trying to use, perhaps there is a helpful hint there that you
missed the first time? If you are having hardware trouble, or FreeBSD
refuses to boot at all, read the Hardware Guide provided on the boot
floppy for a list of possible solutions.</para>
<para>The FreeBSD boot floppies contain all the on-line documentation you
should need to be able to navigate through an installation and if it
does not then we would like to know what you found most confusing. Send
@ -1186,10 +1186,10 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
painful &ldquo;step-by-step&rdquo; guides are no longer necessary. It
may take us a little while to reach that objective, but that is the
objective!</para>
<para>Meanwhile, you may also find the following &ldquo;typical
installation sequence&rdquo; to be helpful:</para>
<orderedlist>
<listitem>
<para>Boot the <filename>kern.flp</filename> floppy and, when asked,
@ -1243,7 +1243,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<para>Many FreeBSD users wish to install FreeBSD on PCs inhabited by
MS-DOS. Here are some commonly asked questions about installing FreeBSD
on such systems.</para>
<para><emphasis>Help! I have no space! Do I need to delete everything
first?</emphasis></para>
@ -1252,7 +1252,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
find the FIPS utility, provided in the <filename>tools</filename>
directory on the FreeBSD CDROM or on the various FreeBSD ftp sites, to
be quite useful.</para>
<para>FIPS allows you to split an existing MS-DOS partition into two
pieces, preserving the original partition and allowing you to install
onto the second free piece. You first defragment your MS-DOS partition,
@ -1262,24 +1262,24 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
See the <emphasis>Distributions</emphasis> menu for an estimation of how
much free space you will need for the kind of installation you
want.</para>
<para><emphasis>Can I use compressed MS-DOS filesystems from
FreeBSD?</emphasis></para>
<para>No. If you are using a utility such as Stacker(tm) or
DoubleSpace(tm), FreeBSD will only be able to use whatever portion of
the filesystem you leave uncompressed. The rest of the filesystem will
show up as one large file (the stacked/dblspaced file!). <emphasis>Do
not remove that file!</emphasis> You will probably regret it
greatly!</para>
<para>It is probably better to create another uncompressed MS-DOS primary
partition and use this for communications between MS-DOS and
FreeBSD.</para>
<para><emphasis>Can I mount my MS-DOS extended
partitions?</emphasis></para>
<para>Yes. DOS extended partitions are mapped in at the end of the other
&ldquo;slices&rdquo; in FreeBSD, e.g. your <devicename>D:</devicename>
drive might be <filename>/dev/da0s5</filename>, your
@ -1289,7 +1289,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<filename>da</filename> appropriately. You otherwise mount extended
partitions exactly like you would mount any other DOS drive,
e.g.:</para>
<screen>&prompt.root; <userinput>mount -t msdos /dev/da0s5 /dos_d</userinput></screen>
</sect1>
</chapter>

44
en_US.ISO8859-1/books/handbook/introduction/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml,v 1.18 1999/09/14 03:13:50 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml,v 1.19 1999/09/22 12:15:45 jkh Exp $
-->
<chapter id="introduction">
@ -27,7 +27,7 @@
architecture. FreeBSD provides you with many advanced features
previously available only on much more expensive systems.
These features include:</para>
<itemizedlist>
<listitem>
<para><emphasis>Preemptive multitasking</emphasis> with
@ -139,7 +139,7 @@
the commercial giants struggle to field PC operating systems with such
features, performance and reliability, FreeBSD can offer them
<emphasis>now</emphasis>!</para>
<para>The applications to which FreeBSD can be put are truly limited only
by your own imagination. From software development to factory
automation, inventory control to azimuth correction of remote satellite
@ -149,7 +149,7 @@
applications developed by research centers and universities around the
world, often available at little to no cost. Commercial applications are
also available and appearing in greater numbers every day.</para>
<para>Because the source code for FreeBSD itself is generally available,
the system can also be customized to an almost unheard of degree for
special applications or projects, and in ways not generally possible
@ -188,7 +188,7 @@
<para>And more...</para>
</listitem>
</itemizedlist>
<para>With FreeBSD, you can easily start out small with an
inexpensive 386 class PC and upgrade all the way up to a
quad-processor Xeon with RAID storage as your enterprise
@ -271,7 +271,7 @@
snapshot. Those plans came to a rude halt when Bill Jolitz suddenly
decided to withdraw his sanction from the project and without any clear
indication of what would be done instead.</para>
<para>It did not take us long to decide that the goal remained worthwhile,
even without Bill's support, and so we adopted the name
&ldquo;FreeBSD&rdquo;, coined by David Greenman. Our initial objectives
@ -285,14 +285,14 @@
Walnut Creek CDROM's almost unprecedented degree of faith in what was,
at the time, a completely unknown project, it is quite unlikely that
FreeBSD would have gotten as far, as fast, as it has today.</para>
<para>The first CDROM (and general net-wide) distribution was FreeBSD 1.0,
released in December of 1993. This was based on the 4.3BSD-Lite
(&ldquo;Net/2&rdquo;) tape from U.C. Berkeley, with many components also
provided by 386BSD and the Free Software Foundation. It was a fairly
reasonable success for a first offering, and we followed it with the
highly successful FreeBSD 1.1 release in May of 1994.</para>
<para>Around this time, some rather unexpected storm clouds formed on the
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
@ -306,7 +306,7 @@
1994 to stop shipping its own Net/2 based product. Under the terms of
that agreement, the project was allowed one last release before the
deadline, that release being FreeBSD 1.1.5.1.</para>
<para>FreeBSD then set about the arduous task of literally re-inventing
itself from a completely new and rather incomplete set of 4.4BSD-Lite
bits. The &ldquo;Lite&rdquo; releases were light in part because
@ -319,7 +319,7 @@
rough around the edges, the release was a significant success and was
followed by the more robust and easier to install FreeBSD 2.0.5 release
in June of 1995.</para>
<para>We released FreeBSD 2.1.5 in August of 1996, and it appeared to be
popular enough among the ISP and commercial communities that another
release along the 2.1-stable branch was merited. This was FreeBSD
@ -327,7 +327,7 @@
development on 2.1-stable. Now in maintenance mode, only security
enhancements and other critical bug fixes will be done on this branch
(RELENG_2_1_0).</para>
<para>FreeBSD 2.2 was branched from the development mainline
(&ldquo;-current&rdquo;) in November 1996 as the RELENG_2_2 branch, and
the first full release (2.2.1) was released in April, 1997. Further
@ -362,7 +362,7 @@
provides the widest possible benefit. This is, I believe, one of the
most fundamental goals of Free Software and one that we enthusiastically
support.</para>
<para>That code in our source tree which falls under the GNU General Public
License (GPL) or Library General Public License (LGPL) comes with slightly
more strings attached, though at least on the side of enforced access
@ -389,10 +389,10 @@
to distribute their own patches or work-in-progress sources. The
&a.announce; is also available to those wishing to make other FreeBSD
users aware of major areas of work.</para>
<para>Useful things to know about the FreeBSD project and its development
process, whether working independently or in close cooperation:</para>
<variablelist>
<varlistentry>
<term>The CVS repository<anchor
@ -434,7 +434,7 @@
<varlistentry>
<term>The FreeBSD core team<anchor id="development-core"></term>
<listitem>
<para>The <link linkend="staff-core">FreeBSD core team</link> would
be equivalent to the board of directors if the FreeBSD Project
@ -468,7 +468,7 @@
<varlistentry>
<term>Outside contributors</term>
<listitem>
<para>Last, but definitely not least, the largest group of
developers are the users themselves who provide feedback and
@ -515,7 +515,7 @@
Alpha based computer systems. It is based primarily on software from U.C.
Berkeley's CSRG group, with some enhancements from NetBSD, OpenBSD, 386BSD,
and the Free Software Foundation.</para>
<para>Since our release of FreeBSD 2.0 in late 94, the performance,
feature set, and stability of FreeBSD has improved dramatically. The
largest change is a revamped virtual memory system with a merged VM/file
@ -526,12 +526,12 @@
an improved SCSI subsystem, ISDN support, support for ATM, FDDI, Fast
and Gigabit Ethernet (1000Mbit) adapters, improved support for the latest
Adaptec controllers and many hundreds of bug fixes.</para>
<para>We have also taken the comments and suggestions of many of our users
to heart and have attempted to provide what we hope is a more sane and
easily understood installation process. Your feedback on this
(constantly evolving) process is especially welcome!</para>
<para>In addition to the base distributions, FreeBSD offers a new ported
software collection with hundreds of commonly sought-after programs. By
mid-September 1999, there were more than 2600 ports! The list of
@ -550,7 +550,7 @@
pre-compiled &ldquo;package&rdquo; which can be installed with a simple
command (pkg_add) by those who do not wish to compile their own ports
from source.</para>
<para>A number of additional documents which you may find very helpful in
the process of installing and using FreeBSD may now also be found in the
<filename>/usr/share/doc</filename> directory on any machine running
@ -569,7 +569,7 @@
<varlistentry>
<term>The FreeBSD FAQ</term>
<listitem>
<para><ulink
url="file:/usr/share/doc/FAQ/FAQ.html">file:/usr/share/doc/FAQ/FAQ.html</ulink></para>
@ -589,7 +589,7 @@
outside the U.S.) exportable European distribution of DES for our
non-U.S. users also exists and is described in the <ulink
url="../FAQ/FAQ.html">FreeBSD FAQ</ulink>.</para>
<para>If password security for FreeBSD is all you need, and you have no
requirement for copying encrypted passwords from different hosts (Suns,
DEC machines, etc) into FreeBSD password entries, then FreeBSD's MD5

136
en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.20 1999/09/06 06:52:59 peter Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.21 1999/11/01 19:16:06 nik Exp $
-->
<chapter id="kernelconfig">
@ -68,7 +68,7 @@
while everything outside the <filename>i386</filename> directory is
common to all platforms which FreeBSD could potentially be ported
to.</para>
<note>
<para>If there is <emphasis>not</emphasis> a
<filename>/usr/src/sys</filename> directory on your system, then the
@ -90,7 +90,7 @@
maintaining multiple FreeBSD machines with different hardware, it is a
good idea to name it after your machine's hostname. We will call it
<filename>MYKERNEL</filename> for the purpose of this example.</para>
<note>
<para>You must execute these and all of the following commands under the
root account or you will get <errortype>permission denied</errortype>
@ -107,7 +107,7 @@
comment lines at the top to reflect your configuration or the changes
you have made to differentiate it from
<filename>GENERIC</filename>.</para>
<para>If you have build a kernel under SunOS or some other BSD operating
system, much of this file will be very familiar to you. If you are
coming from some other operating system such as DOS, on the other hand,
@ -169,14 +169,14 @@
directory as <filename>GENERIC</filename>. If you are in doubt as to
the purpose or necessity of a line, check first in
<filename>LINT</filename>.</para>
<para>The kernel is currently being moved to a better organization of the
option handling. Traditionally, each option in the config file was
simply converted into a <option>-D</option> switch for the
<acronym>CFLAGS</acronym> line of the kernel Makefile. Naturally, this
caused a creeping optionism, with nobody really knowing which option has
been referenced in what files.</para>
<para>In the new scheme, every <literal>#ifdef</literal> that is intended
to be dependent upon an option gets this option out of an
<filename>opt_<replaceable>foo</replaceable>.h</filename> declaration
@ -226,7 +226,7 @@
<replaceable>alpha</replaceable>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>cpu
"<replaceable>cpu_type</replaceable>"</literal></term>
@ -277,7 +277,7 @@
<replaceable>cpu_type</replaceable>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ident
<replaceable>machine_name</replaceable></literal></term>
@ -302,7 +302,7 @@
<literal>vax</literal>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>maxusers
<replaceable>number</replaceable></literal></term>
@ -344,7 +344,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>config
<replaceable>kernel_name</replaceable></literal> root on
@ -393,7 +393,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options "COMPAT_43"</literal></term>
@ -402,7 +402,7 @@
will act strangely if you comment this out.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options UCONSOLE</literal></term>
@ -414,7 +414,7 @@
as any console messages sent by the kernel.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options SYSVSHM</literal></term>
@ -427,7 +427,7 @@
definitely want to include this.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options SYSVSEM</literal></term>
@ -436,7 +436,7 @@
only adds a few hundred bytes to the kernel.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options SYSVMSG</literal></term>
@ -476,7 +476,7 @@
from the hard disk.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options NFS</literal></term>
@ -486,7 +486,7 @@
out.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options MSDOSFS</literal></term>
@ -501,7 +501,7 @@
all).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options "CD9660"</literal></term>
@ -512,7 +512,7 @@
data CD). Audio CD's do not need this filesystem.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options PROCFS</literal></term>
@ -523,7 +523,7 @@
what processes are running.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options MFS</literal></term>
@ -557,7 +557,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options "EXT2FS"</literal></term>
@ -568,7 +568,7 @@
the two systems.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options QUOTA</literal></term>
@ -600,7 +600,7 @@
run FreeBSD at this time.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller eisa0</literal></term>
<listitem>
@ -609,7 +609,7 @@
EISA bus.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller pci0</literal></term>
@ -619,7 +619,7 @@
ISA bus.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller fdc0</literal></term>
@ -638,7 +638,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller wdc0</literal></term>
@ -652,7 +652,7 @@
all six lines, for example).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device acd0<anchor
id="kernelconfig-atapi"></literal></term>
@ -665,7 +665,7 @@
line <literal>options ATAPI</literal>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device npx0 at isa? port "IO_NPX" irq 13
vector npxintr</literal></term>
@ -677,7 +677,7 @@
optional.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device wt0 at isa? port 0x300 bio irq 5 drq 1 vector
wtintr</literal></term>
@ -686,7 +686,7 @@
<para>Wangtek and Archive QIC-02/QIC-36 tape drive support</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Proprietary CD-ROM support</term>
@ -848,7 +848,7 @@
</variablelist>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options SCSI_DELAY=15000</literal></term>
@ -861,7 +861,7 @@
your SCSI devices, you will have to raise it back up.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller scbus0</literal></term>
@ -871,7 +871,7 @@
and the following three lines, out.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device da0</literal></term>
@ -879,7 +879,7 @@
<para>Support for SCSI hard drives.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device sa0</literal></term>
@ -887,7 +887,7 @@
<para>Support for SCSI tape drives.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device cd0</literal></term>
@ -895,7 +895,7 @@
<para>Support for SCSI CD-ROM drives.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device ch0</literal></term>
@ -904,7 +904,7 @@
as tape libraries.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device pass0</literal></term>
@ -1056,7 +1056,7 @@
</variablelist>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device mse0 at isa? port 0x23c tty irq 5 vector
ms</literal></term>
@ -1073,7 +1073,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device psm0 at isa? port "IO_KBD" conflicts tty irq
12 vector psmintr</literal></term>
@ -1122,7 +1122,7 @@
used.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller ppbus0</literal></term>
@ -1130,7 +1130,7 @@
<para>Provides support for the parallel port bus.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device ppc0 at isa? port? tty irq 7</literal></term>
@ -1138,7 +1138,7 @@
<para>ISA-bus parallel port interface.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device lpt0 at ppbus?</literal></term>
@ -1173,7 +1173,7 @@
your PC) so this is essentially mandatory.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Ethernet cards</term>
@ -1362,7 +1362,7 @@
back at you through this pseudo-device. Mandatory.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device ether</literal></term>
@ -1372,7 +1372,7 @@
code.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device sl
<replaceable>number</replaceable></literal></term>
@ -1389,7 +1389,7 @@
linkend="slips">server</link>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device ppp
<replaceable>number</replaceable></literal></term>
@ -1407,7 +1407,7 @@
simultaneous PPP connections to support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device tun
<replaceable>number</replaceable></literal></term>
@ -1422,7 +1422,7 @@
for more information.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device bpfilter
<replaceable>number</replaceable></literal></term>
@ -1463,7 +1463,7 @@
<literal>pcm</literal>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device pas0 at isa? port 0x388 irq 10 drq 6 vector
pasintr</literal></term>
@ -1472,7 +1472,7 @@
<para>ProAudioSpectrum digital audio and MIDI.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device sb0 at isa? port 0x220 irq 7 conflicts drq 1
vector sbintr</literal></term>
@ -1488,7 +1488,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device sbxvi0 at isa? drq 5</literal></term>
@ -1502,7 +1502,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device sbmidi0 at isa? port 0x330</literal></term>
@ -1512,7 +1512,7 @@
compile.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device gus0 at isa? port 0x220 irq 10 drq 1 vector
gusintr</literal></term>
@ -1521,7 +1521,7 @@
<para>Gravis Ultrasound.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device mss0 at isa? port 0x530 irq 10 drq 1 vector
adintr</literal></term>
@ -1530,7 +1530,7 @@
<para>Microsoft Sound System.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device opl0 at isa? port 0x388
conflicts</literal></term>
@ -1542,7 +1542,7 @@
(in the ports collection).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device mpu0 at isa? port 0x330 irq 6 drq
0</literal></term>
@ -1551,7 +1551,7 @@
<para>Roland MPU-401 stand-alone card.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device uart0 at isa? port 0x330 irq 5 vector
"m6850intr"</literal></term>
@ -1560,7 +1560,7 @@
<para>Stand-alone 6850 UART for MIDI.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device pca0 at isa? port "IO_TIMER1"
tty</literal><anchor id="kernelconfig-pcaudio"></term>
@ -1619,7 +1619,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device log</literal></term>
@ -1628,7 +1628,7 @@
messages. Mandatory.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device pty
<replaceable>number</replaceable></literal><anchor
@ -1646,7 +1646,7 @@
accordingly, up to a maximum of 256.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device snp
<replaceable>number</replaceable></literal></term>
@ -1660,7 +1660,7 @@
of simultaneous snoop sessions. Optional.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device vn</literal></term>
@ -1672,7 +1672,7 @@
Optional.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device ccd
<replaceable>number</replaceable></literal></term>
@ -1707,7 +1707,7 @@
<para>PC joystick device.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device speaker</literal></term>
@ -1745,7 +1745,7 @@
of them, so when you add support for a new device, it pays to make sure
that the appropriate entries are in this directory, and if not, add
them. Here is a simple example:</para>
<para>Suppose you add the IDE CD-ROM support to the kernel. The line to
add is:</para>
@ -1764,7 +1764,7 @@ device acd0</programlisting>
<para>When this script finishes, you will find that there are now
<filename>acd0c</filename> and <filename>racd0c</filename> entries in
<filename>/dev</filename> so you know that it executed correctly.</para>
<para>For sound cards, the command:
<screen>&prompt.root; <userinput>sh MAKEDEV snd0</userinput></screen>
@ -1833,7 +1833,7 @@ device acd0</programlisting>
<varlistentry>
<term>Kernel will not boot<anchor id="kernelconfig-noboot"></term>
<listitem>
<para>If your new kernel does not boot, or fails to recognize your
devices, do not panic! Fortunately, BSD has an excellent mechanism
@ -1881,7 +1881,7 @@ device acd0</programlisting>
<varlistentry>
<term>Kernel works, but <command>ps</command> does not work any
more!</term>
<listitem>
<para>If you have installed a different version of the kernel from
the one that the system utilities have been built with, for

40
en_US.ISO8859-1/books/handbook/kerneldebug/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml,v 1.18 1999/09/06 06:52:59 peter Exp $
-->
<chapter id="kerneldebug">
@ -55,7 +55,7 @@
some 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 memory will be wasted.</para>
<para>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 one in
order to get your system up and running again, boot it only into single
@ -186,7 +186,7 @@
<varlistentry>
<term>line 20:</term>
<listitem>
<para>This is the location of function <function>trap()</function>
in the stack trace.</para>
@ -195,7 +195,7 @@
<varlistentry>
<term>line 36:</term>
<listitem>
<para>Force usage of a new stack frame; this is no longer necessary
now. The stack frames are supposed to point to the right
@ -210,7 +210,7 @@
<varlistentry>
<term>line 52:</term>
<listitem>
<para>The pointer looks suspicious, but happens to be a valid
address.</para>
@ -219,7 +219,7 @@
<varlistentry>
<term>line 56:</term>
<listitem>
<para>However, it obviously points to garbage, so we have found our
error! (For those unfamiliar with that particular piece of code:
@ -251,7 +251,7 @@
<para>What do you do if a kernel dumped core but you did not expect it,
and it is therefore not compiled using <command>config -g</command>? Not
everything is lost here. Do not panic!</para>
<para>Of course, you still need to enable crash dumps. See above on the
options you have to specify in order to do this.</para>
@ -271,14 +271,14 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols</
faulting one but some debugging symbols. You should at least verify the
old and new sizes with the &man.size.1; command. If there is a
mismatch, you probably need to give up here.</para>
<para>Go and examine the dump as described above. The debugging symbols
might be incomplete for some places, as can be seen in the stack trace
in the example above where some functions are displayed without line
numbers and argument lists. If you need more debugging symbols, remove
the appropriate object files and repeat the <command>kgdb</command>
session until you know enough.</para>
<para>All this is not guaranteed to work, but it will do it fine in most
cases.</para>
</sect1>
@ -290,14 +290,14 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols</
high level of user interface, there are some things it cannot do. The
most important ones being breakpointing and single-stepping kernel
code.</para>
<para>If you need to do low-level debugging on your kernel, there is an
on-line debugger available called DDB. It allows to setting
breakpoints, single-stepping kernel functions, examining and changing
kernel variables, etc. However, it cannot access kernel source files,
and only has access to the global and static symbols, not to the full
debug information like <command>kgdb</command>.</para>
<para>To configure your kernel to include DDB, add the option line
<programlisting>
@ -318,7 +318,7 @@ options DDB</programlisting>
<option>-d</option> right at the boot prompt. The kernel will start up
in debug mode and enter DDB prior to any device probing. Hence you can
even debug the device probe/attach functions.</para>
<para>The second scenario is a hot-key on the keyboard, usually
Ctrl-Alt-ESC. For syscons, this can be remapped; some of the
distributed maps do this, so watch out. There is an option available
@ -327,11 +327,11 @@ options DDB</programlisting>
in the kernel config file). It is not the default since there are a lot
of crappy serial adapters around that gratuitously generate a BREAK
condition, for example when pulling the cable.</para>
<para>The third way is that any panic condition will branch to DDB if the
kernel is configured to use it. For this reason, it is not wise to
configure a kernel with DDB for a machine running unattended.</para>
<para>The DDB commands roughly resemble some <command>gdb</command>
commands. The first thing you probably need to do is to set a
breakpoint:</para>
@ -344,7 +344,7 @@ options DDB</programlisting>
<literal>a-f</literal> need to be preceded with <literal>0x</literal>
(this is optional for other numbers). Simple expressions are allowed,
for example: <literal>function-name + 0x103</literal>.</para>
<para>To continue the operation of an interrupted kernel, simply
type:</para>
@ -419,11 +419,11 @@ options DDB</programlisting>
specifies the size of the data to be written, the first following
expression is the address to write to and the remainder is interpreted
as data to write to successive memory locations.</para>
<para>If you need to know the current registers, use:</para>
<screen><userinput>show reg</userinput></screen>
<para>Alternatively, you can display a single register value by e.g.
<screen><userinput>p $eax</userinput></screen>
@ -468,7 +468,7 @@ options DDB</programlisting>
<para>is the final way out of disaster and almost the same as hitting the
Big Red Button.</para>
<para>If you need a short command summary, simply type:</para>
<screen><userinput>help</userinput></screen>
@ -493,7 +493,7 @@ options DDB</programlisting>
with all the symbols in it, and the other one is the target machine that
simply runs a similar copy of the very same kernel (but stripped of the
debugging information).</para>
<para>You should configure the kernel in question with <command>config
-g</command>, include <option>DDB</option> into the configuration, and
compile it as usual. This gives a large blurb of a binary, due to the
@ -573,7 +573,7 @@ text_addr = 0xf5109020? (y or n) <userinput>y</userinput>
<sect1>
<title>Debugging a Console Driver</title>
<para>Since you need a console driver to run DDB on, things are more
complicated if the console driver itself is failing. You might remember
the use of a serial console (either with modified boot blocks, or by

30
en_US.ISO8859-1/books/handbook/kernelopts/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelopts/chapter.sgml,v 1.11 1999/09/06 06:53:00 peter Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelopts/chapter.sgml,v 1.12 1999/11/06 19:32:39 eivind Exp $
-->
<chapter id="kernelopts">
@ -41,39 +41,39 @@
#ifndef THIS_OPTION
#define THIS_OPTION (some_default_value)
#endif /* THIS_OPTION */</programlisting>
<para>This way, an administrator mentioning another value for the option
in his config file will take the default out of effect, and replace it
with his new value. Clearly, the new value will be substituted into the
source code during the preprocessor run, so it must be a valid C
expression in whatever context the default value would have been
used.</para>
<para>It is also possible to create value-less options that simply enable
or disable a particular piece of code by embracing it in</para>
<programlisting>
#ifdef THAT_OPTION
[your code here]
#endif</programlisting>
<para>Simply mentioning <literal>THAT_OPTION</literal> in the config file
(with or without any value) will then turn on the corresponding piece of
code.</para>
<para>People familiar with the C language will immediately recognize that
everything could be counted as a &ldquo;config option&rdquo; where there
is at least a single <literal>#ifdef</literal> referencing it...
However, it's unlikely that many people would put</para>
<programlisting>
options notyet,notdef</programlisting>
<para>in their config file, and then wonder why the kernel compilation
falls over. <!-- smiley -->:-)</para>
<para>Clearly, using arbitrary names for the options makes it very hard to
track their usage throughout the kernel source tree. That is the
rationale behind the <emphasis>new-style</emphasis> option scheme, where
@ -83,7 +83,7 @@ options notyet,notdef</programlisting>
the usual Makefile dependencies could be applied, and
<command>make</command> can determine what needs to be recompiled once
an option has been changed.</para>
<para>The old-style option mechanism still has one advantage for local
options or maybe experimental options that have a short anticipated
lifetime: since it is easy to add a new <literal>#ifdef</literal> to the
@ -104,7 +104,7 @@ options notyet,notdef</programlisting>
e. g. <filename>sys/i386/conf/options.i386</filename>), and select an
<filename>opt_<replaceable>foo</replaceable>.h</filename> file where
your new option would best go into.</para>
<para>If there is already something that comes close to the purpose of the
new option, pick this. For example, options modifying the overall
behaviour of the SCSI subsystem can go into
@ -113,7 +113,7 @@ options notyet,notdef</programlisting>
implies its value will go into the corresponding file
<filename>opt_foo.h</filename>. This can be overridden on the
right-hand side of a rule by specifying another filename.</para>
<para>If there is no
<filename>opt_<replaceable>foo</replaceable>.h</filename> already
available for the intended new option, invent a new name. Make it
@ -122,12 +122,12 @@ options notyet,notdef</programlisting>
file. &man.config.8; will automagically pick up the change, and create
that file next time it is run. Most options should go in a header file
by themselves..</para>
<para>Packing too many options into a single
<filename>opt_<replaceable>foo</replaceable>.h</filename> will cause too
many kernel files to be rebuilt when one of the options has been changed
in the config file.</para>
<para>Finally, find out which kernel files depend on the new option.
Unless you have just invented your option, and it does not exist
anywhere yet, <screen>&prompt.user; <userinput>find /usr/src/sys -name
@ -139,7 +139,7 @@ options notyet,notdef</programlisting>
the regular include files, if the defaults are of the form
<programlisting> #ifndef NEW_OPTION #define NEW_OPTION (something)
#endif</programlisting> in the regular header.</para>
<para>Adding an option that overrides something in a system header file
(i.e., a file sitting in <filename>/usr/include/sys/</filename>) is
almost always a mistake.

28
en_US.ISO8859-1/books/handbook/l10n/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml,v 1.14 1999/09/06 06:53:00 peter Exp $
-->
<chapter id="l10n">
@ -30,7 +30,7 @@ options "SC_MOUSE_CHAR=0x03"</programlisting>
to move character codes used for mouse cursor off KOI8-R
pseudographics range.</para>
</step>
<step>
<para>Russian console entry in
<filename>/etc/rc.conf</filename> should looks like:</para>
@ -59,7 +59,7 @@ font8x8=cp866-8x8</programlisting>
<literal>Shift+CapsLock</literal>. CapsLock LED will indicate RUS
mode, not CapsLock mode.</para>
</step>
<step>
<para>For each <literal>ttyv?</literal> entry in
<filename>/etc/ttys</filename> change terminal type from
@ -83,7 +83,7 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure</programlisting>
<para><envar>LANG</envar> for POSIX &man.setlocale.3; family
functions;</para>
</listitem>
<listitem>
<para><envar>MM_CHARSET</envar> for applications MIME character
set.</para>
@ -97,17 +97,17 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure</programlisting>
<sect3 id="russian-class">
<title>Login Class Method</title>
<para>First of all check your <filename>/etc/login.conf</filename>
have <literal>russian</literal> login class, this entry may looks
like:</para>
<programlisting>
russian:Russian Users Accounts:\
:charset=KOI8-R:\
:lang=ru_RU.KOI8-R:\
:tc=default:</programlisting>
<sect4>
<title>How to do it with &man.vipw.8;</title>
@ -118,7 +118,7 @@ russian:Russian Users Accounts:\
<programlisting>
user:password:1111:11:russian:0:0:User Name:/home/user:/bin/csh</programlisting>
</sect4>
<sect4>
<title>How to do it with &man.adduser.8;</title>
@ -153,7 +153,7 @@ defaultclass = russian</programlisting>
</listitem>
</itemizedlist>
</sect4>
<sect4>
<title>How to do it with &man.pw.8;</title>
@ -166,12 +166,12 @@ defaultclass = russian</programlisting>
<sect3>
<title>Shell Startup Files Method</title>
<para>If you don't want to use <link linkend="russian-class">login
class method</link> for some reasons, just set this <link
linkend="russian-env">two environment variables</link> in the
following shell startup files:</para>
<itemizedlist>
<listitem>
<para><filename>/etc/profile</filename>:</para>
@ -189,7 +189,7 @@ setenv LANG ru_RU.KOI8-R
setenv MM_CHARSET KOI8-R</programlisting>
</listitem>
</itemizedlist>
<para>Alternatively you can add this instructions to</para>
<itemizedlist>
@ -259,7 +259,7 @@ lp|Russian local line printer:\
less than 3.3 first).</para>
</note>
</step>
<step>
<para>Go to <filename>/usr/ports/russian/X.language</filename>
directory and say
@ -281,7 +281,7 @@ FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/100dpi"</programlisting>
<para>If you use high resolution video mode, swap 75 dpi and 100 dpi
lines.</para>
</step>
<step>
<para>To activate Russian keyboard add

42
en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml,v 1.22 1999/09/15 18:34:26 obrien Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml,v 1.24 1999/09/15 19:29:38 obrien Exp $
-->
<chapter id="linuxemu">
@ -19,16 +19,16 @@
&rel.current;-RELEASE is vastly more capable and runs all these as well
as Oracle8, WordPerfect, StarOffice, Acrobat, Quake, Abuse, IDL, and
netrek for Linux and a whole host of other programs.</para>
<para>There are some Linux-specific operating system features that are not
supported on FreeBSD. Linux binaries will not work on FreeBSD if they
overly use the Linux <filename>/proc</filename> filesystem (which is
different from the optional FreeBSD <filename>/proc</filename> filesystem)
or i386-specific calls, such as enabling virtual 8086 mode.</para>
<para>Depending on which version of FreeBSD you are running, how you get
Linux mode up will vary somewhat:</para>
<sect2>
<title>Installing Linux Mode in 3.0-RELEASE and later</title>
@ -210,7 +210,7 @@ linux</programlisting>
<sect3>
<title>Installing using the linux_base port</title>
<para>Most Linux applications use shared libraries, so you are still
not done until you install the shared libraries. It is possible to
do this by hand, however, it is vastly simpler to just grab the
@ -231,7 +231,7 @@ linux</programlisting>
<sect3>
<title>Installing libraries manually</title>
<para>If you do not have the &ldquo;ports&rdquo; distribution, you can
install the libraries by hand instead. You will need the Linux
shared libraries that the program depends on and the runtime linker.
@ -262,7 +262,7 @@ linux</programlisting>
<sect3>
<title>How to install additional shared libraries</title>
<para>What if you install the <filename>linux_base</filename> port and
your application still complains about missing shared libraries? How
do you know which shared libraries Linux binaries need, and where to
@ -281,7 +281,7 @@ linux</programlisting>
libXt.so.3 (DLL Jump 3.1) =&gt; /usr/X11/lib/libXt.so.3.1.0
libX11.so.3 (DLL Jump 3.1) =&gt; /usr/X11/lib/libX11.so.3.1.0
libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
<para>You would need to get all the files from the last column, and
put them under <filename>/compat/linux</filename>, with the names in
the first column as symbolic links pointing to them. This means you
@ -321,7 +321,7 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
<screen>/compat/linux/lib/libc.so.4.6.29
/compat/linux/lib/libc.so.4 -&gt; libc.so.4.6.29</screen>
</note>
<note>
<para>The symbolic link mechanism is <emphasis>only</emphasis>
needed for Linux binaries. The FreeBSD runtime linker takes care
@ -333,7 +333,7 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
<sect3>
<title>Configuring the <filename>ld.so</filename> &mdash; for FreeBSD
2.2-RELEASE and later</title>
<para>This section applies only to FreeBSD 2.2-RELEASE and later.
Those running 2.1-STABLE should skip this section.</para>
@ -350,7 +350,7 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
extra files you need from various ftp sites. Information on where
to look for the various files is appended below. For now, let us
assume you know where to get the files.</para>
<para>Retrieve the following files (all from the same ftp site to
avoid any version mismatches), and install them under
<filename>/compat/linux</filename> (i.e.
@ -402,7 +402,7 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
the names of all the shared libraries and should be rerun to
recreate this file whenever you install additional shared
libraries.</para>
<para>On 2.1-STABLE do not install
<filename>/compat/linux/etc/ld.so.cache</filename> or run
<command>ldconfig</command>; in 2.1-STABLE the syscalls are
@ -471,10 +471,10 @@ Abort</screen>
<title>Configuring the host name resolver</title>
<para>If DNS does not work or you get the messages
<screen>resolv+: "bind" is an invalid keyword resolv+:
"hosts" is an invalid keyword</screen>
then you need to configure a
<filename>/compat/linux/etc/host.conf</filename> file containing:
@ -526,7 +526,7 @@ multi on</programlisting>
<listitem>
<para>sunsite.unc.edu:/pub/Linux/distributions</para>
</listitem>
<listitem>
<para>tsx-11.mit.edu:/pub/linux/distributions</para>
</listitem>
@ -538,11 +538,11 @@ multi on</programlisting>
<listitem>
<para>ftp.luth.se:/pub/linux/distributions</para>
</listitem>
<listitem>
<para>ftp.demon.co.uk:/pub/unix/linux</para>
</listitem>
<listitem>
<para>src.doc.ic.ac.uk:/packages/linux/distributions</para>
</listitem>
@ -666,15 +666,15 @@ multi on</programlisting>
<listitem>
<para><filename>slakware/a2/ldso.tgz</filename></para>
</listitem>
<listitem>
<para><filename>slakware/a2/shlibs.tgz</filename></para>
</listitem>
<listitem>
<para><filename>slakware/x6/oldlibs.tgz</filename></para>
</listitem>
<listitem>
<para><filename>slakware/x9/xf_lib.tgz</filename></para>
</listitem>
@ -705,7 +705,7 @@ multi on</programlisting>
DOS the cost of upgrading to the Linux version at the time this was
written, March 1996, was &#36;45.00. It can be ordered directly from
Wolfram at (217) 398-6500 and paid for by credit card.</para>
<sect2>
<title>Unpacking the Mathematica distribution</title>

8
en_US.ISO8859-1/books/handbook/mail/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mail/chapter.sgml,v 1.14 1999/09/06 06:53:01 peter Exp $
-->
<chapter id="mail">
@ -25,7 +25,7 @@
<para>These are the major programs involved in an E-Mail exchange. A
&ldquo;mailhost&rdquo; is a server that is responsible for delivering
and receiving all email for your host, and possibly your network.</para>
<sect2>
<title>User program</title>
@ -94,7 +94,7 @@
This handbook section has a complete reference on the <link
linkend="ports">Ports</link> system.</para>
</step>
<step>
<para>Modify <filename>/etc/inetd.conf</filename> to load the POP
server.</para>
@ -123,7 +123,7 @@
your own domain <hostid role="domainname">smallminingco.com
</hostid></para>
</listitem>
<listitem>
<para>Get mail delivered to the current DNS name for your host. Ie:
<hostid role="fqdn">dorm6.ahouse.school.edu </hostid></para>

114
en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml,v 1.42 1999/10/03 18:54:42 jdp Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml,v 1.43 1999/10/12 20:32:32 tom Exp $
-->
<chapter id="mirrors">
@ -98,7 +98,7 @@
<varlistentry>
<term><anchor id="mirrors-au">Australia</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@au.FreeBSD.org</email> for this domain.</para>
@ -129,7 +129,7 @@
<varlistentry>
<term><anchor id="mirrors-br">Brazil</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@br.FreeBSD.org</email> for this domain.</para>
@ -175,7 +175,7 @@
<varlistentry>
<term><anchor id="mirrors-ca">Canada</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@ca.FreeBSD.org</email> for this domain.</para>
@ -211,7 +211,7 @@
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@cz.FreeBSD.org</email> for this domain.</para>
<itemizedlist>
<listitem>
<para><ulink
@ -227,7 +227,7 @@
<varlistentry>
<term><anchor id="mirrors-dk">Denmark</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@dk.FreeBSD.org</email> for this domain.</para>
@ -243,7 +243,7 @@
<varlistentry>
<term><anchor id="mirrors-ee">Estonia</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@ee.FreeBSD.org</email> for this domain.</para>
@ -259,7 +259,7 @@
<varlistentry>
<term><anchor id="mirrors-fi">Finland</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@fi.FreeBSD.org</email> for this domain.</para>
@ -275,7 +275,7 @@
<varlistentry>
<term><anchor id="mirrors-fr">France</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@fr.FreeBSD.org</email> for this domain.</para>
@ -305,7 +305,7 @@
<varlistentry>
<term><anchor id="mirrors-de">Germany</term>
<listitem>
<para>In case of problems, please contact the mirrors admins
<email>de-bsd-hubs@de.freebsd.org </email> for this domain.</para>
@ -351,7 +351,7 @@
<varlistentry>
<term><anchor id="mirrors-hk">Hong Kong</term>
<listitem>
<itemizedlist>
@ -365,7 +365,7 @@
<varlistentry>
<term><anchor id="mirrors-ie">Ireland</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@ie.FreeBSD.org</email> for this domain.</para>
@ -381,7 +381,7 @@
<varlistentry>
<term><anchor id="mirrors-il">Israel</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@il.FreeBSD.org</email> for this domain.</para>
@ -402,7 +402,7 @@
<varlistentry>
<term><anchor id="mirrors-jp">Japan</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@jp.FreeBSD.org</email> for this domain.</para>
@ -443,7 +443,7 @@
<varlistentry>
<term><anchor id="mirrors-kr">Korea</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@kr.FreeBSD.org</email> for this domain.</para>
@ -481,7 +481,7 @@
<varlistentry>
<term><anchor id="mirrors-nl">Netherlands</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@nl.FreeBSD.org</email> for this domain.</para>
@ -497,7 +497,7 @@
<varlistentry>
<term><anchor id="mirrors-nz">New Zealand</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@nz.FreeBSD.org</email> for this domain.</para>
@ -512,7 +512,7 @@
<varlistentry>
<term><anchor id="mirrors-pl">Poland</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@pl.FreeBSD.org</email> for this domain.</para>
@ -528,7 +528,7 @@
<varlistentry>
<term><anchor id="mirrors-pt">Portugal</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@pt.FreeBSD.org</email> for this domain.</para>
@ -549,7 +549,7 @@
<varlistentry>
<term><anchor id="mirrors-ru">Russia</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@ru.FreeBSD.org</email> for this domain.</para>
@ -595,7 +595,7 @@
<varlistentry>
<term><anchor id="mirrors-za">South Africa</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@za.FreeBSD.org</email> for this domain.</para>
@ -621,7 +621,7 @@
<varlistentry>
<term><anchor id="mirrors-sk">Slovak Republic</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@sk.FreeBSD.org</email> for this domain.</para>
@ -635,7 +635,7 @@
</varlistentry>
<varlistentry><term><anchor id="mirrors-si">Slovenia</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@si.FreeBSD.org</email> for this domain.</para>
@ -651,7 +651,7 @@
<varlistentry>
<term><anchor id="mirrors-es">Spain</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@es.FreeBSD.org</email> for this domain.</para>
@ -666,7 +666,7 @@
<varlistentry>
<term><anchor id="mirrors-se">Sweden</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@se.FreeBSD.org</email> for this domain.</para>
@ -723,7 +723,7 @@
<varlistentry>
<term><anchor id="mirrors-th">Thailand</term>
<listitem>
<itemizedlist>
<listitem>
@ -736,7 +736,7 @@
<varlistentry>
<term><anchor id="mirrors-ua">Ukraine</term>
<listitem>
<itemizedlist>
<listitem>
@ -749,7 +749,7 @@
<varlistentry>
<term><anchor id="mirrors-uk">UK</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@uk.FreeBSD.org</email> for this domain.</para>
@ -780,7 +780,7 @@
<varlistentry>
<term><anchor id="mirrors-us">USA</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@FreeBSD.org</email> for this domain.</para>
@ -829,7 +829,7 @@
<variablelist>
<varlistentry>
<term>South Africa</term>
<listitem>
<para>Hostmaster <email>hostmaster@internat.FreeBSD.org</email> for
this domain.</para>
@ -850,7 +850,7 @@
<varlistentry>
<term>Brazil</term>
<listitem>
<para>Hostmaster <email>hostmaster@br.FreeBSD.org</email> for this
domain.</para>
@ -866,7 +866,7 @@
<varlistentry>
<term>Finland</term>
<listitem>
<itemizedlist>
<listitem>
@ -885,7 +885,7 @@
<para><link linkend="ctm">CTM</link>/FreeBSD is available via anonymous
FTP from the following mirror sites. If you choose to obtain CTM via
anonymous FTP, please try to use a site near you.</para>
<para>In case of problems, please contact &a.phk;.</para>
<variablelist>
@ -904,7 +904,7 @@
<varlistentry>
<term>Germany, Trier</term>
<listitem>
<itemizedlist>
<listitem>
@ -917,7 +917,7 @@
<varlistentry>
<term>South Africa, backup server for old deltas</term>
<listitem>
<itemizedlist>
<listitem>
@ -930,7 +930,7 @@
<varlistentry>
<term>Taiwan/R.O.C, Chiayi</term>
<listitem>
<itemizedlist>
<listitem>
@ -982,7 +982,7 @@
<varlistentry>
<term>Australia</term>
<listitem>
<itemizedlist>
<listitem>
@ -995,7 +995,7 @@
<varlistentry>
<term>Brazil</term>
<listitem>
<itemizedlist>
<listitem>
@ -1057,7 +1057,7 @@
<varlistentry>
<term>Denmark</term>
<listitem>
<itemizedlist>
<listitem>
@ -1083,7 +1083,7 @@
<varlistentry>
<term>Finland</term>
<listitem>
<itemizedlist>
<listitem>
@ -1114,7 +1114,7 @@
<varlistentry>
<term>Germany</term>
<listitem>
<itemizedlist>
<listitem>
@ -1137,7 +1137,7 @@
<varlistentry>
<term>Iceland</term>
<listitem>
<itemizedlist>
<listitem>
@ -1150,7 +1150,7 @@
<varlistentry>
<term>Japan</term>
<listitem>
<itemizedlist>
@ -1184,7 +1184,7 @@
<varlistentry>
<term>Korea</term>
<listitem>
<itemizedlist>
@ -1198,7 +1198,7 @@
<varlistentry>
<term>Netherlands</term>
<listitem>
<itemizedlist>
<listitem>
@ -1216,7 +1216,7 @@
<varlistentry>
<term>Norway</term>
<listitem>
<itemizedlist>
<listitem>
@ -1229,7 +1229,7 @@
<varlistentry>
<term>Poland</term>
<listitem>
<itemizedlist>
<listitem>
@ -1242,7 +1242,7 @@
<varlistentry>
<term>Russia</term>
<listitem>
<itemizedlist>
<listitem>
@ -1260,7 +1260,7 @@
<varlistentry>
<term>Slovak Republic</term>
<listitem>
<itemizedlist>
<listitem>
@ -1291,7 +1291,7 @@
<varlistentry>
<term>South Africa</term>
<listitem>
<itemizedlist>
<listitem>
@ -1322,7 +1322,7 @@
<varlistentry>
<term>Sweden</term>
<listitem>
<itemizedlist>
<listitem>
@ -1335,7 +1335,7 @@
<varlistentry>
<term>Taiwan</term>
<listitem>
<itemizedlist>
<listitem>
@ -1359,7 +1359,7 @@
<varlistentry>
<term>Ukraine</term>
<listitem>
<itemizedlist>
@ -1373,7 +1373,7 @@
<varlistentry>
<term>United Kingdom</term>
<listitem>
<itemizedlist>
<listitem>
@ -1391,7 +1391,7 @@
<varlistentry>
<term>USA</term>
<listitem>
<itemizedlist>
<listitem>
@ -1453,7 +1453,7 @@
</listitem>
</varlistentry>
</variablelist>
<para>The following <application>CVSup</application> site is especially
designed for <link linkend="ctm">CTM</link> users. Unlike the other
CVSup mirrors, it is kept up-to-date by <application>CTM</application>.
@ -1508,7 +1508,7 @@
<variablelist>
<varlistentry>
<term>Sweden</term>
<listitem>
<para>The path to the files are:
<filename>/afs/stacken.kth.se/ftp/pub/FreeBSD/</filename></para>

4
en_US.ISO8859-1/books/handbook/pgpkeys/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/pgpkeys/chapter.sgml,v 1.18 1999/10/26 04:55:42 cpiazza Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/pgpkeys/chapter.sgml,v 1.19 1999/10/26 05:18:01 cpiazza Exp $
-->
<chapter id="pgpkeys">
@ -317,7 +317,7 @@ Sb97WRLEYDi686osaGfsuKNA87Rm+q5F+jxeUV4w4szoqp60gGvCbD0KCB2hWraP
=QoiM
-----END PGP PUBLIC KEY BLOCK-----</programlisting>
</sect2>
<sect2>
<title>&a.jdp;</title>

38
en_US.ISO8859-1/books/handbook/policies/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.11 1999/09/06 06:53:02 peter Exp $
-->
<chapter id="policies">
@ -20,27 +20,27 @@
<para>If a particular portion of the FreeBSD distribution is being
maintained by a person or group of persons, they can communicate this
fact to the world by adding a
<programlisting>
MAINTAINER= email-addresses</programlisting>
line to the <filename>Makefile</filename>s covering this portion of the
source tree.</para>
<para>The semantics of this are as follows:</para>
<para>The maintainer owns and is responsible for that code. This means
that he is responsible for fixing bugs and answer problem reports
pertaining to that piece of the code, and in the case of contributed
software, for tracking new versions, as appropriate.</para>
<para>Changes to directories which have a maintainer defined shall be sent
to the maintainer for review before being committed. Only if the
maintainer does not respond for an unacceptable period of time, to
several emails, will it be acceptable to commit changes without review
by the maintainer. However, it is suggested that you try and have the
changes reviewed by someone else if at all possible.</para>
<para>It is of course not acceptable to add a person or group as
maintainer unless they agree to assume this duty. On the other hand it
doesn't have to be a committer and it can easily be a group of
@ -58,11 +58,11 @@ MAINTAINER= email-addresses</programlisting>
actively being maintained outside the FreeBSD project. For historical
reasons, we call this <emphasis>contributed</emphasis> software. Some
examples are perl, gcc and patch.</para>
<para>Over the last couple of years, various methods have been used in
dealing with this type of software and all have some number of
advantages and drawbacks. No clear winner has emerged.</para>
<para>Since this is the case, after some debate one of these methods has
been selected as the &ldquo;official&rdquo; method and will be required
for future imports of software of this kind. Furthermore, it is
@ -72,7 +72,7 @@ MAINTAINER= email-addresses</programlisting>
&ldquo;official&rdquo; versions of the source by everyone (even without
cvs access). This will make it significantly easier to return changes
to the primary developers of the contributed software.</para>
<para>Ultimately, however, it comes down to the people actually doing the
work. If using this model is particularly unsuited to the package being
dealt with, exceptions to these rules may be granted only with the
@ -93,28 +93,28 @@ MAINTAINER= email-addresses</programlisting>
<para>The <application>Tcl</application> embedded programming
language will be used as example of how this model works:</para>
<para><filename>src/contrib/tcl</filename> contains the source as
distributed by the maintainers of this package. Parts that are entirely
not applicable for FreeBSD can be removed. In the case of Tcl, the
<filename>mac</filename>, <filename>win</filename> and
<filename>compat</filename> subdirectories were eliminated before the
import</para>
<para><filename>src/lib/libtcl</filename> contains only a "bmake style"
<filename>Makefile</filename> that uses the standard
<filename>bsd.lib.mk</filename> makefile rules to produce the library
and install the documentation.</para>
<para><filename>src/usr.bin/tclsh</filename> contains only a bmake style
<filename>Makefile</filename> which will produce and install the
<command>tclsh</command> program and its associated man-pages using the
standard <filename>bsd.prog.mk</filename> rules.</para>
<para><filename>src/tools/tools/tcl_bmake</filename> contains a couple of
shell-scripts that can be of help when the tcl software needs updating.
These are not part of the built or installed software.</para>
<para>The important thing here is that the
<filename>src/contrib/tcl</filename> directory is created according to
the rules: It is supposed to contain the sources as distributed (on a
@ -133,7 +133,7 @@ MAINTAINER= email-addresses</programlisting>
be patched into the FreeBSD checked out version and "committed", as this
destroys the vendor branch coherency and makes importing future versions
rather difficult as there will be conflicts.</para>
<para>Since many packages contain files that are meant for compatibility
with other architectures and environments that FreeBSD, it is
permissible to remove parts of the distribution tree that are of no
@ -148,7 +148,7 @@ MAINTAINER= email-addresses</programlisting>
check in such utilities (as necessary) in the
<filename>src/tools</filename> directory along with the port itself so
that it is available to future maintainers.</para>
<para>In the <filename>src/contrib/tcl</filename> level directory, a file
called <filename>FREEBSD-upgrade</filename> should be added and it
should states things like:</para>
@ -177,7 +177,7 @@ MAINTAINER= email-addresses</programlisting>
with the contributed source. Rather you should <command>cvs add
FREEBSD-upgrade ; cvs ci</command> after the initial import. Example
wording from <filename>src/contrib/cpio</filename> is below:</para>
<programlisting>
This directory contains virgin sources of the original distribution files
on a "vendor" branch. Do not, under any circumstances, attempt to upgrade
@ -316,12 +316,12 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
<para><emphasis>Contributed by &a.asami;, &a.peter;, and &a.obrien; 9
December 1996.</emphasis></para>
<para>If you are adding shared library support to a port or other piece of
software that doesn't have one, the version numbers should follow these
rules. Generally, the resulting numbers will have nothing to do with
the release version of the software.</para>
<para>The three principles of shared library building are:</para>
<itemizedlist>

136
en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.16 1999/09/06 06:53:03 peter Exp $
-->
<chapter id="ppp-and-slip">
@ -36,13 +36,13 @@
ppp program can be run as and when desired. No PPP interface needs to
be compiled into the kernel, as the program can use the generic tunnel
device to get data into and out of the kernel.</para>
<para>From here on out, user ppp will be referred to simply as ppp unless
a distinction needs to be made between it and any other PPP
client/server software such as <command>pppd</command>. Unless
otherwise stated, all commands in this section should be executed as
root.</para>
<para>There are a large number of enhancements in version 2 of ppp. You
can discover what version you have by running ppp with no arguments and
typing <command>show version</command> at the prompt. It is a simple
@ -66,13 +66,13 @@
<listitem>
<para>Your ISPs phone number(s).</para>
</listitem>
<listitem>
<para>Your login name and password. This can be either a regular
unix style login/password pair, or a PPP PAP or CHAP
login/password pair.</para>
</listitem>
<listitem>
<para>The IP addresses of one or more nameservers. Normally, you
will be given two IP numbers. You <emphasis>must</emphasis> have
@ -100,7 +100,7 @@
<para>This IP number is referred to as <literal>HISADDR</literal>
by ppp.</para>
</listitem>
<listitem>
<para>Your ISP's netmask. If your ISP hasn't given you this
information, you can safely use a netmask of <hostid
@ -232,7 +232,7 @@ tun0: flags=8010&lt;POINTOPOINT,MULTICAST> mtu 1500</screen>
<sect3>
<title>Edit the <filename>/etc/host.conf</filename> file</title>
<para>This file should contain the following two lines (in this
order):</para>
@ -247,7 +247,7 @@ bind</programlisting>
<sect3>
<title>Edit the <filename>/etc/hosts</filename>(5) file</title>
<para>This file should contain the IP addresses and names of machines
on your network. At a bare minimum it should contain entries for
the machine which will be running ppp. Assuming that your machine
@ -258,7 +258,7 @@ bind</programlisting>
<programlisting>
127.0.0.1 localhost
10.0.0.1 foo.bar.com foo</programlisting>
<para>The first line defines the alias <hostid>localhost</hostid> as a
synonym for the current machine. Regardless of your own IP address,
the IP address for this line should always be <hostid
@ -274,7 +274,7 @@ bind</programlisting>
<sect3>
<title>Edit the <filename>/etc/resolv.conf</filename> file</title>
<para><filename>/etc/resolv.conf</filename> tells the resolver how to
behave. If you are running your own DNS, you may leave this file
empty. Normally, you will need to enter the following
@ -294,7 +294,7 @@ domain <replaceable>bar.com</replaceable></programlisting>
and is probably unnecessary. Refer to the
<filename>resolv.conf</filename> manual page for details of other
possible entries in this file.</para>
<para>If you are running PPP version 2 or greater, the <command>enable
dns</command> command will tell PPP to request that your ISP
confirms the nameserver values. If your ISP supplies different
@ -322,17 +322,17 @@ domain <replaceable>bar.com</replaceable></programlisting>
<sect3 id="userppp-staticIP">
<title>PPP and Static IP addresses</title>
<para>You will need to create a configuration file called
<filename>/etc/ppp/ppp.conf</filename>. It should look similar to
the example below.</para>
<note>
<para>Lines that end in a <literal>:</literal> start in the first
column, all other lines should be indented as shown using spaces
or tabs.</para>
</note>
<programlisting>
1 default:
2 set device /dev/cuaa0
@ -498,21 +498,21 @@ protocol: ppp</screen>
</listitem>
</varlistentry>
</variablelist>
<para>It is not necessary to add an entry to
<filename>ppp.linkup</filename> when you have a static IP address as
your routing table entries are already correct before you connect.
You may however wish to create an entry to invoke programs after
connection. This is explained later with the sendmail
example.</para>
<para>Example configuration files can be found in the
<filename>/etc/ppp</filename> directory.</para>
</sect3>
<sect3 id="userppp-dynamicIP">
<title>PPP and Dynamic IP addresses</title>
<para>If your service provider does not assign static IP numbers,
<command>ppp</command> can be configured to negotiate the local and
remote addresses. This is done by &ldquo;guessing&rdquo; an IP
@ -549,7 +549,7 @@ protocol: ppp</screen>
</listitem>
</varlistentry>
</variablelist>
<para>If you are running version 1.x of PPP, you will also need to
create an entry in <filename>/etc/ppp/ppp.linkup</filename>.
<filename>ppp.linkup</filename> is used after a connection has been
@ -599,7 +599,7 @@ protocol: ppp</screen>
</listitem>
</varlistentry>
</variablelist>
<para>See the pmdemand entry in the files
<filename>/etc/ppp/ppp.conf.sample</filename> and
<filename>/etc/ppp/ppp.linkup.sample</filename> for a detailed
@ -619,7 +619,7 @@ protocol: ppp</screen>
<para>This section describes setting up <command>ppp</command> in a
server role.</para>
<para>When you configure <command>ppp</command> to receive incoming
calls on a machine connected to a LAN, you must decide if you wish
to forward packets to the LAN. If you do, you should allocate the
@ -661,7 +661,7 @@ gateway=YES</programlisting>
AutoPPP</link> for more information on
<command>mgetty</command>.</para>
</sect4>
<sect4>
<title>PPP permissions</title>
@ -683,7 +683,7 @@ allow users fred mary</programlisting>
<para>If this command is used in the <literal>default</literal>
section, it gives the specified users access to everything.</para>
</sect4>
<sect4>
<title>Setting up a PPP shell for dynamic-IP users</title>
@ -729,7 +729,7 @@ pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialup</programlistin
which prevents <filename>/etc/motd</filename> from being
displayed.</para>
</sect4>
<sect4>
<title>Setting up a PPP shell for static-IP users</title>
@ -751,7 +751,7 @@ pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialup</programlistin
<username>mary</username>'s shell should be
<filename>/etc/ppp/ppp-mary</filename>).</para>
</sect4>
<sect4>
<title>Setting up ppp.conf for dynamic-IP users</title>
@ -782,7 +782,7 @@ ttyd1:
unique IP address from your pool of IP addresses for dynamic
users.</para>
</sect4>
<sect4>
<title>Setting up <filename>ppp.conf</filename> for static-IP
users</title>
@ -820,7 +820,7 @@ sam:
mary:
add 203.14.103.0 netmask 255.255.255.0 HISADDR</programlisting>
</sect4>
<sect4>
<title>More on <command>mgetty</command>, AutoPPP, and MS
extensions</title>
@ -921,7 +921,7 @@ set nbns 203.14.100.5</programlisting>
<sect3 id="userppp-PAPnCHAP">
<title>PAP and CHAP authentication</title>
<para>Some ISPs set their system up so that the authentication part of
your connection is done using either of the PAP or CHAP
authentication mechanisms. If this is the case, your ISP will not
@ -996,7 +996,7 @@ set nbns 203.14.100.5</programlisting>
<sect3>
<title>Changing your <command>ppp</command> configuration on the
fly</title>
<para>It is possible to talk to the <command>ppp</command> program
while it is running in the background, but only if a suitable
diagnostic port has been set up. To do this, add the following line
@ -1004,7 +1004,7 @@ set nbns 203.14.100.5</programlisting>
<programlisting>
set server /var/run/ppp-tun%d DiagnosticPassword 0177</programlisting>
<para>This will tell PPP to listen to the specified unix-domain
socket, asking clients for the specified password before allowing
access. The <literal>%d</literal> in the name is replaced with the
@ -1123,29 +1123,29 @@ sendmail_flags="-bd"</programlisting>
<para>Ensure that the <devicename>tun</devicename> device is built
into your kernel.</para>
</step>
<step>
<para>Ensure that the
<filename>tun<replaceable>X</replaceable></filename> device file
is available in the <filename>/dev</filename> directory.</para>
</step>
<step>
<para>Create an entry in <filename>/etc/ppp/ppp.conf</filename>.
The <filename>pmdemand</filename> example should suffice for most
ISPs.</para>
</step>
<step>
<para>If you have a dynamic IP address, create an entry in
<filename>/etc/ppp/ppp.linkup</filename>.</para>
</step>
<step>
<para>Update your <filename>/etc/rc.conf</filename> (or
<filename>sysconfig</filename>) file.</para>
</step>
<step>
<para>Create a <filename>start_if.tun0</filename> script if you
require demand dialing.</para>
@ -1159,34 +1159,34 @@ sendmail_flags="-bd"</programlisting>
<para>Ensure that the <devicename>tun</devicename> device is built
into your kernel.</para>
</step>
<step>
<para>Ensure that the
<filename>tun<replaceable>X</replaceable></filename> device file
is available in the <filename>/dev</filename> directory.</para>
</step>
<step>
<para>Create an entry in <filename>/etc/passwd</filename> (using the
&man.vipw.8; program).</para>
</step>
<step>
<para>Create a profile in this users home directory that runs
<command>ppp -direct direct-server</command> or similar.</para>
</step>
<step>
<para>Create an entry in <filename>/etc/ppp/ppp.conf</filename>.
The <filename>direct-server</filename> example should
suffice.</para>
</step>
<step>
<para>Create an entry in
<filename>/etc/ppp/ppp.linkup</filename>.</para>
</step>
<step>
<para>Update your <filename>/etc/rc.conf</filename> (or
<filename>sysconfig</filename>) file.</para>
@ -1219,9 +1219,9 @@ sendmail_flags="-bd"</programlisting>
<para>Before you start setting up PPP on your machine make sure that
<command>pppd</command> is located in <filename>/usr/sbin</filename> and
directory <filename>/etc/ppp</filename> exists.</para>
<para><command>pppd</command> can work in two modes:</para>
<orderedlist>
<listitem>
<para>as a &ldquo;client&rdquo;, i.e. you want to connect your machine
@ -1237,10 +1237,10 @@ sendmail_flags="-bd"</programlisting>
<para>In both cases you will need to set up an options file
(<filename>/etc/ppp/options</filename> or <filename>~/.ppprc</filename>
if you have more then one user on your machine that uses PPP).</para>
<para>You also will need some modem/serial software (preferably kermit) so
you can dial and establish connection with remote host.</para>
<sect2>
<title>Working as a PPP client</title>
@ -1272,11 +1272,11 @@ defaultroute # put this if you want that PPP server will be your
enter your user name and password (or whatever is needed to enable
PPP on the remote host)</para>
</step>
<step>
<para>Exit kermit (without hanging up the line).</para>
</step>
<step>
<para>enter:</para>
@ -1654,12 +1654,12 @@ exit 1
<title>Setting up a SLIP Client</title>
<para><emphasis>Contributed by &a.asami; 8 Aug 1995.</emphasis></para>
<para>The following is one way to set up a FreeBSD machine for SLIP on a
static host network. For dynamic hostname assignments (i.e., your
address changes each time you dial up), you probably need to do
something much fancier.</para>
<para>First, determine which serial port your modem is connected to. I
have a symbolic link to <filename>/dev/modem</filename> from
<filename>/dev/cuaa1</filename>, and only use the modem name in my
@ -1681,7 +1681,7 @@ pseudo-device sl 1</programlisting>
in your kernel's config file. It is included in the
<filename>GENERIC</filename> kernel, so this will not be a problem
unless you deleted it.</para>
<sect2>
<title>Things you have to do only once</title>
@ -1707,7 +1707,7 @@ pseudo-device sl 1</programlisting>
<option>bind</option> in your <filename>/etc/host.conf</filename>.
Otherwise, funny things may happen.</para>
</step>
<step>
<para>Edit the file <filename>/etc/rc.conf</filename>. Note that
you should edit the file <filename>/etc/sysconfig</filename>
@ -1757,7 +1757,7 @@ defaultrouter=slip-gateway</programlisting>
</listitem>
</orderedlist>
</step>
<step>
<para>Make a file <filename>/etc/resolv.conf</filename> which
contains:</para>
@ -1821,7 +1821,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
am just too lazy.</para>
</note>
</step>
<step>
<para>Leave the kermit there (you can suspend it by
<command>z</command>) and as root, type:</para>
@ -1835,7 +1835,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
</step>
</procedure>
</sect2>
<sect2>
<title>How to shutdown the connection</title>
@ -1869,12 +1869,12 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
slattach (I have no idea why this can be fatal, but adding this
flag solved the problem for at least one person)</para>
</listitem>
<listitem>
<para>Using <option>s10</option> instead of <option>sl0</option>
(might be hard to see the difference on some fonts).</para>
</listitem>
<listitem>
<para>Try <command>ifconfig sl0</command> to see your interface
status. I get:</para>
@ -1925,7 +1925,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438
not answer all of your questions, and the author cannot be responsible
if you damage your system or lose data due to attempting to follow the
suggestions here.</para>
<para>This guide was originally written for SLIP Server services on a
FreeBSD 1.x system. It has been modified to reflect changes in the
pathnames and the removal of the SLIP interface compression flags in
@ -1933,7 +1933,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438
between FreeBSD versions. If you do encounter mistakes in this
document, please email the author with enough information to help
correct the problem.</para>
<sect2 id="slips-prereqs">
<title>Prerequisites</title>
@ -1981,7 +1981,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438
<sect3>
<title>An Example of a SLIP Server Login</title>
<para>For example, if a SLIP user ID were
<username>Shelmerg</username>, <username>Shelmerg</username>'s entry
in <filename>/etc/master.passwd</filename> would look something like
@ -2107,10 +2107,10 @@ pseudo-device sl 2</programlisting>
<sect3>
<title><filename>slip.hosts</filename> Configuration</title>
<para><filename>/etc/sliphome/slip.hosts</filename> contains lines
which have at least four items, separated by whitespace:</para>
<itemizedlist>
<listitem>
<para>SLIP user's login ID</para>
@ -2129,7 +2129,7 @@ pseudo-device sl 2</programlisting>
<para>Network mask</para>
</listitem>
</itemizedlist>
<para>The local and remote addresses may be host names (resolved to IP
addresses by <filename>/etc/hosts</filename> or by the domain name
service, depending on your specifications in
@ -2147,7 +2147,7 @@ pseudo-device sl 2</programlisting>
Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting>
<para>At the end of the line is one or more of the options.</para>
<itemizedlist>
<listitem>
<para><option>normal</option> &mdash; no header compression</para>
@ -2168,7 +2168,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
your bandwidth)</para>
</listitem>
</itemizedlist>
<para>Note that <command>sliplogin</command> under early releases of
FreeBSD 2 ignored the options that FreeBSD 1.x recognized, so the
options <option>normal</option>, <option>compress</option>,
@ -2208,7 +2208,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
<sect3>
<title><filename>slip.login</filename> Configuration</title>
<para>The typical <filename>/etc/sliphome/slip.login</filename> file
looks like this:</para>
@ -2288,7 +2288,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
<sect3>
<title><filename>slip.logout</filename> Configuration</title>
<para><filename>/etc/sliphome/slip.logout</filename> is not strictly
needed (unless you are implementing &ldquo;proxy ARP&rdquo;), but if
you decide to create it, this is an example of a basic
@ -2351,7 +2351,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
<sect3>
<title>Static Routes</title>
<para>Adding static routes to your nearest default routers can be
troublesome (or impossible, if you do not have authority to do
so...). If you have a multiple-router network in your organization,
@ -2364,7 +2364,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
<sect3>
<title>Running <command>gated</command></title>
<para>An alternative to the headaches of static routes is to install
<command>gated</command> on your FreeBSD SLIP server and configure
it to use the appropriate routing protocols (RIP/OSPF/BGP/EGP) to
@ -2462,7 +2462,7 @@ import proto rip interface ed {
<para></para>
</listitem>
</varlistentry>
<varlistentry>
<term>Piero Serini</term>

222
en_US.ISO8859-1/books/handbook/printing/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/printing/chapter.sgml,v 1.21 1999/09/06 06:53:04 peter Exp $
-->
<chapter id="printing">
@ -23,10 +23,10 @@
<sect1 id="printing-intro-spooler">
<title>What the Spooler Does</title>
<para>LPD controls everything about a host's printers. It is responsible
for a number of things:</para>
<itemizedlist>
<listitem>
<para>It controls access to attached printers and printers attached to
@ -155,13 +155,13 @@
accept data to print instead of a serial or parallel interface, see
<link linkend="printing-advanced-network-net-if">Printers With Networked
Data Stream Interaces</link>.</para>
<para>Although this section is called &ldquo;Simple Printer Setup,&rdquo;
it is actually fairly complex. Getting the printer to work with your
computer and the LPD spooler is the hardest part. The advanced options
like header pages and accounting are fairly easy once you get the
printer working.</para>
<sect2 id="printing-hardware">
<title>Hardware Setup</title>
@ -177,7 +177,7 @@
<sect3 id="printing-ports">
<title>Ports and Cables</title>
<para>Nearly all printers you can get for a PC today support one or
both of the following interfaces:</para>
@ -251,7 +251,7 @@
<sect3 id="printing-parallel">
<title>Parallel Ports</title>
<para>To hook up a printer using a parallel interface, connect the
Centronics cable between the printer and the computer. The
instructions that came with the printer, the computer, or both
@ -264,12 +264,12 @@
<sect3 id="printing-serial">
<title>Serial Ports</title>
<para>To hook up a printer using a serial interface, connect the
proper serial cable between the printer and the computer. The
instructions that came with the printer, the computer, or both
should give you complete guidance.</para>
<para>If you are unsure what the &ldquo;proper serial cable&rdquo; is,
you may wish to try one of the following alternatives:</para>
@ -339,7 +339,7 @@
Communications</link> gives some suggestions on how to do
this.</para>
</step>
<step>
<para>Set up LPD for the printer by modifying the file
<filename>/etc/printcap</filename>. Section <link
@ -350,7 +350,7 @@
<sect3 id="printing-kernel">
<title>Kernel Configuration</title>
<para>The operating system kernel is compiled to work with a specific
set of devices. The serial or parallel interface for your printer
is a part of that set. Therefore, it might be necessary to add
@ -365,22 +365,22 @@
<para>Where <replaceable>N</replaceable> is the number of the serial
port, starting from zero. If you see output similar to the
following:</para>
<screen>sio2 at 0x3e8-0x3ef irq 5 on isa
sio2: type 16550A</screen>
<para>then the kernel supports the port.</para>
<para>To find out if the kernel supports a parallel interface,
type:</para>
<screen>&prompt.root; <userinput>dmesg | grep lpt<replaceable>N</replaceable></userinput></screen>
<para>Where <replaceable>N</replaceable> is the number of the parallel
port, starting from zero. If you see output similar to the
following <screen>lpt0 at 0x378-0x37f on isa</screen> then the
kernel supports the port.</para>
<para>You might have to reconfigure your kernel in order for the
operating system to recognize and use the parallel or serial port
you are using for the printer.</para>
@ -436,7 +436,7 @@ sio2: type 16550A</screen>
</step>
</procedure>
</sect4>
<sect4 id="printing-parallel-port-mode">
<title>Setting the Communication Mode for the Parallel Port</title>
@ -535,7 +535,7 @@ device lpt0 at isa? port? tty vector lptintr</programlisting>
your system boots. See &man.lptcontrol.8; for more
information.</para>
</sect4>
<sect4 id="printing-testing">
<title>Checking Printer Communications</title>
@ -722,7 +722,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
<sect3 id="printing-printcap">
<title>Enabling the Spooler: The <filename>/etc/printcap</filename>
File</title>
<para>At this point, your printer should be hooked up, your kernel
configured to communicate with it (if necessary), and you have been
able to send some simple data to the printer. Now, we are ready to
@ -743,7 +743,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
<para>The simple spooler configuration consists of the following
steps:</para>
<procedure>
<step>
<para>Pick a name (and a few convenient aliases) for the printer,
@ -792,7 +792,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
linkend="printing-troubleshooting">Troubleshooting</link>.</para>
</step>
</procedure>
<note>
<para>Language-based printers, such as PostScript printers, cannot
directly print plain text. The simple setup outlined above and
@ -800,7 +800,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
installing such a printer you will print only files that the
printer can understand.</para>
</note>
<para>Users often expect that they can print plain text to any of the
printers installed on your system. Programs that interface to LPD
to do their printing usually make the same assumption. If you are
@ -861,7 +861,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:</programlisting>
<literal>S</literal>, <literal>panasonic</literal>, and
<literal>Panasonic KX-P4455 PostScript v51.4</literal>.</para>
</sect4>
<sect4 id="printing-no-header-pages">
<title>Suppressing Header Pages</title>
@ -893,7 +893,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
single TAB. Every line in an entry except the last ends in a
backslash character.</para>
</sect4>
<sect4 id="printing-spooldir">
<title>Making the Spooling Directory</title>
@ -1108,7 +1108,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
:sh:sd=/var/spool/lpd/bamboo:\
:lp=/dev/ttyd5:fs#0x82000c1:xs#0x820:</programlisting>
</sect4>
<sect4 id="printing-textfilter">
<title>Installing the Text Filter</title>
@ -1174,7 +1174,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
:lp=/dev/ttyd5:fs#0x82000e1:xs#0x820:\
:if=/usr/local/libexec/if-simple:</programlisting>
</sect4>
<sect4 id="printing-trying">
<title>Trying It Out</title>
@ -1224,7 +1224,7 @@ $%&amp;'()*+,-./01234567
<para>If the printer did not work, see the next section, <link
linkend="printing-troubleshooting">Troubleshooting</link>.</para>
</sect4>
<sect4 id="printing-troubleshooting">
<title>Troubleshooting</title>
@ -1533,7 +1533,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<para>This section tells you how to use printers you have setup with
FreeBSD. Here is an overview of the user-level commands:</para>
<variablelist>
<varlistentry>
<term>&man.lpr.1;</term>
@ -1545,7 +1545,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<varlistentry>
<term>&man.lpq.1;</term>
<listitem>
<para>Check printer queues</para>
</listitem>
@ -1553,7 +1553,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<varlistentry>
<term>&man.lprm.1;</term>
<listitem>
<para>Remove jobs from a printer's queue</para>
</listitem>
@ -1597,7 +1597,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<para>To select a specific printer, type:</para>
<screen>&prompt.user; <userinput>lpr -P <replaceable>printer-name</replaceable> <replaceable>filename</replaceable> <replaceable>...</replaceable></userinput></screen>
<para>This example prints a long listing of the current directory to the
printer named <literal>rattan</literal>:</para>
@ -1676,7 +1676,7 @@ kelly: 2nd [job 010rose]
mary: 3rd [job 011rose]
/home/orchid/mary/research/venus/alpha-regio/mapping 78519 bytes</screen>
</sect2>
<sect2 id="printing-lprm">
<title>Removing Jobs</title>
@ -1707,7 +1707,7 @@ mary: 3rd [job 011rose]
you.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>lprm <replaceable>user</replaceable></term>
@ -1717,7 +1717,7 @@ mary: 3rd [job 011rose]
users' jobs; you can remove only your own jobs.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>lprm</term>
@ -1771,7 +1771,7 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-format">
<title>Formatting and Conversion Options</title>
<para>The following &man.lpr.1; options control formatting of the
files in the job. Use these options if the job does not contain
plain text or if you want plain text formatted through the
@ -1796,7 +1796,7 @@ cfA013rose dequeued
linkend="printing-advanced-convfilters">Conversion
Filters</link> gives details.</para>
</note>
<variablelist>
<varlistentry>
<term><option>-c</option></term>
@ -1919,7 +1919,7 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-job-handling">
<title>Job Handling Options</title>
<para>The following options to &man.lpr.1; tell LPD to handle the job
specially:</para>
@ -1999,7 +1999,7 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-misc">
<title>Header Page Options</title>
<para>These options to &man.lpr.1; adjust the text that normally
appears on a job's header page. If header pages are suppressed for
the destination printer, these options have no effect. See section
@ -2059,11 +2059,11 @@ cfA013rose dequeued
<listitem>
<para>Start and stop the printers</para>
</listitem>
<listitem>
<para>Enable and disable their queues</para>
</listitem>
<listitem>
<para>Rearrange the order of the jobs in each queue.</para>
</listitem>
@ -2102,7 +2102,7 @@ cfA013rose dequeued
still submit jobs if the queue's enabled.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>clean
<replaceable>printer-name</replaceable></command></term>
@ -2116,7 +2116,7 @@ cfA013rose dequeued
removes them.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>disable
<replaceable>printer-name</replaceable></command></term>
@ -2134,7 +2134,7 @@ cfA013rose dequeued
<command>enable</command> command.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>down <replaceable>printer-name</replaceable>
<replaceable>message</replaceable></command></term>
@ -2148,7 +2148,7 @@ cfA013rose dequeued
status</command>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>enable
<replaceable>printer-name</replaceable></command></term>
@ -2158,7 +2158,7 @@ cfA013rose dequeued
the printer will not print anything until it is started.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>help
<replaceable>command-name</replaceable></command></term>
@ -2170,7 +2170,7 @@ cfA013rose dequeued
commands available.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>restart
<replaceable>printer-name</replaceable></command></term>
@ -2185,7 +2185,7 @@ cfA013rose dequeued
<command>start</command>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>start
<replaceable>printer-name</replaceable></command></term>
@ -2195,7 +2195,7 @@ cfA013rose dequeued
queue.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>stop
<replaceable>printer-name</replaceable></command></term>
@ -2207,7 +2207,7 @@ cfA013rose dequeued
queue.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>topq <replaceable>printer-name</replaceable>
<replaceable>job-or-username</replaceable></command></term>
@ -2222,7 +2222,7 @@ cfA013rose dequeued
<replaceable>printer-name</replaceable>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>up
<replaceable>printer-name</replaceable></command></term>
@ -2249,7 +2249,7 @@ cfA013rose dequeued
<para>This section describes filters for printing specially formatted
files, header pages, printing across networks, and restricting and
accounting for printer usage.</para>
<sect2 id="printing-advanced-filter-intro">
<title>Filters</title>
@ -2301,7 +2301,7 @@ cfA013rose dequeued
should do to overcome this problem. I recommend reading this
section if you have a PostScript printer.</para>
</listitem>
<listitem>
<para>PostScript is a popular output format for many programs. Even
some people (myself included) write PostScript code directly. But
@ -2333,7 +2333,7 @@ cfA013rose dequeued
linkend="printing-advanced-header-pages">Header Pages</link>),
you can probably skip that section altogether.</para>
</listitem>
<listitem>
<para>Section <link linkend="printing-advanced-lpf">lpf: a Text
Filter</link> describes <command>lpf</command>, a fairly
@ -2348,7 +2348,7 @@ cfA013rose dequeued
<sect3 id="printing-advanced-filters">
<title>How Filters Work</title>
<para>As mentioned before, a filter is an executable program started
by LPD to handle the device-dependent part of communicating with the
printer.</para>
@ -2370,10 +2370,10 @@ cfA013rose dequeued
<literal>if</literal> filter (this is mostly true: see <link
linkend="printing-advanced-of">Output Filters</link> for
details).</para>
<para>There are three kinds of filters you can specify in
<filename>/etc/printcap</filename>:</para>
<itemizedlist>
<listitem>
<para>The <emphasis>text filter</emphasis>, confusingly called the
@ -2514,7 +2514,7 @@ cfA013rose dequeued
<option>-l</option> arguments.</para>
</listitem>
</itemizedlist>
<para>Filters should also <emphasis>exit</emphasis> with the
following exit status:</para>
@ -2546,13 +2546,13 @@ cfA013rose dequeued
</listitem>
</varlistentry>
</variablelist>
<para>The text filter that comes with the FreeBSD release,
<filename>/usr/libexec/lpr/lpf</filename>, takes advantage of the
page width and length arguments to determine when to send a form
feed and how to account for printer usage. It uses the login, host,
and accounting file arguments to make the accounting entries.</para>
<para>If you are shopping for filters, see if they are LPD-compatible.
If they are, they must support the argument lists described above.
If you plan on writing filters for general use, then have them
@ -2561,7 +2561,7 @@ cfA013rose dequeued
<sect3 id="printing-advanced-if-conversion">
<title>Accommodating Plain Text Jobs on PostScript Printers</title>
<para>If you are the only user of your computer and PostScript (or
other language-based) printer, and you promise to never send plain
text to your printer and to never use features of various programs
@ -2579,7 +2579,7 @@ cfA013rose dequeued
will convert the text into PostScript and print the result.</para>
<para>How do we do this?</para>
<para>If you have got a serial printer, a great way to do it is to
install <command>lprps</command>. <command>lprps</command> is a
PostScript printer filter which performs two-way communication with
@ -2649,7 +2649,7 @@ fi</programlisting>
<sect3 id="printing-advanced-ps">
<title>Simulating PostScript on Non-PostScript Printers</title>
<para>PostScript is the <emphasis>de facto</emphasis> standard for
high quality typesetting and printing. PostScript is, however, an
<emphasis>expensive</emphasis> standard. Thankfully, Alladin
@ -2737,7 +2737,7 @@ exit 2</programlisting>
<sect3 id="printing-advanced-convfilters">
<title>Conversion Filters</title>
<para>After completing the simple setup described in <link
linkend="printing-simple">Simple Printer Setup</link>, the first
thing you will probably want to do is install conversion filters for
@ -2777,7 +2777,7 @@ exit 2</programlisting>
text, the filter converts the file into a format the printer can
understand.</para>
</sect4>
<sect4>
<title>Which Conversions Filters Should I Install?</title>
@ -2869,7 +2869,7 @@ exit 2</programlisting>
<command>lpr -g</command> mean &ldquo;print Printerleaf
files.&rdquo;</para>
</sect4>
<sect4>
<title>Installing Conversion Filters</title>
@ -3129,7 +3129,7 @@ dvilj2p -M1 -q -e- dfhp$$.dvi
cleanup
exit 0</programlisting>
</sect4>
<sect4 id="printing-advanced-autoconv">
<title>Automated Conversion: An Alternative To Conversion
Filters</title>
@ -3161,7 +3161,7 @@ exit 0</programlisting>
<sect3 id="printing-advanced-of">
<title>Output Filters</title>
<para>The LPD spooling system supports one other type of filter that
we have not yet explored: an output filter. An output filter is
intended for printing plain text only, like the text filter, but
@ -3197,7 +3197,7 @@ exit 0</programlisting>
question.</para>
</listitem>
</itemizedlist>
<para>Do not be seduced by an output filter's simplicity. If you
would like each file in a job to start on a different page an output
filter <emphasis>will not work</emphasis>. Use a text filter (also
@ -3244,7 +3244,7 @@ exit 0</programlisting>
<sect3 id="printing-advanced-lpf">
<title><command>lpf</command>: a Text Filter</title>
<para>The program <filename>/usr/libexec/lpr/lpf</filename> that comes
with FreeBSD binary distribution is a text filter (input filter)
that can indent output (job submitted with <command>lpr
@ -3298,15 +3298,15 @@ exit 0</programlisting>
<sect3 id="printing-advanced-header-pages-enabling">
<title>Enabling Header Pages</title>
<para>In the <link linkend="printing-simple">Simple Printer
Setup</link>, we turned off header pages by specifying
<literal>sh</literal> (meaning &ldquo;suppress header&rdquo;) in the
<filename>/etc/printcap</filename> file. To enable header pages for
a printer, just remove the <literal>sh</literal> capability.</para>
<para>Sounds too easy, right?</para>
<para>You are right. You <emphasis>might</emphasis> have to provide
an output filter to send initialization strings to the printer.
Here is an example output filter for Hewlett Packard PCL-compatible
@ -3357,7 +3357,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
<sect3 id="printing-advanced-header-pages-controlling">
<title>Controlling Header Pages</title>
<para>By enabling header pages, LPD will produce a <emphasis>long
header</emphasis>, a full page of large letters identifying the
user, host, and job. Here is an example (kelly printed the job
@ -3424,7 +3424,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
<programlisting>
rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995</programlisting>
<para>Also by default, LPD prints the header page first, then the job.
To reverse that, specify <literal>hl</literal> (header last) in
<filename>/etc/printcap</filename>.</para>
@ -3432,13 +3432,13 @@ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995</programlisting>
<sect3 id="printing-advanced-header-pages-accounting">
<title>Accounting for Header Pages</title>
<para>Using LPD's built-in header pages enforces a particular paradigm
when it comes to printer accounting: header pages must be
<emphasis>free of charge</emphasis>.</para>
<para>Why?</para>
<para>Because the output filter is the only external program that will
have control when the header page is printed that could do
accounting, and it is not provided with any <emphasis>user or
@ -3458,9 +3458,9 @@ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995</programlisting>
header pages with <command>lpr -h</command>, they will still get
them and be charged for them since LPD does not pass any knowledge
of the <option>-h</option> option to any of the filters.</para>
<para>So, what are your options?</para>
<para>You can:</para>
<itemizedlist>
@ -3501,7 +3501,7 @@ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995</programlisting>
<sect3 id="printing-advanced-header-pages-ps">
<title>Header Pages on PostScript Printers</title>
<para>As described above, LPD can generate a plain text header page
suitable for many printers. Of course, PostScript cannot directly
print plain text, so the header page feature of LPD is
@ -3684,7 +3684,7 @@ done
linkend="printing-advanced-network-rm">Printers Installed on
Remote Hosts</link> tells how to do this.</para>
</listitem>
<listitem>
<para>Accessing a printer attached directly to a network. The
printer has a network interface in addition (or in place of) a
@ -3716,7 +3716,7 @@ done
<sect3 id="printing-advanced-network-rm">
<title>Printers Installed on Remote Hosts</title>
<para>The LPD spooling system has built-in support for sending jobs to
other hosts also running LPD (or are compatible with LPD). This
feature enables you to install a printer on one host and make it
@ -3745,7 +3745,7 @@ done
<para>Then, on the other hosts you want to have access to the printer,
make an entry in their <filename>/etc/printcap</filename> files with
the following:</para>
<orderedlist>
<listitem>
<para>Name the entry anything you want. For simplicity, though,
@ -3779,7 +3779,7 @@ done
<para>That is it. You do not need to list conversion filters, page
dimensions, or anything else in the
<filename>/etc/printcap</filename> file.</para>
<para>Here is an example. The host <hostid>rose</hostid> has two
printers, <literal>bamboo</literal> and <literal>rattan</literal>.
We will enable users on the host orchid to print to those printers.
@ -3789,7 +3789,7 @@ done
Pages</link>). It already had the entry for the printer
<literal>teak</literal>; we have added entries for the two printers
on the host rose:</para>
<programlisting>
#
# /etc/printcap for host orchid - added (remote) printers on rose
@ -3840,7 +3840,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<sect3 id="printing-advanced-network-net-if">
<title>Printers with Networked Data Stream Interfaces</title>
<para>Often, when you buy a network interface card for a printer, you
can get two versions: one which emulates a spooler (the more
expensive version), or one which just lets you send data to it as if
@ -3920,7 +3920,7 @@ exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100</pro
<sect3 id="printing-advanced-restricting-copies">
<title>Restricting Multiple Copies</title>
<para>The LPD system makes it easy for users to print multiple copies
of a file. Users can print jobs with <command>lpr -#5</command>
(for example) and get five copies of each file in the job. Whether
@ -3933,8 +3933,8 @@ exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100</pro
with the <option>-#</option> option, they will see:</para>
<screen>lpr: multiple copies are not allowed</screen>
<para>Note that if you have set up access to a printer remotely (see
section <link linkend="printing-advanced-network-rm">Printers
Installed on Remote Hosts</link>), you need the
@ -3971,7 +3971,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<filename>/etc/printcap</filename> (and while we are at it, let us
disable multiple copies for the printer
<literal>teak</literal>):</para>
<programlisting>
#
# /etc/printcap for host orchid - no multiple copies for local
@ -4002,7 +4002,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<sect3 id="printing-advanced-restricting-access">
<title>Restricting Access To Printers</title>
<para>You can control who can print to what printers by using the UNIX
group mechanism and the <literal>rg</literal> capability in
<filename>/etc/printcap</filename>. Just place the users you want
@ -4014,7 +4014,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<errorname>lpr: Not a member of the restricted group</errorname>
if they try to print to the controlled printer.</para>
<para>As with the <literal>sc</literal> (suppress multiple copies)
capability, you need to specify <literal>rg</literal> on remote
hosts that also have access to your printers, if you feel it is
@ -4058,7 +4058,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<sect3 id="printing-advanced-restricting-sizes">
<title>Controlling Sizes of Jobs Submitted</title>
<para>If you have many users accessing the printers, you probably need
to put an upper limit on the sizes of the files users can submit to
print. After all, there is only so much free space on the
@ -4076,7 +4076,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<para>The limit applies to <emphasis>files</emphasis> in a job, and
<emphasis>not</emphasis> the total job size.</para>
</note>
<para>LPD will not refuse a file that is larger than the limit you
place on a printer. Instead, it will queue as much of the file up
to the limit, which will then get printed. The rest will be
@ -4128,7 +4128,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<sect3 id="printing-advanced-restricting-remote">
<title>Restricting Jobs from Remote Printers</title>
<para>The LPD spooling system provides several ways to restrict print
jobs submitted from remote hosts:</para>
@ -4296,7 +4296,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<sect3>
<title>Quick and Dirty Printer Accounting</title>
<para>FreeBSD comes with two programs that can get you set up with
simple periodic accounting right away. They are the text filter
<command>lpf</command>, described in section <link
@ -4312,7 +4312,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
of this file comes from the <literal>af</literal> capability in
<filename>/etc/printcap</filename>, and if not specified as an
absolute path, is relative to the spooling directory.</para>
<para>LPD starts <command>lpf</command> with page width and length
arguments (from the <literal>pw</literal> and <literal>pl</literal>
capabilities). <command>lpf</command> uses these arguments to
@ -4353,7 +4353,7 @@ rose:root 26.00 12 $ 0.52
total 337.00 154 $ 6.74</screen>
<para>These are the arguments &man.pac.8; expects:</para>
<variablelist>
<varlistentry>
<term><option>-P<replaceable>printer</replaceable></option></term>
@ -4427,7 +4427,7 @@ total 337.00 154 $ 6.74</screen>
</listitem>
</varlistentry>
</variablelist>
<para>In the default summary that &man.pac.8; produces, you see the
number of pages printed by each user from various hosts. If, at
your site, host does not matter (because users can use any host),
@ -4458,7 +4458,7 @@ total 337.00 154 $ 6.74</screen>
makes each page cost one dollar and fifty cents. You can really
rake in the profits by using this option.</para>
<para>Finally, running <command>pac -s</command> will save the summary
information in a summary accounting file, which is named the same as
the printer's accounting file, but with <literal>_sum</literal>
@ -4470,7 +4470,7 @@ total 337.00 154 $ 6.74</screen>
<sect3>
<title>How Can You Count Pages Printed?</title>
<para>In order to perform even remotely accurate accounting, you need
to be able to determine how much paper a job uses. This is the
essential problem of printer accounting.</para>
@ -4488,20 +4488,20 @@ total 337.00 154 $ 6.74</screen>
to examine <command>lpf</command>'s source code.</para>
<para>How do you handle other file formats, though?</para>
<para>Well, for DVI-to-LaserJet or DVI-to-PostScript conversion, you
can have your filter parse the diagnostic output of
<command>dvilj</command> or <command>dvips</command> and look to see
how many pages were converted. You might be able to do similar
things with other file formats and conversion programs.</para>
<para>But these methods suffer from the fact that the printer may not
actually print all those pages. For example, it could jam, run out
of toner, or explode&mdash;and the user would still get
charged.</para>
<para>So, what can you do?</para>
<para>There is only one <emphasis>sure</emphasis> way to do
<emphasis>accurate</emphasis> accounting. Get a printer that can
tell you how much paper it uses, and attach it via a serial line or
@ -4528,15 +4528,15 @@ total 337.00 154 $ 6.74</screen>
many of its shortcomings, which naturally leads to the question:
&ldquo;What other spooling systems are out there (and work with
FreeBSD)?&rdquo;</para>
<para>Unfortunately, I have located only <emphasis>two</emphasis>
alternatives&mdash;and they are almost identical to each other! They
are:</para>
<variablelist>
<varlistentry>
<term>PLP, the Portable Line Printer Spooler System</term>
<listitem>
<para>PLP was based on software developed by Patrick Powell and then
maintained by an Internet-wide group of developers. The main site
@ -4579,7 +4579,7 @@ total 337.00 154 $ 6.74</screen>
<varlistentry>
<term>LPRng</term>
<listitem>
<para>LPRng, which purportedly means &ldquo;LPR: the Next
Generation&rdquo; is a complete rewrite of PLP. Patrick Powell
@ -4596,12 +4596,12 @@ total 337.00 154 $ 6.74</screen>
<para>I would like to thank the following people who have assisted in the
development of this document:</para>
<variablelist>
<varlistentry>
<term>Daniel Eischen
<email>deischen@iworks.interworks.org</email></term>
<listitem>
<para>For providing a plethora of HP filter programs for
perusal.</para>
@ -4610,7 +4610,7 @@ total 337.00 154 $ 6.74</screen>
<varlistentry>
<term>&a.jehamby;</term>
<listitem>
<para>For the Ghostscript-to-HP filter.</para>
</listitem>
@ -4618,7 +4618,7 @@ total 337.00 154 $ 6.74</screen>
<varlistentry>
<term>&a.jfieber;</term>
<listitem>
<para> For debugging why printing from Windows 95 to a FreeBSD
system simulating a PostScript printer with Ghostscript didn't
@ -4641,7 +4641,7 @@ total 337.00 154 $ 6.74</screen>
<varlistentry>
<term>My wife, Mary Kelly
<email>urquhart@argyre.colorado.edu</email></term>
<listitem>
<para>For allowing me to spend more time with FreeBSD than
with her.</para>

90
en_US.ISO8859-1/books/handbook/security/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/security/chapter.sgml,v 1.20 1999/09/06 06:53:07 peter Exp $
-->
<chapter id="security">
@ -12,7 +12,7 @@
<para><emphasis>Contributed by &a.wollman; 24 September
1995.</emphasis></para>
<para>In order to protect the security of passwords on UN*X systems from
being easily exposed, passwords have traditionally been scrambled in
some way. Starting with Bell Labs' Seventh Edition Unix, passwords were
@ -27,7 +27,7 @@
available, because national governments in many places like to place
restrictions on cross-border transport of DES and other encryption
software.</para>
<para>So, the FreeBSD team was faced with a dilemma: how could we provide
compatibility with all those UNIX systems out there while still not
running afoul of the law? We decided to take a dual-track approach: we
@ -43,7 +43,7 @@
Because neither of these functions involve encryption, they are believed
to be exportable from the US and importable into many other
countries.</para>
<para>Meanwhile, work was also underway on the DES-based password hash
function. First, a version of the <function>crypt</function> function
which was written outside the US was imported, thus synchronizing the US
@ -128,7 +128,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -&gt; libdescrypt_p.a</s
distributions since version 1.1.5, and is also implemented on a large
and growing number of other systems. S/Key is a registered trademark of
Bell Communications Research, Inc.</para>
<para>There are three different sorts of passwords which we will talk
about in the discussion below. The first is your usual UNIX-style or
Kerberos password; we will call this a &ldquo;UNIX password&rdquo;. The
@ -140,14 +140,14 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -&gt; libdescrypt_p.a</s
(and sometimes the <command>keyinit</command> program) which it uses to
generate one-time passwords; we will call it a &ldquo;secret
password&rdquo; or just unqualified &ldquo;password&rdquo;.</para>
<para>The secret password does not necessarily have anything to do with
your UNIX password (while they can be the same, this is not
recommended). While UNIX passwords are limited to eight characters in
length, your S/Key secret password can be as long as you like; I use
seven-word phrases. In general, the S/Key system operates completely
independently of the UNIX password system.</para>
<para>There are in addition two other sorts of data involved in the S/Key
system; one is called the &ldquo;seed&rdquo; or (confusingly)
&ldquo;key&rdquo;, and consists of two letters and five digits, and the
@ -165,7 +165,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -&gt; libdescrypt_p.a</s
each successful login to keep the user and login program in sync. (When
you get the iteration count down to 1, it is time to reinitialize
S/Key.)</para>
<para>There are four programs involved in the S/Key system which we will
discuss below. The <command>key</command> program accepts an iteration
count, a seed, and a secret password, and generates a one-time password.
@ -180,7 +180,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -&gt; libdescrypt_p.a</s
The <command>login</command> program is also capable of disallowing the
use of UNIX passwords on connections coming from specified
addresses.</para>
<para>There are four different sorts of operations we will cover. The
first is using the <command>keyinit</command> program over a secure
connection to set up S/Key for the first time, or to change your
@ -193,7 +193,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -&gt; libdescrypt_p.a</s
number of keys which can be written down or printed out to carry with
you when going to some location without secure connections to anywhere
(like at a conference).</para>
<sect2>
<title>Secure connection initialization</title>
@ -294,7 +294,7 @@ s/key 92 hi52030
annotation <literal>(s/key required)</literal>, indicating that only
S/Key one-time passwords will be accepted.</para>
</sect2>
<sect2>
<title>Generating a single one-time password</title>
@ -415,16 +415,16 @@ permit port ttyd0</programlisting>
Services such as remote login, remote copy, secure inter-system file
copying and other high-risk tasks are made considerably safer and more
controllable.</para>
<para>The following instructions can be used as a guide on how to set up
Kerberos as distributed for FreeBSD. However, you should refer to the
relevant manual pages for a complete description.</para>
<para>In FreeBSD, the Kerberos is not that from the original 4.4BSD-Lite,
distribution, but eBones, which had been previously ported to FreeBSD
1.1.5.1, and was sourced from outside the USA/Canada, and is thus
available to system owners outside those countries.</para>
<para>For those needing to get a legal foreign distribution of this
software, please <emphasis>do not</emphasis> get it from a USA or Canada
site. You will get that site in <emphasis>big</emphasis> trouble! A
@ -594,7 +594,7 @@ Principal's new key version = 1
Edit O.K.
<prompt>Principal name:</prompt> &lt;---- null entry here will cause an exit</screen>
</sect2>
<sect2>
<title>Creating the server file</title>
@ -668,7 +668,7 @@ Principal's new key version = 1
Edit O.K.
<prompt>Principal name:</prompt> &lt;---- null entry here will cause an exit</screen>
</sect2>
<sect2>
<title>Testing it all out</title>
@ -729,7 +729,7 @@ Verifying password
<prompt>New Password for jane:</prompt>
Password changed.</screen>
</sect2>
<sect2>
<title>Adding <command>su</command> privileges</title>
@ -798,7 +798,7 @@ Principal: jane.root@GRONDAR.ZA
Issued Expires Principal
May 2 20:43:12 May 3 04:43:12 krbtgt.GRONDAR.ZA@GRONDAR.ZA</screen>
</sect2>
<sect2>
<title>Using other commands</title>
@ -861,15 +861,15 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<sect1 id="firewalls">
<title>Firewalls</title>
<para><emphasis>Contributed by &a.gpalmer; and &a.alex;.</emphasis></para>
<para>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 implement them.</para>
<note>
<para>People often think that having a firewall between your companies
internal network and the &ldquo;Big Bad Internet&rdquo; will solve all
@ -883,7 +883,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
firewall to be impenetrable, you have just made the crackers job that
bit easier.</para>
</note>
<sect2>
<title>What is a firewall?</title>
@ -912,7 +912,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<sect3 id="firewalls-packet-filters">
<title>Packet filtering routers</title>
<para>A router is a machine which forwards packets between two or more
networks. A packet filtering router has an extra piece of code in
its kernel, which compares each packet to a list of rules before
@ -968,7 +968,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
depends largely on what proxy software you choose.</para>
</sect3>
</sect2>
<sect2>
<title>What does IPFW allow me to do?</title>
@ -993,7 +993,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<application>IPFW</application>, and the same commands and techniques
should be used in this situation.</para>
</sect2>
<sect2>
<title>Enabling IPFW on FreeBSD</title>
@ -1027,7 +1027,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
happen.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options IPFIREWALL_VERBOSE_LIMIT=10</literal></term>
@ -1055,7 +1055,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
the firewall code automatically includes accounting
facilities.</para>
</sect2>
<sect2>
<title>Configuring IPFW</title>
@ -1075,7 +1075,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<sect3>
<title>Altering the IPFW rules</title>
<para>The syntax for this form of the command is:
<cmdsynopsis>
<command>ipfw</command>
@ -1088,10 +1088,10 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<arg choice="plain">addresses</arg>
<arg>options</arg>
</cmdsynopsis></para>
<para>There is one valid flag when using this form of the
command:</para>
<variablelist>
<varlistentry>
<term>-N</term>
@ -1101,7 +1101,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
</listitem>
</varlistentry>
</variablelist>
<para>The <emphasis>command</emphasis> given can be shortened to the
shortest unique form. The valid <emphasis>commands</emphasis>
are:</para>
@ -1124,7 +1124,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
</listitem>
</varlistentry>
</variablelist>
<para>Previous versions of <application>IPFW</application> used
separate firewall and accounting entries. The present version
provides packet accounting with each firewall entry.</para>
@ -1181,7 +1181,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
</listitem>
</varlistentry>
</variablelist>
<para>Each <emphasis>action</emphasis> will be recognized by the
shortest unambiguous prefix.</para>
@ -1221,9 +1221,9 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
</listitem>
</varlistentry>
</variablelist>
<para>The <emphasis>address</emphasis> specification is:</para>
<cmdsynopsis>
<arg choice="plain">from</arg>
<arg choice="plain"><replaceable>address/mask</replaceable></arg><arg><replaceable>port</replaceable></arg>
@ -1256,7 +1256,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<screen><replaceable>address</replaceable>:<replaceable>mask-pattern</replaceable></screen>
</para>
<para>A valid hostname may be specified in place of the IP address.
<option><replaceable>mask-bits</replaceable></option> is a decimal
number representing how many bits in the address mask should be set.
@ -1284,7 +1284,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
with a list, but the range must always be specified first.</para>
<para>The <emphasis>options</emphasis> available are:</para>
<variablelist>
<varlistentry>
<term>frag</term>
@ -1382,7 +1382,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<sect3>
<title>Listing the IPFW rules</title>
<para>The syntax for this form of the command is:
<cmdsynopsis>
<command>ipfw</command>
@ -1391,7 +1391,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<arg>-N</arg>
<arg choice="plain">l</arg>
</cmdsynopsis></para>
<para>There are three valid flags when using this form of the
command:</para>
@ -1428,13 +1428,13 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<sect3>
<title>Flushing the IPFW rules</title>
<para>The syntax for flushing the chain is:
<cmdsynopsis>
<command>ipfw</command>
<arg choice="plain">flush</arg>
</cmdsynopsis></para>
<para>This causes all entries in the firewall chain to be removed
except the fixed default policy enforced by the kernel (index
65535). Use caution when flushing rules, the default deny policy
@ -1444,21 +1444,21 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<sect3>
<title>Clearing the IPFW packet counters</title>
<para>The syntax for clearing one or more packet counters is:
<cmdsynopsis>
<command>ipfw</command>
<arg choice="plain">zero</arg>
<arg choice="opt"><replaceable>index</replaceable></arg>
</cmdsynopsis></para>
<para>When used without an <replaceable>index</replaceable> argument,
all packet counters are cleared. If an
<replaceable>index</replaceable> is supplied, the clearing operation
only affects a specific chain entry.</para>
</sect3>
</sect2>
<sect2>
<title>Example commands for ipfw</title>
@ -1554,7 +1554,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
where most of the security sensitive services are, like finger,
SMTP (mail) and telnet.</para>
</listitem>
<listitem>
<para>Block <emphasis>all</emphasis> incoming UDP traffic. There
are very few useful services that travel over UDP, and what useful

192
en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/serialcomms/chapter.sgml,v 1.14 1999/09/06 06:53:08 peter Exp $
-->
<chapter id="serialcomms">
@ -15,7 +15,7 @@
<para>This section should give you some general information about serial
ports. If you do not find what you want here, check into the Terminal
and Dialup sections of the handbook.</para>
<para>The <filename>ttyd<replaceable>X</replaceable></filename> (or
<filename>cuaa<replaceable>X</replaceable></filename>) device is the
regular device you will want to open for your applications. When a
@ -38,17 +38,17 @@
Now, an application will have these settings by default when it opens
<filename>ttyd5</filename>. It can still change these settings to its
liking, though.</para>
<para>You can also prevent certain settings from being changed by an
application by making adjustments to the &ldquo;lock state&rdquo;
device. For example, to lock the speed of <filename>ttyd5</filename> to
57600 bps, do</para>
<screen>&prompt.root; <userinput>stty -f /dev/ttyld5 57600</userinput></screen>
<para>Now, an application that opens <filename>ttyd5</filename> and tries
to change the speed of the port will be stuck with 57600 bps.</para>
<para>Naturally, you should make the initial state and lock state devices
writable only by <username>root</username>. The
<filename>MAKEDEV</filename> script does <emphasis>not</emphasis> do
@ -59,12 +59,12 @@
<title>Terminals</title>
<para><emphasis>Contributed by &a.kelly; 28 July 1996</emphasis></para>
<para>Terminals provide a convenient and low-cost way to access the power
of your FreeBSD system when you are not at the computer's console or on
a connected network. This section describes how to use terminals with
FreeBSD.</para>
<sect2 id="term-uses">
<title>Uses and Types of Terminals</title>
@ -95,11 +95,11 @@
<listitem>
<para><link linkend="term-dumb">Dumb terminals</link></para>
</listitem>
<listitem>
<para><link linkend="term-pcs">PCs acting as terminals</link></para>
</listitem>
<listitem>
<para><link linkend="term-x">X terminals</link></para>
</listitem>
@ -109,7 +109,7 @@
<sect3 id="term-dumb">
<title>Dumb Terminals</title>
<para>Dumb terminals are specialized pieces of hardware that let you
connect to computers over serial lines. They are called
&ldquo;dumb&rdquo; because they have only enough computational power
@ -132,7 +132,7 @@
<sect3 id="term-pcs">
<title>PCs Acting As Terminals</title>
<para>If a <link linkend="term-dumb">dumb terminal</link> has just
enough ability to display, send, and receive text, then certainly
any spare personal computer can be a dumb terminal. All you need is
@ -147,7 +147,7 @@
<sect3 id="term-x">
<title>X Terminals</title>
<para>X terminals are the most sophisticated kind of terminal
available. Instead of connecting to a serial port, they usually
connect to a network like Ethernet. Instead of being relegated to
@ -170,7 +170,7 @@
<sect3 id="term-cables">
<title>Cables</title>
<para>Because terminals use serial ports, you need to use
serial&mdash;also known as RS-232C&mdash;cables to connect the
terminal to the FreeBSD system.</para>
@ -195,7 +195,7 @@
linkend="term-std">standard</link> cable.</para>
</listitem>
</itemizedlist>
<para>Also, the serial port on <emphasis>both</emphasis> the terminal
and your FreeBSD system must have connectors that will fit the cable
you are using.</para>
@ -299,7 +299,7 @@
hood.</para>
</note>
</sect4>
<sect4 id="term-std">
<title>Standard RS-232C Cables</title>
@ -314,12 +314,12 @@
<sect3 id="term-ports">
<title>Ports</title>
<para>Serial ports are the devices through which data is transferred
between the FreeBSD host computer and the terminal. This section
describes the kinds of ports that exist and how they are addressed
in FreeBSD.</para>
<sect4 id="term-portkinds">
<title>Kinds of Ports</title>
@ -336,7 +336,7 @@
specifications on the kind of port in use. A visual inspection of
the port often works, too.</para>
</sect4>
<sect4 id="term-portnames">
<title>Port Names</title>
@ -406,18 +406,18 @@
the <filename>/dev</filename> directory for the serial port if it
is not already there.</para>
</step>
<step>
<para>Specify that <filename>/usr/libexec/getty</filename> be run on
the port, and specify the appropriate
<replaceable>getty</replaceable> type from the
<filename>/etc/gettytab</filename> file.</para>
</step>
<step>
<para>Specify the default terminal type.</para>
</step>
<step>
<para>Set the port to &ldquo;on.&rdquo;</para>
</step>
@ -426,7 +426,7 @@
<para>Specify whether the port should be
&ldquo;secure.&rdquo;</para>
</step>
<step>
<para>Force <command>init</command> to reread the
<filename>/etc/ttys</filename> file.</para>
@ -453,11 +453,11 @@
<sect3 id="term-etcttys">
<title>Adding an Entry to <filename>/etc/ttys</filename></title>
<para>First, you need to add an entry to the
<filename>/etc/ttys</filename> file, unless one is already
there.</para>
<para>The <filename>/etc/ttys</filename> file lists all of the ports
on your FreeBSD system where you want to allow logins. For example,
the first virtual console <filename>ttyv0</filename> has an entry in
@ -486,7 +486,7 @@ ttyd5</programlisting>
<sect3 id="term-getty">
<title>Specifying the <replaceable>getty</replaceable> Type</title>
<para>Next, we need to specify what program will be run to handle the
logins on a terminal. For FreeBSD, the standard program to do that
is <filename>/usr/libexec/getty</filename>. It is what provides the
@ -529,7 +529,7 @@ ttyd5 "/usr/libexec/getty std.19200"</programlisting>
<sect3 id="term-deftermtype">
<title>Specifying the Default Terminal Type</title>
<para>The third field in the <filename>/etc/ttys</filename> file lists
the default terminal type for the port. For dialup ports, you
typically put <literal>unknown</literal> or
@ -537,18 +537,18 @@ ttyd5 "/usr/libexec/getty std.19200"</programlisting>
with practically any kind of terminal or software. For hardwired
terminals, the terminal type does not change, so you can put a real
terminal type in this field.</para>
<para>Users will usually use the <command>tset</command> program in
their <filename>.login</filename> or <filename>.profile</filename>
files to check the terminal type and prompt for one if necessary.
By setting a terminal type in the <filename>/etc/ttys</filename>
file, users can forego such prompting.</para>
<para>To find out what terminal types FreeBSD supports, see the
file <filename>/usr/share/misc/termcap</filename>. It lists
about 600 terminal types. You can add more if you wish. See
the &man.termcap.5; manual page for information.</para>
<para>In our example, the Wyse-50 is a Wyse-50 type of terminal
(although it can emulate others, we will leave it in Wyse-50 mode).
The 286 PC is running Procomm which will be set to emulate a VT-100.
@ -562,7 +562,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100</programlisting>
<sect3 id="term-enable">
<title>Enabling the Port</title>
<para>The next field in <filename>/etc/ttys</filename>, the fourth
field, tells whether to enable the port. Putting
<literal>on</literal> here will have the <command>init</command>
@ -582,7 +582,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on</programlisting>
<sect3 id="term-secure">
<title>Specifying Secure Ports</title>
<para>We have arrived at the last field (well, almost: there is an
optional <literal>window</literal> specifier, but we will ignore
that). The last field tells whether the port is secure.</para>
@ -592,9 +592,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on</programlisting>
<para>It means that the root account (or any account with a user ID of
0) may login on the port. Insecure ports do not allow root to
login.</para>
<para>How do you use secure and insecure ports?</para>
<para>By marking a port as insecure, the terminal to which it is
connected will not allow root to login. People who know the root
password to your FreeBSD system will first have to login using a
@ -613,7 +613,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on</programlisting>
command records.</para>
<para>Which should you use?</para>
<para>Just use &ldquo;insecure.&rdquo; Use &ldquo;insecure&rdquo;
<emphasis>even</emphasis> for terminals <emphasis>not</emphasis> in
public user areas or behind locked doors. It is quite easy to login
@ -632,7 +632,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<sect3 id="term-hup">
<title>Force <command>init</command> to Reread
<filename>/etc/ttys</filename></title>
<para>When you boot FreeBSD, the first process,
<command>init</command>, will read the
<filename>/etc/ttys</filename> file and start the programs listed
@ -704,7 +704,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
Make sure you have run <command>kill -HUP 1</command>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Garbage appears instead of a login prompt</term>
@ -716,7 +716,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
-HUP 1</command>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Characters appear doubled; the password appears when
typed</term>
@ -744,7 +744,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
specific enough to your environment. The author cannot be responsible if
you damage your system or lose data due to attempting to follow the
suggestions here.</para>
<sect2 id="dialup-prereqs">
<title>Prerequisites</title>
@ -757,7 +757,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<sect3>
<title>FreeBSD Version</title>
<para>First, it is assumed that you are using FreeBSD version 1.1 or
higher (including versions 2.x). FreeBSD version 1.0 included two
different serial drivers, which complicates the situation. Also,
@ -769,9 +769,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<sect3>
<title>Terminology</title>
<para>A quick rundown of terminology:</para>
<variablelist>
<varlistentry>
<term>bps</term>
@ -807,12 +807,12 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
</listitem>
</varlistentry>
</variablelist>
<para>If you need more information about these terms and data
communications in general, the author remembers reading that
<emphasis>The RS-232 Bible</emphasis> (anybody have an ISBN?) is a
good reference.</para>
<para>When talking about communications data rates, the author does
not use the term &ldquo;baud&rdquo;. Baud refers to the number of
electrical state transitions that may be made in a period of time,
@ -823,7 +823,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<sect3>
<title>External vs. Internal Modems</title>
<para>External modems seem to be more convenient for dialup, because
external modems often can be semi-permanently configured via
parameters stored in non-volatile RAM and they usually provide
@ -842,7 +842,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<title>Modems and Cables</title>
<para>A background knowledge of these items is assumed</para>
<itemizedlist>
<listitem>
<para>You know how to connect your modem to your computer so that
@ -861,7 +861,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
RAM parameters</para>
</listitem>
</itemizedlist>
<para>The first, connecting your modem, is usually simple &mdash; most
straight-through serial cables work without any problems. You need
to have a cable with appropriate connectors (DB-25 or DB-9, male or
@ -901,7 +901,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<para>Signal Ground (<acronym>SG</acronym>)</para>
</listitem>
</itemizedlist>
<para>FreeBSD needs the <acronym>RTS</acronym> and
<acronym>CTS</acronym> signals for flow-control at speeds above
2400bps, the <acronym>CD</acronym> signal to detect when a call has
@ -930,7 +930,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<sect3>
<title>Serial Interface Considerations</title>
<para>FreeBSD supports NS8250-, NS16450-, NS16550-, and NS16550A-based
EIA RS-232C (CCITT V.24) communications interfaces. The 8250 and
16450 devices have single-character buffers. The 16550 device
@ -1074,7 +1074,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
&man.config.8; manual page to prepare a kernel building directory,
then build, install, and test the new kernel.</para>
</sect2>
<sect2>
<title>Device Special Files</title>
@ -1103,7 +1103,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<sect3>
<title>Making Device Special Files</title>
<para>A shell script called <command>MAKEDEV</command> in the
<filename>/dev</filename> directory manages the device special
files. (The manual page for &man.MAKEDEV.8; on FreeBSD 1.1.5 is
@ -1195,12 +1195,12 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen>
<sect3>
<title><filename>/etc/gettytab</filename></title>
<para><filename>/etc/gettytab</filename> is a &man.termcap.5;-style
file of configuration information for &man.getty.8;. Please see the
&man.gettytab.5; manual page for complete information on the
format of the file and the list of capabilities.</para>
<sect4>
<title>Locked-Speed Config</title>
@ -1208,7 +1208,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen>
particular speed, you probably will not need to make any changes
to <filename>/etc/gettytab</filename>.</para>
</sect4>
<sect4>
<title>Matching-Speed Config</title>
@ -1297,7 +1297,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
<sect3 id="dialup-ttys">
<title><filename>/etc/ttys</filename></title>
<para><filename>/etc/ttys</filename> is the list of
<filename>ttys</filename> for <command>init</command> to monitor.
<filename>/etc/ttys</filename> also provides security information to
@ -1350,7 +1350,7 @@ ttyd0 "/usr/libexec/getty xxx" dialup on</programlisting>
first time setting up the system, though, you may want to wait until
your modem(s) are properly configured and connected before signaling
<command>init</command>.</para>
<sect4>
<title>Locked-Speed Config</title>
@ -1370,7 +1370,7 @@ ttyd0 "/usr/libexec/getty std.19200" dialup on</programlisting>
<filename>/etc/gettytab</filename> for your modem's data
rate.</para>
</sect4>
<sect4>
<title>Matching-Speed Config</title>
@ -1391,7 +1391,7 @@ ttyd0 "/usr/libexec/getty V19200" dialup on</programlisting>
<sect3>
<title><filename>/etc/rc.serial</filename> or
<filename>/etc/rc.local</filename></title>
<para>High-speed modems, like V.32, V.32bis, and V.34 modems, need to
use hardware (<filename>RTS/CTS</filename>) flow control. You can
add <command>stty</command> commands to
@ -1447,28 +1447,28 @@ stty -f /dev/ttyd3 crtscts</programlisting>
<listitem>
<para><acronym>CD</acronym> asserted when connected</para>
</listitem>
<listitem>
<para><acronym>DTR</acronym> asserted for operation; dropping DTR
hangs up line &amp; resets modem</para>
</listitem>
<listitem>
<para><acronym>CTS</acronym> transmitted data flow control</para>
</listitem>
<listitem>
<para>Disable <acronym>XON/XOFF</acronym> flow control</para>
</listitem>
<listitem>
<para><acronym>RTS</acronym> received data flow control</para>
</listitem>
<listitem>
<para>Quiet mode (no result codes)</para>
</listitem>
<listitem>
<para>No command echo</para>
</listitem>
@ -1497,32 +1497,32 @@ AT&amp;C1&amp;D2&amp;H1&amp;I0&amp;R2&amp;W</programlisting>
<listitem>
<para>Switch 1: UP &mdash; DTR Normal</para>
</listitem>
<listitem>
<para>Switch 2: Do not care (Verbal Result Codes/Numeric Result
Codes)</para>
</listitem>
<listitem>
<para>Switch 3: UP &mdash; Suppress Result Codes</para>
</listitem>
<listitem>
<para>Switch 4: DOWN &mdash; No echo, offline commands</para>
</listitem>
<listitem>
<para>Switch 5: UP &mdash; Auto Answer</para>
</listitem>
<listitem>
<para>Switch 6: UP &mdash; Carrier Detect Normal</para>
</listitem>
<listitem>
<para>Switch 7: UP &mdash; Load NVRAM Defaults</para>
</listitem>
<listitem>
<para>Switch 8: Do not care (Smart Mode/Dumb Mode)</para>
</listitem>
@ -1537,7 +1537,7 @@ AT&amp;C1&amp;D2&amp;H1&amp;I0&amp;R2&amp;W</programlisting>
<sect3>
<title>Locked-speed Config</title>
<para>For a locked-speed configuration, you will need to configure the
modem to maintain a constant modem-to-computer data rate independent
of the communications rate. On a USR Sportster 14,400 external
@ -1551,7 +1551,7 @@ AT&amp;B1&amp;W</programlisting>
<sect3>
<title>Matching-speed Config</title>
<para>For a variable-speed configuration, you will need to configure
your modem to adjust its serial port data rate to match the incoming
call rate. On a USR Sportster 14,400 external modem, these commands
@ -1566,7 +1566,7 @@ AT&amp;B2&amp;W</programlisting>
<sect3>
<title>Checking the Modem's Configuration</title>
<para>Most high-speed modems provide commands to view the modem's
current operating parameters in a somewhat human-readable fashion.
On the USR Sportster 14,400 external modems, the command
@ -1589,7 +1589,7 @@ AT&amp;B2&amp;W</programlisting>
<sect3>
<title>Checking out the FreeBSD system</title>
<para>Hook up your modem to your FreeBSD system, boot the system, and,
if your modem has status indication lights, watch to see whether the
modem's <acronym>DTR</acronym> indicator lights when the
@ -1603,7 +1603,7 @@ AT&amp;B2&amp;W</programlisting>
ax</command> to see if FreeBSD is trying to run a
<command>getty</command> process on the correct port. You should see
a lines like this among the processes displayed:</para>
<screen> 114 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd0
115 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd1</screen>
@ -1635,7 +1635,7 @@ AT&amp;B2&amp;W</programlisting>
<sect3>
<title>Try Dialing In</title>
<para>Try dialing into the system; be sure to use 8 bits, no parity, 1
stop bit on the remote system. If you do not get a prompt right
away, or get garbage, try pressing <literal>&lt;Enter&gt;</literal>
@ -1649,7 +1649,7 @@ AT&amp;B2&amp;W</programlisting>
<para>If you still cannot get a <prompt>login:</prompt> prompt, check
<filename>/etc/gettytab</filename> again and double-check
that</para>
<itemizedlist>
<listitem>
<para>The initial capability name specified in
@ -1667,7 +1667,7 @@ AT&amp;B2&amp;W</programlisting>
<filename>gettytab</filename> capability name</para>
</listitem>
</itemizedlist>
<para>If you dial but the modem on the FreeBSD system will not answer,
make sure that the modem is configured to answer the phone when
<acronym>DTR</acronym> is asserted. If the modem seems to be
@ -1715,7 +1715,7 @@ AT&amp;B2&amp;W</programlisting>
the Internet if you have problems with PPP. If you need to ftp
something and PPP is broken, use the terminal session to ftp it. Then
use zmodem to transfer it to your machine.</para>
<sect2>
<title>Why cannot I run <command>tip</command> or
<command>cu</command>?</title>
@ -2044,7 +2044,7 @@ raisechar=^^</programlisting>
cable and a null-modem adapter. See <xref linkend="term"> for
a discussion on serial cables.</para>
</step>
<step>
<para>Unplug your keyboard.</para>
@ -2085,7 +2085,7 @@ raisechar=^^</programlisting>
not much good without the keyboard anyway.</para>
</note>
</step>
<step>
<para>Plug a dumb terminal into <devicename>COM1:</devicename>
(<devicename>sio0</devicename>).</para>
@ -2175,7 +2175,7 @@ device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4</programlisting>
<para>If the flags were not set, you need to run UserConfig (on a
different console) or recompile the kernel.</para>
</step>
<step>
<para>Create <filename>boot.config</filename> in the root directory
of the <literal>a</literal> partition on the boot drive.</para>
@ -2259,7 +2259,7 @@ device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4</programlisting>
serial port as the console only during the boot block; the boot
loader will use the internal video display as the console.</para>
</step>
<step>
<para>Boot the machine.</para>
@ -2363,9 +2363,9 @@ boot:</screen>
<sect3>
<title>Case 1: You set the flags to 0x10 for sio0</title>
<programlisting>device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4</programlisting>
<informaltable frame="none">
<tgroup cols="4">
<thead>
@ -2426,7 +2426,7 @@ boot:</screen>
<sect3>
<title>Case 2: You set the flags to 0x30 for sio0</title>
<programlisting>device sio0 at isa? port "IO_COM1" tty flags 0x30 irq 4</programlisting>
<informaltable frame="none">
@ -2493,13 +2493,13 @@ boot:</screen>
<sect3>
<title>Setting A Faster Serial Port Speed</title>
<para>By default the serial port settings are set to 9600 baud, 8
bits, no parity, 1 stop bit. If you wish to change the speed, you
need to recompile at least the boot blocks. Add the following line
to <filename>/etc/make.conf</filename> and compile new boot
blocks:</para>
<programlisting>BOOT_COMCONSOLE_SPEED=19200</programlisting>
<para>If the serial console is configured in some other way than by
@ -2514,7 +2514,7 @@ boot:</screen>
<sect3 id="serialconsole-com2">
<title>Using Serial Port Other Than <devicename>sio0</devicename> For
The Console</title>
<para>Using a port other than <devicename>sio0</devicename> as the
console requires some recompiling. If you want to use another
serial port for whatever reasons, recompile the boot blocks, the
@ -2581,7 +2581,7 @@ boot:</screen>
<sect3>
<title>Entering the DDB Debugger from the Serial Line</title>
<para>If you wish to drop into the kernel debugger from the serial
console (useful for remote diagnostics, but also dangerous if you
generate a spurious BREAK on the serial port!) then you should
@ -2593,7 +2593,7 @@ options DDB</programlisting>
<sect3>
<title>Getting a Login Prompt on the Serial Console</title>
<para>While this is not required, you may wish to get a
<emphasis>login</emphasis> prompt over the serial line, now that you
can see boot messages and can enter the kernel debugging session
@ -2636,7 +2636,7 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
<sect3>
<title>Setting Up the Serial Console</title>
<para>You can easily specify the boot loader and the kernel to use the
serial console by writing just one line in
<filename>/boot/loader.rc</filename>:</para>
@ -2651,7 +2651,7 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
the serial console as early as possible.</para>
<para>Likewise, you can specify the internal console as:</para>
<programlisting>set console=vidconsole</programlisting>
<para>If you do not set the boot loader environment variable
@ -2674,11 +2674,11 @@ start</programlisting>
<programlisting>console=comconsole</programlisting>
<para>or</para>
<programlisting>console=vidconsole</programlisting>
<para>See &man.loader.conf.5; for more information.</para>
<note>
<para>At the moment, the boot loader has no option equivalent to the
<option>-P</option> option in the boot block, and there is no
@ -2690,7 +2690,7 @@ start</programlisting>
<sect3>
<title>Using Serial Port Other than <devicename>sio0</devicename> for
the Console</title>
<para>You need to recompile the boot loader to use a serial port other
than <devicename>sio0</devicename> for the serial console. Follow the
procedure described in <xref linkend="serialconsole-com2">.</para>

54
en_US.ISO8859-1/books/handbook/staff/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/staff/chapter.sgml,v 1.75 1999/11/04 08:50:31 phantom Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/staff/chapter.sgml,v 1.76 1999/11/04 09:11:53 phantom Exp $
-->
<!--
@ -22,9 +22,9 @@
Directors&rdquo;, responsible for deciding the project's overall goals
and direction as well as managing <link linkend="staff-who">specific
areas</link> of the FreeBSD project landscape.</para>
<para>(in alphabetical order by last name):</para>
<itemizedlist>
<listitem>
<para>&a.asami;</para>
@ -737,11 +737,11 @@
Documentation Project</ulink> is responsible for a number of different
services, each service being run by an individual and his
<emphasis>deputies</emphasis> (if any):</para>
<variablelist>
<varlistentry>
<term>Documentation Project Architect</term>
<listitem>
<para>&a.nik;</para>
</listitem>
@ -749,7 +749,7 @@
<varlistentry>
<term>Webmaster</term>
<listitem>
<para>&a.wosch;</para>
</listitem>
@ -757,7 +757,7 @@
<varlistentry>
<term>Handbook &amp; FAQ Editor</term>
<listitem>
<para>&a.faq;</para>
</listitem>
@ -765,7 +765,7 @@
<varlistentry>
<term>News Editor</term>
<listitem>
<para>-</para>
@ -776,7 +776,7 @@
<varlistentry>
<term>In the Press Editor</term>
<listitem>
<para>&a.jkoshy;</para>
</listitem>
@ -784,7 +784,7 @@
<varlistentry>
<term>FreeBSD Really-Quick NewsLetter Editor</term>
<listitem>
<para>Chris Coleman <email>chrisc@vmunix.com</email></para>
</listitem>
@ -792,7 +792,7 @@
<varlistentry>
<term>Gallery Editor</term>
<listitem>
<para>-</para>
@ -803,7 +803,7 @@
<varlistentry>
<term>Commercial Editor</term>
<listitem>
<para>&a.nik;</para>
</listitem>
@ -811,7 +811,7 @@
<varlistentry>
<term>Web Changes Editor</term>
<listitem>
<para>-</para>
</listitem>
@ -819,7 +819,7 @@
<varlistentry>
<term>User Groups Editor</term>
<listitem>
<para>&a.grog;</para>
</listitem>
@ -827,7 +827,7 @@
<varlistentry>
<term>LinuxDoc to DocBook conversion</term>
<listitem>
<para>&a.nik;</para>
</listitem>
@ -851,7 +851,7 @@
<term><ulink
url="http://www.FreeBSD.org/docproj/docproj.html">Documentation
Project Manager</ulink></term>
<listitem>
<para>&a.nik;</para>
</listitem>
@ -859,14 +859,14 @@
<varlistentry>
<term><link linkend="l10n">Internationalization</link></term>
<listitem>
<para>&a.ache;</para>
</listitem>
</varlistentry>
<varlistentry><term>Networking</term>
<listitem>
<para>&a.wollman;</para>
</listitem>
@ -874,7 +874,7 @@
<varlistentry>
<term><link linkend="eresources-mail">Postmaster</link></term>
<listitem>
<para>&a.jmb;</para>
</listitem>
@ -882,7 +882,7 @@
<varlistentry>
<term>Release Coordinator</term>
<listitem>
<para>&a.jkh;</para>
</listitem>
@ -890,7 +890,7 @@
<varlistentry>
<term>Public Relations &amp; Corporate Liaison</term>
<listitem>
<para>&a.jkh;</para>
</listitem>
@ -899,7 +899,7 @@
<varlistentry>
<term><ulink url="http://www.FreeBSD.org/security/">Security
Officer</ulink></term>
<listitem>
<para>&a.imp;</para>
</listitem>
@ -908,7 +908,7 @@
<varlistentry>
<term><ulink url="http://www.FreeBSD.org/support.html#cvs">Source
Repository Managers</ulink></term>
<listitem>
<para>Principal: &a.peter;</para>
@ -921,7 +921,7 @@
<varlistentry>
<term><ulink url="http://www.FreeBSD.org/ports/">Ports
Manager</ulink></term>
<listitem>
<para>&a.asami;</para>
</listitem>
@ -929,7 +929,7 @@
<varlistentry>
<term>XFree86 Project, Inc. Liaison</term>
<listitem>
<para>&a.rich;</para>
</listitem>
@ -937,7 +937,7 @@
<varlistentry>
<term><link linkend="eresources-news">Usenet Support</link></term>
<listitem>
<para>&a.joerg;</para>
</listitem>
@ -955,7 +955,7 @@
<varlistentry>
<term><ulink
url="http://www.FreeBSD.org/internal/">Webmaster</ulink></term>
<listitem>
<para>&a.wosch;</para>
</listitem>

44
en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.15 1999/09/06 06:52:53 peter Exp $
-->
<chapter id="advanced-networking">
@ -12,7 +12,7 @@
<para><emphasis>Contributed by &a.gryphon;. 6 October
1995.</emphasis></para>
<para>For one machine to be able to find another, there must be a
mechanism in place to describe how to get from one to the other. This is
called Routing. A &ldquo;route&rdquo; is a defined pair of addresses: a
@ -25,7 +25,7 @@
We will talk a little bit more about default routes later on. There are
also three types of gateways: individual hosts, interfaces (also called
&ldquo;links&rdquo;), and ethernet hardware addresses.</para>
<sect2>
<title>An example</title>
@ -325,7 +325,7 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
can lead to serious network problems, particularly with NFS. This
difficulty is not specific to FreeBSD, but FreeBSD systems are affected
by it.</para>
<para>The problem nearly always occurs when (FreeBSD) PC systems are
networked with high-performance workstations, such as those made by
Silicon Graphics, Inc., and Sun Microsystems, Inc. The NFS mount will
@ -336,7 +336,7 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
many systems, there is no way to shut down the client gracefully once
this problem has manifested itself. The only solution is often to reset
the client, because the NFS situation cannot be resolved.</para>
<para>Though the &ldquo;correct&rdquo; solution is to get a higher
performance and capacity Ethernet adapter for the FreeBSD system, there
is a simple workaround that will allow satisfactory operation. If the
@ -347,13 +347,13 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
specified using the fourth field of the <filename>fstab</filename> entry
on the client for automatic mounts, or by using the <option>-o</option>
parameter of the mount command for manual mounts.</para>
<para>It should be noted that there is a different problem, sometimes
mistaken for this one, when the NFS servers and clients are on different
networks. If that is the case, make <emphasis>certain</emphasis> that
your routers are routing the necessary UDP information, or you will not
get anywhere, no matter what else you are doing.</para>
<para>In the following examples, <hostid>fastws</hostid> is the host
(interface) name of a high-performance workstation, and
<hostid>freebox</hostid> is the host (interface) name of a FreeBSD
@ -364,7 +364,7 @@ Local1 (10.20.30.1, 10.9.9.30) --&gt; T1-GW (10.9.9.1)
cases, note that additional options, such as <option>hard</option> or
<option>soft</option> and <option>bg</option> may be desirable in your
application.</para>
<para>Examples for the FreeBSD system (<hostid>freebox</hostid>) as the
client: in <filename>/etc/fstab</filename> on freebox:</para>
@ -387,7 +387,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0</programlisting>
<para>Nearly any 16-bit Ethernet adapter will allow operation without the
above restrictions on the read or write size.</para>
<para>For anyone who cares, here is what happens when the failure occurs,
which also explains why it is unrecoverable. NFS typically works with a
&ldquo;block&rdquo; size of 8k (though it may do fragments of smaller
@ -407,7 +407,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0</programlisting>
<para>By keeping the unit size below the Ethernet packet size limitation,
we ensure that any complete Ethernet packet received can be acknowledged
individually, avoiding the deadlock situation.</para>
<para>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 guaranteed on NFS &ldquo;units&rdquo;. When an overrun
@ -425,7 +425,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0</programlisting>
allow you to boot your FreeBSD machine over the network and run FreeBSD
without having a disk on your client. Under 2.0 it is now possible to
have local swap. Swapping over NFS is also still supported.</para>
<para>Supported Ethernet cards include: Western Digital/SMC 8003, 8013,
8216 and compatibles; NE1000/NE2000 and compatibles (requires
recompile)</para>
@ -451,7 +451,7 @@ freebox:/sharedfs /project nfs rw,-w=1024 0 0</programlisting>
</listitem>
</itemizedlist>
</step>
<step>
<para>Set up a bootp server to provide the client with IP, gateway,
netmask.</para>
@ -467,7 +467,7 @@ diskless:\
:gw=192.1.2.5:\
:vm=rfc1048:</programlisting>
</step>
<step>
<para>Set up a TFTP server (on same machine as bootp server) to
provide booting information to client. The name of this file is
@ -572,7 +572,7 @@ hostname myclient.mydomain</programlisting>
rootfs 192.1.2.3:/rootfs/myclient
hostname myclient.mydomain</programlisting>
</step>
<step>
<para>Ensure that your NFS server has exported the root (and swap if
applicable) filesystems to your client, and that the client has
@ -610,7 +610,7 @@ hostname myclient.mydomain</programlisting>
<screen>&prompt.root; <userinput>chmod 0600 /swapfs/swap.192.1.2.4</userinput></screen>
</step>
<step>
<para>Unpack the root filesystem in the directory the client will
use for its root filesystem (<filename>/rootfs/myclient</filename>
@ -634,7 +634,7 @@ hostname myclient.mydomain</programlisting>
</listitem>
</itemizedlist>
</step>
<step>
<para>Run <command>netboot.com</command> on the client or make an
EPROM from the <filename>netboot.rom</filename> file</para>
@ -671,7 +671,7 @@ hostname myclient.mydomain</programlisting>
<para>A good resource for information on ISDN technology and hardware is
<ulink url="http://alumni.caltech.edu/~dank/isdn/">Dan Kegel's ISDN
Page</ulink>.</para>
<para>A quick simple roadmap to ISDN follows:</para>
<itemizedlist>
@ -734,7 +734,7 @@ hostname myclient.mydomain</programlisting>
<para>In case you are interested in adding support for a different ISDN
protocol, a currently unsupported ISDN PC card or otherwise enhancing
isdn4bsd, please get in touch with <email>hm@kts.org</email>.</para>
<para>A majordomo maintained mailing list is available. To join the
list, send mail to <email>majordomo@FreeBSD.org</email> and
specify:</para>
@ -782,7 +782,7 @@ subscribe freebsd-isdn</programlisting>
<listitem>
<para>Motorola BitSurfer and Bitsurfer Pro</para>
</listitem>
<listitem>
<para>Adtran</para>
</listitem>
@ -857,7 +857,7 @@ subscribe freebsd-isdn</programlisting>
<example>
<title>Branch office or Home network</title>
<para>Network is 10 Base T Ethernet. Connect router to network cable
with AUI/10BT transceiver, if necessary.</para>
@ -880,9 +880,9 @@ ISDN BRI line</programlisting>
<example>
<title>Head office or other lan</title>
<para>Network is Twisted Pair Ethernet.</para>
<!-- This should be a graphic -->
<programlisting>
-------Novell Server

22
en_US.ISO_8859-1/books/handbook/backups/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml,v 1.12 1999/09/10 00:56:44 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/backups/chapter.sgml,v 1.13 1999/10/26 21:39:59 nik Exp $
-->
<chapter id="backups">
@ -337,7 +337,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
most widely used backup strategy. There are no initial costs. There
is no backup schedule to follow. Just say no. If something happens
to your data, grin and bear it!</para>
<para>If your time and your data is worth little to nothing, then
&ldquo;Do nothing&rdquo; is the most suitable backup program for your
computer. But beware, Unix is a useful tool, you may find that within
@ -377,7 +377,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<sect3>
<title>Before the Disaster</title>
<para>There are only four steps that you need to perform in
preparation for any disaster that may occur.</para>
@ -581,14 +581,14 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
<sect3>
<title>After the Disaster</title>
<para>The key question is: did your hardware survive? You have been
doing regular backups so there is no need to worry about the
software.</para>
<para>If the hardware has been damaged. First, replace those parts
that have been damaged.</para>
<para>If your hardware is okay, check your floppies. If you are using
a custom boot floppy, boot single-user (type <literal>-s</literal>
at the <prompt>boot:</prompt> prompt). Skip the following
@ -605,7 +605,7 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
located in <filename>/mnt2/stand</filename>.</para>
<para>Recover each filesystem separately.</para>
<para>Try to &man.mount.8; (e.g. <command>mount /dev/da0a
/mnt</command>) the root partition of your first disk. If the
disklabel was damaged, use &man.disklabel.8; to re-partition and
@ -617,7 +617,7 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
/dev/sa0</command>). Unmount the filesystem (e.g. <command>umount
/mnt</command>) Repeat for each filesystem that was
damaged.</para>
<para>Once your system is running, backup your data onto new tapes.
Whatever caused the crash or data loss may strike again. An another
hour spent now, may save you from further distress later.</para>
@ -625,7 +625,7 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
<sect3>
<title>* I did not prepare for the Disaster, What Now?</title>
<para></para>
</sect3>
</sect2>
@ -645,11 +645,11 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
<para>The media is unreliable, especially over long periods of
time</para>
</listitem>
<listitem>
<para>Backing up and restoring is very slow</para>
</listitem>
<listitem>
<para>They have a very limited capacity (the days of backing up
an entire hard disk onto a dozen or so floppies has long since

8
en_US.ISO_8859-1/books/handbook/basics/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/basics/chapter.sgml,v 1.11 1999/09/06 06:52:54 peter Exp $
-->
<chapter id="basics">
@ -79,7 +79,7 @@
documentation, so &man.chmod.1; refers to the
<command>chmod</command> user command and &man.chmod.2; refers to the
system call.</para>
<para>This is fine if you know the name of the command and simply wish to
know how to use it, but what if you cannot recall the command name? You
can use <command>man</command> to search for keywords in the command
@ -92,7 +92,7 @@
have the keyword &ldquo;mail&rdquo; in their descriptions. This is
actually functionally equivalent to using the <command>apropos</command>
command.</para>
<para>So, you are looking at all those fancy commands in
<filename>/usr/bin</filename> but do not even have the faintest idea
what most of them actually do? Simply do a
@ -116,7 +116,7 @@
<command>info</command> command or, if you installed
<command>emacs</command>, the info mode of
<command>emacs</command>.</para>
<para>To use the &man.info.1; command, simply type:</para>
<screen>&prompt.user; <userinput>info</userinput></screen>

74
en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.125 1999/10/31 05:02:06 jdp Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.126 1999/11/02 23:45:01 jim Exp $
-->
<chapter id="contrib">
@ -50,7 +50,7 @@
interested in working on one of the tasks you see here, send mail to the
coordinator listed by clicking on their names. If no coordinator has
been appointed, maybe you would like to volunteer?</para>
<sect2>
<title>High priority tasks</title>
@ -69,7 +69,7 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Filesystem problems. Overall coordination: &a.fs;</para>
@ -88,7 +88,7 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Implement Int13 vm86 disk driver. Coordinator:
&a.hackers;</para>
@ -129,11 +129,11 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Kernel issues. Overall coordination: &a.hackers;</para>
</listitem>
<listitem>
<para>Add more pro-active security infrastructure. Overall
coordination: &a.security;</para>
@ -214,7 +214,7 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>PCMCIA/PCCARD. Coordinators: &a.msmith; and &a.phk;</para>
@ -248,7 +248,7 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Advanced Power Management. Coordinators: &a.msmith; and
&a.phk;</para>
@ -292,17 +292,17 @@
network cards. The same thing for NDIS drivers and NetWare SCSI
drivers.</para>
</listitem>
<listitem>
<para>An "upgrade system" option that works on Linux boxes instead
of just previous rev FreeBSD boxes.</para>
</listitem>
<listitem>
<para>Symmetric Multiprocessing with kernel preemption (requires
kernel preemption).</para>
</listitem>
<listitem>
<para>A concerted effort at support for portable computers. This is
somewhat handled by changing PCMCIA bridging rules and power
@ -334,21 +334,21 @@
the latest release from it and report any failures in the
process.</para>
</listitem>
<listitem>
<para>Read the freebsd-bugs mailing list. There might be a
problem you can comment constructively on or with patches you
can test. Or you could even try to fix one of the problems
yourself.</para>
</listitem>
<listitem>
<para>Read through the FAQ and Handbook periodically. If anything
is badly explained, out of date or even just completely wrong, let
us know. Even better, send us a fix (SGML is not difficult to
learn, but there is no objection to ASCII submissions).</para>
</listitem>
<listitem>
<para>Help translate FreeBSD documentation into your native language
(if not already available) &mdash; just send an email to &a.doc;
@ -357,7 +357,7 @@
by doing this &mdash; in fact, the documentation most in need of
translation is the installation instructions.</para>
</listitem>
<listitem>
<para>Read the freebsd-questions mailing list and &ng.misc
occasionally (or even regularly). It can be very satisfying to
@ -365,19 +365,19 @@
sometimes you may even learn something new yourself! These forums
can also be a source of ideas for things to work on.</para>
</listitem>
<listitem>
<para>If you know of any bugfixes which have been successfully
applied to -current but have not been merged into -stable after a
decent interval (normally a couple of weeks), send the committer a
polite reminder.</para>
</listitem>
<listitem>
<para>Move contributed software to <filename>src/contrib</filename>
in the source tree.</para>
</listitem>
<listitem>
<para>Make sure code in <filename>src/contrib</filename> is up to
date.</para>
@ -386,23 +386,23 @@
<listitem>
<para>Look for year 2000 bugs (and fix any you find!)</para>
</listitem>
<listitem>
<para>Build the source tree (or just part of it) with extra warnings
enabled and clean up the warnings.</para>
</listitem>
<listitem>
<para>Fix warnings for ports which do deprecated things like using
gets() or including malloc.h.</para>
</listitem>
<listitem>
<para>If you have contributed any ports, send your patches back to
the original author (this will make your life easier when they
bring out the next version)</para>
</listitem>
<listitem>
<para>Suggest further tasks for this list!</para>
</listitem>
@ -434,7 +434,7 @@
<para>Contributions to the system generally fall into one or more of the
following 6 categories:</para>
<sect2 id="contrib-general">
<title>Bug reports and general commentary</title>
@ -508,7 +508,7 @@
<screen>&prompt.user; <userinput>diff -c oldfile newfile</userinput></screen>
or
<screen>&prompt.user; <userinput>diff -c -r olddir newdir</userinput></screen>
would generate such a set of context diffs for the given source file
@ -567,7 +567,7 @@
participation by commercial interests who might eventually be
inclined to invest something of their own into FreeBSD.</para>
</listitem>
<listitem>
<para>The GNU Public License, or &ldquo;GPL&rdquo;. This license is
not quite as popular with us due to the amount of extra effort
@ -637,7 +637,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<sect3>
<title><anchor id="donations">Donating funds</title>
<para>While the FreeBSD Project is not a 501(c)(3) (charitable)
corporation and hence cannot offer special tax incentives for any
donations made, any such donations will be gratefully accepted on
@ -660,12 +660,12 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<city>Concord</city>
<state>CA</state>, <postcode>94520</postcode>
</address>
<para>(currently using the Walnut Creek CDROM address until a PO box
can be opened)</para>
<para>Wire transfers may also be sent directly to:</para>
<address>
<otheraddr>Bank Of America</otheraddr>
<otheraddr>Concord Main Office</otheraddr>
@ -676,7 +676,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<otheraddr>Routing #: 121-000-358</otheraddr>
<otheraddr>Account #: 01411-07441 (FreeBSD, Inc.)</otheraddr>
</address>
<para>Any correspondence related to donations should be sent to &a.jkh,
either via email or to the FreeBSD, Inc. postal address given above.
</para>
@ -688,7 +688,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<sect3>
<title>Donating hardware</title>
<para>Donations of hardware in any of the 3 following categories are
also gladly accepted by the FreeBSD Project:</para>
@ -722,7 +722,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<sect3>
<title>Donating Internet access</title>
<para>We can always use new mirror sites for FTP, WWW or
<command>cvsup</command>. If you would like to be such a mirror,
please contact the FreeBSD project administrators
@ -783,7 +783,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<listitem>
<para><emphasis>Direct funding:</emphasis></para>
<para>The following individuals and businesses have generously
contributed direct funding to the project:</para>
@ -897,11 +897,11 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<listitem>
<para><emphasis>Hardware contributors:</emphasis></para>
<para>The following individuals and businesses have generously
contributed hardware for testing and device driver
development/support:</para>
<itemizedlist>
<listitem>
<para>Walnut Creek CDROM for providing the Pentium P5-90 and
@ -968,7 +968,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<listitem>
<para><emphasis>Special contributors:</emphasis></para>
<itemizedlist>
<listitem>
<para><ulink url="http://www.cdrom.com/">Walnut Creek CDROM</ulink>
@ -1069,7 +1069,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
4.4BSD-Lite release provided by the Computer Science Research Group
(CSRG) at the University of California, Berkeley and associated academic
contributors.</para>
<para>There are also portions of NetBSD and OpenBSD that have been
integrated into FreeBSD as well, and we would therefore like to thank
all the contributors to NetBSD and OpenBSD for their work.</para>

190
en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.31 1999/09/26 18:41:18 nik Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.32 1999/10/29 09:29:15 jkh Exp $
-->
<chapter id="cutting-edge">
@ -46,7 +46,7 @@
part of the source tree and for whom keeping &ldquo;current&rdquo;
is an absolute requirement.</para>
</listitem>
<listitem>
<para>Members of the FreeBSD group who are active testers, willing
to spend time working through problems in order to ensure that
@ -54,7 +54,7 @@
who wish to make topical suggestions on changes and the general
direction of FreeBSD.</para>
</listitem>
<listitem>
<para>Peripheral members of the FreeBSD (or some other) group who
merely wish to keep an eye on things and use the current sources
@ -74,11 +74,11 @@
there is some cool new feature in there and you want to be the
first on your block to have it.</para>
</listitem>
<listitem>
<para>A quick way of getting bug fixes.</para>
</listitem>
<listitem>
<para>In any way &ldquo;officially supported&rdquo; by us. We do
our best to help people genuinely in one of the 3
@ -125,7 +125,7 @@ subscribe cvs-all</programlisting>
how to subscribe and unsubscribe to the various other mailing
lists we support.</para>
</listitem>
<listitem>
<para>Grab the sources from <hostid
role="fqdn">ftp.FreeBSD.org</hostid>. You can do this in three
@ -174,7 +174,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
</listitem>
</orderedlist>
</listitem>
<listitem>
<para>Essentially, if you need rapid on-demand access to the source
and communications bandwidth is not a consideration, use
@ -249,7 +249,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<title>Using FreeBSD-stable</title>
<orderedlist>
<listitem>
<para>Join the &a.stable;. This will keep you informed of
build-dependencies that may appear in <emphasis>stable</emphasis>
@ -274,7 +274,7 @@ subscribe cvs-all</programlisting>
how to subscribe and unsubscribe to the various other mailing
lists we support.</para>
</listitem>
<listitem>
<para>If you are installing a new system and want it to be as stable
as possible, you can simply grab the latest dated branch snapshot
@ -331,14 +331,14 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
</listitem>
</orderedlist>
</listitem>
<listitem>
<para>Essentially, if you need rapid on-demand access to the source
and communications bandwidth is not a consideration, use
<command>cvsup</command> or <command>ftp</command>. Otherwise,
use <application>CTM</application>.</para>
</listitem>
<listitem>
<para>Before compiling stable, read the Makefile in
<filename>/usr/src</filename> carefully. You should at least run
@ -356,14 +356,14 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<title>Synchronizing Source Trees over the Internet</title>
<para><emphasis>Contributed by &a.jkh;.</emphasis></para>
<para>There are various ways of using an Internet (or email) connection to
stay up-to-date with any given area of the FreeBSD project sources, or
all areas, depending on what interests you. The primary services we
offer are <link linkend="anoncvs">Anonymous CVS</link>, <link
linkend="cvsup">CVSup</link>, and <link
linkend="ctm">CTM</link>.</para>
<para><application>Anonymous CVS</application> and
<application>CVSup</application> use the <emphasis>pull</emphasis> model
of updating sources. In the case of <application>CVSup</application>
@ -380,7 +380,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
from a remote CVS repository. <application>CVSup</application> can do
this far more efficiently, but <application>Anonymous CVS</application>
is easier to use.</para>
<para><application>CTM</application>, on the other hand, does not
interactively compare the sources you have with those on the master
archive or otherwise pull them across.. Instead, a script which
@ -404,7 +404,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
will have to start from scratch (from the most recent CVS &ldquo;base
delta&rdquo;) and rebuild it all with CTM or, with anoncvs, simply
delete the bad bits and resync.</para>
<para>For more information on <application>Anonymous CVS</application>,
<application>CTM</application>, and <application>CVSup</application>,
please see one of the following sections:</para>
@ -416,7 +416,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title><anchor id="anoncvs-intro">Introduction</title>
<para>Anonymous CVS (or, as it is otherwise known,
<emphasis>anoncvs</emphasis>) is a feature provided by the CVS
utilities bundled with FreeBSD for synchronizing with a remote CVS
@ -454,7 +454,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title><anchor id="anoncvs-usage">Using Anonymous CVS</title>
<para>Configuring &man.cvs.1; to use an Anonymous CVS repository is a
simple matter of setting the <envar>CVSROOT</envar> environment
variable to point to one of the FreeBSD project's
@ -467,7 +467,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
anoncvs@anoncvs.FreeBSD.org:/cvs</para>
</listitem>
</itemizedlist>
<para>Since CVS allows one to &ldquo;check out&rdquo; virtually any
version of the FreeBSD sources that ever existed (or, in some cases,
will exist <!-- smiley -->:), you need to be familiar with the
@ -481,7 +481,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
the latest revision on a given line of development, at any given
time. Because a branch tag does not refer to a specific revision,
it may mean something different tomorrow than it means today.</para>
<para>Here are the branch tags that users might be interested
in:</para>
@ -523,10 +523,10 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
</listitem>
</varlistentry>
</variablelist>
<para>Here are the revision tags that users might be interested
in:</para>
<variablelist>
<varlistentry>
<term>RELENG_3_3_0_RELEASE</term>
@ -659,7 +659,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
</listitem>
</varlistentry>
</variablelist>
<para>When you specify a branch tag, you normally receive the latest
versions of the files on that line of development. If you wish to
receive some past version, you can do so by specifying a date with
@ -669,7 +669,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Examples</title>
<para>While it really is recommended that you read the manual page for
&man.cvs.1; thoroughly before doing anything, here are some
quick examples which essentially show how to use Anonymous
@ -684,7 +684,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
&prompt.user; <userinput>cvs co ls</userinput>
&prompt.user; <userinput>cvs release -d ls</userinput></screen>
</example>
<example>
<title>Checking out the version of ls(1) in the 2.2-stable
branch:</title>
@ -694,7 +694,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
&prompt.user; <userinput>cvs co -rRELENG_2_2 ls</userinput>
&prompt.user; <userinput>cvs release -d ls</userinput></screen>
</example>
<example>
<title>Creating a list of changes (as unidiffs) to &man.ls.1;</title>
@ -716,10 +716,10 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Other Resources</title>
<para>The following additional resources may be helpful in learning
CVS:</para>
<itemizedlist>
<listitem>
<para><ulink
@ -756,7 +756,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Why should I use <application>CTM</application>?</title>
<para><application>CTM</application> will give you a local copy of the
FreeBSD source trees. There are a number of &ldquo;flavors&rdquo;
of the tree available. Whether you wish to track the entire cvs
@ -781,7 +781,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>What do I need to use <application>CTM</application>?</title>
<para>You will need two things: The <application>CTM</application>
program and the initial deltas to feed it (to get up to
&ldquo;current&rdquo; levels).</para>
@ -807,7 +807,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/">ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/</ulink></para>
<para>or see section <link linkend="mirrors-ctm">mirrors</link>.</para>
<para>FTP the relevant directory and fetch the
<filename>README</filename> file, starting from there.</para>
@ -880,9 +880,9 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Using <application>CTM</application> in your daily life</title>
<para>To apply the deltas, simply say:</para>
<screen>&prompt.root; <userinput>cd /where/ever/you/want/the/stuff</userinput>
&prompt.root; <userinput>ctm -v -v /where/you/store/your/deltas/src-xxx.*</userinput></screen>
@ -918,7 +918,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Keeping your local changes</title>
<para>As a developer one would like to experiment with and change
files in the source tree. <application>CTM</application> supports
local modifications in a limited way: before checking for the
@ -935,7 +935,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Other interesting <application>CTM</application> options</title>
<sect4>
<title>Finding out exactly what would be touched by an
update</title>
@ -949,7 +949,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
pre- or post- process the modified files in any manner, or just
are feeling a tad paranoid <!-- smiley -->:-).</para>
</sect4>
<sect4>
<title>Making backups before updating</title>
@ -961,7 +961,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
touched by a given <application>CTM</application> delta to
<filename>backup-file</filename>.</para>
</sect4>
<sect4>
<title>Restricting the files touched by an update</title>
@ -993,9 +993,9 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Future plans for <application>CTM</application></title>
<para>Tons of them:</para>
<itemizedlist>
<listitem>
<para>Use some kind of authentication into the CTM system, so as
@ -1007,7 +1007,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
became confusing and counter intuitive.</para>
</listitem>
</itemizedlist>
<para>The bad news is that I am very busy, so any help in doing this
will be most welcome. And do not forget to tell me what you want
also...</para>
@ -1015,7 +1015,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Miscellaneous stuff</title>
<para>All the &ldquo;DES infected&rdquo; (e.g. export controlled)
source is not included. You will get the
&ldquo;international&rdquo; version only. If sufficient interest
@ -1028,7 +1028,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3>
<title>Thanks!</title>
<variablelist>
<varlistentry>
<term>&a.bde;</term>
@ -1081,7 +1081,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3 id="cvsup-intro">
<title>Introduction</title>
<para><application>CVSup</application> is a software package for
distributing and updating source trees from a master CVS repository
on a remote server host. The FreeBSD sources are maintained in a
@ -1119,7 +1119,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3 id="cvsup-install">
<title>Installation</title>
<para>The easiest way to install <application>CVSup</application> if
you are running FreeBSD 2.2 or later is to use either <ulink
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ports-current/net/cvsup.tar">the
@ -1178,16 +1178,16 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupd-bin-16.0.tar.gz">ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupd-bin-16.0.tar.gz</ulink> (server).</para>
</listitem>
</itemizedlist>
<para>as well as from the many FreeBSD <link linkend="mirrors-ftp">FTP
mirror sites</link> around the world.</para>
<para>Most users will need only the client. These executables are
entirely self-contained, and they will run on any version of FreeBSD
from FreeBSD-2.1.0 to FreeBSD-current.</para>
<para>In summary, your options for installing CVSup are:</para>
<itemizedlist>
<listitem>
<para>FreeBSD-2.2 or later: static binary, port, or
@ -1206,7 +1206,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<sect3 id="cvsup-config">
<title>CVSup Configuration</title>
<para><application>CVSup</application>'s operation is controlled by a
configuration file called the <filename>supfile</filename>.
Beginning with FreeBSD-2.2, there are some sample
@ -1214,7 +1214,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
url="file:/usr/share/examples/cvsup/">/usr/share/examples/cvsup/</ulink>.
These examples are also available from <ulink
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/">ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/</ulink> if you are on a pre-2.2 system.</para>
<para>The information in a <filename>supfile</filename> answers the
following questions for cvsup:</para>
@ -1244,7 +1244,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
your status files?</link></para>
</listitem>
</itemizedlist>
<para>In the following sections, we will construct a typical
<filename>supfile</filename> by answering each of these questions in
turn. First, we describe the overall structure of a
@ -1290,7 +1290,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
<filename>supfile</filename> for receiving and updating the main
source tree of <link
linkend="current">FreeBSD-current</link>.</para>
<itemizedlist>
<listitem>
<para>Which files do you want to receive?<anchor
@ -1695,7 +1695,7 @@ cvs-crypto</programlisting>
<sect3>
<title>Running <application>CVSup</application></title>
<para>You are now ready to try an update. The command line for doing
this is quite simple:</para>
@ -1716,7 +1716,7 @@ cvs-crypto</programlisting>
trial run without touching your precious files. Just create an
empty directory somewhere convenient, and name it as an extra
argument on the command line:</para>
<screen>&prompt.root; <userinput>mkdir /var/tmp/dest</userinput>
&prompt.root; <userinput>cvsup supfile /var/tmp/dest</userinput></screen>
@ -1750,7 +1750,7 @@ cvs-crypto</programlisting>
<para>There are plenty of other options available. For a brief list
of them, type <command>cvsup -H</command>. For more detailed
descriptions, see the manual page.</para>
<para>Once you are satisfied with the way updates are working, you can
arrange for regular runs of cvsup using &man.cron.8;.
Obviously, you should not let cvsup use its GUI when running it from
@ -1773,7 +1773,7 @@ cvs-crypto</programlisting>
<literal>ports-all</literal>. The other collections are used only
by small groups of people for specialized purposes, and some mirror
sites may not carry all of them.</para>
<variablelist>
<varlistentry>
<term><literal>cvs-all release=cvs</literal></term>
@ -2459,7 +2459,7 @@ cvs-crypto</programlisting>
<sect3>
<title>For more information</title>
<para>For the CVSup FAQ and other information about CVSup, see <ulink
url="http://www.polstra.com/projects/freeware/CVSup/">The CVSup
Home Page</ulink>.</para>
@ -2477,14 +2477,14 @@ cvs-crypto</programlisting>
<sect1 id="makeworld">
<title>Using <command>make world</command> to rebuild your system</title>
<para><emphasis>Contributed by &a.nik;.</emphasis></para>
<para>Once you have synchronised your local source tree against a
particular version of FreeBSD (<literal>stable</literal>,
<literal>current</literal> and so on) you must then use the source tree
to rebuild the system.</para>
<warning>
<title>Take a backup</title>
@ -2539,7 +2539,7 @@ cvs-crypto</programlisting>
<note>
<title/Version 2.1.7 and below/
<para>If your machine has a floating point unit (386DX, 486DX, Pentium
and up class machines) then you can also uncomment the HAVE_FPU
line.</para>
@ -2587,9 +2587,9 @@ cvs-crypto</programlisting>
<para>If you are feeling particularly paranoid, you can check your
system to see which files are owned by the group you are renaming or
deleting.</para>
<screen>&prompt.root; <userinput>find / -group <replaceable>GID</replaceable> -print</userinput></screen>
<para>will show all files owned by group <replaceable>GID</replaceable>
(which can be either a group name or a numeric group ID).</para>
</tip>
@ -2609,7 +2609,7 @@ cvs-crypto</programlisting>
<note>
<title>Version 2.2.5 and above</title>
<para>As described in more detail below, versions 2.2.5 and above of
FreeBSD have separated the building process from the installing
process. You can therefore <emphasis>build</emphasis> the new
@ -2618,9 +2618,9 @@ cvs-crypto</programlisting>
</note>
<para>As the superuser, you can execute
<screen>&prompt.root; <userinput/shutdown now/</screen>
from a running system, which will drop it to single user mode.</para>
<para>Alternatively, reboot the system, and at the boot prompt, enter
@ -2662,9 +2662,9 @@ cvs-crypto</programlisting>
<sect3>
<title>All versions</title>
<para>You must be in the <filename>/usr/src</filename> directory, so
<screen>&prompt.root; <userinput>cd /usr/src</userinput></screen>
(unless, of course, your source code is elsewhere, in which case
@ -2674,7 +2674,7 @@ cvs-crypto</programlisting>
command reads instructions from the <filename>Makefile</filename>
which describes how the programs that comprise FreeBSD should be
rebuilt, the order they should be built in, and so on.</para>
<para>The general format of the command line you will type is as
follows;</para>
@ -2695,7 +2695,7 @@ cvs-crypto</programlisting>
<para>is another way of specifying that profiled libaries should not be
built, and corresponds with the
<programlisting>NOPROFILE= true
# Avoid compiling profiled libraries</programlisting>
@ -2719,7 +2719,7 @@ cvs-crypto</programlisting>
<sect3>
<title>Saving the output</title>
<para>It's a good idea to save the output you get from running
&man.make.1; to another file. If something goes wrong you will
have a copy of the error message, and a complete list of where the
@ -2749,11 +2749,11 @@ Script done, &hellip;</screen>
<sect3>
<title>Version 2.2.2 and below</title>
<para><filename>/usr/src/Makefile</filename> contains the
<maketarget>world</maketarget> target, which will rebuild the entire
system and then install it.</para>
<para>Use it like this.</para>
<screen>&prompt.root; <userinput>make world</userinput></screen>
@ -2761,7 +2761,7 @@ Script done, &hellip;</screen>
<sect3>
<title>Version 2.2.5 and above</title>
<para>Beginning with version 2.2.5 of FreeBSD (actually, it was first
created on the -current branch, and then retrofitted to -stable
midway between 2.2.2 and 2.2.5) the <maketarget>world</maketarget>
@ -2817,7 +2817,7 @@ Script done, &hellip;</screen>
<sect3>
<title>-current and above</title>
<para>If you are tracking -current you can also pass the
<option>-j</option> option to <command>make</command>. This lets
<command>make</command> spawn several simultaneous processes.</para>
@ -2837,7 +2837,7 @@ Script done, &hellip;</screen>
<para>If you have a multi-CPU machine and you are using an SMP
configured kernel try values between 6 and 10 and see how they speed
things up.</para>
<para>Be aware that (at the time of writing) this is still
experimental, and commits to the source tree may occasionally break
this feature. If the world fails to compile using this parameter
@ -2849,7 +2849,7 @@ Script done, &hellip;</screen>
<para>Assuming everything goes well you have anywhere between an hour
and a half and a day or so to wait.</para>
<para>As a general rule of thumb, a 200MHz P6 with more than 32MB of
RAM and reasonable SCSI disks will complete <command>make
world</command> in about an hour and a half. A 32MB P133 will
@ -2881,14 +2881,14 @@ Script done, &hellip;</screen>
<warning>
<title>Backup your existing <filename>/etc</filename></title>
<para>Although, in theory, nothing is going to touch this directory
automatically, it is always better to be sure. So copy your
existing <filename>/etc</filename> directory somewhere safe.
Something like:</para>
<screen>&prompt.root; <userinput>cp -Rp /etc /etc.old</userinput></screen>
<para><option>-R</option> does a recursive copy, <option>-p</option>
preserves times, ownerships on files and suchlike.</para>
</warning>
@ -2898,11 +2898,11 @@ Script done, &hellip;</screen>
put this dummy directory in <filename>/var/tmp/root</filename>, and
there are a number of subdirectories required under this as
well.</para>
<screen>&prompt.root; <userinput>mkdir /var/tmp/root</userinput>
&prompt.root; <userinput>cd /usr/src/etc</userinput>
&prompt.root; <userinput>make DESTDIR=/var/tmp/root distrib-dirs distribution</userinput></screen>
<para>This will build the necessary directory structure and install the
files. A lot of the subdirectories that have been created under
<filename>/var/tmp/root</filename> are empty and should be deleted.
@ -2945,15 +2945,15 @@ Script done, &hellip;</screen>
<title>Name the new root directory
(<filename>/var/tmp/root</filename>)with a timestamp, so you can
easily compare differences between versions</title>
<para>Frequently remaking the world means that you have to update
<filename>/etc</filename> frequently as well, which can be a bit of
a chore.</para>
<para>You can speed this process up by keeping a copy of the last set
of changed files that you merged into <filename>/etc</filename>.
The following procedure gives one idea of how to do this.</para>
<procedure>
<step>
<para>Make the world as normal. When you want to update
@ -3013,7 +3013,7 @@ Script done, &hellip;</screen>
to <filename>/etc</filename>.</para>
</step>
</procedure>
<para>You can use &man.date.1; to automate the generation of the
directory names.</para>
@ -3026,7 +3026,7 @@ Script done, &hellip;</screen>
<note>
<title>DEVFS</title>
<para>If you are using DEVFS then this is probably unnecessary.</para>
</note>
@ -3036,7 +3036,7 @@ Script done, &hellip;</screen>
<step>
<para>Copy <filename>/var/tmp/root/dev/MAKEDEV</filename> to
<filename>/dev</filename>.</para>
<screen>&prompt.root; <userinput>cp /var/tmp/root/dev/MAKEDEV /dev</userinput></screen>
</step>
@ -3097,7 +3097,7 @@ Script done, &hellip;</screen>
<note>
<title>Source older than 2 April 1998</title>
<para>If your source code is older than 2nd April 1998, or the
<filename>Makefile</filename> version is not 1.68 or higher (for
FreeBSD current and 3.x systems) or 1.48.2.21 or higher (for 2.2.x
@ -3545,27 +3545,27 @@ Antonio</screen>
<listitem>
<para>Sue Blake, <email>sue@welearn.com.au</email></para>
</listitem>
<listitem>
<para>Brian Haskin, <email>haskin@ptway.com</email></para>
</listitem>
<listitem>
<para>Kees Jan Koster, <email>kjk1@ukc.ac.uk</email></para>
</listitem>
<listitem>
<para>A Joseph Kosy, <email>koshy@india.hp.com</email></para>
</listitem>
<listitem>
<para>Greg Lehey, <email>grog@lemis.com</email></para>
</listitem>
<listitem>
<para>Wes Peters, <email>softweyr@xmission.com</email></para>
</listitem>
<listitem>
<para>Joseph Stein, <email>joes@wstein.com</email></para>
</listitem>
@ -3573,12 +3573,12 @@ Antonio</screen>
<listitem>
<para>Studded, <email>studded@dal.net</email></para>
</listitem>
<listitem>
<para>Axel Thimm,
<email>Axel.Thimm@physik.fu-berlin.de</email></para>
</listitem>
<listitem>
<para>Matthew Thyer,
<email>Matthew.Thyer@dsto.defence.gov.au</email></para>

106
en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.34 1999/10/13 13:02:46 jdp Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.35 1999/10/13 13:08:21 jdp Exp $
-->
<chapter id="eresources">
@ -32,7 +32,7 @@
questions to the appropriate mailing list you will reach both us and a
concentrated FreeBSD audience, invariably assuring a better (or at least
faster) response.</para>
<para>The charters for the various lists are given at the bottom of this
document. <emphasis>Please read the charter before joining or sending
mail to any list</emphasis>. Most of our list subscribers now receive
@ -41,7 +41,7 @@
signal-to-noise ratio of the lists high. To do less would see the
mailing lists ultimately fail as an effective communications medium for
the project.</para>
<para>Archives are kept for all of the mailing lists and can be searched
using the <ulink url="http://www.FreeBSD.org/search.html">FreeBSD World
Wide Web server</ulink>. The keyword searchable archive offers an
@ -354,7 +354,7 @@
be redistributed to mailing list members world-wide.</para>
<para>To subscribe to a list, send mail to &a.majordomo; and include
<programlisting>
subscribe &lt;listname&gt; [&lt;optional address&gt;]</programlisting>
@ -416,7 +416,7 @@ help
<email>freebsd-chat@FreeBSD.org</email> mailing list is freely
available and should be used instead.</para>
</listitem>
<listitem>
<para>No posting should be made to more than 2 mailing lists, and
only to 2 when a clear and obvious need to post to both lists
@ -442,7 +442,7 @@ help
therefore probably rate a warning (or ban) on that basis
alone.</para>
</listitem>
<listitem>
<para>Advertising of non-FreeBSD related products or services is
strictly prohibited and will result in an immediate ban if it is
@ -463,7 +463,7 @@ help
CMU/Transarc</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-ANNOUNCE</term>
@ -478,7 +478,7 @@ help
moderated mailing list.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-ARCH</term>
@ -521,7 +521,7 @@ help
discussion has been resolved.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-BUGS</term>
@ -536,7 +536,7 @@ help
interface</ulink> to it.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-CHAT</term>
@ -555,7 +555,7 @@ help
this -chat list.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-CORE</term>
@ -568,7 +568,7 @@ help
scrutiny.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-CURRENT</term>
@ -584,7 +584,7 @@ help
for which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-CURRENT-DIGEST</term>
@ -600,7 +600,7 @@ help
to.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-DOC</term>
@ -614,7 +614,7 @@ help
list; feel free to join and contribute!</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-FS</term>
@ -639,7 +639,7 @@ help
expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-ISDN</term>
@ -650,7 +650,7 @@ help
development of ISDN support for FreeBSD.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-JAVA</term>
@ -662,7 +662,7 @@ help
porting and maintenance of JDKs.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-HACKERS</term>
@ -678,7 +678,7 @@ help
expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-HACKERS-DIGEST</term>
@ -717,7 +717,7 @@ help
mirror sites.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-INSTALL</term>
@ -728,7 +728,7 @@ help
development for the future releases.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-ISP</term>
@ -742,7 +742,7 @@ help
expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-NEWBIES</term>
@ -761,7 +761,7 @@ help
newbies.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-PLATFORMS</term>
@ -785,7 +785,7 @@ help
Core Team Policy decisions.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-PORTS</term>
@ -800,7 +800,7 @@ help
for which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-QUESTIONS</term>
@ -813,7 +813,7 @@ help
technical.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-QUESTIONS-DIGEST</term>
@ -826,7 +826,7 @@ help
message. The average digest size is about 40kB.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-SCSI</term>
@ -838,7 +838,7 @@ help
which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-SECURITY</term>
@ -850,7 +850,7 @@ help
list for which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-SECURITY-NOTIFICATIONS</term>
@ -861,7 +861,7 @@ help
FreeBSD-security.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-SMALL</term>
@ -871,7 +871,7 @@ help
list for which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-STABLE</term>
@ -887,7 +887,7 @@ help
for which strictly technical content is expected.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>FREEBSD-USER-GROUPS</term>
@ -923,7 +923,7 @@ help
<para><ulink
url="news:comp.unix.bsd.freebsd.announce">comp.unix.bsd.freebsd.announce</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.bsd.freebsd.misc">comp.unix.bsd.freebsd.misc</ulink></para>
@ -938,62 +938,62 @@ help
<listitem>
<para><ulink url="news:comp.unix">comp.unix</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.questions">comp.unix.questions</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.admin">comp.unix.admin</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.programmer">comp.unix.programmer</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.shell">comp.unix.shell</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.user-friendly">comp.unix.user-friendly</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.security.unix">comp.security.unix</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.sources.unix">comp.sources.unix</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.advocacy">comp.unix.advocacy</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.misc">comp.unix.misc</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.bugs.4bsd">comp.bugs.4bsd</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.bugs.4bsd.ucb-fixes">comp.bugs.4bsd.ucb-fixes</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.unix.bsd">comp.unix.bsd</ulink></para>
@ -1009,37 +1009,37 @@ help
<para><ulink
url="news:comp.windows.x.i386unix">comp.windows.x.i386unix</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x">comp.windows.x</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.apps">comp.windows.x.apps</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.announce">comp.windows.x.announce</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.intrinsics">comp.windows.x.intrinsics</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.motif">comp.windows.x.motif</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.windows.x.pex">comp.windows.x.pex</ulink></para>
</listitem>
<listitem>
<para><ulink
url="news:comp.emulators.ms-windows.wine">comp.emulators.ms-windows.wine</ulink></para>
@ -1332,7 +1332,7 @@ help
<entry>Read-only cvs, personal webspace, email</entry>
<entry>&a.brian</entry>
</row>
<row>
<entry>dogma.freebsd-uk.eu.org</entry>
<entry>Telnet/FTP/SSH</entry>

262
en_US.ISO_8859-1/books/handbook/hw/chapter.sgml
View file

File diff suppressed because it is too large Load diff

162
en_US.ISO_8859-1/books/handbook/install/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/install/chapter.sgml,v 1.25 1999/09/21 16:43:15 chris Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/install/chapter.sgml,v 1.26 1999/09/23 21:12:05 chris Exp $
-->
<chapter id="install">
@ -111,7 +111,7 @@
live in the <filename>floppies</filename> subdirectory, as is
typically the case).</para>
</listitem>
<listitem>
<para>If you are using a UNIX system to create the floppy
images:</para>
@ -199,7 +199,7 @@
<para>After adjusting the kernel to match how you have your hardware
configured, type <command>Q</command> to continue booting with the new
settings.</para>
<para>After FreeBSD has been installed, changes made in the configuration
mode will be permanent so you do not have to reconfigure every time you
boot. Even so, it is likely that you will want to build a custom kernel
@ -215,16 +215,16 @@
386sx is not recommended). Support for generic IDE or ESDI drive
configurations, various SCSI controller, network and serial cards is
also provided.</para>
<para>A minimum of four megabytes of RAM is required to run FreeBSD. To
run the X Window System, eight megabytes of RAM is the recommended
minimum.</para>
<para>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.</para>
<sect2>
<title>Disk Controllers</title>
@ -232,15 +232,15 @@
<listitem>
<para>WD1003 (any generic MFM/RLL)</para>
</listitem>
<listitem>
<para>WD1007 (any generic IDE/ESDI)</para>
</listitem>
<listitem>
<para>IDE</para>
</listitem>
<listitem>
<para>ATA</para>
</listitem>
@ -403,7 +403,7 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE
IV and SmartRAID IV SCSI/RAID controllers are supported. The DPT
@ -415,7 +415,7 @@
SMART, SMART-2/E, Smart-2/P, SMART-2SL, Smart Array 3200,
Smart Array 3100ES and Smart Array 221.</para>
</listitem>
<listitem>
<para>SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820,
53C825a, 53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI
@ -451,12 +451,12 @@
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>QLogic 1020, 1040, 1040B, 1080, 1240 and 2100 SCSI and Fibre
Channel Adapters</para>
</listitem>
<listitem>
<para>DTC 3290 EISA SCSI controller in 1542 emulation mode.</para>
</listitem>
@ -478,21 +478,21 @@
<para>SoundBlaster SCSI and ProAudio Spectrum SCSI
(<literal>cd</literal>)</para>
</listitem>
<listitem>
<para>Mitsumi (all models) proprietary interface
(<literal>mcd</literal>)</para>
</listitem>
<listitem>
<para>Matsushita/Panasonic (Creative) CR-562/CR-563 proprietary
interface (<literal>matcd</literal>)</para>
</listitem>
<listitem>
<para>Sony proprietary interface (<literal>scd</literal>)</para>
</listitem>
<listitem>
<para>ATAPI IDE interface (<literal>wcd</literal>)</para>
</listitem>
@ -506,15 +506,15 @@
<para>Tekram DC390 and DC390T controllers (maybe other cards based
on the AMD 53c974 as well).</para>
</listitem>
<listitem>
<para>NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.</para>
</listitem>
<listitem>
<para>UltraStor 14F, 24F and 34F SCSI controllers.</para>
</listitem>
<listitem>
<para>Seagate ST01/02 SCSI controllers.</para>
</listitem>
@ -522,7 +522,7 @@
<listitem>
<para>Future Domain 8xx/950 series SCSI controllers.</para>
</listitem>
<listitem>
<para>WD7000 SCSI controller.</para>
</listitem>
@ -531,11 +531,11 @@
<para>Adaptec 1510 series ISA SCSI controllers (not for bootable
devices)</para>
</listitem>
<listitem>
<para>Adaptec 152x series ISA SCSI controllers</para>
</listitem>
<listitem>
<para>Adaptec AIC-6260 and AIC-6360 based boards, which includes the
AHA-152x and SoundBlaster SCSI cards.</para>
@ -550,22 +550,22 @@
<listitem>
<para>Allied-Telesis AT1700 and RE2000 cards</para>
</listitem>
<listitem>
<para>SMC Elite 16 WD8013 Ethernet interface, and most other
WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and
WD8013EBT based clones. SMC Elite Ultra and 9432TX based cards
are also supported.</para>
</listitem>
<listitem>
<para>DEC EtherWORKS III NICs (DE203, DE204, and DE205)</para>
</listitem>
<listitem>
<para>DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)</para>
</listitem>
<listitem>
<para>DEC DC21040/DC21041/DC21140 based NICs:</para>
@ -643,75 +643,75 @@
<listitem>
<para>DEC FDDI (DEFPA/DEFEA) NICs</para>
</listitem>
<listitem>
<para>Fujitsu FMV-181 and FMV-182</para>
</listitem>
<listitem>
<para>Fujitsu MB86960A/MB86965A</para>
</listitem>
<listitem>
<para>Intel EtherExpress</para>
</listitem>
<listitem>
<para>Intel EtherExpress Pro/100B 100Mbit.</para>
</listitem>
<listitem>
<para>Isolan AT 4141-0 (16 bit)</para>
</listitem>
<listitem>
<para>Isolink 4110 (8 bit)</para>
</listitem>
<listitem>
<para>Lucent WaveLAN wireless networking interface.</para>
</listitem>
<listitem>
<para>Novell NE1000, NE2000, and NE2100 ethernet interface.</para>
</listitem>
<listitem>
<para>3Com 3C501 cards</para>
</listitem>
<listitem>
<para>3Com 3C503 Etherlink II</para>
</listitem>
<listitem>
<para>3Com 3c505 Etherlink/+</para>
</listitem>
<listitem>
<para>3Com 3C507 Etherlink 16/TP</para>
</listitem>
<listitem>
<para>3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III</para>
</listitem>
<listitem>
<para>3Com 3C590, 3C595 Etherlink III</para>
</listitem>
<listitem>
<para>3Com 3C90x cards.</para>
</listitem>
<listitem>
<para>HP PC Lan Plus (27247B and 27252A)</para>
</listitem>
<listitem>
<para>Toshiba ethernet cards</para>
</listitem>
<listitem>
<para>PCMCIA ethernet cards from IBM and National Semiconductor are
also supported.</para>
@ -732,71 +732,71 @@
<listitem>
<para>AST 4 port serial card using shared IRQ.</para>
</listitem>
<listitem>
<para>ARNET 8 port serial card using shared IRQ.</para>
</listitem>
<listitem>
<para>BOCA IOAT66 6 port serial card using shared IRQ.</para>
</listitem>
<listitem>
<para>BOCA 2016 16 port serial card using shared IRQ.</para>
</listitem>
<listitem>
<para>Cyclades Cyclom-y Serial Board.</para>
</listitem>
<listitem>
<para>STB 4 port card using shared IRQ.</para>
</listitem>
<listitem>
<para>SDL Communications Riscom/8 Serial Board.</para>
</listitem>
<listitem>
<para>SDL Communications RISCom/N2 and N2pci sync serial
cards.</para>
</listitem>
<listitem>
<para>Digiboard Sync/570i high-speed sync serial card.</para>
</listitem>
<listitem>
<para>Decision-Computer Intl. &ldquo;Eight-Serial&rdquo; 8 port
serial cards using shared IRQ.</para>
</listitem>
<listitem>
<para>Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum,
Gravis UltraSound, Gravis UltraSound MAX and Roland MPU-401 sound
cards.</para>
</listitem>
<listitem>
<para>Matrox Meteor video frame grabber.</para>
</listitem>
<listitem>
<para>Creative Labs Video spigot frame grabber.</para>
</listitem>
<listitem>
<para>Omnimedia Talisman frame grabber.</para>
</listitem>
<listitem>
<para>Brooktree BT848 chip based frame grabbers.</para>
</listitem>
<listitem>
<para>X-10 power controllers.</para>
</listitem>
<listitem>
<para>PC joystick and speaker.</para>
</listitem>
@ -947,7 +947,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<filename>c:\freebsd</filename> &mdash; the <literal>BIN</literal> dist
is only the minimal requirement.</para>
</sect2>
<sect2>
<title>Before installing from QIC/SCSI Tape</title>
@ -974,7 +974,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
installation probe may otherwise fail to find it.</para>
</note>
</sect2>
<sect2>
<title>Before installing over a network</title>
@ -989,7 +989,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<para>SLIP or PPP</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Parallel port</term>
@ -997,7 +997,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<para>PLIP (laplink cable)</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Ethernet</term>
@ -1062,7 +1062,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<sect3>
<title>Preparing for NFS installation</title>
<para>NFS installation is fairly straight-forward: Simply copy the
FreeBSD distribution files you want onto a server somewhere and then
point the NFS media selection at it.</para>
@ -1094,7 +1094,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<sect3>
<title>Preparing for FTP Installation</title>
<para>FTP installation may be done from any mirror site containing a
reasonably up-to-date version of FreeBSD &rel.current;. A full menu
of reasonable choices from almost anywhere in the world is provided
@ -1134,13 +1134,13 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
</listitem>
</varlistentry>
</variablelist>
<note>
<para>Active and passive modes are not the same as a
&ldquo;proxy&rdquo; connection, where a proxy FTP server is
listening and forwarding FTP requests!</para>
</note>
<para>For a proxy FTP server, you should usually give name of the
server you really want as a part of the username, after an @-sign.
The proxy server then 'fakes' the real server. An example: Say you
@ -1170,14 +1170,14 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<para>Once you have taken note of the appropriate preinstallation steps,
you should be able to install FreeBSD without any further
trouble.</para>
<para>Should this not be true, then you may wish to go back and re-read
the relevant preparation section above for the installation media type
you are trying to use, perhaps there is a helpful hint there that you
missed the first time? If you are having hardware trouble, or FreeBSD
refuses to boot at all, read the Hardware Guide provided on the boot
floppy for a list of possible solutions.</para>
<para>The FreeBSD boot floppies contain all the on-line documentation you
should need to be able to navigate through an installation and if it
does not then we would like to know what you found most confusing. Send
@ -1186,10 +1186,10 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
painful &ldquo;step-by-step&rdquo; guides are no longer necessary. It
may take us a little while to reach that objective, but that is the
objective!</para>
<para>Meanwhile, you may also find the following &ldquo;typical
installation sequence&rdquo; to be helpful:</para>
<orderedlist>
<listitem>
<para>Boot the <filename>kern.flp</filename> floppy and, when asked,
@ -1243,7 +1243,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<para>Many FreeBSD users wish to install FreeBSD on PCs inhabited by
MS-DOS. Here are some commonly asked questions about installing FreeBSD
on such systems.</para>
<para><emphasis>Help! I have no space! Do I need to delete everything
first?</emphasis></para>
@ -1252,7 +1252,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
find the FIPS utility, provided in the <filename>tools</filename>
directory on the FreeBSD CDROM or on the various FreeBSD ftp sites, to
be quite useful.</para>
<para>FIPS allows you to split an existing MS-DOS partition into two
pieces, preserving the original partition and allowing you to install
onto the second free piece. You first defragment your MS-DOS partition,
@ -1262,24 +1262,24 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
See the <emphasis>Distributions</emphasis> menu for an estimation of how
much free space you will need for the kind of installation you
want.</para>
<para><emphasis>Can I use compressed MS-DOS filesystems from
FreeBSD?</emphasis></para>
<para>No. If you are using a utility such as Stacker(tm) or
DoubleSpace(tm), FreeBSD will only be able to use whatever portion of
the filesystem you leave uncompressed. The rest of the filesystem will
show up as one large file (the stacked/dblspaced file!). <emphasis>Do
not remove that file!</emphasis> You will probably regret it
greatly!</para>
<para>It is probably better to create another uncompressed MS-DOS primary
partition and use this for communications between MS-DOS and
FreeBSD.</para>
<para><emphasis>Can I mount my MS-DOS extended
partitions?</emphasis></para>
<para>Yes. DOS extended partitions are mapped in at the end of the other
&ldquo;slices&rdquo; in FreeBSD, e.g. your <devicename>D:</devicename>
drive might be <filename>/dev/da0s5</filename>, your
@ -1289,7 +1289,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting>
<filename>da</filename> appropriately. You otherwise mount extended
partitions exactly like you would mount any other DOS drive,
e.g.:</para>
<screen>&prompt.root; <userinput>mount -t msdos /dev/da0s5 /dos_d</userinput></screen>
</sect1>
</chapter>

130
en_US.ISO_8859-1/books/handbook/internals/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/internals/chapter.sgml,v 1.13 1999/09/06 06:52:58 peter Exp $
-->
<chapter id="internals">
@ -12,11 +12,11 @@
<para><emphasis>Contributed by &a.phk;. v1.1, April
26th.</emphasis></para>
<para>Booting FreeBSD is essentially a three step process: load the
kernel, determine the root filesystem and initialize user-land things.
This leads to some interesting possibilities shown below.</para>
<sect2>
<title>Loading a kernel</title>
@ -36,7 +36,7 @@
<para>Biosboot can load a kernel from a FreeBSD filesystem.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Dosboot</term>
@ -53,7 +53,7 @@
for its case.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Netboot</term>
@ -64,7 +64,7 @@
</varlistentry>
</variablelist>
</sect2>
<sect2>
<title>Determine the root filesystem</title>
@ -95,7 +95,7 @@
&ldquo;UNIXisms&rdquo;.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>MFS</term>
@ -106,7 +106,7 @@
function.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>CD9660</term>
@ -114,7 +114,7 @@
<para>This is for using a CD-ROM as root filesystem.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>NFS</term>
@ -125,7 +125,7 @@
</varlistentry>
</variablelist>
</sect2>
<sect2>
<title>Initialize user-land things</title>
@ -187,7 +187,7 @@
disk...</para>
</listitem>
</varlistentry>
<varlistentry>
<term>B &mdash; Using NFS</term>
@ -200,7 +200,7 @@
control the NFS server...</para>
</listitem>
</varlistentry>
<varlistentry>
<term>C &mdash; Start an X-server</term>
@ -222,7 +222,7 @@
ago...</para>
</listitem>
</varlistentry>
<varlistentry>
<term>E &mdash; Acts as a firewall/web-server/what do I
know...</term>
@ -239,25 +239,25 @@
<sect1 id="memoryuse">
<title>PC Memory Utilization</title>
<para><emphasis>Contributed by &a.joerg;. 16 Apr
1995.</emphasis></para>
<para><emphasis>A short description of how FreeBSD uses memory on the i386
platform</emphasis></para>
<para>The boot sector will be loaded at <literal>0:0x7c00</literal>, and
relocates itself immediately to <literal>0x7c0:0</literal>. (This is
nothing magic, just an adjustment for the <literal>%cs</literal>
selector, done by an <literal>ljmp</literal>.)</para>
<para>It then loads the first 15 sectors at <literal>0x10000</literal>
(segment <makevar>BOOTSEG</makevar> in the biosboot Makefile), and sets
up the stack to work below <literal>0x1fff0</literal>. After this, it
jumps to the entry of boot2 within that code. I.e., it jumps over
itself and the (dummy) partition table, and it is going to adjust the
%cs selector&mdash;we are still in 16-bit mode there.</para>
<para>boot2 asks for the boot file, and examines the
<filename>a.out</filename> header. It masks the file entry point
(usually <literal>0xf0100000</literal>) by
@ -265,7 +265,7 @@
usual load point is 1 MB (<literal>0x00100000</literal>). During load,
the boot code toggles back and forth between real and protected mode, to
use the BIOS in real mode.</para>
<para>The boot code itself uses segment selectors <literal>0x18</literal>
and <literal>0x20</literal> for <literal>%cs</literal> and
<literal>%ds/%es</literal> in protected mode, and
@ -273,16 +273,16 @@
finally started with <literal>%cs</literal> <literal>0x08</literal> and
<literal>%ds/%es/%ss</literal> <literal>0x10</literal>, which refer to
dummy descriptors covering the entire address space.</para>
<para>The kernel will be started at its load point. Since it has been
linked for another (high) address, it will have to execute PIC until the
page table and page directory stuff is setup properly, at which point
paging will be enabled and the kernel will finally run at the address
for which it was linked.</para>
<para><emphasis>Contributed by &a.dg;. 16 Apr
1995.</emphasis></para>
<para>The physical pages immediately following the kernel BSS contain
proc0's page directory, page tables, and upages. Some time later when
the VM system is initialized, the physical memory between
@ -297,43 +297,43 @@
<para><emphasis>Copyright &copy; 1995,1997 &a.uhclem;, All Rights
Reserved. 10 December 1996. Last Update 8 October
1997.</emphasis></para>
<para>Direct Memory Access (DMA) is a method of allowing data to be moved
from one location to another in a computer without intervention from the
central processor (CPU).</para>
<para>The way that the DMA function is implemented varies between computer
architectures, so this discussion will limit itself to the
implementation and workings of the DMA subsystem on the IBM Personal
Computer (PC), the IBM PC/AT and all of its successors and
clones.</para>
<para>The PC DMA subsystem is based on the Intel 8237 DMA controller. The
8237 contains four DMA channels that can be programmed independently and
any one of the channels may be active at any moment. These channels are
numbered 0, 1, 2 and 3. Starting with the PC/AT, IBM added a second
8237 chip, and numbered those channels 4, 5, 6 and 7.</para>
<para>The original DMA controller (0, 1, 2 and 3) moves one byte in each
transfer. The second DMA controller (4, 5, 6, and 7) moves 16-bits from
two adjacent memory locations in each transfer, with the first byte
always coming from an even-numbered address. The two controllers are
identical components and the difference in transfer size is caused by
the way the second controller is wired into the system.</para>
<para>The 8237 has two electrical signals for each channel, named DRQ and
-DACK. There are additional signals with the names HRQ (Hold Request),
HLDA (Hold Acknowledge), -EOP (End of Process), and the bus control
signals -MEMR (Memory Read), -MEMW (Memory Write), -IOR (I/O Read), and
-IOW (I/O Write).</para>
<para>The 8237 DMA is known as a &ldquo;fly-by&rdquo; DMA controller.
This means that the data being moved from one location to another does
not pass through the DMA chip and is not stored in the DMA chip.
Subsequently, the DMA can only transfer data between an I/O port and a
memory address, but not between two I/O ports or two memory
locations.</para>
<note>
<para>The 8237 does allow two channels to be connected together to allow
memory-to-memory DMA operations in a non-&ldquo;fly-by&rdquo; mode,
@ -341,11 +341,11 @@
it is faster to move data between memory locations using the
CPU.</para>
</note>
<para>In the PC architecture, each DMA channel is normally activated only
when the hardware that uses a given DMA channel requests a transfer by
asserting the DRQ line for that channel.</para>
<sect2>
<title>A Sample DMA transfer</title>
@ -514,7 +514,7 @@
32 bit address space, without the use of bounce buffers.</para>
</note>
</sect2>
<sect2>
<title>DMA Operational Modes and Settings</title>
@ -536,7 +536,7 @@
only has a one-byte buffer, so it uses this mode.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Block/Demand</term>
@ -562,7 +562,7 @@
locations used in the transfer were above the 16Meg mark.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Cascade</term>
@ -644,7 +644,7 @@
other high-performance peripheral controllers.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Autoinitialize</term>
@ -669,7 +669,7 @@
</varlistentry>
</variablelist>
</sect2>
<sect2>
<title>Programming the DMA</title>
@ -701,7 +701,7 @@
system, which describes where the DMA and Page Register ports are
located. A complete port map table is located below.</para>
</sect2>
<sect2>
<title>DMA Port Map</title>
@ -817,9 +817,9 @@
</tbody>
</tgroup>
</informaltable>
<para>DMA Command Registers</para>
<informaltable frame="none">
<tgroup cols="3">
<tbody>
@ -927,9 +927,9 @@
<sect3>
<title>0xc0&ndash;0xdf DMA Controller #2 (Channels 4, 5, 6 and
7)</title>
<para>DMA Address and Count Registers</para>
<informaltable frame="none">
<tgroup cols="3">
<tbody>
@ -1031,9 +1031,9 @@
</tbody>
</tgroup>
</informaltable>
<para>DMA Command Registers</para>
<informaltable frame="none">
<tgroup cols="3">
<tbody>
@ -1141,7 +1141,7 @@
<sect3>
<title>0x80&ndash;0x9f DMA Page Registers</title>
<informaltable frame="none">
<tgroup cols="3">
<tbody>
@ -1199,7 +1199,7 @@
<sect3>
<title>0x400&ndash;0x4ff 82374 Enhanced DMA Registers</title>
<para>The Intel 82374 EISA System Component (ESC) was introduced in
early 1996 and includes a DMA controller that provides a superset of
8237 functionality as well as other PC-compatible core peripheral
@ -1216,7 +1216,7 @@
Writing to a traditional 8237 register forces the contents of some
of the 82374 enhanced registers to zero to provide backward software
compatibility.</para>
<informaltable frame="none">
<tgroup cols="3">
<tbody>
@ -1624,7 +1624,7 @@
Except for the wired state, the page is typically placed in a doubly
link list queue representing the state that it is in. Wired pages
are not placed on any queue.</para>
<para>FreeBSD implements a more involved paging queue for cached and
free pages in order to implement page coloring. Each of these states
involves multiple queues arranged according to the size of the
@ -1632,12 +1632,12 @@
FreeBSD attempts to obtain one that is reasonably well aligned from
the point of view of the L1 and L2 caches relative to the VM object
the page is being allocated for.</para>
<para>Additionally, a page may be held with a reference count or locked
with a busy count. The VM system also implements an &ldquo;ultimate
locked&rdquo; state for a page using the PG_BUSY bit in the page's
flags.</para>
<para>In general terms, each of the paging queues operates in a LRU
fashion. A page is typically placed in a wired or active state
initially. When wired, the page is usually associated with a page
@ -1649,14 +1649,14 @@
the number of pages in the free queue, but a certain minimum number of
truly free pages must be maintained in order to accommodate page
allocation at interrupt time.</para>
<para>If a process attempts to access a page that does not exist in its
page table but does exist in one of the paging queues ( such as the
inactive or cache queues), a relatively inexpensive page reactivation
fault occurs which causes the page to be reactivated. If the page
does not exist in system memory at all, the process must block while
the page is brought in from disk.</para>
<para>FreeBSD dynamically tunes its paging queues and attempts to
maintain reasonable ratios of pages in the various queues as well as
attempts to maintain a reasonable breakdown of clean vs dirty pages.
@ -1682,14 +1682,14 @@
file-backed storage. Since the filesystem uses the same VM objects to
manage in-core data relating to files, the result is a unified buffer
cache.</para>
<para>VM objects can be <emphasis>shadowed</emphasis>. That is, they
can be stacked on top of each other. For example, you might have a
swap-backed VM object stacked on top of a file-backed VM object in
order to implement a MAP_PRIVATE mmap()ing. This stacking is also
used to implement various sharing properties, including,
copy-on-write, for forked address spaces.</para>
<para>It should be noted that a <literal>vm_page_t</literal> can only be
associated with one VM object at a time. The VM object shadowing
implements the perceived sharing of the same page across multiple
@ -1707,7 +1707,7 @@
its backing s tore. Additionally, filesystems need to be able to map
portions of a file or file metadata into KVM in order to operate on
it.</para>
<para>The entities used to manage this are known as filesystem buffers,
<literal>struct buf</literal>'s, and also known as
<literal>bp</literal>'s. When a filesystem needs to operate on a
@ -1719,7 +1719,7 @@
duration of the I/O. Filesystem buffers also have their own notion of
being busy, which is useful to filesystem driver code which would
rather operate on filesystem buffers instead of hard VM pages.</para>
<para>FreeBSD reserves a limited amount of KVM to hold mappings from
struct bufs, but it should be made clear that this KVM is used solely
to hold mappings and does not limit the ability to cache data.
@ -1739,7 +1739,7 @@
fly and are usually considered throwaway. Special page tables such as
those managing KVM are typically permanently preallocated. These page
tables are not throwaway.</para>
<para>FreeBSD associates portions of vm_objects with address ranges in
virtual memory through <literal>vm_map_t</literal> and
<literal>vm_entry_t</literal> structures. Page tables are directly
@ -1763,14 +1763,14 @@
<para>FreeBSD uses KVM to hold various kernel structures. The single
largest entity held in KVM is the filesystem buffer cache. That is,
mappings relating to <literal>struct buf</literal> entities.</para>
<para>Unlike Linux, FreeBSD does NOT map all of physical memory into
KVM. This means that FreeBSD can handle memory configurations up to
4G on 32 bit platforms. In fact, if the mmu were capable of it,
FreeBSD could theoretically handle memory configurations up to 8TB on
a 32 bit platform. However, since most 32 bit platforms are only
capable of mapping 4GB of ram, this is a moot point.</para>
<para>KVM is managed through several mechanisms. The main mechanism
used to manage KVM is the <emphasis>zone allocator</emphasis>. The
zone allocator takes a chunk of KVM and splits it up into
@ -1790,7 +1790,7 @@
<filename>/usr/src/sys/i386/conf/<replaceable>CONFIG_FILE</replaceable></filename>.
A description of all available kernel configuration options can be
found in <filename>/usr/src/sys/i386/conf/LINT</filename>.</para>
<para>In a large system configuration you may wish to increase
<literal>maxusers</literal>. Values typically range from 10 to 128.
Note that raising <literal>maxusers</literal> too high can cause the
@ -1798,11 +1798,11 @@
It is better to leave maxusers at some reasonable number and add other
options, such as <literal>NMBCLUSTERS</literal>, to increase specific
resources.</para>
<para>If your system is going to use the network heavily, you may want
to increase <literal>NMBCLUSTERS</literal>. Typical values range from
1024 to 4096.</para>
<para>The <literal>NBUF</literal> parameter is also traditionally used
to scale the system. This parameter determines the amount of KVA the
system can use to map filesystem buffers for I/O. Note that this
@ -1823,16 +1823,16 @@
<programlisting>makeoptions DEBUG="-g"
makeoptions COPTFLAGS="-O2 -pipe"</programlisting>
<para>Sysctl provides a way to tune kernel parameters at run-time. You
typically do not need to mess with any of the sysctl variables,
especially the VM related ones.</para>
<para>Run time VM and system tuning is relatively straightforward.
First, use softupdates on your UFS/FFS filesystems whenever possible.
<filename>/usr/src/contrib/sys/softupdates/README</filename> contains
instructions (and restrictions) on how to configure it up.</para>
<para>Second, configure sufficient swap. You should have a swap
partition configured on each physical disk, up to four, even on your
&ldquo;work&rdquo; disks. You should have at least 2x the swap space
@ -1843,7 +1843,7 @@ makeoptions COPTFLAGS="-O2 -pipe"</programlisting>
able to accommodate a crash dump, your first swap partition must be at
least as large as main memory and <filename>/var/crash</filename> must
have sufficient free space to hold the dump.</para>
<para>NFS-based swap is perfectly acceptable on -4.x or later systems,
but you must be aware that the NFS server will take the brunt of the
paging load.</para>

44
en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml,v 1.18 1999/09/14 03:13:50 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/introduction/chapter.sgml,v 1.19 1999/09/22 12:15:45 jkh Exp $
-->
<chapter id="introduction">
@ -27,7 +27,7 @@
architecture. FreeBSD provides you with many advanced features
previously available only on much more expensive systems.
These features include:</para>
<itemizedlist>
<listitem>
<para><emphasis>Preemptive multitasking</emphasis> with
@ -139,7 +139,7 @@
the commercial giants struggle to field PC operating systems with such
features, performance and reliability, FreeBSD can offer them
<emphasis>now</emphasis>!</para>
<para>The applications to which FreeBSD can be put are truly limited only
by your own imagination. From software development to factory
automation, inventory control to azimuth correction of remote satellite
@ -149,7 +149,7 @@
applications developed by research centers and universities around the
world, often available at little to no cost. Commercial applications are
also available and appearing in greater numbers every day.</para>
<para>Because the source code for FreeBSD itself is generally available,
the system can also be customized to an almost unheard of degree for
special applications or projects, and in ways not generally possible
@ -188,7 +188,7 @@
<para>And more...</para>
</listitem>
</itemizedlist>
<para>With FreeBSD, you can easily start out small with an
inexpensive 386 class PC and upgrade all the way up to a
quad-processor Xeon with RAID storage as your enterprise
@ -271,7 +271,7 @@
snapshot. Those plans came to a rude halt when Bill Jolitz suddenly
decided to withdraw his sanction from the project and without any clear
indication of what would be done instead.</para>
<para>It did not take us long to decide that the goal remained worthwhile,
even without Bill's support, and so we adopted the name
&ldquo;FreeBSD&rdquo;, coined by David Greenman. Our initial objectives
@ -285,14 +285,14 @@
Walnut Creek CDROM's almost unprecedented degree of faith in what was,
at the time, a completely unknown project, it is quite unlikely that
FreeBSD would have gotten as far, as fast, as it has today.</para>
<para>The first CDROM (and general net-wide) distribution was FreeBSD 1.0,
released in December of 1993. This was based on the 4.3BSD-Lite
(&ldquo;Net/2&rdquo;) tape from U.C. Berkeley, with many components also
provided by 386BSD and the Free Software Foundation. It was a fairly
reasonable success for a first offering, and we followed it with the
highly successful FreeBSD 1.1 release in May of 1994.</para>
<para>Around this time, some rather unexpected storm clouds formed on the
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
@ -306,7 +306,7 @@
1994 to stop shipping its own Net/2 based product. Under the terms of
that agreement, the project was allowed one last release before the
deadline, that release being FreeBSD 1.1.5.1.</para>
<para>FreeBSD then set about the arduous task of literally re-inventing
itself from a completely new and rather incomplete set of 4.4BSD-Lite
bits. The &ldquo;Lite&rdquo; releases were light in part because
@ -319,7 +319,7 @@
rough around the edges, the release was a significant success and was
followed by the more robust and easier to install FreeBSD 2.0.5 release
in June of 1995.</para>
<para>We released FreeBSD 2.1.5 in August of 1996, and it appeared to be
popular enough among the ISP and commercial communities that another
release along the 2.1-stable branch was merited. This was FreeBSD
@ -327,7 +327,7 @@
development on 2.1-stable. Now in maintenance mode, only security
enhancements and other critical bug fixes will be done on this branch
(RELENG_2_1_0).</para>
<para>FreeBSD 2.2 was branched from the development mainline
(&ldquo;-current&rdquo;) in November 1996 as the RELENG_2_2 branch, and
the first full release (2.2.1) was released in April, 1997. Further
@ -362,7 +362,7 @@
provides the widest possible benefit. This is, I believe, one of the
most fundamental goals of Free Software and one that we enthusiastically
support.</para>
<para>That code in our source tree which falls under the GNU General Public
License (GPL) or Library General Public License (LGPL) comes with slightly
more strings attached, though at least on the side of enforced access
@ -389,10 +389,10 @@
to distribute their own patches or work-in-progress sources. The
&a.announce; is also available to those wishing to make other FreeBSD
users aware of major areas of work.</para>
<para>Useful things to know about the FreeBSD project and its development
process, whether working independently or in close cooperation:</para>
<variablelist>
<varlistentry>
<term>The CVS repository<anchor
@ -434,7 +434,7 @@
<varlistentry>
<term>The FreeBSD core team<anchor id="development-core"></term>
<listitem>
<para>The <link linkend="staff-core">FreeBSD core team</link> would
be equivalent to the board of directors if the FreeBSD Project
@ -468,7 +468,7 @@
<varlistentry>
<term>Outside contributors</term>
<listitem>
<para>Last, but definitely not least, the largest group of
developers are the users themselves who provide feedback and
@ -515,7 +515,7 @@
Alpha based computer systems. It is based primarily on software from U.C.
Berkeley's CSRG group, with some enhancements from NetBSD, OpenBSD, 386BSD,
and the Free Software Foundation.</para>
<para>Since our release of FreeBSD 2.0 in late 94, the performance,
feature set, and stability of FreeBSD has improved dramatically. The
largest change is a revamped virtual memory system with a merged VM/file
@ -526,12 +526,12 @@
an improved SCSI subsystem, ISDN support, support for ATM, FDDI, Fast
and Gigabit Ethernet (1000Mbit) adapters, improved support for the latest
Adaptec controllers and many hundreds of bug fixes.</para>
<para>We have also taken the comments and suggestions of many of our users
to heart and have attempted to provide what we hope is a more sane and
easily understood installation process. Your feedback on this
(constantly evolving) process is especially welcome!</para>
<para>In addition to the base distributions, FreeBSD offers a new ported
software collection with hundreds of commonly sought-after programs. By
mid-September 1999, there were more than 2600 ports! The list of
@ -550,7 +550,7 @@
pre-compiled &ldquo;package&rdquo; which can be installed with a simple
command (pkg_add) by those who do not wish to compile their own ports
from source.</para>
<para>A number of additional documents which you may find very helpful in
the process of installing and using FreeBSD may now also be found in the
<filename>/usr/share/doc</filename> directory on any machine running
@ -569,7 +569,7 @@
<varlistentry>
<term>The FreeBSD FAQ</term>
<listitem>
<para><ulink
url="file:/usr/share/doc/FAQ/FAQ.html">file:/usr/share/doc/FAQ/FAQ.html</ulink></para>
@ -589,7 +589,7 @@
outside the U.S.) exportable European distribution of DES for our
non-U.S. users also exists and is described in the <ulink
url="../FAQ/FAQ.html">FreeBSD FAQ</ulink>.</para>
<para>If password security for FreeBSD is all you need, and you have no
requirement for copying encrypted passwords from different hosts (Suns,
DEC machines, etc) into FreeBSD password entries, then FreeBSD's MD5

136
en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.20 1999/09/06 06:52:59 peter Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.21 1999/11/01 19:16:06 nik Exp $
-->
<chapter id="kernelconfig">
@ -68,7 +68,7 @@
while everything outside the <filename>i386</filename> directory is
common to all platforms which FreeBSD could potentially be ported
to.</para>
<note>
<para>If there is <emphasis>not</emphasis> a
<filename>/usr/src/sys</filename> directory on your system, then the
@ -90,7 +90,7 @@
maintaining multiple FreeBSD machines with different hardware, it is a
good idea to name it after your machine's hostname. We will call it
<filename>MYKERNEL</filename> for the purpose of this example.</para>
<note>
<para>You must execute these and all of the following commands under the
root account or you will get <errortype>permission denied</errortype>
@ -107,7 +107,7 @@
comment lines at the top to reflect your configuration or the changes
you have made to differentiate it from
<filename>GENERIC</filename>.</para>
<para>If you have build a kernel under SunOS or some other BSD operating
system, much of this file will be very familiar to you. If you are
coming from some other operating system such as DOS, on the other hand,
@ -169,14 +169,14 @@
directory as <filename>GENERIC</filename>. If you are in doubt as to
the purpose or necessity of a line, check first in
<filename>LINT</filename>.</para>
<para>The kernel is currently being moved to a better organization of the
option handling. Traditionally, each option in the config file was
simply converted into a <option>-D</option> switch for the
<acronym>CFLAGS</acronym> line of the kernel Makefile. Naturally, this
caused a creeping optionism, with nobody really knowing which option has
been referenced in what files.</para>
<para>In the new scheme, every <literal>#ifdef</literal> that is intended
to be dependent upon an option gets this option out of an
<filename>opt_<replaceable>foo</replaceable>.h</filename> declaration
@ -226,7 +226,7 @@
<replaceable>alpha</replaceable>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>cpu
"<replaceable>cpu_type</replaceable>"</literal></term>
@ -277,7 +277,7 @@
<replaceable>cpu_type</replaceable>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>ident
<replaceable>machine_name</replaceable></literal></term>
@ -302,7 +302,7 @@
<literal>vax</literal>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>maxusers
<replaceable>number</replaceable></literal></term>
@ -344,7 +344,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>config
<replaceable>kernel_name</replaceable></literal> root on
@ -393,7 +393,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options "COMPAT_43"</literal></term>
@ -402,7 +402,7 @@
will act strangely if you comment this out.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options UCONSOLE</literal></term>
@ -414,7 +414,7 @@
as any console messages sent by the kernel.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options SYSVSHM</literal></term>
@ -427,7 +427,7 @@
definitely want to include this.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options SYSVSEM</literal></term>
@ -436,7 +436,7 @@
only adds a few hundred bytes to the kernel.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options SYSVMSG</literal></term>
@ -476,7 +476,7 @@
from the hard disk.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options NFS</literal></term>
@ -486,7 +486,7 @@
out.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options MSDOSFS</literal></term>
@ -501,7 +501,7 @@
all).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options "CD9660"</literal></term>
@ -512,7 +512,7 @@
data CD). Audio CD's do not need this filesystem.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options PROCFS</literal></term>
@ -523,7 +523,7 @@
what processes are running.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options MFS</literal></term>
@ -557,7 +557,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options "EXT2FS"</literal></term>
@ -568,7 +568,7 @@
the two systems.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options QUOTA</literal></term>
@ -600,7 +600,7 @@
run FreeBSD at this time.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller eisa0</literal></term>
<listitem>
@ -609,7 +609,7 @@
EISA bus.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller pci0</literal></term>
@ -619,7 +619,7 @@
ISA bus.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller fdc0</literal></term>
@ -638,7 +638,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller wdc0</literal></term>
@ -652,7 +652,7 @@
all six lines, for example).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device acd0<anchor
id="kernelconfig-atapi"></literal></term>
@ -665,7 +665,7 @@
line <literal>options ATAPI</literal>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device npx0 at isa? port "IO_NPX" irq 13
vector npxintr</literal></term>
@ -677,7 +677,7 @@
optional.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device wt0 at isa? port 0x300 bio irq 5 drq 1 vector
wtintr</literal></term>
@ -686,7 +686,7 @@
<para>Wangtek and Archive QIC-02/QIC-36 tape drive support</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Proprietary CD-ROM support</term>
@ -848,7 +848,7 @@
</variablelist>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options SCSI_DELAY=15000</literal></term>
@ -861,7 +861,7 @@
your SCSI devices, you will have to raise it back up.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller scbus0</literal></term>
@ -871,7 +871,7 @@
and the following three lines, out.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device da0</literal></term>
@ -879,7 +879,7 @@
<para>Support for SCSI hard drives.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device sa0</literal></term>
@ -887,7 +887,7 @@
<para>Support for SCSI tape drives.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device cd0</literal></term>
@ -895,7 +895,7 @@
<para>Support for SCSI CD-ROM drives.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device ch0</literal></term>
@ -904,7 +904,7 @@
as tape libraries.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device pass0</literal></term>
@ -1056,7 +1056,7 @@
</variablelist>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device mse0 at isa? port 0x23c tty irq 5 vector
ms</literal></term>
@ -1073,7 +1073,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device psm0 at isa? port "IO_KBD" conflicts tty irq
12 vector psmintr</literal></term>
@ -1122,7 +1122,7 @@
used.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>controller ppbus0</literal></term>
@ -1130,7 +1130,7 @@
<para>Provides support for the parallel port bus.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device ppc0 at isa? port? tty irq 7</literal></term>
@ -1138,7 +1138,7 @@
<para>ISA-bus parallel port interface.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device lpt0 at ppbus?</literal></term>
@ -1173,7 +1173,7 @@
your PC) so this is essentially mandatory.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Ethernet cards</term>
@ -1362,7 +1362,7 @@
back at you through this pseudo-device. Mandatory.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device ether</literal></term>
@ -1372,7 +1372,7 @@
code.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device sl
<replaceable>number</replaceable></literal></term>
@ -1389,7 +1389,7 @@
linkend="slips">server</link>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device ppp
<replaceable>number</replaceable></literal></term>
@ -1407,7 +1407,7 @@
simultaneous PPP connections to support.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device tun
<replaceable>number</replaceable></literal></term>
@ -1422,7 +1422,7 @@
for more information.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device bpfilter
<replaceable>number</replaceable></literal></term>
@ -1463,7 +1463,7 @@
<literal>pcm</literal>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device pas0 at isa? port 0x388 irq 10 drq 6 vector
pasintr</literal></term>
@ -1472,7 +1472,7 @@
<para>ProAudioSpectrum digital audio and MIDI.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device sb0 at isa? port 0x220 irq 7 conflicts drq 1
vector sbintr</literal></term>
@ -1488,7 +1488,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device sbxvi0 at isa? drq 5</literal></term>
@ -1502,7 +1502,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device sbmidi0 at isa? port 0x330</literal></term>
@ -1512,7 +1512,7 @@
compile.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device gus0 at isa? port 0x220 irq 10 drq 1 vector
gusintr</literal></term>
@ -1521,7 +1521,7 @@
<para>Gravis Ultrasound.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device mss0 at isa? port 0x530 irq 10 drq 1 vector
adintr</literal></term>
@ -1530,7 +1530,7 @@
<para>Microsoft Sound System.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device opl0 at isa? port 0x388
conflicts</literal></term>
@ -1542,7 +1542,7 @@
(in the ports collection).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device mpu0 at isa? port 0x330 irq 6 drq
0</literal></term>
@ -1551,7 +1551,7 @@
<para>Roland MPU-401 stand-alone card.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device uart0 at isa? port 0x330 irq 5 vector
"m6850intr"</literal></term>
@ -1560,7 +1560,7 @@
<para>Stand-alone 6850 UART for MIDI.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>device pca0 at isa? port "IO_TIMER1"
tty</literal><anchor id="kernelconfig-pcaudio"></term>
@ -1619,7 +1619,7 @@
</note>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device log</literal></term>
@ -1628,7 +1628,7 @@
messages. Mandatory.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device pty
<replaceable>number</replaceable></literal><anchor
@ -1646,7 +1646,7 @@
accordingly, up to a maximum of 256.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device snp
<replaceable>number</replaceable></literal></term>
@ -1660,7 +1660,7 @@
of simultaneous snoop sessions. Optional.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device vn</literal></term>
@ -1672,7 +1672,7 @@
Optional.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device ccd
<replaceable>number</replaceable></literal></term>
@ -1707,7 +1707,7 @@
<para>PC joystick device.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>pseudo-device speaker</literal></term>
@ -1745,7 +1745,7 @@
of them, so when you add support for a new device, it pays to make sure
that the appropriate entries are in this directory, and if not, add
them. Here is a simple example:</para>
<para>Suppose you add the IDE CD-ROM support to the kernel. The line to
add is:</para>
@ -1764,7 +1764,7 @@ device acd0</programlisting>
<para>When this script finishes, you will find that there are now
<filename>acd0c</filename> and <filename>racd0c</filename> entries in
<filename>/dev</filename> so you know that it executed correctly.</para>
<para>For sound cards, the command:
<screen>&prompt.root; <userinput>sh MAKEDEV snd0</userinput></screen>
@ -1833,7 +1833,7 @@ device acd0</programlisting>
<varlistentry>
<term>Kernel will not boot<anchor id="kernelconfig-noboot"></term>
<listitem>
<para>If your new kernel does not boot, or fails to recognize your
devices, do not panic! Fortunately, BSD has an excellent mechanism
@ -1881,7 +1881,7 @@ device acd0</programlisting>
<varlistentry>
<term>Kernel works, but <command>ps</command> does not work any
more!</term>
<listitem>
<para>If you have installed a different version of the kernel from
the one that the system utilities have been built with, for

40
en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kerneldebug/chapter.sgml,v 1.18 1999/09/06 06:52:59 peter Exp $
-->
<chapter id="kerneldebug">
@ -55,7 +55,7 @@
some 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 memory will be wasted.</para>
<para>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 one in
order to get your system up and running again, boot it only into single
@ -186,7 +186,7 @@
<varlistentry>
<term>line 20:</term>
<listitem>
<para>This is the location of function <function>trap()</function>
in the stack trace.</para>
@ -195,7 +195,7 @@
<varlistentry>
<term>line 36:</term>
<listitem>
<para>Force usage of a new stack frame; this is no longer necessary
now. The stack frames are supposed to point to the right
@ -210,7 +210,7 @@
<varlistentry>
<term>line 52:</term>
<listitem>
<para>The pointer looks suspicious, but happens to be a valid
address.</para>
@ -219,7 +219,7 @@
<varlistentry>
<term>line 56:</term>
<listitem>
<para>However, it obviously points to garbage, so we have found our
error! (For those unfamiliar with that particular piece of code:
@ -251,7 +251,7 @@
<para>What do you do if a kernel dumped core but you did not expect it,
and it is therefore not compiled using <command>config -g</command>? Not
everything is lost here. Do not panic!</para>
<para>Of course, you still need to enable crash dumps. See above on the
options you have to specify in order to do this.</para>
@ -271,14 +271,14 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols</
faulting one but some debugging symbols. You should at least verify the
old and new sizes with the &man.size.1; command. If there is a
mismatch, you probably need to give up here.</para>
<para>Go and examine the dump as described above. The debugging symbols
might be incomplete for some places, as can be seen in the stack trace
in the example above where some functions are displayed without line
numbers and argument lists. If you need more debugging symbols, remove
the appropriate object files and repeat the <command>kgdb</command>
session until you know enough.</para>
<para>All this is not guaranteed to work, but it will do it fine in most
cases.</para>
</sect1>
@ -290,14 +290,14 @@ makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols</
high level of user interface, there are some things it cannot do. The
most important ones being breakpointing and single-stepping kernel
code.</para>
<para>If you need to do low-level debugging on your kernel, there is an
on-line debugger available called DDB. It allows to setting
breakpoints, single-stepping kernel functions, examining and changing
kernel variables, etc. However, it cannot access kernel source files,
and only has access to the global and static symbols, not to the full
debug information like <command>kgdb</command>.</para>
<para>To configure your kernel to include DDB, add the option line
<programlisting>
@ -318,7 +318,7 @@ options DDB</programlisting>
<option>-d</option> right at the boot prompt. The kernel will start up
in debug mode and enter DDB prior to any device probing. Hence you can
even debug the device probe/attach functions.</para>
<para>The second scenario is a hot-key on the keyboard, usually
Ctrl-Alt-ESC. For syscons, this can be remapped; some of the
distributed maps do this, so watch out. There is an option available
@ -327,11 +327,11 @@ options DDB</programlisting>
in the kernel config file). It is not the default since there are a lot
of crappy serial adapters around that gratuitously generate a BREAK
condition, for example when pulling the cable.</para>
<para>The third way is that any panic condition will branch to DDB if the
kernel is configured to use it. For this reason, it is not wise to
configure a kernel with DDB for a machine running unattended.</para>
<para>The DDB commands roughly resemble some <command>gdb</command>
commands. The first thing you probably need to do is to set a
breakpoint:</para>
@ -344,7 +344,7 @@ options DDB</programlisting>
<literal>a-f</literal> need to be preceded with <literal>0x</literal>
(this is optional for other numbers). Simple expressions are allowed,
for example: <literal>function-name + 0x103</literal>.</para>
<para>To continue the operation of an interrupted kernel, simply
type:</para>
@ -419,11 +419,11 @@ options DDB</programlisting>
specifies the size of the data to be written, the first following
expression is the address to write to and the remainder is interpreted
as data to write to successive memory locations.</para>
<para>If you need to know the current registers, use:</para>
<screen><userinput>show reg</userinput></screen>
<para>Alternatively, you can display a single register value by e.g.
<screen><userinput>p $eax</userinput></screen>
@ -468,7 +468,7 @@ options DDB</programlisting>
<para>is the final way out of disaster and almost the same as hitting the
Big Red Button.</para>
<para>If you need a short command summary, simply type:</para>
<screen><userinput>help</userinput></screen>
@ -493,7 +493,7 @@ options DDB</programlisting>
with all the symbols in it, and the other one is the target machine that
simply runs a similar copy of the very same kernel (but stripped of the
debugging information).</para>
<para>You should configure the kernel in question with <command>config
-g</command>, include <option>DDB</option> into the configuration, and
compile it as usual. This gives a large blurb of a binary, due to the
@ -573,7 +573,7 @@ text_addr = 0xf5109020? (y or n) <userinput>y</userinput>
<sect1>
<title>Debugging a Console Driver</title>
<para>Since you need a console driver to run DDB on, things are more
complicated if the console driver itself is failing. You might remember
the use of a serial console (either with modified boot blocks, or by

30
en_US.ISO_8859-1/books/handbook/kernelopts/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelopts/chapter.sgml,v 1.11 1999/09/06 06:53:00 peter Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/kernelopts/chapter.sgml,v 1.12 1999/11/06 19:32:39 eivind Exp $
-->
<chapter id="kernelopts">
@ -41,39 +41,39 @@
#ifndef THIS_OPTION
#define THIS_OPTION (some_default_value)
#endif /* THIS_OPTION */</programlisting>
<para>This way, an administrator mentioning another value for the option
in his config file will take the default out of effect, and replace it
with his new value. Clearly, the new value will be substituted into the
source code during the preprocessor run, so it must be a valid C
expression in whatever context the default value would have been
used.</para>
<para>It is also possible to create value-less options that simply enable
or disable a particular piece of code by embracing it in</para>
<programlisting>
#ifdef THAT_OPTION
[your code here]
#endif</programlisting>
<para>Simply mentioning <literal>THAT_OPTION</literal> in the config file
(with or without any value) will then turn on the corresponding piece of
code.</para>
<para>People familiar with the C language will immediately recognize that
everything could be counted as a &ldquo;config option&rdquo; where there
is at least a single <literal>#ifdef</literal> referencing it...
However, it's unlikely that many people would put</para>
<programlisting>
options notyet,notdef</programlisting>
<para>in their config file, and then wonder why the kernel compilation
falls over. <!-- smiley -->:-)</para>
<para>Clearly, using arbitrary names for the options makes it very hard to
track their usage throughout the kernel source tree. That is the
rationale behind the <emphasis>new-style</emphasis> option scheme, where
@ -83,7 +83,7 @@ options notyet,notdef</programlisting>
the usual Makefile dependencies could be applied, and
<command>make</command> can determine what needs to be recompiled once
an option has been changed.</para>
<para>The old-style option mechanism still has one advantage for local
options or maybe experimental options that have a short anticipated
lifetime: since it is easy to add a new <literal>#ifdef</literal> to the
@ -104,7 +104,7 @@ options notyet,notdef</programlisting>
e. g. <filename>sys/i386/conf/options.i386</filename>), and select an
<filename>opt_<replaceable>foo</replaceable>.h</filename> file where
your new option would best go into.</para>
<para>If there is already something that comes close to the purpose of the
new option, pick this. For example, options modifying the overall
behaviour of the SCSI subsystem can go into
@ -113,7 +113,7 @@ options notyet,notdef</programlisting>
implies its value will go into the corresponding file
<filename>opt_foo.h</filename>. This can be overridden on the
right-hand side of a rule by specifying another filename.</para>
<para>If there is no
<filename>opt_<replaceable>foo</replaceable>.h</filename> already
available for the intended new option, invent a new name. Make it
@ -122,12 +122,12 @@ options notyet,notdef</programlisting>
file. &man.config.8; will automagically pick up the change, and create
that file next time it is run. Most options should go in a header file
by themselves..</para>
<para>Packing too many options into a single
<filename>opt_<replaceable>foo</replaceable>.h</filename> will cause too
many kernel files to be rebuilt when one of the options has been changed
in the config file.</para>
<para>Finally, find out which kernel files depend on the new option.
Unless you have just invented your option, and it does not exist
anywhere yet, <screen>&prompt.user; <userinput>find /usr/src/sys -name
@ -139,7 +139,7 @@ options notyet,notdef</programlisting>
the regular include files, if the defaults are of the form
<programlisting> #ifndef NEW_OPTION #define NEW_OPTION (something)
#endif</programlisting> in the regular header.</para>
<para>Adding an option that overrides something in a system header file
(i.e., a file sitting in <filename>/usr/include/sys/</filename>) is
almost always a mistake.

28
en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/l10n/chapter.sgml,v 1.14 1999/09/06 06:53:00 peter Exp $
-->
<chapter id="l10n">
@ -30,7 +30,7 @@ options "SC_MOUSE_CHAR=0x03"</programlisting>
to move character codes used for mouse cursor off KOI8-R
pseudographics range.</para>
</step>
<step>
<para>Russian console entry in
<filename>/etc/rc.conf</filename> should looks like:</para>
@ -59,7 +59,7 @@ font8x8=cp866-8x8</programlisting>
<literal>Shift+CapsLock</literal>. CapsLock LED will indicate RUS
mode, not CapsLock mode.</para>
</step>
<step>
<para>For each <literal>ttyv?</literal> entry in
<filename>/etc/ttys</filename> change terminal type from
@ -83,7 +83,7 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure</programlisting>
<para><envar>LANG</envar> for POSIX &man.setlocale.3; family
functions;</para>
</listitem>
<listitem>
<para><envar>MM_CHARSET</envar> for applications MIME character
set.</para>
@ -97,17 +97,17 @@ ttyv0 "/usr/libexec/getty Pc" cons25r on secure</programlisting>
<sect3 id="russian-class">
<title>Login Class Method</title>
<para>First of all check your <filename>/etc/login.conf</filename>
have <literal>russian</literal> login class, this entry may looks
like:</para>
<programlisting>
russian:Russian Users Accounts:\
:charset=KOI8-R:\
:lang=ru_RU.KOI8-R:\
:tc=default:</programlisting>
<sect4>
<title>How to do it with &man.vipw.8;</title>
@ -118,7 +118,7 @@ russian:Russian Users Accounts:\
<programlisting>
user:password:1111:11:russian:0:0:User Name:/home/user:/bin/csh</programlisting>
</sect4>
<sect4>
<title>How to do it with &man.adduser.8;</title>
@ -153,7 +153,7 @@ defaultclass = russian</programlisting>
</listitem>
</itemizedlist>
</sect4>
<sect4>
<title>How to do it with &man.pw.8;</title>
@ -166,12 +166,12 @@ defaultclass = russian</programlisting>
<sect3>
<title>Shell Startup Files Method</title>
<para>If you don't want to use <link linkend="russian-class">login
class method</link> for some reasons, just set this <link
linkend="russian-env">two environment variables</link> in the
following shell startup files:</para>
<itemizedlist>
<listitem>
<para><filename>/etc/profile</filename>:</para>
@ -189,7 +189,7 @@ setenv LANG ru_RU.KOI8-R
setenv MM_CHARSET KOI8-R</programlisting>
</listitem>
</itemizedlist>
<para>Alternatively you can add this instructions to</para>
<itemizedlist>
@ -259,7 +259,7 @@ lp|Russian local line printer:\
less than 3.3 first).</para>
</note>
</step>
<step>
<para>Go to <filename>/usr/ports/russian/X.language</filename>
directory and say
@ -281,7 +281,7 @@ FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/100dpi"</programlisting>
<para>If you use high resolution video mode, swap 75 dpi and 100 dpi
lines.</para>
</step>
<step>
<para>To activate Russian keyboard add

42
en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml,v 1.22 1999/09/15 18:34:26 obrien Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml,v 1.24 1999/09/15 19:29:38 obrien Exp $
-->
<chapter id="linuxemu">
@ -19,16 +19,16 @@
&rel.current;-RELEASE is vastly more capable and runs all these as well
as Oracle8, WordPerfect, StarOffice, Acrobat, Quake, Abuse, IDL, and
netrek for Linux and a whole host of other programs.</para>
<para>There are some Linux-specific operating system features that are not
supported on FreeBSD. Linux binaries will not work on FreeBSD if they
overly use the Linux <filename>/proc</filename> filesystem (which is
different from the optional FreeBSD <filename>/proc</filename> filesystem)
or i386-specific calls, such as enabling virtual 8086 mode.</para>
<para>Depending on which version of FreeBSD you are running, how you get
Linux mode up will vary somewhat:</para>
<sect2>
<title>Installing Linux Mode in 3.0-RELEASE and later</title>
@ -210,7 +210,7 @@ linux</programlisting>
<sect3>
<title>Installing using the linux_base port</title>
<para>Most Linux applications use shared libraries, so you are still
not done until you install the shared libraries. It is possible to
do this by hand, however, it is vastly simpler to just grab the
@ -231,7 +231,7 @@ linux</programlisting>
<sect3>
<title>Installing libraries manually</title>
<para>If you do not have the &ldquo;ports&rdquo; distribution, you can
install the libraries by hand instead. You will need the Linux
shared libraries that the program depends on and the runtime linker.
@ -262,7 +262,7 @@ linux</programlisting>
<sect3>
<title>How to install additional shared libraries</title>
<para>What if you install the <filename>linux_base</filename> port and
your application still complains about missing shared libraries? How
do you know which shared libraries Linux binaries need, and where to
@ -281,7 +281,7 @@ linux</programlisting>
libXt.so.3 (DLL Jump 3.1) =&gt; /usr/X11/lib/libXt.so.3.1.0
libX11.so.3 (DLL Jump 3.1) =&gt; /usr/X11/lib/libX11.so.3.1.0
libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
<para>You would need to get all the files from the last column, and
put them under <filename>/compat/linux</filename>, with the names in
the first column as symbolic links pointing to them. This means you
@ -321,7 +321,7 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
<screen>/compat/linux/lib/libc.so.4.6.29
/compat/linux/lib/libc.so.4 -&gt; libc.so.4.6.29</screen>
</note>
<note>
<para>The symbolic link mechanism is <emphasis>only</emphasis>
needed for Linux binaries. The FreeBSD runtime linker takes care
@ -333,7 +333,7 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
<sect3>
<title>Configuring the <filename>ld.so</filename> &mdash; for FreeBSD
2.2-RELEASE and later</title>
<para>This section applies only to FreeBSD 2.2-RELEASE and later.
Those running 2.1-STABLE should skip this section.</para>
@ -350,7 +350,7 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
extra files you need from various ftp sites. Information on where
to look for the various files is appended below. For now, let us
assume you know where to get the files.</para>
<para>Retrieve the following files (all from the same ftp site to
avoid any version mismatches), and install them under
<filename>/compat/linux</filename> (i.e.
@ -402,7 +402,7 @@ libc.so.4 (DLL Jump 4.5pl26) =&gt; /lib/libc.so.4.6.29</screen>
the names of all the shared libraries and should be rerun to
recreate this file whenever you install additional shared
libraries.</para>
<para>On 2.1-STABLE do not install
<filename>/compat/linux/etc/ld.so.cache</filename> or run
<command>ldconfig</command>; in 2.1-STABLE the syscalls are
@ -471,10 +471,10 @@ Abort</screen>
<title>Configuring the host name resolver</title>
<para>If DNS does not work or you get the messages
<screen>resolv+: "bind" is an invalid keyword resolv+:
"hosts" is an invalid keyword</screen>
then you need to configure a
<filename>/compat/linux/etc/host.conf</filename> file containing:
@ -526,7 +526,7 @@ multi on</programlisting>
<listitem>
<para>sunsite.unc.edu:/pub/Linux/distributions</para>
</listitem>
<listitem>
<para>tsx-11.mit.edu:/pub/linux/distributions</para>
</listitem>
@ -538,11 +538,11 @@ multi on</programlisting>
<listitem>
<para>ftp.luth.se:/pub/linux/distributions</para>
</listitem>
<listitem>
<para>ftp.demon.co.uk:/pub/unix/linux</para>
</listitem>
<listitem>
<para>src.doc.ic.ac.uk:/packages/linux/distributions</para>
</listitem>
@ -666,15 +666,15 @@ multi on</programlisting>
<listitem>
<para><filename>slakware/a2/ldso.tgz</filename></para>
</listitem>
<listitem>
<para><filename>slakware/a2/shlibs.tgz</filename></para>
</listitem>
<listitem>
<para><filename>slakware/x6/oldlibs.tgz</filename></para>
</listitem>
<listitem>
<para><filename>slakware/x9/xf_lib.tgz</filename></para>
</listitem>
@ -705,7 +705,7 @@ multi on</programlisting>
DOS the cost of upgrading to the Linux version at the time this was
written, March 1996, was &#36;45.00. It can be ordered directly from
Wolfram at (217) 398-6500 and paid for by credit card.</para>
<sect2>
<title>Unpacking the Mathematica distribution</title>

8
en_US.ISO_8859-1/books/handbook/mail/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mail/chapter.sgml,v 1.14 1999/09/06 06:53:01 peter Exp $
-->
<chapter id="mail">
@ -25,7 +25,7 @@
<para>These are the major programs involved in an E-Mail exchange. A
&ldquo;mailhost&rdquo; is a server that is responsible for delivering
and receiving all email for your host, and possibly your network.</para>
<sect2>
<title>User program</title>
@ -94,7 +94,7 @@
This handbook section has a complete reference on the <link
linkend="ports">Ports</link> system.</para>
</step>
<step>
<para>Modify <filename>/etc/inetd.conf</filename> to load the POP
server.</para>
@ -123,7 +123,7 @@
your own domain <hostid role="domainname">smallminingco.com
</hostid></para>
</listitem>
<listitem>
<para>Get mail delivered to the current DNS name for your host. Ie:
<hostid role="fqdn">dorm6.ahouse.school.edu </hostid></para>

114
en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml,v 1.42 1999/10/03 18:54:42 jdp Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/mirrors/chapter.sgml,v 1.43 1999/10/12 20:32:32 tom Exp $
-->
<chapter id="mirrors">
@ -98,7 +98,7 @@
<varlistentry>
<term><anchor id="mirrors-au">Australia</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@au.FreeBSD.org</email> for this domain.</para>
@ -129,7 +129,7 @@
<varlistentry>
<term><anchor id="mirrors-br">Brazil</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@br.FreeBSD.org</email> for this domain.</para>
@ -175,7 +175,7 @@
<varlistentry>
<term><anchor id="mirrors-ca">Canada</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@ca.FreeBSD.org</email> for this domain.</para>
@ -211,7 +211,7 @@
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@cz.FreeBSD.org</email> for this domain.</para>
<itemizedlist>
<listitem>
<para><ulink
@ -227,7 +227,7 @@
<varlistentry>
<term><anchor id="mirrors-dk">Denmark</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@dk.FreeBSD.org</email> for this domain.</para>
@ -243,7 +243,7 @@
<varlistentry>
<term><anchor id="mirrors-ee">Estonia</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@ee.FreeBSD.org</email> for this domain.</para>
@ -259,7 +259,7 @@
<varlistentry>
<term><anchor id="mirrors-fi">Finland</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@fi.FreeBSD.org</email> for this domain.</para>
@ -275,7 +275,7 @@
<varlistentry>
<term><anchor id="mirrors-fr">France</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@fr.FreeBSD.org</email> for this domain.</para>
@ -305,7 +305,7 @@
<varlistentry>
<term><anchor id="mirrors-de">Germany</term>
<listitem>
<para>In case of problems, please contact the mirrors admins
<email>de-bsd-hubs@de.freebsd.org </email> for this domain.</para>
@ -351,7 +351,7 @@
<varlistentry>
<term><anchor id="mirrors-hk">Hong Kong</term>
<listitem>
<itemizedlist>
@ -365,7 +365,7 @@
<varlistentry>
<term><anchor id="mirrors-ie">Ireland</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@ie.FreeBSD.org</email> for this domain.</para>
@ -381,7 +381,7 @@
<varlistentry>
<term><anchor id="mirrors-il">Israel</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@il.FreeBSD.org</email> for this domain.</para>
@ -402,7 +402,7 @@
<varlistentry>
<term><anchor id="mirrors-jp">Japan</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@jp.FreeBSD.org</email> for this domain.</para>
@ -443,7 +443,7 @@
<varlistentry>
<term><anchor id="mirrors-kr">Korea</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@kr.FreeBSD.org</email> for this domain.</para>
@ -481,7 +481,7 @@
<varlistentry>
<term><anchor id="mirrors-nl">Netherlands</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@nl.FreeBSD.org</email> for this domain.</para>
@ -497,7 +497,7 @@
<varlistentry>
<term><anchor id="mirrors-nz">New Zealand</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@nz.FreeBSD.org</email> for this domain.</para>
@ -512,7 +512,7 @@
<varlistentry>
<term><anchor id="mirrors-pl">Poland</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@pl.FreeBSD.org</email> for this domain.</para>
@ -528,7 +528,7 @@
<varlistentry>
<term><anchor id="mirrors-pt">Portugal</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@pt.FreeBSD.org</email> for this domain.</para>
@ -549,7 +549,7 @@
<varlistentry>
<term><anchor id="mirrors-ru">Russia</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@ru.FreeBSD.org</email> for this domain.</para>
@ -595,7 +595,7 @@
<varlistentry>
<term><anchor id="mirrors-za">South Africa</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@za.FreeBSD.org</email> for this domain.</para>
@ -621,7 +621,7 @@
<varlistentry>
<term><anchor id="mirrors-sk">Slovak Republic</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@sk.FreeBSD.org</email> for this domain.</para>
@ -635,7 +635,7 @@
</varlistentry>
<varlistentry><term><anchor id="mirrors-si">Slovenia</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@si.FreeBSD.org</email> for this domain.</para>
@ -651,7 +651,7 @@
<varlistentry>
<term><anchor id="mirrors-es">Spain</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@es.FreeBSD.org</email> for this domain.</para>
@ -666,7 +666,7 @@
<varlistentry>
<term><anchor id="mirrors-se">Sweden</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@se.FreeBSD.org</email> for this domain.</para>
@ -723,7 +723,7 @@
<varlistentry>
<term><anchor id="mirrors-th">Thailand</term>
<listitem>
<itemizedlist>
<listitem>
@ -736,7 +736,7 @@
<varlistentry>
<term><anchor id="mirrors-ua">Ukraine</term>
<listitem>
<itemizedlist>
<listitem>
@ -749,7 +749,7 @@
<varlistentry>
<term><anchor id="mirrors-uk">UK</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@uk.FreeBSD.org</email> for this domain.</para>
@ -780,7 +780,7 @@
<varlistentry>
<term><anchor id="mirrors-us">USA</term>
<listitem>
<para>In case of problems, please contact the hostmaster
<email>hostmaster@FreeBSD.org</email> for this domain.</para>
@ -829,7 +829,7 @@
<variablelist>
<varlistentry>
<term>South Africa</term>
<listitem>
<para>Hostmaster <email>hostmaster@internat.FreeBSD.org</email> for
this domain.</para>
@ -850,7 +850,7 @@
<varlistentry>
<term>Brazil</term>
<listitem>
<para>Hostmaster <email>hostmaster@br.FreeBSD.org</email> for this
domain.</para>
@ -866,7 +866,7 @@
<varlistentry>
<term>Finland</term>
<listitem>
<itemizedlist>
<listitem>
@ -885,7 +885,7 @@
<para><link linkend="ctm">CTM</link>/FreeBSD is available via anonymous
FTP from the following mirror sites. If you choose to obtain CTM via
anonymous FTP, please try to use a site near you.</para>
<para>In case of problems, please contact &a.phk;.</para>
<variablelist>
@ -904,7 +904,7 @@
<varlistentry>
<term>Germany, Trier</term>
<listitem>
<itemizedlist>
<listitem>
@ -917,7 +917,7 @@
<varlistentry>
<term>South Africa, backup server for old deltas</term>
<listitem>
<itemizedlist>
<listitem>
@ -930,7 +930,7 @@
<varlistentry>
<term>Taiwan/R.O.C, Chiayi</term>
<listitem>
<itemizedlist>
<listitem>
@ -982,7 +982,7 @@
<varlistentry>
<term>Australia</term>
<listitem>
<itemizedlist>
<listitem>
@ -995,7 +995,7 @@
<varlistentry>
<term>Brazil</term>
<listitem>
<itemizedlist>
<listitem>
@ -1057,7 +1057,7 @@
<varlistentry>
<term>Denmark</term>
<listitem>
<itemizedlist>
<listitem>
@ -1083,7 +1083,7 @@
<varlistentry>
<term>Finland</term>
<listitem>
<itemizedlist>
<listitem>
@ -1114,7 +1114,7 @@
<varlistentry>
<term>Germany</term>
<listitem>
<itemizedlist>
<listitem>
@ -1137,7 +1137,7 @@
<varlistentry>
<term>Iceland</term>
<listitem>
<itemizedlist>
<listitem>
@ -1150,7 +1150,7 @@
<varlistentry>
<term>Japan</term>
<listitem>
<itemizedlist>
@ -1184,7 +1184,7 @@
<varlistentry>
<term>Korea</term>
<listitem>
<itemizedlist>
@ -1198,7 +1198,7 @@
<varlistentry>
<term>Netherlands</term>
<listitem>
<itemizedlist>
<listitem>
@ -1216,7 +1216,7 @@
<varlistentry>
<term>Norway</term>
<listitem>
<itemizedlist>
<listitem>
@ -1229,7 +1229,7 @@
<varlistentry>
<term>Poland</term>
<listitem>
<itemizedlist>
<listitem>
@ -1242,7 +1242,7 @@
<varlistentry>
<term>Russia</term>
<listitem>
<itemizedlist>
<listitem>
@ -1260,7 +1260,7 @@
<varlistentry>
<term>Slovak Republic</term>
<listitem>
<itemizedlist>
<listitem>
@ -1291,7 +1291,7 @@
<varlistentry>
<term>South Africa</term>
<listitem>
<itemizedlist>
<listitem>
@ -1322,7 +1322,7 @@
<varlistentry>
<term>Sweden</term>
<listitem>
<itemizedlist>
<listitem>
@ -1335,7 +1335,7 @@
<varlistentry>
<term>Taiwan</term>
<listitem>
<itemizedlist>
<listitem>
@ -1359,7 +1359,7 @@
<varlistentry>
<term>Ukraine</term>
<listitem>
<itemizedlist>
@ -1373,7 +1373,7 @@
<varlistentry>
<term>United Kingdom</term>
<listitem>
<itemizedlist>
<listitem>
@ -1391,7 +1391,7 @@
<varlistentry>
<term>USA</term>
<listitem>
<itemizedlist>
<listitem>
@ -1453,7 +1453,7 @@
</listitem>
</varlistentry>
</variablelist>
<para>The following <application>CVSup</application> site is especially
designed for <link linkend="ctm">CTM</link> users. Unlike the other
CVSup mirrors, it is kept up-to-date by <application>CTM</application>.
@ -1508,7 +1508,7 @@
<variablelist>
<varlistentry>
<term>Sweden</term>
<listitem>
<para>The path to the files are:
<filename>/afs/stacken.kth.se/ftp/pub/FreeBSD/</filename></para>

4
en_US.ISO_8859-1/books/handbook/pgpkeys/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/pgpkeys/chapter.sgml,v 1.18 1999/10/26 04:55:42 cpiazza Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/pgpkeys/chapter.sgml,v 1.19 1999/10/26 05:18:01 cpiazza Exp $
-->
<chapter id="pgpkeys">
@ -317,7 +317,7 @@ Sb97WRLEYDi686osaGfsuKNA87Rm+q5F+jxeUV4w4szoqp60gGvCbD0KCB2hWraP
=QoiM
-----END PGP PUBLIC KEY BLOCK-----</programlisting>
</sect2>
<sect2>
<title>&a.jdp;</title>

38
en_US.ISO_8859-1/books/handbook/policies/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/policies/chapter.sgml,v 1.11 1999/09/06 06:53:02 peter Exp $
-->
<chapter id="policies">
@ -20,27 +20,27 @@
<para>If a particular portion of the FreeBSD distribution is being
maintained by a person or group of persons, they can communicate this
fact to the world by adding a
<programlisting>
MAINTAINER= email-addresses</programlisting>
line to the <filename>Makefile</filename>s covering this portion of the
source tree.</para>
<para>The semantics of this are as follows:</para>
<para>The maintainer owns and is responsible for that code. This means
that he is responsible for fixing bugs and answer problem reports
pertaining to that piece of the code, and in the case of contributed
software, for tracking new versions, as appropriate.</para>
<para>Changes to directories which have a maintainer defined shall be sent
to the maintainer for review before being committed. Only if the
maintainer does not respond for an unacceptable period of time, to
several emails, will it be acceptable to commit changes without review
by the maintainer. However, it is suggested that you try and have the
changes reviewed by someone else if at all possible.</para>
<para>It is of course not acceptable to add a person or group as
maintainer unless they agree to assume this duty. On the other hand it
doesn't have to be a committer and it can easily be a group of
@ -58,11 +58,11 @@ MAINTAINER= email-addresses</programlisting>
actively being maintained outside the FreeBSD project. For historical
reasons, we call this <emphasis>contributed</emphasis> software. Some
examples are perl, gcc and patch.</para>
<para>Over the last couple of years, various methods have been used in
dealing with this type of software and all have some number of
advantages and drawbacks. No clear winner has emerged.</para>
<para>Since this is the case, after some debate one of these methods has
been selected as the &ldquo;official&rdquo; method and will be required
for future imports of software of this kind. Furthermore, it is
@ -72,7 +72,7 @@ MAINTAINER= email-addresses</programlisting>
&ldquo;official&rdquo; versions of the source by everyone (even without
cvs access). This will make it significantly easier to return changes
to the primary developers of the contributed software.</para>
<para>Ultimately, however, it comes down to the people actually doing the
work. If using this model is particularly unsuited to the package being
dealt with, exceptions to these rules may be granted only with the
@ -93,28 +93,28 @@ MAINTAINER= email-addresses</programlisting>
<para>The <application>Tcl</application> embedded programming
language will be used as example of how this model works:</para>
<para><filename>src/contrib/tcl</filename> contains the source as
distributed by the maintainers of this package. Parts that are entirely
not applicable for FreeBSD can be removed. In the case of Tcl, the
<filename>mac</filename>, <filename>win</filename> and
<filename>compat</filename> subdirectories were eliminated before the
import</para>
<para><filename>src/lib/libtcl</filename> contains only a "bmake style"
<filename>Makefile</filename> that uses the standard
<filename>bsd.lib.mk</filename> makefile rules to produce the library
and install the documentation.</para>
<para><filename>src/usr.bin/tclsh</filename> contains only a bmake style
<filename>Makefile</filename> which will produce and install the
<command>tclsh</command> program and its associated man-pages using the
standard <filename>bsd.prog.mk</filename> rules.</para>
<para><filename>src/tools/tools/tcl_bmake</filename> contains a couple of
shell-scripts that can be of help when the tcl software needs updating.
These are not part of the built or installed software.</para>
<para>The important thing here is that the
<filename>src/contrib/tcl</filename> directory is created according to
the rules: It is supposed to contain the sources as distributed (on a
@ -133,7 +133,7 @@ MAINTAINER= email-addresses</programlisting>
be patched into the FreeBSD checked out version and "committed", as this
destroys the vendor branch coherency and makes importing future versions
rather difficult as there will be conflicts.</para>
<para>Since many packages contain files that are meant for compatibility
with other architectures and environments that FreeBSD, it is
permissible to remove parts of the distribution tree that are of no
@ -148,7 +148,7 @@ MAINTAINER= email-addresses</programlisting>
check in such utilities (as necessary) in the
<filename>src/tools</filename> directory along with the port itself so
that it is available to future maintainers.</para>
<para>In the <filename>src/contrib/tcl</filename> level directory, a file
called <filename>FREEBSD-upgrade</filename> should be added and it
should states things like:</para>
@ -177,7 +177,7 @@ MAINTAINER= email-addresses</programlisting>
with the contributed source. Rather you should <command>cvs add
FREEBSD-upgrade ; cvs ci</command> after the initial import. Example
wording from <filename>src/contrib/cpio</filename> is below:</para>
<programlisting>
This directory contains virgin sources of the original distribution files
on a "vendor" branch. Do not, under any circumstances, attempt to upgrade
@ -316,12 +316,12 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
<para><emphasis>Contributed by &a.asami;, &a.peter;, and &a.obrien; 9
December 1996.</emphasis></para>
<para>If you are adding shared library support to a port or other piece of
software that doesn't have one, the version numbers should follow these
rules. Generally, the resulting numbers will have nothing to do with
the release version of the software.</para>
<para>The three principles of shared library building are:</para>
<itemizedlist>

136
en_US.ISO_8859-1/books/handbook/ppp-and-slip/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.16 1999/09/06 06:53:03 peter Exp $
-->
<chapter id="ppp-and-slip">
@ -36,13 +36,13 @@
ppp program can be run as and when desired. No PPP interface needs to
be compiled into the kernel, as the program can use the generic tunnel
device to get data into and out of the kernel.</para>
<para>From here on out, user ppp will be referred to simply as ppp unless
a distinction needs to be made between it and any other PPP
client/server software such as <command>pppd</command>. Unless
otherwise stated, all commands in this section should be executed as
root.</para>
<para>There are a large number of enhancements in version 2 of ppp. You
can discover what version you have by running ppp with no arguments and
typing <command>show version</command> at the prompt. It is a simple
@ -66,13 +66,13 @@
<listitem>
<para>Your ISPs phone number(s).</para>
</listitem>
<listitem>
<para>Your login name and password. This can be either a regular
unix style login/password pair, or a PPP PAP or CHAP
login/password pair.</para>
</listitem>
<listitem>
<para>The IP addresses of one or more nameservers. Normally, you
will be given two IP numbers. You <emphasis>must</emphasis> have
@ -100,7 +100,7 @@
<para>This IP number is referred to as <literal>HISADDR</literal>
by ppp.</para>
</listitem>
<listitem>
<para>Your ISP's netmask. If your ISP hasn't given you this
information, you can safely use a netmask of <hostid
@ -232,7 +232,7 @@ tun0: flags=8010&lt;POINTOPOINT,MULTICAST> mtu 1500</screen>
<sect3>
<title>Edit the <filename>/etc/host.conf</filename> file</title>
<para>This file should contain the following two lines (in this
order):</para>
@ -247,7 +247,7 @@ bind</programlisting>
<sect3>
<title>Edit the <filename>/etc/hosts</filename>(5) file</title>
<para>This file should contain the IP addresses and names of machines
on your network. At a bare minimum it should contain entries for
the machine which will be running ppp. Assuming that your machine
@ -258,7 +258,7 @@ bind</programlisting>
<programlisting>
127.0.0.1 localhost
10.0.0.1 foo.bar.com foo</programlisting>
<para>The first line defines the alias <hostid>localhost</hostid> as a
synonym for the current machine. Regardless of your own IP address,
the IP address for this line should always be <hostid
@ -274,7 +274,7 @@ bind</programlisting>
<sect3>
<title>Edit the <filename>/etc/resolv.conf</filename> file</title>
<para><filename>/etc/resolv.conf</filename> tells the resolver how to
behave. If you are running your own DNS, you may leave this file
empty. Normally, you will need to enter the following
@ -294,7 +294,7 @@ domain <replaceable>bar.com</replaceable></programlisting>
and is probably unnecessary. Refer to the
<filename>resolv.conf</filename> manual page for details of other
possible entries in this file.</para>
<para>If you are running PPP version 2 or greater, the <command>enable
dns</command> command will tell PPP to request that your ISP
confirms the nameserver values. If your ISP supplies different
@ -322,17 +322,17 @@ domain <replaceable>bar.com</replaceable></programlisting>
<sect3 id="userppp-staticIP">
<title>PPP and Static IP addresses</title>
<para>You will need to create a configuration file called
<filename>/etc/ppp/ppp.conf</filename>. It should look similar to
the example below.</para>
<note>
<para>Lines that end in a <literal>:</literal> start in the first
column, all other lines should be indented as shown using spaces
or tabs.</para>
</note>
<programlisting>
1 default:
2 set device /dev/cuaa0
@ -498,21 +498,21 @@ protocol: ppp</screen>
</listitem>
</varlistentry>
</variablelist>
<para>It is not necessary to add an entry to
<filename>ppp.linkup</filename> when you have a static IP address as
your routing table entries are already correct before you connect.
You may however wish to create an entry to invoke programs after
connection. This is explained later with the sendmail
example.</para>
<para>Example configuration files can be found in the
<filename>/etc/ppp</filename> directory.</para>
</sect3>
<sect3 id="userppp-dynamicIP">
<title>PPP and Dynamic IP addresses</title>
<para>If your service provider does not assign static IP numbers,
<command>ppp</command> can be configured to negotiate the local and
remote addresses. This is done by &ldquo;guessing&rdquo; an IP
@ -549,7 +549,7 @@ protocol: ppp</screen>
</listitem>
</varlistentry>
</variablelist>
<para>If you are running version 1.x of PPP, you will also need to
create an entry in <filename>/etc/ppp/ppp.linkup</filename>.
<filename>ppp.linkup</filename> is used after a connection has been
@ -599,7 +599,7 @@ protocol: ppp</screen>
</listitem>
</varlistentry>
</variablelist>
<para>See the pmdemand entry in the files
<filename>/etc/ppp/ppp.conf.sample</filename> and
<filename>/etc/ppp/ppp.linkup.sample</filename> for a detailed
@ -619,7 +619,7 @@ protocol: ppp</screen>
<para>This section describes setting up <command>ppp</command> in a
server role.</para>
<para>When you configure <command>ppp</command> to receive incoming
calls on a machine connected to a LAN, you must decide if you wish
to forward packets to the LAN. If you do, you should allocate the
@ -661,7 +661,7 @@ gateway=YES</programlisting>
AutoPPP</link> for more information on
<command>mgetty</command>.</para>
</sect4>
<sect4>
<title>PPP permissions</title>
@ -683,7 +683,7 @@ allow users fred mary</programlisting>
<para>If this command is used in the <literal>default</literal>
section, it gives the specified users access to everything.</para>
</sect4>
<sect4>
<title>Setting up a PPP shell for dynamic-IP users</title>
@ -729,7 +729,7 @@ pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialup</programlistin
which prevents <filename>/etc/motd</filename> from being
displayed.</para>
</sect4>
<sect4>
<title>Setting up a PPP shell for static-IP users</title>
@ -751,7 +751,7 @@ pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialup</programlistin
<username>mary</username>'s shell should be
<filename>/etc/ppp/ppp-mary</filename>).</para>
</sect4>
<sect4>
<title>Setting up ppp.conf for dynamic-IP users</title>
@ -782,7 +782,7 @@ ttyd1:
unique IP address from your pool of IP addresses for dynamic
users.</para>
</sect4>
<sect4>
<title>Setting up <filename>ppp.conf</filename> for static-IP
users</title>
@ -820,7 +820,7 @@ sam:
mary:
add 203.14.103.0 netmask 255.255.255.0 HISADDR</programlisting>
</sect4>
<sect4>
<title>More on <command>mgetty</command>, AutoPPP, and MS
extensions</title>
@ -921,7 +921,7 @@ set nbns 203.14.100.5</programlisting>
<sect3 id="userppp-PAPnCHAP">
<title>PAP and CHAP authentication</title>
<para>Some ISPs set their system up so that the authentication part of
your connection is done using either of the PAP or CHAP
authentication mechanisms. If this is the case, your ISP will not
@ -996,7 +996,7 @@ set nbns 203.14.100.5</programlisting>
<sect3>
<title>Changing your <command>ppp</command> configuration on the
fly</title>
<para>It is possible to talk to the <command>ppp</command> program
while it is running in the background, but only if a suitable
diagnostic port has been set up. To do this, add the following line
@ -1004,7 +1004,7 @@ set nbns 203.14.100.5</programlisting>
<programlisting>
set server /var/run/ppp-tun%d DiagnosticPassword 0177</programlisting>
<para>This will tell PPP to listen to the specified unix-domain
socket, asking clients for the specified password before allowing
access. The <literal>%d</literal> in the name is replaced with the
@ -1123,29 +1123,29 @@ sendmail_flags="-bd"</programlisting>
<para>Ensure that the <devicename>tun</devicename> device is built
into your kernel.</para>
</step>
<step>
<para>Ensure that the
<filename>tun<replaceable>X</replaceable></filename> device file
is available in the <filename>/dev</filename> directory.</para>
</step>
<step>
<para>Create an entry in <filename>/etc/ppp/ppp.conf</filename>.
The <filename>pmdemand</filename> example should suffice for most
ISPs.</para>
</step>
<step>
<para>If you have a dynamic IP address, create an entry in
<filename>/etc/ppp/ppp.linkup</filename>.</para>
</step>
<step>
<para>Update your <filename>/etc/rc.conf</filename> (or
<filename>sysconfig</filename>) file.</para>
</step>
<step>
<para>Create a <filename>start_if.tun0</filename> script if you
require demand dialing.</para>
@ -1159,34 +1159,34 @@ sendmail_flags="-bd"</programlisting>
<para>Ensure that the <devicename>tun</devicename> device is built
into your kernel.</para>
</step>
<step>
<para>Ensure that the
<filename>tun<replaceable>X</replaceable></filename> device file
is available in the <filename>/dev</filename> directory.</para>
</step>
<step>
<para>Create an entry in <filename>/etc/passwd</filename> (using the
&man.vipw.8; program).</para>
</step>
<step>
<para>Create a profile in this users home directory that runs
<command>ppp -direct direct-server</command> or similar.</para>
</step>
<step>
<para>Create an entry in <filename>/etc/ppp/ppp.conf</filename>.
The <filename>direct-server</filename> example should
suffice.</para>
</step>
<step>
<para>Create an entry in
<filename>/etc/ppp/ppp.linkup</filename>.</para>
</step>
<step>
<para>Update your <filename>/etc/rc.conf</filename> (or
<filename>sysconfig</filename>) file.</para>
@ -1219,9 +1219,9 @@ sendmail_flags="-bd"</programlisting>
<para>Before you start setting up PPP on your machine make sure that
<command>pppd</command> is located in <filename>/usr/sbin</filename> and
directory <filename>/etc/ppp</filename> exists.</para>
<para><command>pppd</command> can work in two modes:</para>
<orderedlist>
<listitem>
<para>as a &ldquo;client&rdquo;, i.e. you want to connect your machine
@ -1237,10 +1237,10 @@ sendmail_flags="-bd"</programlisting>
<para>In both cases you will need to set up an options file
(<filename>/etc/ppp/options</filename> or <filename>~/.ppprc</filename>
if you have more then one user on your machine that uses PPP).</para>
<para>You also will need some modem/serial software (preferably kermit) so
you can dial and establish connection with remote host.</para>
<sect2>
<title>Working as a PPP client</title>
@ -1272,11 +1272,11 @@ defaultroute # put this if you want that PPP server will be your
enter your user name and password (or whatever is needed to enable
PPP on the remote host)</para>
</step>
<step>
<para>Exit kermit (without hanging up the line).</para>
</step>
<step>
<para>enter:</para>
@ -1654,12 +1654,12 @@ exit 1
<title>Setting up a SLIP Client</title>
<para><emphasis>Contributed by &a.asami; 8 Aug 1995.</emphasis></para>
<para>The following is one way to set up a FreeBSD machine for SLIP on a
static host network. For dynamic hostname assignments (i.e., your
address changes each time you dial up), you probably need to do
something much fancier.</para>
<para>First, determine which serial port your modem is connected to. I
have a symbolic link to <filename>/dev/modem</filename> from
<filename>/dev/cuaa1</filename>, and only use the modem name in my
@ -1681,7 +1681,7 @@ pseudo-device sl 1</programlisting>
in your kernel's config file. It is included in the
<filename>GENERIC</filename> kernel, so this will not be a problem
unless you deleted it.</para>
<sect2>
<title>Things you have to do only once</title>
@ -1707,7 +1707,7 @@ pseudo-device sl 1</programlisting>
<option>bind</option> in your <filename>/etc/host.conf</filename>.
Otherwise, funny things may happen.</para>
</step>
<step>
<para>Edit the file <filename>/etc/rc.conf</filename>. Note that
you should edit the file <filename>/etc/sysconfig</filename>
@ -1757,7 +1757,7 @@ defaultrouter=slip-gateway</programlisting>
</listitem>
</orderedlist>
</step>
<step>
<para>Make a file <filename>/etc/resolv.conf</filename> which
contains:</para>
@ -1821,7 +1821,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
am just too lazy.</para>
</note>
</step>
<step>
<para>Leave the kermit there (you can suspend it by
<command>z</command>) and as root, type:</para>
@ -1835,7 +1835,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
</step>
</procedure>
</sect2>
<sect2>
<title>How to shutdown the connection</title>
@ -1869,12 +1869,12 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
slattach (I have no idea why this can be fatal, but adding this
flag solved the problem for at least one person)</para>
</listitem>
<listitem>
<para>Using <option>s10</option> instead of <option>sl0</option>
(might be hard to see the difference on some fonts).</para>
</listitem>
<listitem>
<para>Try <command>ifconfig sl0</command> to see your interface
status. I get:</para>
@ -1925,7 +1925,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438
not answer all of your questions, and the author cannot be responsible
if you damage your system or lose data due to attempting to follow the
suggestions here.</para>
<para>This guide was originally written for SLIP Server services on a
FreeBSD 1.x system. It has been modified to reflect changes in the
pathnames and the removal of the SLIP interface compression flags in
@ -1933,7 +1933,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438
between FreeBSD versions. If you do encounter mistakes in this
document, please email the author with enough information to help
correct the problem.</para>
<sect2 id="slips-prereqs">
<title>Prerequisites</title>
@ -1981,7 +1981,7 @@ silvia.HIP.Berke localhost.Berkeley UGH 34 47641234 lo0 - 0.438
<sect3>
<title>An Example of a SLIP Server Login</title>
<para>For example, if a SLIP user ID were
<username>Shelmerg</username>, <username>Shelmerg</username>'s entry
in <filename>/etc/master.passwd</filename> would look something like
@ -2107,10 +2107,10 @@ pseudo-device sl 2</programlisting>
<sect3>
<title><filename>slip.hosts</filename> Configuration</title>
<para><filename>/etc/sliphome/slip.hosts</filename> contains lines
which have at least four items, separated by whitespace:</para>
<itemizedlist>
<listitem>
<para>SLIP user's login ID</para>
@ -2129,7 +2129,7 @@ pseudo-device sl 2</programlisting>
<para>Network mask</para>
</listitem>
</itemizedlist>
<para>The local and remote addresses may be host names (resolved to IP
addresses by <filename>/etc/hosts</filename> or by the domain name
service, depending on your specifications in
@ -2147,7 +2147,7 @@ pseudo-device sl 2</programlisting>
Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting>
<para>At the end of the line is one or more of the options.</para>
<itemizedlist>
<listitem>
<para><option>normal</option> &mdash; no header compression</para>
@ -2168,7 +2168,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
your bandwidth)</para>
</listitem>
</itemizedlist>
<para>Note that <command>sliplogin</command> under early releases of
FreeBSD 2 ignored the options that FreeBSD 1.x recognized, so the
options <option>normal</option>, <option>compress</option>,
@ -2208,7 +2208,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
<sect3>
<title><filename>slip.login</filename> Configuration</title>
<para>The typical <filename>/etc/sliphome/slip.login</filename> file
looks like this:</para>
@ -2288,7 +2288,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
<sect3>
<title><filename>slip.logout</filename> Configuration</title>
<para><filename>/etc/sliphome/slip.logout</filename> is not strictly
needed (unless you are implementing &ldquo;proxy ARP&rdquo;), but if
you decide to create it, this is an example of a basic
@ -2351,7 +2351,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
<sect3>
<title>Static Routes</title>
<para>Adding static routes to your nearest default routers can be
troublesome (or impossible, if you do not have authority to do
so...). If you have a multiple-router network in your organization,
@ -2364,7 +2364,7 @@ Shelmerg dc-slip sl-helmerg 0xfffffc00 autocomp</programlisting
<sect3>
<title>Running <command>gated</command></title>
<para>An alternative to the headaches of static routes is to install
<command>gated</command> on your FreeBSD SLIP server and configure
it to use the appropriate routing protocols (RIP/OSPF/BGP/EGP) to
@ -2462,7 +2462,7 @@ import proto rip interface ed {
<para></para>
</listitem>
</varlistentry>
<varlistentry>
<term>Piero Serini</term>

222
en_US.ISO_8859-1/books/handbook/printing/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/printing/chapter.sgml,v 1.21 1999/09/06 06:53:04 peter Exp $
-->
<chapter id="printing">
@ -23,10 +23,10 @@
<sect1 id="printing-intro-spooler">
<title>What the Spooler Does</title>
<para>LPD controls everything about a host's printers. It is responsible
for a number of things:</para>
<itemizedlist>
<listitem>
<para>It controls access to attached printers and printers attached to
@ -155,13 +155,13 @@
accept data to print instead of a serial or parallel interface, see
<link linkend="printing-advanced-network-net-if">Printers With Networked
Data Stream Interaces</link>.</para>
<para>Although this section is called &ldquo;Simple Printer Setup,&rdquo;
it is actually fairly complex. Getting the printer to work with your
computer and the LPD spooler is the hardest part. The advanced options
like header pages and accounting are fairly easy once you get the
printer working.</para>
<sect2 id="printing-hardware">
<title>Hardware Setup</title>
@ -177,7 +177,7 @@
<sect3 id="printing-ports">
<title>Ports and Cables</title>
<para>Nearly all printers you can get for a PC today support one or
both of the following interfaces:</para>
@ -251,7 +251,7 @@
<sect3 id="printing-parallel">
<title>Parallel Ports</title>
<para>To hook up a printer using a parallel interface, connect the
Centronics cable between the printer and the computer. The
instructions that came with the printer, the computer, or both
@ -264,12 +264,12 @@
<sect3 id="printing-serial">
<title>Serial Ports</title>
<para>To hook up a printer using a serial interface, connect the
proper serial cable between the printer and the computer. The
instructions that came with the printer, the computer, or both
should give you complete guidance.</para>
<para>If you are unsure what the &ldquo;proper serial cable&rdquo; is,
you may wish to try one of the following alternatives:</para>
@ -339,7 +339,7 @@
Communications</link> gives some suggestions on how to do
this.</para>
</step>
<step>
<para>Set up LPD for the printer by modifying the file
<filename>/etc/printcap</filename>. Section <link
@ -350,7 +350,7 @@
<sect3 id="printing-kernel">
<title>Kernel Configuration</title>
<para>The operating system kernel is compiled to work with a specific
set of devices. The serial or parallel interface for your printer
is a part of that set. Therefore, it might be necessary to add
@ -365,22 +365,22 @@
<para>Where <replaceable>N</replaceable> is the number of the serial
port, starting from zero. If you see output similar to the
following:</para>
<screen>sio2 at 0x3e8-0x3ef irq 5 on isa
sio2: type 16550A</screen>
<para>then the kernel supports the port.</para>
<para>To find out if the kernel supports a parallel interface,
type:</para>
<screen>&prompt.root; <userinput>dmesg | grep lpt<replaceable>N</replaceable></userinput></screen>
<para>Where <replaceable>N</replaceable> is the number of the parallel
port, starting from zero. If you see output similar to the
following <screen>lpt0 at 0x378-0x37f on isa</screen> then the
kernel supports the port.</para>
<para>You might have to reconfigure your kernel in order for the
operating system to recognize and use the parallel or serial port
you are using for the printer.</para>
@ -436,7 +436,7 @@ sio2: type 16550A</screen>
</step>
</procedure>
</sect4>
<sect4 id="printing-parallel-port-mode">
<title>Setting the Communication Mode for the Parallel Port</title>
@ -535,7 +535,7 @@ device lpt0 at isa? port? tty vector lptintr</programlisting>
your system boots. See &man.lptcontrol.8; for more
information.</para>
</sect4>
<sect4 id="printing-testing">
<title>Checking Printer Communications</title>
@ -722,7 +722,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
<sect3 id="printing-printcap">
<title>Enabling the Spooler: The <filename>/etc/printcap</filename>
File</title>
<para>At this point, your printer should be hooked up, your kernel
configured to communicate with it (if necessary), and you have been
able to send some simple data to the printer. Now, we are ready to
@ -743,7 +743,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
<para>The simple spooler configuration consists of the following
steps:</para>
<procedure>
<step>
<para>Pick a name (and a few convenient aliases) for the printer,
@ -792,7 +792,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
linkend="printing-troubleshooting">Troubleshooting</link>.</para>
</step>
</procedure>
<note>
<para>Language-based printers, such as PostScript printers, cannot
directly print plain text. The simple setup outlined above and
@ -800,7 +800,7 @@ printer:dv=/dev/ttyd2:br#19200:pa=none</programlisting>
installing such a printer you will print only files that the
printer can understand.</para>
</note>
<para>Users often expect that they can print plain text to any of the
printers installed on your system. Programs that interface to LPD
to do their printing usually make the same assumption. If you are
@ -861,7 +861,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:</programlisting>
<literal>S</literal>, <literal>panasonic</literal>, and
<literal>Panasonic KX-P4455 PostScript v51.4</literal>.</para>
</sect4>
<sect4 id="printing-no-header-pages">
<title>Suppressing Header Pages</title>
@ -893,7 +893,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
single TAB. Every line in an entry except the last ends in a
backslash character.</para>
</sect4>
<sect4 id="printing-spooldir">
<title>Making the Spooling Directory</title>
@ -1108,7 +1108,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
:sh:sd=/var/spool/lpd/bamboo:\
:lp=/dev/ttyd5:fs#0x82000c1:xs#0x820:</programlisting>
</sect4>
<sect4 id="printing-textfilter">
<title>Installing the Text Filter</title>
@ -1174,7 +1174,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
:lp=/dev/ttyd5:fs#0x82000e1:xs#0x820:\
:if=/usr/local/libexec/if-simple:</programlisting>
</sect4>
<sect4 id="printing-trying">
<title>Trying It Out</title>
@ -1224,7 +1224,7 @@ $%&amp;'()*+,-./01234567
<para>If the printer did not work, see the next section, <link
linkend="printing-troubleshooting">Troubleshooting</link>.</para>
</sect4>
<sect4 id="printing-troubleshooting">
<title>Troubleshooting</title>
@ -1533,7 +1533,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<para>This section tells you how to use printers you have setup with
FreeBSD. Here is an overview of the user-level commands:</para>
<variablelist>
<varlistentry>
<term>&man.lpr.1;</term>
@ -1545,7 +1545,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<varlistentry>
<term>&man.lpq.1;</term>
<listitem>
<para>Check printer queues</para>
</listitem>
@ -1553,7 +1553,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<varlistentry>
<term>&man.lprm.1;</term>
<listitem>
<para>Remove jobs from a printer's queue</para>
</listitem>
@ -1597,7 +1597,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
<para>To select a specific printer, type:</para>
<screen>&prompt.user; <userinput>lpr -P <replaceable>printer-name</replaceable> <replaceable>filename</replaceable> <replaceable>...</replaceable></userinput></screen>
<para>This example prints a long listing of the current directory to the
printer named <literal>rattan</literal>:</para>
@ -1676,7 +1676,7 @@ kelly: 2nd [job 010rose]
mary: 3rd [job 011rose]
/home/orchid/mary/research/venus/alpha-regio/mapping 78519 bytes</screen>
</sect2>
<sect2 id="printing-lprm">
<title>Removing Jobs</title>
@ -1707,7 +1707,7 @@ mary: 3rd [job 011rose]
you.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>lprm <replaceable>user</replaceable></term>
@ -1717,7 +1717,7 @@ mary: 3rd [job 011rose]
users' jobs; you can remove only your own jobs.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>lprm</term>
@ -1771,7 +1771,7 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-format">
<title>Formatting and Conversion Options</title>
<para>The following &man.lpr.1; options control formatting of the
files in the job. Use these options if the job does not contain
plain text or if you want plain text formatted through the
@ -1796,7 +1796,7 @@ cfA013rose dequeued
linkend="printing-advanced-convfilters">Conversion
Filters</link> gives details.</para>
</note>
<variablelist>
<varlistentry>
<term><option>-c</option></term>
@ -1919,7 +1919,7 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-job-handling">
<title>Job Handling Options</title>
<para>The following options to &man.lpr.1; tell LPD to handle the job
specially:</para>
@ -1999,7 +1999,7 @@ cfA013rose dequeued
<sect3 id="printing-lpr-options-misc">
<title>Header Page Options</title>
<para>These options to &man.lpr.1; adjust the text that normally
appears on a job's header page. If header pages are suppressed for
the destination printer, these options have no effect. See section
@ -2059,11 +2059,11 @@ cfA013rose dequeued
<listitem>
<para>Start and stop the printers</para>
</listitem>
<listitem>
<para>Enable and disable their queues</para>
</listitem>
<listitem>
<para>Rearrange the order of the jobs in each queue.</para>
</listitem>
@ -2102,7 +2102,7 @@ cfA013rose dequeued
still submit jobs if the queue's enabled.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>clean
<replaceable>printer-name</replaceable></command></term>
@ -2116,7 +2116,7 @@ cfA013rose dequeued
removes them.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>disable
<replaceable>printer-name</replaceable></command></term>
@ -2134,7 +2134,7 @@ cfA013rose dequeued
<command>enable</command> command.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>down <replaceable>printer-name</replaceable>
<replaceable>message</replaceable></command></term>
@ -2148,7 +2148,7 @@ cfA013rose dequeued
status</command>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>enable
<replaceable>printer-name</replaceable></command></term>
@ -2158,7 +2158,7 @@ cfA013rose dequeued
the printer will not print anything until it is started.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>help
<replaceable>command-name</replaceable></command></term>
@ -2170,7 +2170,7 @@ cfA013rose dequeued
commands available.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>restart
<replaceable>printer-name</replaceable></command></term>
@ -2185,7 +2185,7 @@ cfA013rose dequeued
<command>start</command>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>start
<replaceable>printer-name</replaceable></command></term>
@ -2195,7 +2195,7 @@ cfA013rose dequeued
queue.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>stop
<replaceable>printer-name</replaceable></command></term>
@ -2207,7 +2207,7 @@ cfA013rose dequeued
queue.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>topq <replaceable>printer-name</replaceable>
<replaceable>job-or-username</replaceable></command></term>
@ -2222,7 +2222,7 @@ cfA013rose dequeued
<replaceable>printer-name</replaceable>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><command>up
<replaceable>printer-name</replaceable></command></term>
@ -2249,7 +2249,7 @@ cfA013rose dequeued
<para>This section describes filters for printing specially formatted
files, header pages, printing across networks, and restricting and
accounting for printer usage.</para>
<sect2 id="printing-advanced-filter-intro">
<title>Filters</title>
@ -2301,7 +2301,7 @@ cfA013rose dequeued
should do to overcome this problem. I recommend reading this
section if you have a PostScript printer.</para>
</listitem>
<listitem>
<para>PostScript is a popular output format for many programs. Even
some people (myself included) write PostScript code directly. But
@ -2333,7 +2333,7 @@ cfA013rose dequeued
linkend="printing-advanced-header-pages">Header Pages</link>),
you can probably skip that section altogether.</para>
</listitem>
<listitem>
<para>Section <link linkend="printing-advanced-lpf">lpf: a Text
Filter</link> describes <command>lpf</command>, a fairly
@ -2348,7 +2348,7 @@ cfA013rose dequeued
<sect3 id="printing-advanced-filters">
<title>How Filters Work</title>
<para>As mentioned before, a filter is an executable program started
by LPD to handle the device-dependent part of communicating with the
printer.</para>
@ -2370,10 +2370,10 @@ cfA013rose dequeued
<literal>if</literal> filter (this is mostly true: see <link
linkend="printing-advanced-of">Output Filters</link> for
details).</para>
<para>There are three kinds of filters you can specify in
<filename>/etc/printcap</filename>:</para>
<itemizedlist>
<listitem>
<para>The <emphasis>text filter</emphasis>, confusingly called the
@ -2514,7 +2514,7 @@ cfA013rose dequeued
<option>-l</option> arguments.</para>
</listitem>
</itemizedlist>
<para>Filters should also <emphasis>exit</emphasis> with the
following exit status:</para>
@ -2546,13 +2546,13 @@ cfA013rose dequeued
</listitem>
</varlistentry>
</variablelist>
<para>The text filter that comes with the FreeBSD release,
<filename>/usr/libexec/lpr/lpf</filename>, takes advantage of the
page width and length arguments to determine when to send a form
feed and how to account for printer usage. It uses the login, host,
and accounting file arguments to make the accounting entries.</para>
<para>If you are shopping for filters, see if they are LPD-compatible.
If they are, they must support the argument lists described above.
If you plan on writing filters for general use, then have them
@ -2561,7 +2561,7 @@ cfA013rose dequeued
<sect3 id="printing-advanced-if-conversion">
<title>Accommodating Plain Text Jobs on PostScript Printers</title>
<para>If you are the only user of your computer and PostScript (or
other language-based) printer, and you promise to never send plain
text to your printer and to never use features of various programs
@ -2579,7 +2579,7 @@ cfA013rose dequeued
will convert the text into PostScript and print the result.</para>
<para>How do we do this?</para>
<para>If you have got a serial printer, a great way to do it is to
install <command>lprps</command>. <command>lprps</command> is a
PostScript printer filter which performs two-way communication with
@ -2649,7 +2649,7 @@ fi</programlisting>
<sect3 id="printing-advanced-ps">
<title>Simulating PostScript on Non-PostScript Printers</title>
<para>PostScript is the <emphasis>de facto</emphasis> standard for
high quality typesetting and printing. PostScript is, however, an
<emphasis>expensive</emphasis> standard. Thankfully, Alladin
@ -2737,7 +2737,7 @@ exit 2</programlisting>
<sect3 id="printing-advanced-convfilters">
<title>Conversion Filters</title>
<para>After completing the simple setup described in <link
linkend="printing-simple">Simple Printer Setup</link>, the first
thing you will probably want to do is install conversion filters for
@ -2777,7 +2777,7 @@ exit 2</programlisting>
text, the filter converts the file into a format the printer can
understand.</para>
</sect4>
<sect4>
<title>Which Conversions Filters Should I Install?</title>
@ -2869,7 +2869,7 @@ exit 2</programlisting>
<command>lpr -g</command> mean &ldquo;print Printerleaf
files.&rdquo;</para>
</sect4>
<sect4>
<title>Installing Conversion Filters</title>
@ -3129,7 +3129,7 @@ dvilj2p -M1 -q -e- dfhp$$.dvi
cleanup
exit 0</programlisting>
</sect4>
<sect4 id="printing-advanced-autoconv">
<title>Automated Conversion: An Alternative To Conversion
Filters</title>
@ -3161,7 +3161,7 @@ exit 0</programlisting>
<sect3 id="printing-advanced-of">
<title>Output Filters</title>
<para>The LPD spooling system supports one other type of filter that
we have not yet explored: an output filter. An output filter is
intended for printing plain text only, like the text filter, but
@ -3197,7 +3197,7 @@ exit 0</programlisting>
question.</para>
</listitem>
</itemizedlist>
<para>Do not be seduced by an output filter's simplicity. If you
would like each file in a job to start on a different page an output
filter <emphasis>will not work</emphasis>. Use a text filter (also
@ -3244,7 +3244,7 @@ exit 0</programlisting>
<sect3 id="printing-advanced-lpf">
<title><command>lpf</command>: a Text Filter</title>
<para>The program <filename>/usr/libexec/lpr/lpf</filename> that comes
with FreeBSD binary distribution is a text filter (input filter)
that can indent output (job submitted with <command>lpr
@ -3298,15 +3298,15 @@ exit 0</programlisting>
<sect3 id="printing-advanced-header-pages-enabling">
<title>Enabling Header Pages</title>
<para>In the <link linkend="printing-simple">Simple Printer
Setup</link>, we turned off header pages by specifying
<literal>sh</literal> (meaning &ldquo;suppress header&rdquo;) in the
<filename>/etc/printcap</filename> file. To enable header pages for
a printer, just remove the <literal>sh</literal> capability.</para>
<para>Sounds too easy, right?</para>
<para>You are right. You <emphasis>might</emphasis> have to provide
an output filter to send initialization strings to the printer.
Here is an example output filter for Hewlett Packard PCL-compatible
@ -3357,7 +3357,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
<sect3 id="printing-advanced-header-pages-controlling">
<title>Controlling Header Pages</title>
<para>By enabling header pages, LPD will produce a <emphasis>long
header</emphasis>, a full page of large letters identifying the
user, host, and job. Here is an example (kelly printed the job
@ -3424,7 +3424,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
<programlisting>
rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995</programlisting>
<para>Also by default, LPD prints the header page first, then the job.
To reverse that, specify <literal>hl</literal> (header last) in
<filename>/etc/printcap</filename>.</para>
@ -3432,13 +3432,13 @@ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995</programlisting>
<sect3 id="printing-advanced-header-pages-accounting">
<title>Accounting for Header Pages</title>
<para>Using LPD's built-in header pages enforces a particular paradigm
when it comes to printer accounting: header pages must be
<emphasis>free of charge</emphasis>.</para>
<para>Why?</para>
<para>Because the output filter is the only external program that will
have control when the header page is printed that could do
accounting, and it is not provided with any <emphasis>user or
@ -3458,9 +3458,9 @@ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995</programlisting>
header pages with <command>lpr -h</command>, they will still get
them and be charged for them since LPD does not pass any knowledge
of the <option>-h</option> option to any of the filters.</para>
<para>So, what are your options?</para>
<para>You can:</para>
<itemizedlist>
@ -3501,7 +3501,7 @@ rose:kelly Job: outline Date: Sun Sep 17 11:07:51 1995</programlisting>
<sect3 id="printing-advanced-header-pages-ps">
<title>Header Pages on PostScript Printers</title>
<para>As described above, LPD can generate a plain text header page
suitable for many printers. Of course, PostScript cannot directly
print plain text, so the header page feature of LPD is
@ -3684,7 +3684,7 @@ done
linkend="printing-advanced-network-rm">Printers Installed on
Remote Hosts</link> tells how to do this.</para>
</listitem>
<listitem>
<para>Accessing a printer attached directly to a network. The
printer has a network interface in addition (or in place of) a
@ -3716,7 +3716,7 @@ done
<sect3 id="printing-advanced-network-rm">
<title>Printers Installed on Remote Hosts</title>
<para>The LPD spooling system has built-in support for sending jobs to
other hosts also running LPD (or are compatible with LPD). This
feature enables you to install a printer on one host and make it
@ -3745,7 +3745,7 @@ done
<para>Then, on the other hosts you want to have access to the printer,
make an entry in their <filename>/etc/printcap</filename> files with
the following:</para>
<orderedlist>
<listitem>
<para>Name the entry anything you want. For simplicity, though,
@ -3779,7 +3779,7 @@ done
<para>That is it. You do not need to list conversion filters, page
dimensions, or anything else in the
<filename>/etc/printcap</filename> file.</para>
<para>Here is an example. The host <hostid>rose</hostid> has two
printers, <literal>bamboo</literal> and <literal>rattan</literal>.
We will enable users on the host orchid to print to those printers.
@ -3789,7 +3789,7 @@ done
Pages</link>). It already had the entry for the printer
<literal>teak</literal>; we have added entries for the two printers
on the host rose:</para>
<programlisting>
#
# /etc/printcap for host orchid - added (remote) printers on rose
@ -3840,7 +3840,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<sect3 id="printing-advanced-network-net-if">
<title>Printers with Networked Data Stream Interfaces</title>
<para>Often, when you buy a network interface card for a printer, you
can get two versions: one which emulates a spooler (the more
expensive version), or one which just lets you send data to it as if
@ -3920,7 +3920,7 @@ exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100</pro
<sect3 id="printing-advanced-restricting-copies">
<title>Restricting Multiple Copies</title>
<para>The LPD system makes it easy for users to print multiple copies
of a file. Users can print jobs with <command>lpr -#5</command>
(for example) and get five copies of each file in the job. Whether
@ -3933,8 +3933,8 @@ exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100</pro
with the <option>-#</option> option, they will see:</para>
<screen>lpr: multiple copies are not allowed</screen>
<para>Note that if you have set up access to a printer remotely (see
section <link linkend="printing-advanced-network-rm">Printers
Installed on Remote Hosts</link>), you need the
@ -3971,7 +3971,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<filename>/etc/printcap</filename> (and while we are at it, let us
disable multiple copies for the printer
<literal>teak</literal>):</para>
<programlisting>
#
# /etc/printcap for host orchid - no multiple copies for local
@ -4002,7 +4002,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<sect3 id="printing-advanced-restricting-access">
<title>Restricting Access To Printers</title>
<para>You can control who can print to what printers by using the UNIX
group mechanism and the <literal>rg</literal> capability in
<filename>/etc/printcap</filename>. Just place the users you want
@ -4014,7 +4014,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<errorname>lpr: Not a member of the restricted group</errorname>
if they try to print to the controlled printer.</para>
<para>As with the <literal>sc</literal> (suppress multiple copies)
capability, you need to specify <literal>rg</literal> on remote
hosts that also have access to your printers, if you feel it is
@ -4058,7 +4058,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<sect3 id="printing-advanced-restricting-sizes">
<title>Controlling Sizes of Jobs Submitted</title>
<para>If you have many users accessing the printers, you probably need
to put an upper limit on the sizes of the files users can submit to
print. After all, there is only so much free space on the
@ -4076,7 +4076,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<para>The limit applies to <emphasis>files</emphasis> in a job, and
<emphasis>not</emphasis> the total job size.</para>
</note>
<para>LPD will not refuse a file that is larger than the limit you
place on a printer. Instead, it will queue as much of the file up
to the limit, which will then get printed. The rest will be
@ -4128,7 +4128,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<sect3 id="printing-advanced-restricting-remote">
<title>Restricting Jobs from Remote Printers</title>
<para>The LPD spooling system provides several ways to restrict print
jobs submitted from remote hosts:</para>
@ -4296,7 +4296,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<sect3>
<title>Quick and Dirty Printer Accounting</title>
<para>FreeBSD comes with two programs that can get you set up with
simple periodic accounting right away. They are the text filter
<command>lpf</command>, described in section <link
@ -4312,7 +4312,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
of this file comes from the <literal>af</literal> capability in
<filename>/etc/printcap</filename>, and if not specified as an
absolute path, is relative to the spooling directory.</para>
<para>LPD starts <command>lpf</command> with page width and length
arguments (from the <literal>pw</literal> and <literal>pl</literal>
capabilities). <command>lpf</command> uses these arguments to
@ -4353,7 +4353,7 @@ rose:root 26.00 12 $ 0.52
total 337.00 154 $ 6.74</screen>
<para>These are the arguments &man.pac.8; expects:</para>
<variablelist>
<varlistentry>
<term><option>-P<replaceable>printer</replaceable></option></term>
@ -4427,7 +4427,7 @@ total 337.00 154 $ 6.74</screen>
</listitem>
</varlistentry>
</variablelist>
<para>In the default summary that &man.pac.8; produces, you see the
number of pages printed by each user from various hosts. If, at
your site, host does not matter (because users can use any host),
@ -4458,7 +4458,7 @@ total 337.00 154 $ 6.74</screen>
makes each page cost one dollar and fifty cents. You can really
rake in the profits by using this option.</para>
<para>Finally, running <command>pac -s</command> will save the summary
information in a summary accounting file, which is named the same as
the printer's accounting file, but with <literal>_sum</literal>
@ -4470,7 +4470,7 @@ total 337.00 154 $ 6.74</screen>
<sect3>
<title>How Can You Count Pages Printed?</title>
<para>In order to perform even remotely accurate accounting, you need
to be able to determine how much paper a job uses. This is the
essential problem of printer accounting.</para>
@ -4488,20 +4488,20 @@ total 337.00 154 $ 6.74</screen>
to examine <command>lpf</command>'s source code.</para>
<para>How do you handle other file formats, though?</para>
<para>Well, for DVI-to-LaserJet or DVI-to-PostScript conversion, you
can have your filter parse the diagnostic output of
<command>dvilj</command> or <command>dvips</command> and look to see
how many pages were converted. You might be able to do similar
things with other file formats and conversion programs.</para>
<para>But these methods suffer from the fact that the printer may not
actually print all those pages. For example, it could jam, run out
of toner, or explode&mdash;and the user would still get
charged.</para>
<para>So, what can you do?</para>
<para>There is only one <emphasis>sure</emphasis> way to do
<emphasis>accurate</emphasis> accounting. Get a printer that can
tell you how much paper it uses, and attach it via a serial line or
@ -4528,15 +4528,15 @@ total 337.00 154 $ 6.74</screen>
many of its shortcomings, which naturally leads to the question:
&ldquo;What other spooling systems are out there (and work with
FreeBSD)?&rdquo;</para>
<para>Unfortunately, I have located only <emphasis>two</emphasis>
alternatives&mdash;and they are almost identical to each other! They
are:</para>
<variablelist>
<varlistentry>
<term>PLP, the Portable Line Printer Spooler System</term>
<listitem>
<para>PLP was based on software developed by Patrick Powell and then
maintained by an Internet-wide group of developers. The main site
@ -4579,7 +4579,7 @@ total 337.00 154 $ 6.74</screen>
<varlistentry>
<term>LPRng</term>
<listitem>
<para>LPRng, which purportedly means &ldquo;LPR: the Next
Generation&rdquo; is a complete rewrite of PLP. Patrick Powell
@ -4596,12 +4596,12 @@ total 337.00 154 $ 6.74</screen>
<para>I would like to thank the following people who have assisted in the
development of this document:</para>
<variablelist>
<varlistentry>
<term>Daniel Eischen
<email>deischen@iworks.interworks.org</email></term>
<listitem>
<para>For providing a plethora of HP filter programs for
perusal.</para>
@ -4610,7 +4610,7 @@ total 337.00 154 $ 6.74</screen>
<varlistentry>
<term>&a.jehamby;</term>
<listitem>
<para>For the Ghostscript-to-HP filter.</para>
</listitem>
@ -4618,7 +4618,7 @@ total 337.00 154 $ 6.74</screen>
<varlistentry>
<term>&a.jfieber;</term>
<listitem>
<para> For debugging why printing from Windows 95 to a FreeBSD
system simulating a PostScript printer with Ghostscript didn't
@ -4641,7 +4641,7 @@ total 337.00 154 $ 6.74</screen>
<varlistentry>
<term>My wife, Mary Kelly
<email>urquhart@argyre.colorado.edu</email></term>
<listitem>
<para>For allowing me to spend more time with FreeBSD than
with her.</para>

38
en_US.ISO_8859-1/books/handbook/quotas/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/quotas/chapter.sgml,v 1.11 1999/09/06 06:53:05 peter Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/quotas/chapter.sgml,v 1.12 1999/09/06 18:38:44 chris Exp $
-->
<chapter id="quotas">
@ -33,14 +33,14 @@ options QUOTA</programlisting>
custom kernel in order to use disk quotas. Please refer to the <link
linkend="kernelconfig">Configuring the FreeBSD Kernel</link> section
for more information on kernel configuration.</para>
<para>Next you will need to enable disk quotas in
<filename>/etc/rc.conf</filename>. This is done by adding the line:
</para>
<programlisting>
enable_quotas=YES</programlisting>
<para>For finer control over your quota startup, there is an additional
configuration variable available. Normally on bootup, the quota integrity
of each file system is checked by the <command>quotacheck</command>
@ -65,7 +65,7 @@ check_quotas=YES</programlisting>
enable disk quotas on a per-file system basis. This is where you can
either enable user or group quotas or both for all of your file
systems.</para>
<para>To enable per-user quotas on a file system, add the
<literal>userquota</literal> option to the options field in the
<filename>/etc/fstab</filename> entry for the file system you want to to
@ -73,7 +73,7 @@ check_quotas=YES</programlisting>
<programlisting>
/dev/da1s2g /home ufs rw,userquota 1 2</programlisting>
<para>Similarly, to enable group quotas, use the
<literal>groupquota</literal> option instead of the
<literal>userquota</literal> keyword. To enable both user and group
@ -81,7 +81,7 @@ check_quotas=YES</programlisting>
<programlisting>
/dev/da1s2g /home ufs rw,userquota,groupquota 1 2</programlisting>
<para>By default the quota files are stored in the root directory of the
file system with the names <filename>quota.user</filename> and
<filename>quota.group</filename> for user and group quotas respectively.
@ -89,13 +89,13 @@ check_quotas=YES</programlisting>
man page says that you can specify an alternate location for the quota
files, this is not recommended since all of the various quota utilities
do not seem to handle this properly.</para>
<para>At this point you should reboot your system with your new kernel.
<filename>/etc/rc</filename> will automatically run the appropriate
commands to create the initial quota files for all of the quotas you
enabled in <filename>/etc/fstab</filename>, so there is no need to
manually create any zero length quota files.</para>
<para>In the normal course of operations you should not be required to run
the <command>quotacheck</command>, <command>quotaon</command>, or
<command>quotaoff</command> commands manually. However, you may want to
@ -112,31 +112,31 @@ check_quotas=YES</programlisting>
<para>You should see a one line summary of disk usage and current quota
limits for each file system that quotas are enabled on.</para>
<para>You are now ready to start assigning quota limits with the
<command>edquota</command> command.</para>
<para>You have several options on how to enforce limits on the amount of
disk space a user or group may allocate, and how many files they may
create. You may limit allocations based on disk space (block quotas) or
number of files (inode quotas) or a combination of both. Each of these
limits are further broken down into two categories: hard and soft
limits.</para>
<para>A hard limit may not be exceeded. Once a user reaches their hard
limit they may not make any further allocations on the file system in
question. For example, if the user has a hard limit of 500 blocks on a
file system and is currently using 490 blocks, the user can only
allocate an additional 10 blocks. Attempting to allocate an additional
11 blocks will fail.</para>
<para>Soft limits on the other hand can be exceeded for a limited amount
of time. This period of time is known as the grace period, which is one
week by default. If a user stays over his or her soft limit longer than
their grace period, the soft limit will turn into a hard limit and no
further allocations will be allowed. When the user drops back below the
soft limit, the grace period will be reset.</para>
<para>The following is an example of what you might see when you run
then <command>edquota</command> command. When the
<command>edquota</command> command is invoked, you are placed into the
@ -164,7 +164,7 @@ Quotas for user test:
<para>The new quota limits will be in place when you exit the
editor.</para>
<para>Sometimes it is desirable to set quota limits on a range of uids.
This can be done by use of the <option>-p</option> option on the
<command>edquota</command> command. First, assign the desired quota
@ -179,7 +179,7 @@ Quotas for user test:
<para>The ability to specify uid ranges was added to the system after 2.1
was released. If you need this feature on a 2.1 system, you will need
to obtain a newer copy of edquota.</para>
<para>See <command>man edquota</command> for more detailed
information.</para>
</sect1>
@ -195,12 +195,12 @@ Quotas for user test:
are not a member of. The <command>repquota</command> command can be
used to get a summary of all quotas and disk usage for file systems with
quotas enabled.</para>
<para>The following is some sample output from the <command>quota
-v</command> command for a user that has quota limits on two file
systems.</para>
<programlisting>
Disk quotas for user test (uid 1002):
Filesystem blocks quota limit grace files quota limit grace
@ -212,7 +212,7 @@ Disk quotas for user test (uid 1002):
has 5 days of their grace period left. Note the asterisk
<literal>*</literal> which indicates that the user is currently over
their quota limit.</para>
<para>Normally file systems that the user is not using any disk space on
will not show up in the output from the <command>quota</command>
command, even if they have a quota limit assigned for that file system.

90
en_US.ISO_8859-1/books/handbook/security/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/security/chapter.sgml,v 1.20 1999/09/06 06:53:07 peter Exp $
-->
<chapter id="security">
@ -12,7 +12,7 @@
<para><emphasis>Contributed by &a.wollman; 24 September
1995.</emphasis></para>
<para>In order to protect the security of passwords on UN*X systems from
being easily exposed, passwords have traditionally been scrambled in
some way. Starting with Bell Labs' Seventh Edition Unix, passwords were
@ -27,7 +27,7 @@
available, because national governments in many places like to place
restrictions on cross-border transport of DES and other encryption
software.</para>
<para>So, the FreeBSD team was faced with a dilemma: how could we provide
compatibility with all those UNIX systems out there while still not
running afoul of the law? We decided to take a dual-track approach: we
@ -43,7 +43,7 @@
Because neither of these functions involve encryption, they are believed
to be exportable from the US and importable into many other
countries.</para>
<para>Meanwhile, work was also underway on the DES-based password hash
function. First, a version of the <function>crypt</function> function
which was written outside the US was imported, thus synchronizing the US
@ -128,7 +128,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -&gt; libdescrypt_p.a</s
distributions since version 1.1.5, and is also implemented on a large
and growing number of other systems. S/Key is a registered trademark of
Bell Communications Research, Inc.</para>
<para>There are three different sorts of passwords which we will talk
about in the discussion below. The first is your usual UNIX-style or
Kerberos password; we will call this a &ldquo;UNIX password&rdquo;. The
@ -140,14 +140,14 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -&gt; libdescrypt_p.a</s
(and sometimes the <command>keyinit</command> program) which it uses to
generate one-time passwords; we will call it a &ldquo;secret
password&rdquo; or just unqualified &ldquo;password&rdquo;.</para>
<para>The secret password does not necessarily have anything to do with
your UNIX password (while they can be the same, this is not
recommended). While UNIX passwords are limited to eight characters in
length, your S/Key secret password can be as long as you like; I use
seven-word phrases. In general, the S/Key system operates completely
independently of the UNIX password system.</para>
<para>There are in addition two other sorts of data involved in the S/Key
system; one is called the &ldquo;seed&rdquo; or (confusingly)
&ldquo;key&rdquo;, and consists of two letters and five digits, and the
@ -165,7 +165,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -&gt; libdescrypt_p.a</s
each successful login to keep the user and login program in sync. (When
you get the iteration count down to 1, it is time to reinitialize
S/Key.)</para>
<para>There are four programs involved in the S/Key system which we will
discuss below. The <command>key</command> program accepts an iteration
count, a seed, and a secret password, and generates a one-time password.
@ -180,7 +180,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -&gt; libdescrypt_p.a</s
The <command>login</command> program is also capable of disallowing the
use of UNIX passwords on connections coming from specified
addresses.</para>
<para>There are four different sorts of operations we will cover. The
first is using the <command>keyinit</command> program over a secure
connection to set up S/Key for the first time, or to change your
@ -193,7 +193,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -&gt; libdescrypt_p.a</s
number of keys which can be written down or printed out to carry with
you when going to some location without secure connections to anywhere
(like at a conference).</para>
<sect2>
<title>Secure connection initialization</title>
@ -294,7 +294,7 @@ s/key 92 hi52030
annotation <literal>(s/key required)</literal>, indicating that only
S/Key one-time passwords will be accepted.</para>
</sect2>
<sect2>
<title>Generating a single one-time password</title>
@ -415,16 +415,16 @@ permit port ttyd0</programlisting>
Services such as remote login, remote copy, secure inter-system file
copying and other high-risk tasks are made considerably safer and more
controllable.</para>
<para>The following instructions can be used as a guide on how to set up
Kerberos as distributed for FreeBSD. However, you should refer to the
relevant manual pages for a complete description.</para>
<para>In FreeBSD, the Kerberos is not that from the original 4.4BSD-Lite,
distribution, but eBones, which had been previously ported to FreeBSD
1.1.5.1, and was sourced from outside the USA/Canada, and is thus
available to system owners outside those countries.</para>
<para>For those needing to get a legal foreign distribution of this
software, please <emphasis>do not</emphasis> get it from a USA or Canada
site. You will get that site in <emphasis>big</emphasis> trouble! A
@ -594,7 +594,7 @@ Principal's new key version = 1
Edit O.K.
<prompt>Principal name:</prompt> &lt;---- null entry here will cause an exit</screen>
</sect2>
<sect2>
<title>Creating the server file</title>
@ -668,7 +668,7 @@ Principal's new key version = 1
Edit O.K.
<prompt>Principal name:</prompt> &lt;---- null entry here will cause an exit</screen>
</sect2>
<sect2>
<title>Testing it all out</title>
@ -729,7 +729,7 @@ Verifying password
<prompt>New Password for jane:</prompt>
Password changed.</screen>
</sect2>
<sect2>
<title>Adding <command>su</command> privileges</title>
@ -798,7 +798,7 @@ Principal: jane.root@GRONDAR.ZA
Issued Expires Principal
May 2 20:43:12 May 3 04:43:12 krbtgt.GRONDAR.ZA@GRONDAR.ZA</screen>
</sect2>
<sect2>
<title>Using other commands</title>
@ -861,15 +861,15 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<sect1 id="firewalls">
<title>Firewalls</title>
<para><emphasis>Contributed by &a.gpalmer; and &a.alex;.</emphasis></para>
<para>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 implement them.</para>
<note>
<para>People often think that having a firewall between your companies
internal network and the &ldquo;Big Bad Internet&rdquo; will solve all
@ -883,7 +883,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
firewall to be impenetrable, you have just made the crackers job that
bit easier.</para>
</note>
<sect2>
<title>What is a firewall?</title>
@ -912,7 +912,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<sect3 id="firewalls-packet-filters">
<title>Packet filtering routers</title>
<para>A router is a machine which forwards packets between two or more
networks. A packet filtering router has an extra piece of code in
its kernel, which compares each packet to a list of rules before
@ -968,7 +968,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
depends largely on what proxy software you choose.</para>
</sect3>
</sect2>
<sect2>
<title>What does IPFW allow me to do?</title>
@ -993,7 +993,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<application>IPFW</application>, and the same commands and techniques
should be used in this situation.</para>
</sect2>
<sect2>
<title>Enabling IPFW on FreeBSD</title>
@ -1027,7 +1027,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
happen.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>options IPFIREWALL_VERBOSE_LIMIT=10</literal></term>
@ -1055,7 +1055,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
the firewall code automatically includes accounting
facilities.</para>
</sect2>
<sect2>
<title>Configuring IPFW</title>
@ -1075,7 +1075,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<sect3>
<title>Altering the IPFW rules</title>
<para>The syntax for this form of the command is:
<cmdsynopsis>
<command>ipfw</command>
@ -1088,10 +1088,10 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<arg choice="plain">addresses</arg>
<arg>options</arg>
</cmdsynopsis></para>
<para>There is one valid flag when using this form of the
command:</para>
<variablelist>
<varlistentry>
<term>-N</term>
@ -1101,7 +1101,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
</listitem>
</varlistentry>
</variablelist>
<para>The <emphasis>command</emphasis> given can be shortened to the
shortest unique form. The valid <emphasis>commands</emphasis>
are:</para>
@ -1124,7 +1124,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
</listitem>
</varlistentry>
</variablelist>
<para>Previous versions of <application>IPFW</application> used
separate firewall and accounting entries. The present version
provides packet accounting with each firewall entry.</para>
@ -1181,7 +1181,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
</listitem>
</varlistentry>
</variablelist>
<para>Each <emphasis>action</emphasis> will be recognized by the
shortest unambiguous prefix.</para>
@ -1221,9 +1221,9 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
</listitem>
</varlistentry>
</variablelist>
<para>The <emphasis>address</emphasis> specification is:</para>
<cmdsynopsis>
<arg choice="plain">from</arg>
<arg choice="plain"><replaceable>address/mask</replaceable></arg><arg><replaceable>port</replaceable></arg>
@ -1256,7 +1256,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<screen><replaceable>address</replaceable>:<replaceable>mask-pattern</replaceable></screen>
</para>
<para>A valid hostname may be specified in place of the IP address.
<option><replaceable>mask-bits</replaceable></option> is a decimal
number representing how many bits in the address mask should be set.
@ -1284,7 +1284,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
with a list, but the range must always be specified first.</para>
<para>The <emphasis>options</emphasis> available are:</para>
<variablelist>
<varlistentry>
<term>frag</term>
@ -1382,7 +1382,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<sect3>
<title>Listing the IPFW rules</title>
<para>The syntax for this form of the command is:
<cmdsynopsis>
<command>ipfw</command>
@ -1391,7 +1391,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<arg>-N</arg>
<arg choice="plain">l</arg>
</cmdsynopsis></para>
<para>There are three valid flags when using this form of the
command:</para>
@ -1428,13 +1428,13 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<sect3>
<title>Flushing the IPFW rules</title>
<para>The syntax for flushing the chain is:
<cmdsynopsis>
<command>ipfw</command>
<arg choice="plain">flush</arg>
</cmdsynopsis></para>
<para>This causes all entries in the firewall chain to be removed
except the fixed default policy enforced by the kernel (index
65535). Use caution when flushing rules, the default deny policy
@ -1444,21 +1444,21 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<sect3>
<title>Clearing the IPFW packet counters</title>
<para>The syntax for clearing one or more packet counters is:
<cmdsynopsis>
<command>ipfw</command>
<arg choice="plain">zero</arg>
<arg choice="opt"><replaceable>index</replaceable></arg>
</cmdsynopsis></para>
<para>When used without an <replaceable>index</replaceable> argument,
all packet counters are cleared. If an
<replaceable>index</replaceable> is supplied, the clearing operation
only affects a specific chain entry.</para>
</sect3>
</sect2>
<sect2>
<title>Example commands for ipfw</title>
@ -1554,7 +1554,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
where most of the security sensitive services are, like finger,
SMTP (mail) and telnet.</para>
</listitem>
<listitem>
<para>Block <emphasis>all</emphasis> incoming UDP traffic. There
are very few useful services that travel over UDP, and what useful

192
en_US.ISO_8859-1/books/handbook/serialcomms/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/serialcomms/chapter.sgml,v 1.14 1999/09/06 06:53:08 peter Exp $
-->
<chapter id="serialcomms">
@ -15,7 +15,7 @@
<para>This section should give you some general information about serial
ports. If you do not find what you want here, check into the Terminal
and Dialup sections of the handbook.</para>
<para>The <filename>ttyd<replaceable>X</replaceable></filename> (or
<filename>cuaa<replaceable>X</replaceable></filename>) device is the
regular device you will want to open for your applications. When a
@ -38,17 +38,17 @@
Now, an application will have these settings by default when it opens
<filename>ttyd5</filename>. It can still change these settings to its
liking, though.</para>
<para>You can also prevent certain settings from being changed by an
application by making adjustments to the &ldquo;lock state&rdquo;
device. For example, to lock the speed of <filename>ttyd5</filename> to
57600 bps, do</para>
<screen>&prompt.root; <userinput>stty -f /dev/ttyld5 57600</userinput></screen>
<para>Now, an application that opens <filename>ttyd5</filename> and tries
to change the speed of the port will be stuck with 57600 bps.</para>
<para>Naturally, you should make the initial state and lock state devices
writable only by <username>root</username>. The
<filename>MAKEDEV</filename> script does <emphasis>not</emphasis> do
@ -59,12 +59,12 @@
<title>Terminals</title>
<para><emphasis>Contributed by &a.kelly; 28 July 1996</emphasis></para>
<para>Terminals provide a convenient and low-cost way to access the power
of your FreeBSD system when you are not at the computer's console or on
a connected network. This section describes how to use terminals with
FreeBSD.</para>
<sect2 id="term-uses">
<title>Uses and Types of Terminals</title>
@ -95,11 +95,11 @@
<listitem>
<para><link linkend="term-dumb">Dumb terminals</link></para>
</listitem>
<listitem>
<para><link linkend="term-pcs">PCs acting as terminals</link></para>
</listitem>
<listitem>
<para><link linkend="term-x">X terminals</link></para>
</listitem>
@ -109,7 +109,7 @@
<sect3 id="term-dumb">
<title>Dumb Terminals</title>
<para>Dumb terminals are specialized pieces of hardware that let you
connect to computers over serial lines. They are called
&ldquo;dumb&rdquo; because they have only enough computational power
@ -132,7 +132,7 @@
<sect3 id="term-pcs">
<title>PCs Acting As Terminals</title>
<para>If a <link linkend="term-dumb">dumb terminal</link> has just
enough ability to display, send, and receive text, then certainly
any spare personal computer can be a dumb terminal. All you need is
@ -147,7 +147,7 @@
<sect3 id="term-x">
<title>X Terminals</title>
<para>X terminals are the most sophisticated kind of terminal
available. Instead of connecting to a serial port, they usually
connect to a network like Ethernet. Instead of being relegated to
@ -170,7 +170,7 @@
<sect3 id="term-cables">
<title>Cables</title>
<para>Because terminals use serial ports, you need to use
serial&mdash;also known as RS-232C&mdash;cables to connect the
terminal to the FreeBSD system.</para>
@ -195,7 +195,7 @@
linkend="term-std">standard</link> cable.</para>
</listitem>
</itemizedlist>
<para>Also, the serial port on <emphasis>both</emphasis> the terminal
and your FreeBSD system must have connectors that will fit the cable
you are using.</para>
@ -299,7 +299,7 @@
hood.</para>
</note>
</sect4>
<sect4 id="term-std">
<title>Standard RS-232C Cables</title>
@ -314,12 +314,12 @@
<sect3 id="term-ports">
<title>Ports</title>
<para>Serial ports are the devices through which data is transferred
between the FreeBSD host computer and the terminal. This section
describes the kinds of ports that exist and how they are addressed
in FreeBSD.</para>
<sect4 id="term-portkinds">
<title>Kinds of Ports</title>
@ -336,7 +336,7 @@
specifications on the kind of port in use. A visual inspection of
the port often works, too.</para>
</sect4>
<sect4 id="term-portnames">
<title>Port Names</title>
@ -406,18 +406,18 @@
the <filename>/dev</filename> directory for the serial port if it
is not already there.</para>
</step>
<step>
<para>Specify that <filename>/usr/libexec/getty</filename> be run on
the port, and specify the appropriate
<replaceable>getty</replaceable> type from the
<filename>/etc/gettytab</filename> file.</para>
</step>
<step>
<para>Specify the default terminal type.</para>
</step>
<step>
<para>Set the port to &ldquo;on.&rdquo;</para>
</step>
@ -426,7 +426,7 @@
<para>Specify whether the port should be
&ldquo;secure.&rdquo;</para>
</step>
<step>
<para>Force <command>init</command> to reread the
<filename>/etc/ttys</filename> file.</para>
@ -453,11 +453,11 @@
<sect3 id="term-etcttys">
<title>Adding an Entry to <filename>/etc/ttys</filename></title>
<para>First, you need to add an entry to the
<filename>/etc/ttys</filename> file, unless one is already
there.</para>
<para>The <filename>/etc/ttys</filename> file lists all of the ports
on your FreeBSD system where you want to allow logins. For example,
the first virtual console <filename>ttyv0</filename> has an entry in
@ -486,7 +486,7 @@ ttyd5</programlisting>
<sect3 id="term-getty">
<title>Specifying the <replaceable>getty</replaceable> Type</title>
<para>Next, we need to specify what program will be run to handle the
logins on a terminal. For FreeBSD, the standard program to do that
is <filename>/usr/libexec/getty</filename>. It is what provides the
@ -529,7 +529,7 @@ ttyd5 "/usr/libexec/getty std.19200"</programlisting>
<sect3 id="term-deftermtype">
<title>Specifying the Default Terminal Type</title>
<para>The third field in the <filename>/etc/ttys</filename> file lists
the default terminal type for the port. For dialup ports, you
typically put <literal>unknown</literal> or
@ -537,18 +537,18 @@ ttyd5 "/usr/libexec/getty std.19200"</programlisting>
with practically any kind of terminal or software. For hardwired
terminals, the terminal type does not change, so you can put a real
terminal type in this field.</para>
<para>Users will usually use the <command>tset</command> program in
their <filename>.login</filename> or <filename>.profile</filename>
files to check the terminal type and prompt for one if necessary.
By setting a terminal type in the <filename>/etc/ttys</filename>
file, users can forego such prompting.</para>
<para>To find out what terminal types FreeBSD supports, see the
file <filename>/usr/share/misc/termcap</filename>. It lists
about 600 terminal types. You can add more if you wish. See
the &man.termcap.5; manual page for information.</para>
<para>In our example, the Wyse-50 is a Wyse-50 type of terminal
(although it can emulate others, we will leave it in Wyse-50 mode).
The 286 PC is running Procomm which will be set to emulate a VT-100.
@ -562,7 +562,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100</programlisting>
<sect3 id="term-enable">
<title>Enabling the Port</title>
<para>The next field in <filename>/etc/ttys</filename>, the fourth
field, tells whether to enable the port. Putting
<literal>on</literal> here will have the <command>init</command>
@ -582,7 +582,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on</programlisting>
<sect3 id="term-secure">
<title>Specifying Secure Ports</title>
<para>We have arrived at the last field (well, almost: there is an
optional <literal>window</literal> specifier, but we will ignore
that). The last field tells whether the port is secure.</para>
@ -592,9 +592,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on</programlisting>
<para>It means that the root account (or any account with a user ID of
0) may login on the port. Insecure ports do not allow root to
login.</para>
<para>How do you use secure and insecure ports?</para>
<para>By marking a port as insecure, the terminal to which it is
connected will not allow root to login. People who know the root
password to your FreeBSD system will first have to login using a
@ -613,7 +613,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on</programlisting>
command records.</para>
<para>Which should you use?</para>
<para>Just use &ldquo;insecure.&rdquo; Use &ldquo;insecure&rdquo;
<emphasis>even</emphasis> for terminals <emphasis>not</emphasis> in
public user areas or behind locked doors. It is quite easy to login
@ -632,7 +632,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<sect3 id="term-hup">
<title>Force <command>init</command> to Reread
<filename>/etc/ttys</filename></title>
<para>When you boot FreeBSD, the first process,
<command>init</command>, will read the
<filename>/etc/ttys</filename> file and start the programs listed
@ -704,7 +704,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
Make sure you have run <command>kill -HUP 1</command>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Garbage appears instead of a login prompt</term>
@ -716,7 +716,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
-HUP 1</command>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Characters appear doubled; the password appears when
typed</term>
@ -744,7 +744,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
specific enough to your environment. The author cannot be responsible if
you damage your system or lose data due to attempting to follow the
suggestions here.</para>
<sect2 id="dialup-prereqs">
<title>Prerequisites</title>
@ -757,7 +757,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<sect3>
<title>FreeBSD Version</title>
<para>First, it is assumed that you are using FreeBSD version 1.1 or
higher (including versions 2.x). FreeBSD version 1.0 included two
different serial drivers, which complicates the situation. Also,
@ -769,9 +769,9 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<sect3>
<title>Terminology</title>
<para>A quick rundown of terminology:</para>
<variablelist>
<varlistentry>
<term>bps</term>
@ -807,12 +807,12 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
</listitem>
</varlistentry>
</variablelist>
<para>If you need more information about these terms and data
communications in general, the author remembers reading that
<emphasis>The RS-232 Bible</emphasis> (anybody have an ISBN?) is a
good reference.</para>
<para>When talking about communications data rates, the author does
not use the term &ldquo;baud&rdquo;. Baud refers to the number of
electrical state transitions that may be made in a period of time,
@ -823,7 +823,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<sect3>
<title>External vs. Internal Modems</title>
<para>External modems seem to be more convenient for dialup, because
external modems often can be semi-permanently configured via
parameters stored in non-volatile RAM and they usually provide
@ -842,7 +842,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<title>Modems and Cables</title>
<para>A background knowledge of these items is assumed</para>
<itemizedlist>
<listitem>
<para>You know how to connect your modem to your computer so that
@ -861,7 +861,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
RAM parameters</para>
</listitem>
</itemizedlist>
<para>The first, connecting your modem, is usually simple &mdash; most
straight-through serial cables work without any problems. You need
to have a cable with appropriate connectors (DB-25 or DB-9, male or
@ -901,7 +901,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<para>Signal Ground (<acronym>SG</acronym>)</para>
</listitem>
</itemizedlist>
<para>FreeBSD needs the <acronym>RTS</acronym> and
<acronym>CTS</acronym> signals for flow-control at speeds above
2400bps, the <acronym>CD</acronym> signal to detect when a call has
@ -930,7 +930,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure # Guest bathroom</pro
<sect3>
<title>Serial Interface Considerations</title>
<para>FreeBSD supports NS8250-, NS16450-, NS16550-, and NS16550A-based
EIA RS-232C (CCITT V.24) communications interfaces. The 8250 and
16450 devices have single-character buffers. The 16550 device
@ -1074,7 +1074,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
&man.config.8; manual page to prepare a kernel building directory,
then build, install, and test the new kernel.</para>
</sect2>
<sect2>
<title>Device Special Files</title>
@ -1103,7 +1103,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
<sect3>
<title>Making Device Special Files</title>
<para>A shell script called <command>MAKEDEV</command> in the
<filename>/dev</filename> directory manages the device special
files. (The manual page for &man.MAKEDEV.8; on FreeBSD 1.1.5 is
@ -1195,12 +1195,12 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen>
<sect3>
<title><filename>/etc/gettytab</filename></title>
<para><filename>/etc/gettytab</filename> is a &man.termcap.5;-style
file of configuration information for &man.getty.8;. Please see the
&man.gettytab.5; manual page for complete information on the
format of the file and the list of capabilities.</para>
<sect4>
<title>Locked-Speed Config</title>
@ -1208,7 +1208,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01</screen>
particular speed, you probably will not need to make any changes
to <filename>/etc/gettytab</filename>.</para>
</sect4>
<sect4>
<title>Matching-Speed Config</title>
@ -1297,7 +1297,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
<sect3 id="dialup-ttys">
<title><filename>/etc/ttys</filename></title>
<para><filename>/etc/ttys</filename> is the list of
<filename>ttys</filename> for <command>init</command> to monitor.
<filename>/etc/ttys</filename> also provides security information to
@ -1350,7 +1350,7 @@ ttyd0 "/usr/libexec/getty xxx" dialup on</programlisting>
first time setting up the system, though, you may want to wait until
your modem(s) are properly configured and connected before signaling
<command>init</command>.</para>
<sect4>
<title>Locked-Speed Config</title>
@ -1370,7 +1370,7 @@ ttyd0 "/usr/libexec/getty std.19200" dialup on</programlisting>
<filename>/etc/gettytab</filename> for your modem's data
rate.</para>
</sect4>
<sect4>
<title>Matching-Speed Config</title>
@ -1391,7 +1391,7 @@ ttyd0 "/usr/libexec/getty V19200" dialup on</programlisting>
<sect3>
<title><filename>/etc/rc.serial</filename> or
<filename>/etc/rc.local</filename></title>
<para>High-speed modems, like V.32, V.32bis, and V.34 modems, need to
use hardware (<filename>RTS/CTS</filename>) flow control. You can
add <command>stty</command> commands to
@ -1447,28 +1447,28 @@ stty -f /dev/ttyd3 crtscts</programlisting>
<listitem>
<para><acronym>CD</acronym> asserted when connected</para>
</listitem>
<listitem>
<para><acronym>DTR</acronym> asserted for operation; dropping DTR
hangs up line &amp; resets modem</para>
</listitem>
<listitem>
<para><acronym>CTS</acronym> transmitted data flow control</para>
</listitem>
<listitem>
<para>Disable <acronym>XON/XOFF</acronym> flow control</para>
</listitem>
<listitem>
<para><acronym>RTS</acronym> received data flow control</para>
</listitem>
<listitem>
<para>Quiet mode (no result codes)</para>
</listitem>
<listitem>
<para>No command echo</para>
</listitem>
@ -1497,32 +1497,32 @@ AT&amp;C1&amp;D2&amp;H1&amp;I0&amp;R2&amp;W</programlisting>
<listitem>
<para>Switch 1: UP &mdash; DTR Normal</para>
</listitem>
<listitem>
<para>Switch 2: Do not care (Verbal Result Codes/Numeric Result
Codes)</para>
</listitem>
<listitem>
<para>Switch 3: UP &mdash; Suppress Result Codes</para>
</listitem>
<listitem>
<para>Switch 4: DOWN &mdash; No echo, offline commands</para>
</listitem>
<listitem>
<para>Switch 5: UP &mdash; Auto Answer</para>
</listitem>
<listitem>
<para>Switch 6: UP &mdash; Carrier Detect Normal</para>
</listitem>
<listitem>
<para>Switch 7: UP &mdash; Load NVRAM Defaults</para>
</listitem>
<listitem>
<para>Switch 8: Do not care (Smart Mode/Dumb Mode)</para>
</listitem>
@ -1537,7 +1537,7 @@ AT&amp;C1&amp;D2&amp;H1&amp;I0&amp;R2&amp;W</programlisting>
<sect3>
<title>Locked-speed Config</title>
<para>For a locked-speed configuration, you will need to configure the
modem to maintain a constant modem-to-computer data rate independent
of the communications rate. On a USR Sportster 14,400 external
@ -1551,7 +1551,7 @@ AT&amp;B1&amp;W</programlisting>
<sect3>
<title>Matching-speed Config</title>
<para>For a variable-speed configuration, you will need to configure
your modem to adjust its serial port data rate to match the incoming
call rate. On a USR Sportster 14,400 external modem, these commands
@ -1566,7 +1566,7 @@ AT&amp;B2&amp;W</programlisting>
<sect3>
<title>Checking the Modem's Configuration</title>
<para>Most high-speed modems provide commands to view the modem's
current operating parameters in a somewhat human-readable fashion.
On the USR Sportster 14,400 external modems, the command
@ -1589,7 +1589,7 @@ AT&amp;B2&amp;W</programlisting>
<sect3>
<title>Checking out the FreeBSD system</title>
<para>Hook up your modem to your FreeBSD system, boot the system, and,
if your modem has status indication lights, watch to see whether the
modem's <acronym>DTR</acronym> indicator lights when the
@ -1603,7 +1603,7 @@ AT&amp;B2&amp;W</programlisting>
ax</command> to see if FreeBSD is trying to run a
<command>getty</command> process on the correct port. You should see
a lines like this among the processes displayed:</para>
<screen> 114 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd0
115 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd1</screen>
@ -1635,7 +1635,7 @@ AT&amp;B2&amp;W</programlisting>
<sect3>
<title>Try Dialing In</title>
<para>Try dialing into the system; be sure to use 8 bits, no parity, 1
stop bit on the remote system. If you do not get a prompt right
away, or get garbage, try pressing <literal>&lt;Enter&gt;</literal>
@ -1649,7 +1649,7 @@ AT&amp;B2&amp;W</programlisting>
<para>If you still cannot get a <prompt>login:</prompt> prompt, check
<filename>/etc/gettytab</filename> again and double-check
that</para>
<itemizedlist>
<listitem>
<para>The initial capability name specified in
@ -1667,7 +1667,7 @@ AT&amp;B2&amp;W</programlisting>
<filename>gettytab</filename> capability name</para>
</listitem>
</itemizedlist>
<para>If you dial but the modem on the FreeBSD system will not answer,
make sure that the modem is configured to answer the phone when
<acronym>DTR</acronym> is asserted. If the modem seems to be
@ -1715,7 +1715,7 @@ AT&amp;B2&amp;W</programlisting>
the Internet if you have problems with PPP. If you need to ftp
something and PPP is broken, use the terminal session to ftp it. Then
use zmodem to transfer it to your machine.</para>
<sect2>
<title>Why cannot I run <command>tip</command> or
<command>cu</command>?</title>
@ -2044,7 +2044,7 @@ raisechar=^^</programlisting>
cable and a null-modem adapter. See <xref linkend="term"> for
a discussion on serial cables.</para>
</step>
<step>
<para>Unplug your keyboard.</para>
@ -2085,7 +2085,7 @@ raisechar=^^</programlisting>
not much good without the keyboard anyway.</para>
</note>
</step>
<step>
<para>Plug a dumb terminal into <devicename>COM1:</devicename>
(<devicename>sio0</devicename>).</para>
@ -2175,7 +2175,7 @@ device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4</programlisting>
<para>If the flags were not set, you need to run UserConfig (on a
different console) or recompile the kernel.</para>
</step>
<step>
<para>Create <filename>boot.config</filename> in the root directory
of the <literal>a</literal> partition on the boot drive.</para>
@ -2259,7 +2259,7 @@ device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4</programlisting>
serial port as the console only during the boot block; the boot
loader will use the internal video display as the console.</para>
</step>
<step>
<para>Boot the machine.</para>
@ -2363,9 +2363,9 @@ boot:</screen>
<sect3>
<title>Case 1: You set the flags to 0x10 for sio0</title>
<programlisting>device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4</programlisting>
<informaltable frame="none">
<tgroup cols="4">
<thead>
@ -2426,7 +2426,7 @@ boot:</screen>
<sect3>
<title>Case 2: You set the flags to 0x30 for sio0</title>
<programlisting>device sio0 at isa? port "IO_COM1" tty flags 0x30 irq 4</programlisting>
<informaltable frame="none">
@ -2493,13 +2493,13 @@ boot:</screen>
<sect3>
<title>Setting A Faster Serial Port Speed</title>
<para>By default the serial port settings are set to 9600 baud, 8
bits, no parity, 1 stop bit. If you wish to change the speed, you
need to recompile at least the boot blocks. Add the following line
to <filename>/etc/make.conf</filename> and compile new boot
blocks:</para>
<programlisting>BOOT_COMCONSOLE_SPEED=19200</programlisting>
<para>If the serial console is configured in some other way than by
@ -2514,7 +2514,7 @@ boot:</screen>
<sect3 id="serialconsole-com2">
<title>Using Serial Port Other Than <devicename>sio0</devicename> For
The Console</title>
<para>Using a port other than <devicename>sio0</devicename> as the
console requires some recompiling. If you want to use another
serial port for whatever reasons, recompile the boot blocks, the
@ -2581,7 +2581,7 @@ boot:</screen>
<sect3>
<title>Entering the DDB Debugger from the Serial Line</title>
<para>If you wish to drop into the kernel debugger from the serial
console (useful for remote diagnostics, but also dangerous if you
generate a spurious BREAK on the serial port!) then you should
@ -2593,7 +2593,7 @@ options DDB</programlisting>
<sect3>
<title>Getting a Login Prompt on the Serial Console</title>
<para>While this is not required, you may wish to get a
<emphasis>login</emphasis> prompt over the serial line, now that you
can see boot messages and can enter the kernel debugging session
@ -2636,7 +2636,7 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
<sect3>
<title>Setting Up the Serial Console</title>
<para>You can easily specify the boot loader and the kernel to use the
serial console by writing just one line in
<filename>/boot/loader.rc</filename>:</para>
@ -2651,7 +2651,7 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
the serial console as early as possible.</para>
<para>Likewise, you can specify the internal console as:</para>
<programlisting>set console=vidconsole</programlisting>
<para>If you do not set the boot loader environment variable
@ -2674,11 +2674,11 @@ start</programlisting>
<programlisting>console=comconsole</programlisting>
<para>or</para>
<programlisting>console=vidconsole</programlisting>
<para>See &man.loader.conf.5; for more information.</para>
<note>
<para>At the moment, the boot loader has no option equivalent to the
<option>-P</option> option in the boot block, and there is no
@ -2690,7 +2690,7 @@ start</programlisting>
<sect3>
<title>Using Serial Port Other than <devicename>sio0</devicename> for
the Console</title>
<para>You need to recompile the boot loader to use a serial port other
than <devicename>sio0</devicename> for the serial console. Follow the
procedure described in <xref linkend="serialconsole-com2">.</para>

54
en_US.ISO_8859-1/books/handbook/staff/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/staff/chapter.sgml,v 1.75 1999/11/04 08:50:31 phantom Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/staff/chapter.sgml,v 1.76 1999/11/04 09:11:53 phantom Exp $
-->
<!--
@ -22,9 +22,9 @@
Directors&rdquo;, responsible for deciding the project's overall goals
and direction as well as managing <link linkend="staff-who">specific
areas</link> of the FreeBSD project landscape.</para>
<para>(in alphabetical order by last name):</para>
<itemizedlist>
<listitem>
<para>&a.asami;</para>
@ -737,11 +737,11 @@
Documentation Project</ulink> is responsible for a number of different
services, each service being run by an individual and his
<emphasis>deputies</emphasis> (if any):</para>
<variablelist>
<varlistentry>
<term>Documentation Project Architect</term>
<listitem>
<para>&a.nik;</para>
</listitem>
@ -749,7 +749,7 @@
<varlistentry>
<term>Webmaster</term>
<listitem>
<para>&a.wosch;</para>
</listitem>
@ -757,7 +757,7 @@
<varlistentry>
<term>Handbook &amp; FAQ Editor</term>
<listitem>
<para>&a.faq;</para>
</listitem>
@ -765,7 +765,7 @@
<varlistentry>
<term>News Editor</term>
<listitem>
<para>-</para>
@ -776,7 +776,7 @@
<varlistentry>
<term>In the Press Editor</term>
<listitem>
<para>&a.jkoshy;</para>
</listitem>
@ -784,7 +784,7 @@
<varlistentry>
<term>FreeBSD Really-Quick NewsLetter Editor</term>
<listitem>
<para>Chris Coleman <email>chrisc@vmunix.com</email></para>
</listitem>
@ -792,7 +792,7 @@
<varlistentry>
<term>Gallery Editor</term>
<listitem>
<para>-</para>
@ -803,7 +803,7 @@
<varlistentry>
<term>Commercial Editor</term>
<listitem>
<para>&a.nik;</para>
</listitem>
@ -811,7 +811,7 @@
<varlistentry>
<term>Web Changes Editor</term>
<listitem>
<para>-</para>
</listitem>
@ -819,7 +819,7 @@
<varlistentry>
<term>User Groups Editor</term>
<listitem>
<para>&a.grog;</para>
</listitem>
@ -827,7 +827,7 @@
<varlistentry>
<term>LinuxDoc to DocBook conversion</term>
<listitem>
<para>&a.nik;</para>
</listitem>
@ -851,7 +851,7 @@
<term><ulink
url="http://www.FreeBSD.org/docproj/docproj.html">Documentation
Project Manager</ulink></term>
<listitem>
<para>&a.nik;</para>
</listitem>
@ -859,14 +859,14 @@
<varlistentry>
<term><link linkend="l10n">Internationalization</link></term>
<listitem>
<para>&a.ache;</para>
</listitem>
</varlistentry>
<varlistentry><term>Networking</term>
<listitem>
<para>&a.wollman;</para>
</listitem>
@ -874,7 +874,7 @@
<varlistentry>
<term><link linkend="eresources-mail">Postmaster</link></term>
<listitem>
<para>&a.jmb;</para>
</listitem>
@ -882,7 +882,7 @@
<varlistentry>
<term>Release Coordinator</term>
<listitem>
<para>&a.jkh;</para>
</listitem>
@ -890,7 +890,7 @@
<varlistentry>
<term>Public Relations &amp; Corporate Liaison</term>
<listitem>
<para>&a.jkh;</para>
</listitem>
@ -899,7 +899,7 @@
<varlistentry>
<term><ulink url="http://www.FreeBSD.org/security/">Security
Officer</ulink></term>
<listitem>
<para>&a.imp;</para>
</listitem>
@ -908,7 +908,7 @@
<varlistentry>
<term><ulink url="http://www.FreeBSD.org/support.html#cvs">Source
Repository Managers</ulink></term>
<listitem>
<para>Principal: &a.peter;</para>
@ -921,7 +921,7 @@
<varlistentry>
<term><ulink url="http://www.FreeBSD.org/ports/">Ports
Manager</ulink></term>
<listitem>
<para>&a.asami;</para>
</listitem>
@ -929,7 +929,7 @@
<varlistentry>
<term>XFree86 Project, Inc. Liaison</term>
<listitem>
<para>&a.rich;</para>
</listitem>
@ -937,7 +937,7 @@
<varlistentry>
<term><link linkend="eresources-news">Usenet Support</link></term>
<listitem>
<para>&a.joerg;</para>
</listitem>
@ -955,7 +955,7 @@
<varlistentry>
<term><ulink
url="http://www.FreeBSD.org/internal/">Webmaster</ulink></term>
<listitem>
<para>&a.wosch;</para>
</listitem>