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

Spelling corrections, addition of <devicename> tags, new man.ppp.8

Browse source 
manual page entity reference.

PR:		docs/11467
Submitted by:	Tom Hukins <tom@eborcom.com>
This commit is contained in:
Joseph Koshy 1999-05-04 05:26:26 +00:00
parent 7c0fa1b1fd
commit ec68dd4abd
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=4800
12 changed files with 50 additions and 47 deletions
en/handbook
contrib
chapter.sgml
ports
chapter.sgml
ppp-and-slip
chapter.sgml
en_US.ISO8859-1
articles/contributing
article.sgml
books
handbook
contrib
chapter.sgml
ports
chapter.sgml
ppp-and-slip
chapter.sgml
porters-handbook
book.sgml
en_US.ISO_8859-1/books
handbook
contrib
chapter.sgml
ports
chapter.sgml
ppp-and-slip
chapter.sgml
porters-handbook
book.sgml

4
en/handbook/contrib/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: chapter.sgml,v 1.32 1999-05-02 04:01:20 sada Exp $
$Id: chapter.sgml,v 1.33 1999-05-04 05:26:20 jkoshy Exp $
-->
<chapter id="contrib">
@ -183,7 +183,7 @@
</listitem>
<listitem>
<para>Add code to teh NFS layer so that you cannot
<para>Add code to the NFS layer so that you cannot
<literal>chdir("..")</literal> out of an NFS partition. E.g.,
<filename>/usr</filename> is a UFS partition with
<filename>/usr/src</filename> NFS exported. Now it is

6
en/handbook/ports/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: chapter.sgml,v 1.14 1999-05-03 05:20:15 simokawa Exp $
$Id: chapter.sgml,v 1.15 1999-05-04 05:26:24 jkoshy Exp $
-->
<chapter id="ports">
@ -1945,7 +1945,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract</programlisting>
<para>Also, add a matching <literal>@exec /sbin/ldconfig -m</literal>
and <literal>@unexec /sbin/ldconfig -R</literal> pair to your
<filename>pkg/PLIST</filename> file so that a user who installed the
package can start using teh shared libraru immediately and
package can start using the shared library immediately and
deinstallation will not cause the system to still believe the
library is there. These lines should immediately follow the line
for the shared library itself, as in:</para>
@ -1958,7 +1958,7 @@ lib/libtvl80.so.1
<para>Never, ever, <emphasis>ever</emphasis> add a line that says
<literal>ldconfig</literal> without any arguments to your
<filename>Makefile</filename> or <filename>pkg/PLIST</filename>.
This will reset the shared libraru cache to the contents of
This will reset the shared library cache to the contents of
<filename>/usr/lib</filename> only, and will royally screw up the
user's machine ("Help, xinit does not run anymore after I install
this port!"). Anybody who does this will be shot and cut in 65,536

