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

Markup Fixes:

Browse source 
Placed sh, bash, csh, tcsh in <command>
  Placed commands in <command>
  Placed options in <option>
  Placed several commands in man entities
  Placed several applications in <application>
  Placed make vars/targets into <makevar>/<maketarget>
  Placed filenames in <filename>
  <literal>chmod()</literal> -> <function>chmod()</function>

Standardize:
  ATT -> AT&amp;T
  endeavour -> endeavor
  tcl -> Tcl

Reviewed by:	murray
This commit is contained in:
Chern Lee 2001-07-19 23:18:09 +00:00
parent d78ef2bfe3
commit a5c8708c40
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9978
14 changed files with 168 additions and 119 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/backups/chapter.sgml,v 1.34 2001/06/26 20:10:23 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/backups/chapter.sgml,v 1.35 2001/07/19 01:11:42 chern Exp $
-->
<chapter id="backups">
@ -258,7 +258,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
mounting one filesystem onto another. &man.dump.8; does not write
files and directories to tape, but rather writes the data blocks that
are the building blocks of files and directories. &man.dump.8; has
quirks that remain from its early days in Version 6 of ATT Unix (circa
quirks that remain from its early days in Version 6 of AT&amp;T Unix (circa
1975). The default parameters are suitable for 9-track tapes (6250
bpi), not the high-density media available today (up to 62,182 ftpi).
These defaults must be overridden on the command line to utilize the
@ -286,7 +286,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<secondary><command>tar</command></secondary>
</indexterm>
<para>&man.tar.1; also dates back to Version 6 of ATT Unix (circa 1975).
<para>&man.tar.1; also dates back to Version 6 of AT&amp;T Unix (circa 1975).
&man.tar.1; operates in cooperation with the filesystem; &man.tar.1;
writes files and directories to tape. &man.tar.1; does not support the
full range of options that are available from &man.cpio.1;, but

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v 1.29 2001/07/17 02:31:55 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v 1.30 2001/07/19 01:11:44 chern Exp $
-->
<chapter id="basics">
@ -203,15 +203,17 @@
from the input channel and execute them. A lot of shells also have
built in functions to help everyday tasks such a file management,
file globing, command line editing, command macros, and environment
variables. FreeBSD comes with a set of shells, such as sh, the
Bourne Shell, and csh, the C-shell. Many other shells are available
variables. FreeBSD comes with a set of shells, such as
<command>sh</command>, the Bourne Shell, and <command>csh</command>,
the C-shell. Many other shells are available
from the FreeBSD Ports Collection that have much more power, such as
tcsh and bash.</para>
<command>tcsh</command> and <command>bash</command>.</para>
<para>Which shell do you use? It is really a matter of taste. If you
are a C programmer you might feel more comfortable with a C-like shell
such as tcsh. If you've come from Linux or are new to a Unix
command line interface you might try bash. The point is that each
such as <command>tcsh</command>. If you've come from Linux or are new
to a Unix command line interface you might try <command>bash</command>.
The point is that each
shell has unique properties that may or may not work with your
preferred working environment, and that you have a choice of what
shell to use.</para>
@ -320,13 +322,16 @@
<indexterm><primary>Bourne shells</primary></indexterm>
<para>To view or set an environment variable differs somewhat from
shell to shell. For example, in the C-Style shells such as tcsh
and csh, you would use <command>setenv</command> to set and view
environment variables. Under Bourne shells such as sh and bash, you
would use <command>set</command> and <command>export</command> to
view and set your current environment variables. For example, to
set or modify the <envar>EDITOR</envar> environment variable, under
csh or tcsh a command like this would set <envar>EDITOR</envar> to
shell to shell. For example, in the C-Style shells such as
<command>tcsh</command> and <command>csh</command>, you would use
<command>setenv</command> to set and view environment variables.
Under Bourne shells such as <command>sh</command> and
<command>bash</command>, you would use <command>set</command> and
<command>export</command> to view and set your current environment
variables. For example, to set or modify the
<envar>EDITOR</envar> environment variable, under <command>csh</command> or
<command>tcsh</command> a
command like this would set <envar>EDITOR</envar> to
<filename>/usr/local/bin/emacs</filename>:</para>
<screen>&prompt.user; <userinput>setenv EDITOR /usr/local/bin/emacs</userinput></screen>
@ -418,7 +423,8 @@
line <command>ee filename</command> where
<literal>filename</literal> is the name of the file to be edited.
For example, to edit <filename>/etc/rc.conf</filename>, type in
<command>ee /etc/rc.conf</command>. Once inside of ee, all of the
<command>ee /etc/rc.conf</command>. Once inside of
<command>ee</command>, all of the
commands for manipulating the editor's functions are listed at the
top of the display. The caret <literal>^</literal> character means
the control key on the keyboard, so ^e expands to pressing the
@ -514,10 +520,11 @@
</orderedlist>
<para>In some cases, the same topic may appear in more than one
section of the online manual. For example, there is a chmod user
command and a <literal>chmod()</literal> system call. In this
case, you can tell the man command which one you want by
specifying the section:</para>
section of the online manual. For example, there is a
<command>chmod</command> user command and a
<function>chmod()</function> system call. In this case, you can
tell the man command which one you want by specifying the
section:</para>
<screen>&prompt.user; <userinput>man 1 chmod</userinput></screen>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.6 2001/07/19 01:11:50 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.7 2001/07/19 13:56:12 dd Exp $
-->
<chapter id="config-tuning">
@ -280,7 +280,7 @@
<filename>/usr/local/etc/rc.d</filename> which is invoked at
system startup with a 'start' argument, and at system shutdown
with a 'stop' argument. This is the recommended way for
starting systemwide services that are to be run as root, or that
starting system-wide services that are to be run as root, or that
expect to be started as root. These scripts are registered as
part of the installation of the package, and will be removed
when the package is removed.</para>
@ -335,13 +335,13 @@ exit 0
<para>It is also possible to use the &man.cron.8; daemon to start
system services. This approach has a number of advantages, not
least being that because cron runs these processes as the owner
of the crontab, services may be started and maintained by
non-root users.</para>
<para>This takes advantage of an undocumented feature of cron; the
least being that because &man.cron.8; runs these processes as the
owner of the <command>crontab</command>, services may be started
and maintained by non-root users.</para>
<para>This takes advantage of an undocumented feature of &man.cron.8; the
time specification may be replaced by '@reboot', which will
cause the job to be run when cron is started shortly after
cause the job to be run when &man.cron.8; is started shortly after
system boot.</para>
</sect1>
@ -622,7 +622,7 @@ cron.* /var/log/cron
<filename>logfile</filename> is moved to
<filename>logfile.1</filename>, <filename>logfile.1</filename>
is moved to <filename>logfile.2</filename>, and so on.
Additionally, the log files may be archived in gzip format
Additionally, the log files may be archived in &man.gzip.1; format
causing them to be named: logfile.0.gz, logfile.1.gz, and so
on.</para>
@ -802,8 +802,8 @@ kern.maxfiles: 2088 -> 5000</screen>
crash you may lose more work than otherwise. Secondly, softupdates
delays the freeing of filesystem blocks. If you have a filesystem
(such as the root filesystem) which is close to full, doing a major
update of it, e.g. make installworld, can run it out of space and
cause the update to fail.</para>
update of it, e.g. <command>make installworld</command>, can run it
out of space and cause the update to fail.</para>
</sect2>
</sect1>
@ -825,7 +825,7 @@ kern.maxfiles: 2088 -> 5000</screen>
indicates the maximum number of file descriptors on your
system. When the file descriptor table is full,
<literal>file: table is full</literal> will show up repeatedly
in dmesg.</para>
in <command>dmesg</command>.</para>
<para>Each open file, socket, or fifo uses one file
descriptor. A large-scale production server may easily
@ -833,9 +833,9 @@ kern.maxfiles: 2088 -> 5000</screen>
kind and number of services running concurrently.</para>
<para><varname>kern.maxfile</varname>'s default value is
dictated by the maxusers option in your kernel config.
<varname>kern.maxfiles</varname> grows proportionally to the
value of maxusers.</para>
dictated by the <option>maxusers</option> option in your
kernel config. <varname>kern.maxfiles</varname> grows
proportionally to the value of <option>maxusers</option>.</para>
</sect3>
</sect2>
</sect1>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.75 2001/07/14 02:21:05 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.76 2001/07/17 23:33:26 chern Exp $
-->
<chapter id="cutting-edge">
@ -178,7 +178,8 @@ subscribe cvs-all</programlisting>
supfile</ulink>. This is the second most recommended
method, since it allows you to grab the entire
collection once and then only what has changed from then
on. Many people run cvsup from cron and keep their
on. Many people run <command>cvsup</command> from
<command>cron</command> and keep their
sources up-to-date automatically. For a fairly easy
interface to this, simply type:</para>
@ -284,7 +285,7 @@ subscribe cvs-all</programlisting>
security advisory for FreeBSD explains how to fix the problem for
the releases it affects.</para>
<para>Although we endeavour to ensure that the &os.stable; branch
<para>Although we endeavor to ensure that the &os.stable; branch
compiles and runs at all times, this cannot be guaranteed. In
addition, while code is developed in &os.current; before including
it in &os.stable;, more people run &os.stable; than &os.current;, so
@ -377,7 +378,8 @@ subscribe cvs-all</programlisting>
supfile</ulink>. This is the second most recommended
method, since it allows you to grab the entire
collection once and then only what has changed from then
on. Many people run cvsup from cron to keep their
on. Many people run <command>cvsup</command> from
<command>cron</command> to keep their
sources up-to-date automatically. For a fairly easy
interface to this, simply type:</para>
@ -460,7 +462,8 @@ subscribe cvs-all</programlisting>
<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> the user (or a cron script) invokes
<application>CVSup</application> the user (or a
<command>cron</command> script) invokes
the <command>cvsup</command> program, and it interacts with a
<command>cvsupd</command> server somewhere to bring your files
up-to-date. The updates you receive are up-to-the-minute and you
@ -602,7 +605,8 @@ subscribe cvs-all</programlisting>
<filename>/etc/defaults/make.conf</filename> to
<filename>/etc/make.conf</filename> and uncomment them.</para>
<para>Examine the other definitions (COPTFLAGS, NOPORTDOCS and so
<para>Examine the other definitions (<makevar>COPTFLAGS</makevar>,
<makevar>NOPORTDOCS</makevar> and so
on) and decide if they are relevant to you.</para>
</sect2>
@ -1402,10 +1406,11 @@ Building everything..
<answer>
<para>This is a fairly easy task, and can save hours of compile
time for many machines. Simply run the buildworld on a central
time for many machines. Simply run the
<makevar>buildworld</makevar> on a central
machine, and then NFS mount <filename>/usr/src</filename> and
<filename>/usr/obj</filename> on the remote machine and
installworld there.</para>
<makevar>installworld</makevar> there.</para>
</answer>
</qandaentry>
@ -1429,7 +1434,7 @@ Building everything..
<listitem>
<para>Better still, put these filesystems across multiple
disks using the <quote>ccd</quote> (concatenated disk
disks using the &man.ccd.4 (concatenated disk
driver) device.</para>
</listitem>
@ -1441,7 +1446,7 @@ Building everything..
<listitem>
<para>Also in <filename>/etc/make.conf</filename>, set
<quote>CFLAGS</quote> to something like <quote>-O
<makevar>CFLAGS</makevar> to something like <quote>-O
-pipe</quote>. The optimization <quote>-O2</quote> is much
slower, and the optimization difference between
<quote>-O</quote> and <quote>-O2</quote> is normally
@ -1459,7 +1464,7 @@ Building everything..
<listitem><para>The filesystem holding
<filename>/usr/src</filename> can be mounted (or remounted)
with the <quote>noatime</quote> option. This prevents the
with the <option>noatime</option> option. This prevents the
filesystem from recording the file access time. You probably
do not need this information anyway.

14
en_US.ISO8859-1/books/handbook/disks/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.37 2001/07/16 15:02:50 nik Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.38 2001/07/19 01:11:52 chern Exp $
-->
<chapter id="disks">
@ -30,7 +30,9 @@
master</quote>. This is especially convenient for some users who have
found that the simplest and cheapest way to keep a system backup is to
buy an identical second hard drive, and perform routine copies of the
first drive to the second drive using Ghost or XCOPY. Then, if the
first drive to the second drive using
<application>Ghost</application> or <application>XCOPY</application>
. Then, if the
first drive fails, or is attacked by a virus, or is scribbled upon by an
operating system defect, he can easily recover by instructing the BIOS
to logically swap the drives. It's like switching the cables on the
@ -422,7 +424,7 @@
<secondary>unmounting</secondary>
</indexterm>
<para>The umount command takes, as a parameter, one of a
<para>The &man.umount.8; command takes, as a parameter, one of a
mountpoint, a device name, or the <option>-a</option> or
<option>-A</option> option.</para>
@ -515,8 +517,8 @@
use the entire disk for FreeBSD. When asked if you want to
<quote>remain cooperative with any future possible operating
systems</quote>, answer <literal>YES</literal>. Write the
changes to the disk using <command>W</command>. Now exit the
FDISK editor using <command>q</command>. Next you will be
changes to the disk using <userinput>W</userinput>. Now exit the
FDISK editor using <userinput>q</userinput>. Next you will be
asked about the Master Boot Record. Since you are adding a
disk to an already running system, choose
<literal>None</literal>.</para>
@ -693,7 +695,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
<secondary>memory filesystem</secondary>
</indexterm>
<para>md is a simple, efficient means to do memory
<para><devicename>md</devicename> is a simple, efficient means to do memory
filesystems.</para>
<para>Simply take a filesystem you've prepared with, for

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml,v 1.59 2001/07/08 01:13:22 dd Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml,v 1.60 2001/07/19 10:31:01 billf Exp $
-->
<appendix id="eresources">
@ -561,7 +561,8 @@ help
subscriber overlap and except for the most esoteric mixes (say
"-stable &amp; -scsi"), there really is no reason to post to more
than one list at a time. If a message is sent to you in such a
way that multiple mailing lists appear on the Cc line then the Cc
way that multiple mailing lists appear on the
<literal>Cc</literal> line then the <literal>Cc</literal>
line should also be trimmed before sending it out again.
<emphasis>You are <emphasis>still</emphasis> responsible for your
own cross-postings, no matter who the originator might have
@ -664,7 +665,7 @@ help
review any code changes.</para>
<para>This list is very heavy on patches, and is probably of no
intrest to the average FreeBSD user. Security discussions
interest to the average FreeBSD user. Security discussions
not related to a particular code change are held on
freebsd-security. Conversely, all developers are encouraged
to send their patches here for review, especially if they

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml,v 1.57 2001/07/17 00:11:20 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml,v 1.58 2001/07/19 12:03:00 dd Exp $
-->
<chapter id="l10n">
@ -426,7 +426,8 @@ keychange="<replaceable>fkey_number sequence</replaceable>"</programlisting>
character matrix in pseudographics area, i.e., to move letters out
of that area if screen font uses a bit 8 column.</para>
<para>If you have the moused daemon enabled by setting the following
<para>If you have the <application>moused daemon</application>
enabled by setting the following
in your <filename>/etc/rc.conf</filename>:</para>
<programlisting>moused_enable="YES"</programlisting>
@ -617,7 +618,8 @@ keychange="<replaceable>fkey_number sequence</replaceable>"</programlisting>
consideration.</para>
<indexterm><primary>MySQL</primary></indexterm>
<para>However, some applications such as MySQL need to be have the
<para>However, some applications such as
<application>MySQL</application> need to be have the
<filename>Makefile</filename> configured with the specific
charset. This is usually done in the
<filename>Makefile</filename> or done by passing a value to

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v 1.130 2001/07/04 18:22:36 jdp Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v 1.131 2001/07/06 13:03:03 dd Exp $
-->
<appendix id="mirrors">
@ -1351,7 +1351,7 @@
automatic email. The sizes of the updates are always kept as
small as possible. This is typically less than 5K, with an
occasional (one in ten) being 10-50K and every now and then a
biggie of 100K+ or more coming around.</para>
large 100K+ or more coming around.</para>
<para>You will also need to make yourself aware of the various
caveats related to working directly from the development sources
@ -1400,7 +1400,7 @@
<para>Send email to &a.majordomo; to subscribe to one of the
<application>CTM</application> distribution lists.
&ldquo;ctm-cvs-cur&rdquo; supports the entire cvs tree.
&ldquo;ctm-cvs-cur&rdquo; supports the entire CVS tree.
&ldquo;ctm-src-cur&rdquo; supports the head of the development
branch. &ldquo;ctm-src-2_2&rdquo; supports the 2.2 release
branch, etc.. (If you do not know how to subscribe yourself
@ -1477,7 +1477,7 @@
<para><application>CTM</application> understands deltas which have
been put through <command>gzip</command>, so you do not need to
gunzip them first, this saves disk space.</para>
<command>gunzip</command> them first, this saves disk space.</para>
<para>Unless it feels very secure about the entire process,
<application>CTM</application> will not touch your tree. To
@ -1739,7 +1739,8 @@
system, which takes a substantial amount of time, memory, and
disk space to build.</para>
<para>If you do not know anything about cvsup at all and want a
<para>If you do not know anything about
<application>CVSup</application> at all and want a
single package which will install it, set up the configuration
file and start the transfer via a pointy-clicky type of
interface, then get the <ulink
@ -1861,9 +1862,10 @@
<para>With <application>CVSup</application>, you can receive
virtually any version of the sources that ever existed.
That is possible because the cvsupd server works directly
from the CVS repository, which contains all of the versions.
You specify which one of them you want using the
That is possible because the
<application>cvsupd</application> server works directly from
the CVS repository, which contains all of the versions. You
specify which one of them you want using the
<literal>tag=</literal> and <option>date=</option> value
fields.</para>
@ -1871,7 +1873,8 @@
<para>Be very careful to specify any <literal>tag=</literal>
fields correctly. Some tags are valid only for certain
collections of files. If you specify an incorrect or
misspelled tag, CVSup will delete files which you probably
misspelled tag, <application>CVSup</application>
will delete files which you probably
do not want deleted. In particular, use <emphasis>only
</emphasis> <literal>tag=.</literal> for the
<literal>ports-*</literal> collections.</para>
@ -2127,7 +2130,8 @@
<programlisting>*default host=cvsup666.FreeBSD.org</programlisting>
<para>You will need to change the host to one that actually
exists before running CVSup. On any particular run of
exists before running <application>CVSup</application>.
On any particular run of
<command>cvsup</command>, you can override the host setting
on the command line, with <option>-h
<replaceable>hostname</replaceable></option>.</para>
@ -2152,7 +2156,8 @@
<para><anchor id="cvsup-config-status">Where should
<command>cvsup</command> maintain its status files?</para>
<para>The cvsup client maintains certain status files in what
<para>The <application>CVSup</application> client maintains
certain status files in what
is called the <quote>base</quote> directory. These files
help <application>CVSup</application> to work more
efficiently, by keeping track of which updates you have
@ -2339,11 +2344,13 @@ src-all</programlisting>
<screen>&prompt.root; <userinput>cvsup -g -L 2 supfile</userinput></screen>
<para>The <option>-g</option> tells cvsup not to use its GUI.
This is automatic if you are not running X11, but otherwise you
have to specify it.</para>
<para>The <option>-g</option> tells
<application>CVSup</application> not to use its GUI. This is
automatic if you are not running X11, but otherwise you have to
specify it.</para>
<para>The <option>-L 2</option> tells cvsup to print out the
<para>The <option>-L 2</option> tells
<application>CVSup</application> to print out the
details of all the file updates it is doing. There are three
levels of verbosity, from <option>-L 0</option> to
<option>-L 2</option>. The default is 0, which means total
@ -2354,9 +2361,10 @@ src-all</programlisting>
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 cron.</para>
can arrange for regular runs of <application>CVSup</application>
using &man.cron.8;.
Obviously, you should not let <application>CVSup</application>
use its GUI when running it from &man.cron.8;.</para>
</sect2>
<sect2 id="cvsup-collec">
@ -3083,8 +3091,9 @@ src-all</programlisting>
<term><literal>distrib release=self</literal></term>
<listitem>
<para>The CVSup server's own configuration files. Used by
CVSup mirror sites.</para>
<para>The <application>CVSup</application> server's own
configuration files. Used by <application>CVSup</application>
mirror sites.</para>
</listitem>
</varlistentry>
@ -3118,7 +3127,8 @@ src-all</programlisting>
<sect2>
<title>For more information</title>
<para>For the CVSup FAQ and other information about CVSup, see
<para>For the <application>CVSup</application> FAQ and other
information about <application>CVSup</application>, see
<ulink url="http://www.polstra.com/projects/freeware/CVSup/">The
CVSup Home Page</ulink>.</para>

5
en_US.ISO8859-1/books/handbook/multimedia/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/sound/chapter.sgml,v 1.6 2001/06/25 22:06:44 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/sound/chapter.sgml,v 1.7 2001/07/06 13:03:06 dd Exp $
-->
<chapter id="sound">
@ -318,7 +318,8 @@ pcm0: &lt;Aureal Vortex 8830&gt; at memory 0xfeb40000 irq 5 (4p/1r +channels dup
<qandaentry>
<question>
<para>I get a "xxx: gus pcm not attached, out of memory"
<para>I get a <errorname>xxx: gus pcm not attached, out of
memory</errorname>
error. What causes that?</para>
</question>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/policies/chapter.sgml,v 1.20 2001/07/13 22:21:27 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/policies/chapter.sgml,v 1.21 2001/07/17 22:20:50 chern Exp $
-->
<chapter id="policies">
@ -58,7 +58,8 @@
<para>Some parts of the FreeBSD distribution consist of software that is
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>
examples are <command>perl</command>, <command>gcc</command> and
<command>patch</command>.</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
@ -107,13 +108,14 @@
<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
<para><filename>src/usr.bin/tclsh</filename> contains only a
<command>bmake</command> 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.
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
@ -121,7 +123,8 @@
the rules: It is supposed to contain the sources as distributed (on a
proper CVS vendor-branch and without RCS keyword expansion) with as few
FreeBSD-specific changes as possible. The 'easy-import' tool on
freefall will assist in doing the import, but if there are any doubts on
<hostid>freefall</hostid> will assist in doing the import, but if there
are any doubts on
how to go about it, it is imperative that you ask first and not blunder
ahead and hope it <quote>works out</quote>. CVS is not forgiving of
import accidents and a fair amount of effort is required to back out

23
en_US.ISO8859-1/books/handbook/ports/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml,v 1.126 2001/07/17 02:45:19 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml,v 1.127 2001/07/19 13:55:58 dd Exp $
-->
<chapter id="ports">
@ -15,7 +15,8 @@
everything you need. If that is not what you are planning to do with
FreeBSD then you will probably want to install additional
software&mdash;perhaps a web server, or a mail reader, or a graphical
environment such as KDE or GNOME.</para>
environment such as <application>KDE</application> or
<application>GNOME</application>.</para>
<para>If you have used a Unix system before you will know that the typical
procedure for installing third party software goes something like
@ -467,7 +468,8 @@ docbook =
<screen>&prompt.root; <userinput>whereis xchat</userinput>
xchat: /usr/ports/irc/xchat</screen>
<para>This tells us that xchat (an irc client) can be found in the
<para>This tells us that <command>xchat</command> (an irc client)
can be found in the
<filename>/usr/ports/irc/xchat</filename> directory.</para>
<para>Yet another way of finding a particular port is by using the
@ -476,7 +478,8 @@ xchat: /usr/ports/irc/xchat</screen>
<filename>/usr/ports</filename> directory. Once in that
directory, run <command>make search key=program-name</command>
where <quote>program-name</quote> is the name of the program you
want to find. For example, if you were looking for xchat:</para>
want to find. For example, if you were looking for
<command>xchat</command>:</para>
<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
&prompt.root; <userinput>make search key=xchat</userinput>
@ -520,7 +523,8 @@ R-deps: XFree86-3.3.5 gettext-0.10.35 giflib-4.1.0 glib-1.2.6 gtk-1.2.6 imlib-1.
<screen>&prompt.root; <userinput>cd /usr/ports/irc/xchat</userinput></screen>
<para>Once inside the xchat directory, you will see the port
<para>Once inside the <filename>xchat</filename> directory,
you will see the port
skeleton. The next step is to compile (also called build) the
port. This is done by simply typing <command>make</command> at
the prompt. Once you have done so, you should see something
@ -655,12 +659,14 @@ Receiving xchat-1.3.8.tar.bz2 (305543 bytes): 100%
later on you decide that you installed the wrong port. The next
few paragraphs will cover just that.</para>
<para>Now we will remove our previous example (which was xchat for
<para>Now we will remove our previous example (which was
<command>xchat</command> for
those of you not paying attention). As with installing ports,
the first thing you must do is change to the port directory,
which if you remember was
<filename>/usr/ports/irc/xchat</filename>. After you change
directories, you are ready to uninstall xchat. This is done with
directories, you are ready to uninstall <command>xchat</command>.
This is done with
the <command>make deinstall</command> command (makes sense
right?):</para>
@ -669,7 +675,8 @@ Receiving xchat-1.3.8.tar.bz2 (305543 bytes): 100%
===&gt; Deinstalling for xchat-1.3.8
&prompt.root;</screen>
<para>That was easy enough. You have now managed to remove xchat
<para>That was easy enough. You have now managed to remove
<command>xchat</command>
from your system. If you would like to reinstall it, you can do
so by running <command>make reinstall</command> from the
<filename>/usr/ports/irc/xchat</filename> directory.</para>

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.38 2001/07/17 00:11:23 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.39 2001/07/17 22:20:51 chern Exp $
-->
<chapter id="ppp-and-slip">
@ -647,7 +647,7 @@ protocol: ppp</screen>
</varlistentry>
</variablelist>
<para>See the pmdemand entry in the files
<para>See the <literal>pmdemand</literal> entry in the files
<filename>/usr/share/examples/ppp/ppp.conf.sample</filename> and
<filename>/usr/share/examples/ppp/ppp.linkup.sample</filename> for a
detailed example.</para>
@ -682,7 +682,7 @@ protocol: ppp</screen>
<para><link linkend="dialup">Configuring FreeBSD for Dial-up
Services</link> provides a good description on enabling
dial-up services using getty.</para>
dial-up services using &man.getty.8;.</para>
<para>An alternative to <command>getty</command> is <ulink
url="http://www.leo.org/~doering/mgetty/index.html">mgetty</ulink>,
@ -1435,8 +1435,8 @@ exit</programlisting>
<para>Here is an alternate method using <command>chat</command>
instead of <command>kermit</command>.</para>
<para>The following two files are sufficient to accomplish a pppd
connection.</para>
<para>The following two files are sufficient to accomplish a
<command>pppd</command> connection.</para>
<para><filename>/etc/ppp/options</filename>:</para>
@ -1734,7 +1734,7 @@ exit 1
<itemizedlist>
<listitem>
<para>options NETGRAPH</para>
<para><option>options NETGRAPH</option></para>
</listitem>
</itemizedlist>
@ -1742,10 +1742,10 @@ exit 1
<itemizedlist>
<listitem>
<para>options NETGRAPH_PPPOE</para>
<para><option>options NETGRAPH_PPPOE</option></para>
</listitem>
<listitem>
<para>options NETGRAPH_SOCKET</para>
<para><option>options NETGRAPH_SOCKET</option></para>
</listitem>
</itemizedlist>
@ -1823,7 +1823,8 @@ ppp_profile="default" # or your provider</programlisting>
<para>Since it does not follow the specification, FreeBSD's PPPoE
implementation will not talk to it. It is very likely that it will
not work under other unixes for that same reason. Complain to <ulink
not work under other Unix systems for that same reason.
Complain to <ulink
url="http://www.3com.com/">3Com</ulink> if you think it should
comply with the PPPoE specification.</para>
@ -2142,7 +2143,8 @@ nameserver 128.32.136.12</programlisting>
</step>
<step>
<para>Set the password for root and toor (and any other
<para>Set the password for <username>root</username> and
<username>toor</username> (and any other
accounts that do not have a password). Use passwd or
&man.vipw.8;, do not edit the
<filename>/etc/passwd</filename> or
@ -2201,7 +2203,8 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
<para>If you are able to <command>ping</command> hosts on the
other side of the router, you are connected! If it does not
work, you might want to try <option>-a</option> instead of
<option>-c</option> as an argument to slattach.</para>
<option>-c</option> as an argument to
<command>slattach</command>.</para>
</step>
</procedure>
</sect3>
@ -2213,13 +2216,14 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
<screen>&prompt.root; <userinput>kill -INT `cat /var/run/slattach.modem.pid`</userinput></screen>
<para>to kill slattach. Keep in mind you must be
<para>to kill <command>slattach</command>. Keep in mind you must be
<username>root</username> to do the above. Then go back to
kermit (<command>fg</command> if you suspended it) and exit from
it (<command>q</command>).</para>
<para>The slattach man page says you have to use <command>ifconfig
sl0 down</command> to mark the interface down, but this does not
<para>The <command>slattach</command> man page says you have
to use <command>ifconfig sl0 down</command>
to mark the interface down, but this does not
seem to make any difference for me.
(<command>ifconfig sl0</command> reports the same thing.)</para>
@ -2237,7 +2241,8 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
<itemizedlist>
<listitem>
<para>Not using <option>-c</option> or <option>-a</option> in
slattach (I have no idea why this can be fatal, but adding
<command>slattach</command> (I have no idea why this
can be fatal, but adding
this flag solved the problem for at least one
person).</para>
</listitem>

5
en_US.ISO8859-1/books/handbook/sound/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/sound/chapter.sgml,v 1.6 2001/06/25 22:06:44 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/sound/chapter.sgml,v 1.7 2001/07/06 13:03:06 dd Exp $
-->
<chapter id="sound">
@ -318,7 +318,8 @@ pcm0: &lt;Aureal Vortex 8830&gt; at memory 0xfeb40000 irq 5 (4p/1r +channels dup
<qandaentry>
<question>
<para>I get a "xxx: gus pcm not attached, out of memory"
<para>I get a <errorname>xxx: gus pcm not attached, out of
memory</errorname>
error. What causes that?</para>
</question>

19
en_US.ISO8859-1/books/handbook/users/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/users/chapter.sgml,v 1.15 2001/07/17 23:33:28 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/users/chapter.sgml,v 1.16 2001/07/19 13:55:38 dd Exp $
-->
<chapter id="users">
@ -173,7 +173,8 @@
<para>To create the initial configuration file, use
<command>adduser -s -config_create</command>.
<footnote>
<para>The <option>-s</option> makes adduser default to
<para>The <option>-s</option> makes <command>adduser</command>
default to
quiet. We use <option>-v</option> later when we want to
change defaults.</para>
</footnote>
@ -362,7 +363,8 @@ Removing files belonging to jru from /var/tmp/vi.recover: done.
information.</para>
<para>Only system administrators, as the superuser, may change
other users' information and passwords with chpass.</para>
other users' information and passwords with
<command>chpass</command>.</para>
<para>When passed no options, aside from an optional username,
<command>chpass</command> displays an editor
@ -407,7 +409,8 @@ Other information:</screen>
<note>
<para><command>chfn</command> and <command>chsh</command> are
just links to chpass, as are <command>ypchpass</command>,
just links to <command>chpass</command>, as
are <command>ypchpass</command>,
<command>ypchfn</command>, and
<command>ypchsh</command>. NIS support is automatic, so
specifying the <literal>yp</literal> before the command is
@ -603,7 +606,8 @@ passwd: done</screen>
running. This includes foreground and background processes
alike. For obvious reasons, this may not be larger than the
system limit specified by the <literal>kern.maxproc</literal>
sysctl. Also note that setting this too small may hinder a
<command>sysctl</command>. Also note that setting this
too small may hinder a
user's productivity: it is often useful to be logged in
multiple times or execute pipelines. Some tasks, such as
compiling a large program, also spawn multiple processes (e.g.,
@ -658,7 +662,7 @@ passwd: done</screen>
open. In FreeBSD, files are also used to represent sockets and
IPC channels; thus, be careful not to set this too low. The
system-wide limit for this is defined by the
<literal>kern.maxfiles</literal> sysctl.</para>
<literal>kern.maxfiles</literal> <command>sysctl</command>.</para>
</listitem>
</varlistentry>
@ -724,7 +728,8 @@ passwd: done</screen>
<listitem>
<para>Remember that many limits apply to individual processes, not
the user as a whole. For example, setting openfiles to 50 means
the user as a whole. For example, setting
<varname>openfiles</varname> to 50 means
that each process the user runs may open up to 50 files. Thus,
the gross amount of files a user may open is the value of
<literal>openfiles</literal> multiplied by the value of