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

Start producing output in the form of <chapter name><section id>.html.

Browse source 
Not objected to by:	-doc
Reviewed by:		ceri, hrs, brueffer
This commit is contained in:
Tom Rhodes 2003-05-20 14:45:34 +00:00
parent 98432520c2
commit b28e47038e
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=16992
4 changed files with 49 additions and 49 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -83,7 +83,7 @@
</itemizedlist>
</sect1>
<sect1 id="routing">
<sect1 id="network-routing">
<sect1info>
<authorgroup>
<author>
@ -138,7 +138,7 @@ host2.example.com link#1 UC 0 0
<indexterm><primary>default route</primary></indexterm>
<para>The first two lines specify the default route (which we
will cover in the <link linkend="routing-default">next
will cover in the <link linkend="network-routing-default">next
section</link>) and the <hostid>localhost</hostid> route.</para>
<indexterm><primary>loopback device</primary></indexterm>
@ -256,7 +256,7 @@ host2.example.com link#1 UC 0 0
</informaltable>
</sect2>
<sect2 id="routing-default">
<sect2 id="network-routing-default">
<title>Default Routes</title>
<indexterm><primary>default route</primary></indexterm>
@ -392,7 +392,7 @@ host2.example.com link#1 UC 0 0
this ability.</para>
</sect2>
<sect2 id="dedicated-router">
<sect2 id="network-dedicated-router">
<title>Building a Router</title>
<indexterm><primary>router</primary></indexterm>
@ -484,7 +484,7 @@ host2.example.com link#1 UC 0 0
</sect2>
</sect1>
<sect1 id="wireless">
<sect1 id="network-wireless">
<sect1info>
<authorgroup>
<author>
@ -624,7 +624,7 @@ wi0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
<para>It should not have produced any errors when loading the
module. If it did, you may need to compile the
&man.bridge.4; code into your kernel. The <link
linkend="bridging">Bridging</link> section of the handbook
linkend="network-bridging">Bridging</link> section of the handbook
should be able to help you accomplish that task.</para>
<para>Now that you have the bridging stuff done, we need to
@ -905,7 +905,7 @@ wi0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
</sect1>
<sect1 id="bridging">
<sect1 id="network-bridging">
<sect1info>
<authorgroup>
<author>
@ -1088,7 +1088,7 @@ wi0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
</sect2>
</sect1>
<sect1 id="nfs">
<sect1 id="network-nfs">
<sect1info>
<authorgroup>
<author>
@ -1203,7 +1203,7 @@ wi0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
</para>
</sect2>
<sect2 id="configuring-nfs">
<sect2 id="network-configuring-nfs">
<title>Configuring <acronym>NFS</acronym></title>
<indexterm>
<primary>NFS</primary>
@ -1415,7 +1415,7 @@ mountd_flags="-r"</programlisting>
</itemizedlist>
</sect2>
<sect2 id="amd">
<sect2 id="network-amd">
<sect2info>
<authorgroup>
<author>
@ -1505,7 +1505,7 @@ Exports list on foobar:
information.</para>
</sect2>
<sect2 id="nfs-integration">
<sect2 id="network-nfs-integration">
<sect2info>
<authorgroup>
<author>
@ -1620,7 +1620,7 @@ Exports list on foobar:
</sect2>
</sect1>
<sect1 id="diskless">
<sect1 id="network-diskless">
<sect1info>
<authorgroup>
<author>
@ -2114,7 +2114,7 @@ Exports list on foobar:
</sect2>
</sect1>
<sect1 id="isdn">
<sect1 id="network-isdn">
<title>ISDN</title>
<para>A good resource for information on ISDN technology and hardware is
@ -2148,7 +2148,7 @@ Exports list on foobar:
choose. The following options are listed from least expensive to most
expensive.</para>
<sect2 id="isdn-cards">
<sect2 id="network-isdn-cards">
<sect2info>
<authorgroup>
<author>
@ -2425,7 +2425,7 @@ ISDN BRI line</literallayout>
</sect2>
</sect1>
<sect1 id="nis">
<sect1 id="network-nis">
<sect1info>
<authorgroup>
<author>
@ -2813,7 +2813,7 @@ ISDN BRI line</literallayout>
<note>
<para>Depending on your NIS setup, you may need to add
further entries. See the <link
linkend="nis-server-is-client">section about NIS servers
linkend="network-nis-server-is-client">section about NIS servers
that are also NIS clients</link>, below, for
details.</para>
</note>
@ -3067,7 +3067,7 @@ nis_client_enable="YES"</programlisting>
<para>This line will afford anyone with a valid account in
the NIS server's password maps an account. There are
many ways to configure your NIS client by changing this
line. See the <link linkend="netgroups">netgroups
line. See the <link linkend="network-netgroups">netgroups
section</link> below for more information.
For more detailed reading see O'Reilly's book on
<literal>Managing NFS and NIS</literal>.</para>
@ -3231,7 +3231,7 @@ nobody:*:65534:65534::0:0:Unprivileged user:/nonexistent:/sbin/nologin
basie&prompt.root;</screen>
</sect2>
<sect2 id="netgroups">
<sect2 id="network-netgroups">
<sect2info>
<authorgroup>
<author>
@ -3695,7 +3695,7 @@ TWO (,hotel,test-domain)
such servers still in use today.</para>
</sect2>
<sect2 id="nis-server-is-client">
<sect2 id="network-nis-server-is-client">
<title>NIS Servers that are also NIS Clients</title>
<para> Care must be taken when running ypserv in a multi-server
@ -3766,7 +3766,7 @@ lrwxr-xr-x 1 root wheel 14 Nov 8 14:27 libscrypt.so@ -> libscrypt.so.2
</sect2>
</sect1>
<sect1 id="dhcp">
<sect1 id="network-dhcp">
<sect1info>
<authorgroup>
<author>
@ -3964,7 +3964,7 @@ dhcp_flags=""</programlisting>
<ulink url="http://www.dhcp.org/">dhcp.org</ulink>.</para>
</sect2>
<sect2 id="dhcp-server">
<sect2 id="network-dhcp-server">
<sect2info>
<authorgroup>
<author>
@ -4189,7 +4189,7 @@ host mailhost {
</sect1>
<sect1 id="dns">
<sect1 id="network-dns">
<sect1info>
<authorgroup>
<author>
@ -4603,7 +4603,7 @@ zone
// chmod 750 /etc/namedb/s</programlisting>
<para>For more information on running BIND in a sandbox, see
<link linkend="named-sandbox">Running named in a sandbox</link>.
<link linkend="network-named-sandbox">Running named in a sandbox</link>.
</para>
<programlisting>/*
@ -4905,7 +4905,7 @@ www IN CNAME @</programlisting>
</para>
</sect2>
<sect2 id="named-sandbox">
<sect2 id="network-named-sandbox">
<sect2info>
<authorgroup>
<author>
@ -5247,7 +5247,7 @@ zone "10.168.192.in-addr.arpa" in {
</sect2>
</sect1>
<sect1 id="ntp">
<sect1 id="network-ntp">
<sect1info>
<authorgroup>
<author>
@ -5477,7 +5477,7 @@ driftfile /var/db/ntp.drift</programlisting>
</sect2>
</sect1>
<sect1 id="natd">
<sect1 id="network-natd">
<sect1info>
<authorgroup>
<author>
@ -5489,7 +5489,7 @@ driftfile /var/db/ntp.drift</programlisting>
</sect1info>
<title>Network Address Translation</title>
<sect2 id="overview">
<sect2 id="network-natoverview">
<title>Overview</title>
<indexterm>
<primary><application>natd</application></primary>
@ -5507,7 +5507,7 @@ driftfile /var/db/ntp.drift</programlisting>
Internet Connection Sharing.</para>
</sect2>
<sect2 id="setup">
<sect2 id="network-natsetup">
<title>Setup</title>
<para>Due to the diminishing IP space in IPv4, and the increased number
of users on high-speed consumer lines such as cable or DSL, people are
@ -5553,7 +5553,7 @@ driftfile /var/db/ntp.drift</programlisting>
machine.</para>
</sect2>
<sect2 id="configuration">
<sect2 id="network-natdkernconfiguration">
<indexterm>
<primary>kernel</primary>
<secondary>configuration</secondary>
@ -5635,7 +5635,7 @@ natd_flags=""</programlisting>
modification for natd to work.</para>
</sect2>
<sect2 id="port-redirection">
<sect2 id="network-natdport-redirection">
<title>Port Redirection</title>
<para>The drawback with natd is that the LAN clients are not accessible
@ -5678,7 +5678,7 @@ natd_flags=""</programlisting>
<para>For further configuration options, consult &man.natd.8;</para>
</sect2>
<sect2 id="address-redirection">
<sect2 id="network-natdaddress-redirection">
<title>Address Redirection</title>
<indexterm><primary>address redirection</primary></indexterm>
<para>Address redirection is useful if several IP addresses are
@ -5731,7 +5731,7 @@ natd_flags=""</programlisting>
</sect2>
</sect1>
<sect1 id="inetd">
<sect1 id="network-inetd">
<sect1info>
<authorgroup>
<author>
@ -5744,7 +5744,7 @@ natd_flags=""</programlisting>
<title>inetd <quote>Super-Server</quote></title>
<sect2 id="inetd-overview">
<sect2 id="network-inetd-overview">
<title>Overview</title>
<para>&man.inetd.8; is referred to as the <quote>Internet
@ -5771,7 +5771,7 @@ natd_flags=""</programlisting>
<filename>/etc/inetd.conf</filename>.</para>
</sect2>
<sect2 id="inetd-settings">
<sect2 id="network-inetd-settings">
<title>Settings</title>
<para><application>inetd</application> is initialized through
@ -5790,7 +5790,7 @@ natd_flags=""</programlisting>
<literal>inetd_flags</literal> option.</para>
</sect2>
<sect2 id="inetd-cmdline">
<sect2 id="network-inetd-cmdline">
<title>Command-Line Options</title>
<para><application>inetd</application> synopsis:</para>
@ -5921,7 +5921,7 @@ natd_flags=""</programlisting>
</sect2>
<sect2 id="inetd-conf">
<sect2 id="network-inetd-conf">
<title><filename>inetd.conf</filename></title>
<para>Configuration of <application>inetd</application> is
@ -5934,7 +5934,7 @@ natd_flags=""</programlisting>
configuration file by sending a HangUP signal to the
<application>inetd</application> process as shown:</para>
<example id="inetd-hangup">
<example id="network-inetd-hangup">
<title>Sending <application>inetd</application> a HangUP Signal</title>
<screen>&prompt.root; <userinput>kill -HUP `cat /var/run/inetd.pid`</userinput></screen>
@ -6131,14 +6131,14 @@ server-program-arguments</programlisting>
</variablelist>
</sect2>
<sect2 id="inetd-security">
<sect2 id="network-inetd-security">
<title>Security</title>
<para>Depending on the security profile chosen at install, many
of <application>inetd</application>'s daemons may be enabled by
default. If there is no apparent need for a particular daemon,
disable it! Place a <quote>#</quote> in front of the daemon in
question, and send a <link linkend="inetd-hangup">hangup signal
question, and send a <link linkend="network-inetd-hangup">hangup signal
to inetd</link>.
Some daemons, such as <application>fingerd</application>, may
not be desired at all because they provide an attacker with too
@ -6157,7 +6157,7 @@ server-program-arguments</programlisting>
invoked daemons.</para>
</sect2>
<sect2 id="inetd-misc">
<sect2 id="network-inetd-misc">
<title>Miscellaneous</title>
<para><application>daytime</application>,
@ -6177,7 +6177,7 @@ server-program-arguments</programlisting>
</sect2>
</sect1>
<sect1 id="plip">
<sect1 id="network-plip">
<title>Parallel Line IP (PLIP)</title>
<indexterm><primary>PLIP</primary></indexterm>
@ -6197,7 +6197,7 @@ server-program-arguments</programlisting>
</listitem>
</itemizedlist>
<sect2 id="create-parallel-cable">
<sect2 id="network-create-parallel-cable">
<title>Creating a Parallel Cable</title>
<para>You can purchase a parallel cable at most computer supply
@ -6320,7 +6320,7 @@ BUSY</literallayout></entry>
</table>
</sect2>
<sect2 id="plip-setup">
<sect2 id="network-plip-setup">
<title>Setting up PLIP</title>
<para>Get a laplink cable.</para>
@ -6388,7 +6388,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
</sect2>
</sect1>
<sect1 id="ipv6">
<sect1 id="network-ipv6">
<sect1info>
<authorgroup>
<author>

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

@ -587,7 +587,7 @@ drwxr-xr-x 2 robert robert 512 Nov 10 11:54 public_html</programlisting>
<para>Another common reason to contain certain directory trees on
other file systems is if they are to be housed on separate
physical disks, or are separate virtual disks, such as <link
linkend="nfs">Network File System</link> mounts, or CDROM
linkend="network-nfs">Network File System</link> mounts, or CDROM
drives.</para>
<sect2 id="disks-fstab">

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

@ -2172,7 +2172,7 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
<secondary>memory</secondary>
</indexterm>
<para>These include network file systems such as the <link
linkend="nfs">Network File System</link> and Coda, memory-based
linkend="network-nfs">Network File System</link> and Coda, memory-based
file systems and
file-backed file systems.</para>

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

@ -3001,7 +3001,7 @@ installation menus to retry whichever operations have failed.
<para>Selecting <guibutton>[ Yes ]</guibutton> will execute
<application>dhclient</application>, and if successful, will fill
in the network configuration information automatically. Refer to
<xref linkend="dhcp"> for more information.</para>
<xref linkend="network-dhcp"> for more information.</para>
<para>The following Network Configuration screen shows the
configuration of the Ethernet device for a system that will act
@ -3143,7 +3143,7 @@ Do you want to configure inetd and the network services that it provides?
<para>These services can be enabled after installation by editing
<filename>/etc/inetd.conf</filename> with your favorite text editor.
See <xref linkend="inetd-overview"> for more information.</para>
See <xref linkend="network-inetd-overview"> for more information.</para>
<para>Select <guibutton>[ Yes ]</guibutton> if you wish to
configure these services during install. An additional
@ -3298,7 +3298,7 @@ Upload subdirectory:
<para>Network File Services (NFS) allows sharing of files across a
network. A machine can be configured as a server, a client, or
both. Refer to <xref linkend="nfs"> for a more information.</para>
both. Refer to <xref linkend="network-nfs"> for a more information.</para>
<sect3 id="nsf-server-options">
<title>NFS Server</title>