17
en/handbook/ppp-and-slip/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: chapter.sgml,v 1.10 1999-03-08 22:04:47 nik Exp $
$Id: chapter.sgml,v 1.11 1999-05-04 05:26:26 jkoshy Exp $
-->
<chapter id="ppp-and-slip">
@ -28,7 +28,8 @@
implemented as a part of the kernel (e.g. as managed by
<command>pppd</command>) and it is thus somewhat hard to debug and/or
modify its behavior. However, in this implementation PPP is done as a
user process with the help of the tunnel device driver (tun).</para>
user process with the help of the tunnel device driver
(<devicename>tun</devicename>).</para>
</blockquote>
<para>In essence, this means that rather than running a PPP daemon, the
@ -136,7 +137,7 @@ pseudo-device tun 1</programlisting>
change anything.</para>
<para>If your kernel configuration file does not have this line in it,
or you need to configure more than one tun device (for example, if you
or you need to configure more than one <devicename>tun</devicename> device (for example, if you
are setting up a server and could have 16 dialup ppp connections at
any one time then you will need to use <literal>16</literal> instead
of <literal>1</literal>), then you should add the line, re-compile,
@ -162,7 +163,7 @@ tun3: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</screen>
been used at some point&mdash;it is not an error if your interface
does not show up as <literal>RUNNING</literal>.</para>
<para>If you have a kernel without the tun device, and you can not
<para>If you have a kernel without the <devicename>tun</devicename> device, and you can not
rebuild it for some reason, all is not lost. You should be able to
dynamically load the code. Refer to the appropriate
&man.modload.8; and &man.lkm.4; pages for further details.</para>
@ -190,7 +191,7 @@ tun3: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</screen>
&prompt.root; <userinput>./MAKEDEV tun0</userinput></screen>
<para>If you require 16 tunnel devices in your kernel, you will need to
create more than just tun0:</para>
create more than just <devicename>tun0</devicename>:</para>
<screen>&prompt.root; <userinput>cd /dev</userinput>
&prompt.root; <userinput>./MAKEDEV tun15</userinput></screen>
@ -407,7 +408,7 @@ domain <replaceable>bar.com</replaceable></programlisting>
<para>Sets the phone number for this provider. Multiple phone
numbers may be specified using the <literal>:</literal> or
<literal>|</literal> character as a separator. The difference
between these spearators is described in the ppp manual page.
between these separators is described in &man.ppp.8;.
To summarize, if you want to rotate through the numbers, use
the <literal>:</literal>. If you want to always attempt to
dial the first number first and only use the other numbers if
@ -1006,8 +1007,8 @@ 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 teh
tun device number that is in use.</para>
access. The <literal>%d</literal> in the name is replaced with the
<devicename>tun</devicename> device number that is in use.</para>
<para>Once a socket has been set up, the
&man.pppctl.8; program may be used in scripts that wish to

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: article.sgml,v 1.32 1999-05-02 04:01:20 sada Exp $
$Id: article.sgml,v 1.33 1999-05-04 05:26:20 jkoshy Exp $
-->
<chapter id="contrib">
@ -183,7 +183,7 @@
</listitem>
<listitem>
<para>Add code to teh NFS layer so that you cannot
<para>Add code to the NFS layer so that you cannot
<literal>chdir("..")</literal> out of an NFS partition. E.g.,
<filename>/usr</filename> is a UFS partition with
<filename>/usr/src</filename> NFS exported. Now it is

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: chapter.sgml,v 1.32 1999-05-02 04:01:20 sada Exp $
$Id: chapter.sgml,v 1.33 1999-05-04 05:26:20 jkoshy Exp $
-->
<chapter id="contrib">
@ -183,7 +183,7 @@
</listitem>
<listitem>
<para>Add code to teh NFS layer so that you cannot
<para>Add code to the NFS layer so that you cannot
<literal>chdir("..")</literal> out of an NFS partition. E.g.,
<filename>/usr</filename> is a UFS partition with
<filename>/usr/src</filename> NFS exported. Now it is

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: chapter.sgml,v 1.14 1999-05-03 05:20:15 simokawa Exp $
$Id: chapter.sgml,v 1.15 1999-05-04 05:26:24 jkoshy Exp $
-->
<chapter id="ports">
@ -1945,7 +1945,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract</programlisting>
<para>Also, add a matching <literal>@exec /sbin/ldconfig -m</literal>
and <literal>@unexec /sbin/ldconfig -R</literal> pair to your
<filename>pkg/PLIST</filename> file so that a user who installed the
package can start using teh shared libraru immediately and
package can start using the shared library immediately and
deinstallation will not cause the system to still believe the
library is there. These lines should immediately follow the line
for the shared library itself, as in:</para>
@ -1958,7 +1958,7 @@ lib/libtvl80.so.1
<para>Never, ever, <emphasis>ever</emphasis> add a line that says
<literal>ldconfig</literal> without any arguments to your
<filename>Makefile</filename> or <filename>pkg/PLIST</filename>.
This will reset the shared libraru cache to the contents of
This will reset the shared library cache to the contents of
<filename>/usr/lib</filename> only, and will royally screw up the
user's machine ("Help, xinit does not run anymore after I install
this port!"). Anybody who does this will be shot and cut in 65,536

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: chapter.sgml,v 1.10 1999-03-08 22:04:47 nik Exp $
$Id: chapter.sgml,v 1.11 1999-05-04 05:26:26 jkoshy Exp $
-->
<chapter id="ppp-and-slip">
@ -28,7 +28,8 @@
implemented as a part of the kernel (e.g. as managed by
<command>pppd</command>) and it is thus somewhat hard to debug and/or
modify its behavior. However, in this implementation PPP is done as a
user process with the help of the tunnel device driver (tun).</para>
user process with the help of the tunnel device driver
(<devicename>tun</devicename>).</para>
</blockquote>
<para>In essence, this means that rather than running a PPP daemon, the
@ -136,7 +137,7 @@ pseudo-device tun 1</programlisting>
change anything.</para>
<para>If your kernel configuration file does not have this line in it,
or you need to configure more than one tun device (for example, if you
or you need to configure more than one <devicename>tun</devicename> device (for example, if you
are setting up a server and could have 16 dialup ppp connections at
any one time then you will need to use <literal>16</literal> instead
of <literal>1</literal>), then you should add the line, re-compile,
@ -162,7 +163,7 @@ tun3: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</screen>
been used at some point&mdash;it is not an error if your interface
does not show up as <literal>RUNNING</literal>.</para>
<para>If you have a kernel without the tun device, and you can not
<para>If you have a kernel without the <devicename>tun</devicename> device, and you can not
rebuild it for some reason, all is not lost. You should be able to
dynamically load the code. Refer to the appropriate
&man.modload.8; and &man.lkm.4; pages for further details.</para>
@ -190,7 +191,7 @@ tun3: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</screen>
&prompt.root; <userinput>./MAKEDEV tun0</userinput></screen>
<para>If you require 16 tunnel devices in your kernel, you will need to
create more than just tun0:</para>
create more than just <devicename>tun0</devicename>:</para>
<screen>&prompt.root; <userinput>cd /dev</userinput>
&prompt.root; <userinput>./MAKEDEV tun15</userinput></screen>
@ -407,7 +408,7 @@ domain <replaceable>bar.com</replaceable></programlisting>
<para>Sets the phone number for this provider. Multiple phone
numbers may be specified using the <literal>:</literal> or
<literal>|</literal> character as a separator. The difference
between these spearators is described in the ppp manual page.
between these separators is described in &man.ppp.8;.
To summarize, if you want to rotate through the numbers, use
the <literal>:</literal>. If you want to always attempt to
dial the first number first and only use the other numbers if
@ -1006,8 +1007,8 @@ 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 teh
tun device number that is in use.</para>
access. The <literal>%d</literal> in the name is replaced with the
<devicename>tun</devicename> device number that is in use.</para>
<para>Once a socket has been set up, the
&man.pppctl.8; program may be used in scripts that wish to

6
en_US.ISO8859-1/books/porters-handbook/book.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: book.sgml,v 1.14 1999-05-03 05:20:15 simokawa Exp $
$Id: book.sgml,v 1.15 1999-05-04 05:26:24 jkoshy Exp $
-->
<chapter id="ports">
@ -1945,7 +1945,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract</programlisting>
<para>Also, add a matching <literal>@exec /sbin/ldconfig -m</literal>
and <literal>@unexec /sbin/ldconfig -R</literal> pair to your
<filename>pkg/PLIST</filename> file so that a user who installed the
package can start using teh shared libraru immediately and
package can start using the shared library immediately and
deinstallation will not cause the system to still believe the
library is there. These lines should immediately follow the line
for the shared library itself, as in:</para>
@ -1958,7 +1958,7 @@ lib/libtvl80.so.1
<para>Never, ever, <emphasis>ever</emphasis> add a line that says
<literal>ldconfig</literal> without any arguments to your
<filename>Makefile</filename> or <filename>pkg/PLIST</filename>.
This will reset the shared libraru cache to the contents of
This will reset the shared library cache to the contents of
<filename>/usr/lib</filename> only, and will royally screw up the
user's machine ("Help, xinit does not run anymore after I install
this port!"). Anybody who does this will be shot and cut in 65,536

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: chapter.sgml,v 1.32 1999-05-02 04:01:20 sada Exp $
$Id: chapter.sgml,v 1.33 1999-05-04 05:26:20 jkoshy Exp $
-->
<chapter id="contrib">
@ -183,7 +183,7 @@
</listitem>
<listitem>
<para>Add code to teh NFS layer so that you cannot
<para>Add code to the NFS layer so that you cannot
<literal>chdir("..")</literal> out of an NFS partition. E.g.,
<filename>/usr</filename> is a UFS partition with
<filename>/usr/src</filename> NFS exported. Now it is

6
en_US.ISO_8859-1/books/handbook/ports/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: chapter.sgml,v 1.14 1999-05-03 05:20:15 simokawa Exp $
$Id: chapter.sgml,v 1.15 1999-05-04 05:26:24 jkoshy Exp $
-->
<chapter id="ports">
@ -1945,7 +1945,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract</programlisting>
<para>Also, add a matching <literal>@exec /sbin/ldconfig -m</literal>
and <literal>@unexec /sbin/ldconfig -R</literal> pair to your
<filename>pkg/PLIST</filename> file so that a user who installed the
package can start using teh shared libraru immediately and
package can start using the shared library immediately and
deinstallation will not cause the system to still believe the
library is there. These lines should immediately follow the line
for the shared library itself, as in:</para>
@ -1958,7 +1958,7 @@ lib/libtvl80.so.1
<para>Never, ever, <emphasis>ever</emphasis> add a line that says
<literal>ldconfig</literal> without any arguments to your
<filename>Makefile</filename> or <filename>pkg/PLIST</filename>.
This will reset the shared libraru cache to the contents of
This will reset the shared library cache to the contents of
<filename>/usr/lib</filename> only, and will royally screw up the
user's machine ("Help, xinit does not run anymore after I install
this port!"). Anybody who does this will be shot and cut in 65,536

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

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: chapter.sgml,v 1.10 1999-03-08 22:04:47 nik Exp $
$Id: chapter.sgml,v 1.11 1999-05-04 05:26:26 jkoshy Exp $
-->
<chapter id="ppp-and-slip">
@ -28,7 +28,8 @@
implemented as a part of the kernel (e.g. as managed by
<command>pppd</command>) and it is thus somewhat hard to debug and/or
modify its behavior. However, in this implementation PPP is done as a
user process with the help of the tunnel device driver (tun).</para>
user process with the help of the tunnel device driver
(<devicename>tun</devicename>).</para>
</blockquote>
<para>In essence, this means that rather than running a PPP daemon, the
@ -136,7 +137,7 @@ pseudo-device tun 1</programlisting>
change anything.</para>
<para>If your kernel configuration file does not have this line in it,
or you need to configure more than one tun device (for example, if you
or you need to configure more than one <devicename>tun</devicename> device (for example, if you
are setting up a server and could have 16 dialup ppp connections at
any one time then you will need to use <literal>16</literal> instead
of <literal>1</literal>), then you should add the line, re-compile,
@ -162,7 +163,7 @@ tun3: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</screen>
been used at some point&mdash;it is not an error if your interface
does not show up as <literal>RUNNING</literal>.</para>
<para>If you have a kernel without the tun device, and you can not
<para>If you have a kernel without the <devicename>tun</devicename> device, and you can not
rebuild it for some reason, all is not lost. You should be able to
dynamically load the code. Refer to the appropriate
&man.modload.8; and &man.lkm.4; pages for further details.</para>
@ -190,7 +191,7 @@ tun3: flags=8010&lt;POINTOPOINT,MULTICAST&gt; mtu 1500</screen>
&prompt.root; <userinput>./MAKEDEV tun0</userinput></screen>
<para>If you require 16 tunnel devices in your kernel, you will need to
create more than just tun0:</para>
create more than just <devicename>tun0</devicename>:</para>
<screen>&prompt.root; <userinput>cd /dev</userinput>
&prompt.root; <userinput>./MAKEDEV tun15</userinput></screen>
@ -407,7 +408,7 @@ domain <replaceable>bar.com</replaceable></programlisting>
<para>Sets the phone number for this provider. Multiple phone
numbers may be specified using the <literal>:</literal> or
<literal>|</literal> character as a separator. The difference
between these spearators is described in the ppp manual page.
between these separators is described in &man.ppp.8;.
To summarize, if you want to rotate through the numbers, use
the <literal>:</literal>. If you want to always attempt to
dial the first number first and only use the other numbers if
@ -1006,8 +1007,8 @@ 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 teh
tun device number that is in use.</para>
access. The <literal>%d</literal> in the name is replaced with the
<devicename>tun</devicename> device number that is in use.</para>
<para>Once a socket has been set up, the
&man.pppctl.8; program may be used in scripts that wish to

6
en_US.ISO_8859-1/books/porters-handbook/book.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$Id: book.sgml,v 1.14 1999-05-03 05:20:15 simokawa Exp $
$Id: book.sgml,v 1.15 1999-05-04 05:26:24 jkoshy Exp $
-->
<chapter id="ports">
@ -1945,7 +1945,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract</programlisting>
<para>Also, add a matching <literal>@exec /sbin/ldconfig -m</literal>
and <literal>@unexec /sbin/ldconfig -R</literal> pair to your
<filename>pkg/PLIST</filename> file so that a user who installed the
package can start using teh shared libraru immediately and
package can start using the shared library immediately and
deinstallation will not cause the system to still believe the
library is there. These lines should immediately follow the line
for the shared library itself, as in:</para>
@ -1958,7 +1958,7 @@ lib/libtvl80.so.1
<para>Never, ever, <emphasis>ever</emphasis> add a line that says
<literal>ldconfig</literal> without any arguments to your
<filename>Makefile</filename> or <filename>pkg/PLIST</filename>.
This will reset the shared libraru cache to the contents of
This will reset the shared library cache to the contents of
<filename>/usr/lib</filename> only, and will royally screw up the
user's machine ("Help, xinit does not run anymore after I install
this port!"). Anybody who does this will be shot and cut in 65,536