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

Pick up the sledgehammer used by Nik for rev 1.114, Ben for rev 1.87, and

Browse source 
others -- and do some major SGML cleanup. Replace <emphasis remap=xx>
by whatever is appropriate.

Reviewed by:	alex
Inspired by:	German FAQ translation, rev. 1.101
This commit is contained in:
Udo Erdelhoff 2001-05-15 21:00:11 +00:00
parent 285bbf2296
commit 76bd774fd3
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9447
2 changed files with 244 additions and 220 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

230
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -14,7 +14,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor> <corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.193 2001/05/14 22:57:35 dd Exp $</pubdate> <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.194 2001/05/15 00:24:18 dd Exp $</pubdate>
<copyright> <copyright>
<year>1995</year> <year>1995</year>
@ -3669,7 +3669,7 @@ quit</programlisting>
<para> <para>
<note> <note>
<para>You can not use a <para>You can not use a
<emphasis remap=bf>dangerously dedicated</emphasis> disk <literal>dangerously dedicated</literal> disk
with an HP Netserver. See <link linkend="dedicate">this with an HP Netserver. See <link linkend="dedicate">this
note</link> for more info.</para> note</link> for more info.</para>
</note></para> </note></para>
@ -3954,7 +3954,7 @@ quit</programlisting>
<literal>2e8</literal>, and the fourth serial port does too. <literal>2e8</literal>, and the fourth serial port does too.
Due to a bug (feature?) in the &man.sio.4; Due to a bug (feature?) in the &man.sio.4;
driver it will touch this port even if you don't have the driver it will touch this port even if you don't have the
fourth serial port, and <emphasis remap=bf>even</emphasis> if fourth serial port, and <emphasis>even</emphasis> if
you disable sio3 (the fourth port) which normally uses this you disable sio3 (the fourth port) which normally uses this
address.</para> address.</para>
@ -5237,7 +5237,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
math co-processor, right? Wrong! :-) The math co-processor, right? Wrong! :-) The
<devicename>npx0</devicename> is <devicename>npx0</devicename> is
<emphasis>MANDATORY</emphasis>. Even if you don't have a <emphasis>MANDATORY</emphasis>. Even if you don't have a
mathematic co-processor, you <emphasis remap=bf>must</emphasis> mathematic co-processor, you <emphasis>must</emphasis>
include the <devicename>npx0</devicename> device.</para> include the <devicename>npx0</devicename> device.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -5289,12 +5289,12 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
</question> </question>
<answer> <answer>
<para><emphasis remap=bf>Q.</emphasis> When I compile a kernel <para>When I compile a kernel
with multi-port serial code, it tells me that only the first with multi-port serial code, it tells me that only the first
port is probed and the rest skipped due to interrupt conflicts. port is probed and the rest skipped due to interrupt conflicts.
How do I fix this?</para> How do I fix this?</para>
<para><emphasis remap=bf>A.</emphasis> The problem here is that <para>The problem here is that
FreeBSD has code built-in to keep the kernel from getting FreeBSD has code built-in to keep the kernel from getting
trashed due to hardware or software conflicts. The way to fix trashed due to hardware or software conflicts. The way to fix
this is to leave out the IRQ settings on all but one port. Here this is to leave out the IRQ settings on all but one port. Here
@ -5650,18 +5650,18 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
</question> </question>
<answer> <answer>
<para><emphasis remap=bf> Digital UNIX</emphasis> UFS CDROMs can <para><literal>Digital UNIX</literal> UFS CDROMs can
be mounted directly on FreeBSD. Mounting disk partitions from be mounted directly on FreeBSD. Mounting disk partitions from
Digital UNIX and other systems that support UFS may be more Digital UNIX and other systems that support UFS may be more
complex, depending on the details of the disk partitioning for complex, depending on the details of the disk partitioning for
the operating system in question.</para> the operating system in question.</para>
<para><emphasis remap=bf> Linux</emphasis>: 2.2 and later have <para><literal>Linux</literal>: 2.2 and later have
support for <emphasis remap=bf>ext2fs</emphasis> partitions. support for <literal>ext2fs</literal> partitions.
See &man.mount.ext2fs.8; See &man.mount.ext2fs.8;
for more information.</para> for more information.</para>
<para><emphasis remap=bf> NT</emphasis>: A read-only NTFS driver <para><literal>NT</literal>: A read-only NTFS driver
exists for FreeBSD. For more information, see this tutorial by exists for FreeBSD. For more information, see this tutorial by
Mark Ovens at Mark Ovens at
<ulink URL="http://ukug.uk.freebsd.org/~mark/ntfs_install.html"> <ulink URL="http://ukug.uk.freebsd.org/~mark/ntfs_install.html">
@ -5699,7 +5699,7 @@ C:\="DOS"</programlisting>
<para>For 2.2.x systems this procedure assumes that DOS, NT, <para>For 2.2.x systems this procedure assumes that DOS, NT,
FreeBSD, or whatever have been installed into their respective FreeBSD, or whatever have been installed into their respective
fdisk partitions on the <emphasis remap=bf>same</emphasis> fdisk partitions on the <emphasis>same</emphasis>
disk. This example was tested on a system where DOS &amp; NT disk. This example was tested on a system where DOS &amp; NT
were on the first fdisk partition, and FreeBSD on the second. were on the first fdisk partition, and FreeBSD on the second.
FreeBSD was also set up to boot from its native partition, not FreeBSD was also set up to boot from its native partition, not
@ -6503,7 +6503,7 @@ rewrite: ruleset 0 returns: $# uucp-dom $@ if-bus $: foo \
the rest.</para> the rest.</para>
<para>If you've got a dynamically assigned IP number and use a <para>If you've got a dynamically assigned IP number and use a
dialup <emphasis remap=bf>ppp</emphasis> connection to the dialup <application>ppp</application> connection to the
internet, you will probably be given a mailbox on your ISPs internet, you will probably be given a mailbox on your ISPs
mail server. Lets assume your ISPs domain is mail server. Lets assume your ISPs domain is
<hostid role="domainname">myISP.com</hostid>, and that your user name is <hostid role="domainname">myISP.com</hostid>, and that your user name is
@ -7365,7 +7365,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<filename>/dev/sysmouse</filename>. All mouse events received <filename>/dev/sysmouse</filename>. All mouse events received
from the real mouse device are written to the sysmouse device from the real mouse device are written to the sysmouse device
via moused. If you wish to use your mouse on one or more via moused. If you wish to use your mouse on one or more
virtual consoles, <emphasis remap=bf>and</emphasis> use X, see virtual consoles, <emphasis>and</emphasis> use X, see
<xref linkend="moused" remap="another section"> and set up <xref linkend="moused" remap="another section"> and set up
moused.</para> moused.</para>
@ -7844,7 +7844,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
URL="http://www.FreeBSD.org/cgi/man.cgi?manpath=xfree86&amp;query=startx"> URL="http://www.FreeBSD.org/cgi/man.cgi?manpath=xfree86&amp;query=startx">
startx</ulink>, the permissions on startx</ulink>, the permissions on
<filename>/dev/console</filename> will <filename>/dev/console</filename> will
<emphasis remap=tt>not</emphasis> get changed, resulting in <emphasis>not</emphasis> get changed, resulting in
things like <ulink things like <ulink
URL="http://www.FreeBSD.org/cgi/man.cgi?manpath=xfree86&amp;query=xterm"> URL="http://www.FreeBSD.org/cgi/man.cgi?manpath=xfree86&amp;query=xterm">
xterm -C</ulink> and <ulink xterm -C</ulink> and <ulink
@ -8740,7 +8740,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
<listitem> <listitem>
<para>Place heavily triggered rules earlier in the rule <para>Place heavily triggered rules earlier in the rule
set than those rarely used (<emphasis remap=bf>without set than those rarely used (<emphasis>without
changing the permissiveness of the firewall</emphasis>, changing the permissiveness of the firewall</emphasis>,
of course). You can see which rules are used most often of course). You can see which rules are used most often
by examining the packet counting statistics with by examining the packet counting statistics with
@ -8970,10 +8970,10 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
<programlisting>set log Phase Chat Connect Carrier lcp ipcp ccp command</programlisting> <programlisting>set log Phase Chat Connect Carrier lcp ipcp ccp command</programlisting>
<para>This command may be typed at the <para>This command may be typed at the
<emphasis remap=bf>ppp</emphasis> command prompt or it may be <application>ppp</application> command prompt or it may be
entered in the <filename>/etc/ppp/ppp.conf</filename> entered in the <filename>/etc/ppp/ppp.conf</filename>
configuration file (the start of the configuration file (the start of the
<emphasis remap=bf>default</emphasis> section is the best <literal>default</literal> section is the best
place to put it). Make sure that place to put it). Make sure that
<filename>/etc/syslog.conf</filename> (see &man.syslog.conf.5;) contains the lines</para> <filename>/etc/syslog.conf</filename> (see &man.syslog.conf.5;) contains the lines</para>
@ -9038,7 +9038,7 @@ default 10.0.0.2 UGSc 0 0 tun0
running an old version of &man.ppp.8; running an old version of &man.ppp.8;
that doesn't understand the word <literal>HISADDR</literal> that doesn't understand the word <literal>HISADDR</literal>
in the ppp.conf file. If your version of in the ppp.conf file. If your version of
<emphasis remap=bf>ppp</emphasis> is from before FreeBSD <application>ppp</application> is from before FreeBSD
2.2.5, change the</para> 2.2.5, change the</para>
<programlisting>add 0 0 HISADDR</programlisting> <programlisting>add 0 0 HISADDR</programlisting>
@ -9080,7 +9080,7 @@ default 10.0.0.2 UGSc 0 0 tun0
file. This is only necessary if you have a dynamic IP address file. This is only necessary if you have a dynamic IP address
or don't know the address of your gateway. If you're using or don't know the address of your gateway. If you're using
interactive mode, you can type the following after entering interactive mode, you can type the following after entering
<emphasis remap=tt>packet mode</emphasis> (packet mode is <literal>packet mode</literal> (packet mode is
indicated by the capitalized <acronym>PPP</acronym> in the indicated by the capitalized <acronym>PPP</acronym> in the
prompt):</para> prompt):</para>
@ -9111,8 +9111,8 @@ add 0 0 HISADDR</programlisting>
closed due to a timeout. It is possible to put this command in closed due to a timeout. It is possible to put this command in
the <filename>ppp.conf</filename> file, or to type it at the the <filename>ppp.conf</filename> file, or to type it at the
prompt in interactive mode. It is also possible to adjust it on prompt in interactive mode. It is also possible to adjust it on
the fly while the line is active by connecting to <emphasis the fly while the line is active by connecting to
remap=bf>ppp</emphasis>s server socket using <application>ppp</application>s server socket using
&man.telnet.1; or &man.pppctl.8;. &man.telnet.1; or &man.pppctl.8;.
Refer to the Refer to the
&man.ppp.8; man &man.ppp.8; man
@ -9267,15 +9267,19 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
would wait for the peer to initiate the Line Control Protocol would wait for the peer to initiate the Line Control Protocol
(LCP). Many ISPs will not initiate negotiations and expect (LCP). Many ISPs will not initiate negotiations and expect
the client to do so. To force the client to do so. To force
<emphasis remap=bf>ppp</emphasis> to initiate the LCP, use the <application>ppp</application> to initiate the LCP, use the
following line:</para> following line:</para>
<programlisting>set openmode active</programlisting> <programlisting>set openmode active</programlisting>
<para><emphasis remap=bf>Note</emphasis>: It usually does no <para>
<note>
<para>It usually does no
harm if both sides initiate negotiation, so openmode is now harm if both sides initiate negotiation, so openmode is now
active by default. However, the next section explains when active by default. However, the next section explains when
it <emphasis remap=bf>does</emphasis> do some harm.</para> it <emphasis>does</emphasis> do some harm.</para>
</note>
</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -9349,44 +9353,44 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
<answer> <answer>
<para>There is currently an implementation mis-feature in <para>There is currently an implementation mis-feature in
<emphasis remap=bf>ppp</emphasis> where it doesn't associate <application>ppp</application> where it doesn't associate
LCP, CCP &amp; IPCP responses with their original requests. As LCP, CCP &amp; IPCP responses with their original requests. As
a result, if one <emphasis remap=bf>ppp</emphasis> a result, if one <application>ppp</application>
implementation is more than 6 seconds slower than the other implementation is more than 6 seconds slower than the other
side, the other side will send two additional LCP configuration side, the other side will send two additional LCP configuration
requests. This is fatal.</para> requests. This is fatal.</para>
<para>Consider two implementations, <para>Consider two implementations,
<emphasis remap=bf>A</emphasis> and <emphasis <hostid>A</hostid> and
remap=bf>B</emphasis>. <emphasis remap=bf>A</emphasis> starts <hostid>B</hostid>. <hostid>A</hostid> starts
sending LCP requests immediately after connecting and <emphasis sending LCP requests immediately after connecting and
remap=bf>B</emphasis> takes 7 seconds to start. When <emphasis <hostid>B</hostid> takes 7 seconds to start. When
remap=bf>B</emphasis> starts, <emphasis remap=bf>A</emphasis> <hostid>B</hostid> starts, <hostid>A</hostid>
has sent 3 LCP REQs. We're assuming the line has ECHO switched has sent 3 LCP REQs. We're assuming the line has ECHO switched
off, otherwise we'd see magic number problems as described in off, otherwise we'd see magic number problems as described in
the previous section. <emphasis remap=bf>B</emphasis> sends a the previous section. <hostid>B</hostid> sends a
REQ, then an ACK to the first of <emphasis REQ, then an ACK to the first of
remap=bf>A</emphasis>'s REQs. This results in <emphasis <hostid>A</hostid>'s REQs. This results in
remap=bf>A</emphasis> entering the <acronym>OPENED</acronym> <hostid>A</hostid> entering the <acronym>OPENED</acronym>
state and sending and ACK (the first) back to <emphasis state and sending and ACK (the first) back to
remap=bf>B</emphasis>. In the meantime, <emphasis <hostid>B</hostid>. In the meantime,
remap=bf>B</emphasis> sends back two more ACKs in response to <hostid>B</hostid> sends back two more ACKs in response to
the two additional REQs sent by <emphasis remap=bf>A</emphasis> the two additional REQs sent by <hostid>A</hostid>
before <emphasis remap=bf>B</emphasis> started up. <emphasis before <hostid>B</hostid> started up.
remap=bf>B</emphasis> then receives the first ACK from <hostid>B</hostid> then receives the first ACK from
<emphasis remap=bf>A</emphasis> and enters the <hostid>A</hostid> and enters the
<acronym>OPENED</acronym> state. <emphasis <acronym>OPENED</acronym> state.
remap=bf>A</emphasis> receives the second ACK from <emphasis <hostid>A</hostid> receives the second ACK from
remap=bf>B</emphasis> and goes back to the <emphasis <hostid>B</hostid> and goes back to the
remap=bf>REQ-SENT</emphasis> state, sending another (forth) REQ <literal>REQ-SENT</literal> state, sending another (forth) REQ
as per the RFC. It then receives the third ACK and enters the as per the RFC. It then receives the third ACK and enters the
<acronym>OPENED</acronym> state. In the meantime, <emphasis <acronym>OPENED</acronym> state. In the meantime,
remap=bf>B</emphasis> receives the forth REQ from <emphasis <hostid>B</hostid> receives the forth REQ from
remap=bf>A</emphasis>, resulting in it reverting to the <hostid>A</hostid>, resulting in it reverting to the
<emphasis remap=bf>ACK-SENT</emphasis> state and sending <literal>ACK-SENT</literal> state and sending
another (second) REQ and (forth) ACK as per the RFC. <emphasis another (second) REQ and (forth) ACK as per the RFC.
remap=bf>A</emphasis> gets the REQ, goes into <emphasis <hostid>A</hostid> gets the REQ, goes into
remap=bf>REQ-SENT</emphasis> and sends another REQ. It <literal>REQ-SENT</literal> and sends another REQ. It
immediately receives the following ACK and enters immediately receives the following ACK and enters
<acronym>OPENED</acronym>.</para> <acronym>OPENED</acronym>.</para>
@ -9394,7 +9398,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
getting nowhere and gives up.</para> getting nowhere and gives up.</para>
<para>The best way to avoid this is to configure one side to be <para>The best way to avoid this is to configure one side to be
<emphasis remap=bf>passive</emphasis> - that is, make one side <literal>passive</literal> - that is, make one side
wait for the other to start negotiating. This can be done wait for the other to start negotiating. This can be done
with the</para> with the</para>
@ -9406,12 +9410,12 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
<programlisting>set stopped N</programlisting> <programlisting>set stopped N</programlisting>
<para>command to limit the amount of time that <para>command to limit the amount of time that
<emphasis remap=bf>ppp</emphasis> waits for the peer to begin <application>ppp</application> waits for the peer to begin
negotiations. Alternatively, the</para> negotiations. Alternatively, the</para>
<programlisting>set openmode active N</programlisting> <programlisting>set openmode active N</programlisting>
<para>command (where <emphasis remap=bf>N</emphasis> is the <para>command (where <replaceable>N</replaceable> is the
number of seconds to wait before starting negotiations) can be number of seconds to wait before starting negotiations) can be
used. Check the manual page for details.</para> used. Check the manual page for details.</para>
</answer> </answer>
@ -9425,11 +9429,11 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
<answer> <answer>
<para>Prior to version 2.2.5 of FreeBSD, it was possible that <para>Prior to version 2.2.5 of FreeBSD, it was possible that
your link was disabled shortly after connection due to your link was disabled shortly after connection due to
<emphasis remap=bf>ppp</emphasis> mis-handling Predictor1 <application>ppp</application> mis-handling Predictor1
compression negotiation. This would only happen if both sides compression negotiation. This would only happen if both sides
tried to negotiate different Compression Control Protocols tried to negotiate different Compression Control Protocols
(CCP). This problem is now corrected, but if you're still (CCP). This problem is now corrected, but if you're still
running an old version of <emphasis remap=bf>ppp</emphasis>, running an old version of <application>ppp</application>,
the problem can be circumvented with the line</para> the problem can be circumvented with the line</para>
<programlisting>disable pred1</programlisting> <programlisting>disable pred1</programlisting>
@ -9465,7 +9469,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
</question> </question>
<answer> <answer>
<para>There is no way for <emphasis remap=bf>ppp</emphasis> to <para>There is no way for <application>ppp</application> to
automatically determine that a direct connection has been automatically determine that a direct connection has been
dropped. This is due to the lines that are used in a dropped. This is due to the lines that are used in a
null-modem serial cable. When using this sort of connection, null-modem serial cable. When using this sort of connection,
@ -9482,7 +9486,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
<para>Why does ppp dial for no reason in -auto mode</para> <para>Why does ppp dial for no reason in -auto mode</para>
</question><answer> </question><answer>
<para>If <emphasis remap=bf>ppp</emphasis> is dialing <para>If <application>ppp</application> is dialing
unexpectedly, you must determine the cause, and set up Dial unexpectedly, you must determine the cause, and set up Dial
filters (dfilters) to prevent such dialing.</para> filters (dfilters) to prevent such dialing.</para>
@ -9497,8 +9501,8 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
<para>You can now disable dialing under these circumstances. <para>You can now disable dialing under these circumstances.
Usually, this sort of problem arises due to DNS lookups. To Usually, this sort of problem arises due to DNS lookups. To
prevent DNS lookups from establishing a connection (this will prevent DNS lookups from establishing a connection (this will
<emphasis remap=bf>not</emphasis> prevent <emphasis>not</emphasis> prevent
<emphasis remap=bf>ppp</emphasis> from passing the packets <application>ppp</application> from passing the packets
through an established connection), use the following:</para> through an established connection), use the following:</para>
<programlisting>set dfilter 1 deny udp src eq 53 <programlisting>set dfilter 1 deny udp src eq 53
@ -9563,7 +9567,7 @@ CCP: Received Terminate Ack (1) state = Req-Sent (6)</programlisting>
via syslogd.</para> via syslogd.</para>
<para>The ppp specification says that an MRU of 1500 should <para>The ppp specification says that an MRU of 1500 should
<emphasis remap=bf>always</emphasis> be accepted as a minimum, <emphasis>always</emphasis> be accepted as a minimum,
despite any LCP negotiations, therefore it is possible that despite any LCP negotiations, therefore it is possible that
should you decrease the MTU to less than 1500, your ISP will should you decrease the MTU to less than 1500, your ISP will
transmit packets of 1500 regardless, and you will tickle this transmit packets of 1500 regardless, and you will tickle this
@ -9602,7 +9606,7 @@ CCP: Received Terminate Ack (1) state = Req-Sent (6)</programlisting>
\"\" ATZ OK-ATZ-OK ATDT\\T TIMEOUT 60 CONNECT \\c \\n"</programlisting> \"\" ATZ OK-ATZ-OK ATDT\\T TIMEOUT 60 CONNECT \\c \\n"</programlisting>
<para>Here, we get our CONNECT, send nothing, then expect a <para>Here, we get our CONNECT, send nothing, then expect a
line-feed, forcing <emphasis remap=bf>ppp</emphasis> to read line-feed, forcing <application>ppp</application> to read
the whole CONNECT response.</para> the whole CONNECT response.</para>
</answer> </answer>
@ -9618,7 +9622,7 @@ CCP: Received Terminate Ack (1) state = Req-Sent (6)</programlisting>
interpret strings such as interpret strings such as
<literal>set phone "123 456 789"</literal> correctly (and <literal>set phone "123 456 789"</literal> correctly (and
realize that the number is actually only realize that the number is actually only
<emphasis remap=bf>one</emphasis> argument. In order to specify <emphasis>one</emphasis> argument. In order to specify
a <literal>"</literal> character, you must escape it using a a <literal>"</literal> character, you must escape it using a
backslash (<literal>\</literal>).</para> backslash (<literal>\</literal>).</para>
@ -9667,9 +9671,9 @@ ATDT1234567</programlisting>
dump core. Because ppp runs with an effective user id of 0, dump core. Because ppp runs with an effective user id of 0,
the operating system will not write ppps core image to disk the operating system will not write ppps core image to disk
before terminating it. If, however ppp before terminating it. If, however ppp
<emphasis remap=bf>is</emphasis> actually termating due to a is actually termating due to a
segmentation violation or some other signal that normally segmentation violation or some other signal that normally
causes core to be dumped, <emphasis remap=bf>and</emphasis> causes core to be dumped, <emphasis>and</emphasis>
you're sure you're using the latest version (see the start of you're sure you're using the latest version (see the start of
this section), then you should do the following:</para> this section), then you should do the following:</para>
@ -9719,18 +9723,18 @@ ATDT1234567</programlisting>
<answer> <answer>
<para>This was a known problem with <para>This was a known problem with
<emphasis remap=bf>ppp</emphasis> set up to negotiate a <application>ppp</application> set up to negotiate a
dynamic local IP number with the peer in auto mode. It is dynamic local IP number with the peer in auto mode. It is
fixed in the latest version - search the man page for fixed in the latest version - search the man page for
<emphasis remap=bf>iface</emphasis>.</para> <literal>iface</literal>.</para>
<para>The problem was that when that initial program calls <para>The problem was that when that initial program calls
&man.connect.2;, the IP number of the tun interface is &man.connect.2;, the IP number of the tun interface is
assigned to the socket endpoint. The kernel creates the first assigned to the socket endpoint. The kernel creates the first
outgoing packet and writes it to the tun device. <emphasis outgoing packet and writes it to the tun device.
remap=bf>Ppp</emphasis> then reads the packet and establishes a <application>ppp</application> then reads the packet and establishes a
connection. If, as a result of <emphasis connection. If, as a result of
remap=bf>ppp</emphasis>s dynamic IP assignment, the interface <application>ppp</application>s dynamic IP assignment, the interface
address is changed, the original socket endpoint will be address is changed, the original socket endpoint will be
invalid. Any subsequent packets sent to the peer will usually invalid. Any subsequent packets sent to the peer will usually
be dropped. Even if they aren't, any responses will not route be dropped. Even if they aren't, any responses will not route
@ -9739,8 +9743,8 @@ ATDT1234567</programlisting>
<para>There are several theoretical ways to approach this <para>There are several theoretical ways to approach this
problem. It would be nicest if the peer would re-assign the problem. It would be nicest if the peer would re-assign the
same IP number if possible <emphasis remap=tt>:-)</emphasis> same IP number if possible <literal>:-)</literal>
The current version of <emphasis remap=bf>ppp</emphasis> does The current version of <application>ppp</application> does
this, but most other implementations don't.</para> this, but most other implementations don't.</para>
<para>The easiest method from our side would be to never change <para>The easiest method from our side would be to never change
@ -9748,7 +9752,7 @@ ATDT1234567</programlisting>
packets so that the source IP number is changed from the packets so that the source IP number is changed from the
interface IP to the negotiated IP on the fly. This is interface IP to the negotiated IP on the fly. This is
essentially what the <literal>iface-alias</literal> option in essentially what the <literal>iface-alias</literal> option in
the latest version of <emphasis remap=bf>ppp</emphasis> is the latest version of <application>ppp</application> is
doing (with the help of doing (with the help of
&man.libalias.3; and ppp's <option>-nat</option> switch) - &man.libalias.3; and ppp's <option>-nat</option> switch) -
it's maintaining all previous interface addresses and NATing it's maintaining all previous interface addresses and NATing
@ -9756,7 +9760,7 @@ ATDT1234567</programlisting>
<para>Another alternative (and probably the most reliable) would <para>Another alternative (and probably the most reliable) would
be to implement a system call that changes all bound sockets be to implement a system call that changes all bound sockets
from one IP to another. <emphasis remap=bf>Ppp</emphasis> would from one IP to another. <application>ppp</application> would
use this call to modify the sockets of all existing programs use this call to modify the sockets of all existing programs
when a new IP number is negotiated. The same system call could when a new IP number is negotiated. The same system call could
be used by dhcp clients when they are forced to re-bind() their be used by dhcp clients when they are forced to re-bind() their
@ -9766,7 +9770,7 @@ ATDT1234567</programlisting>
brought up without an IP number. Outgoing packets would be brought up without an IP number. Outgoing packets would be
given an IP number of 255.255.255.255 up until the first given an IP number of 255.255.255.255 up until the first
SIOCAIFADDR ioctl is done. This would result in fully binding SIOCAIFADDR ioctl is done. This would result in fully binding
the socket. It would be up to <emphasis remap=bf>ppp</emphasis> the socket. It would be up to <application>ppp</application>
to change the source IP number, but only if it's set to to change the source IP number, but only if it's set to
255.255.255.255, and only the IP number and IP checksum would 255.255.255.255, and only the IP number and IP checksum would
need to change. This, however is a bit of a hack as the kernel need to change. This, however is a bit of a hack as the kernel
@ -9821,7 +9825,9 @@ ATDT1234567</programlisting>
<para>If the port numbers aren't consistent, there are three <para>If the port numbers aren't consistent, there are three
more options:</para> more options:</para>
<para><emphasis remap=bf>1)</emphasis> Submit support in <orderedlist>
<listitem>
<para>Submit support in
libalias. Examples of <quote>special cases</quote> can be found libalias. Examples of <quote>special cases</quote> can be found
in <filename>/usr/src/lib/libalias/alias_*.c</filename> in <filename>/usr/src/lib/libalias/alias_*.c</filename>
(<filename>alias_ftp.c</filename> is a good prototype). This (<filename>alias_ftp.c</filename> is a good prototype). This
@ -9834,16 +9840,22 @@ ATDT1234567</programlisting>
<para>This is the most difficult solution, but it is the best <para>This is the most difficult solution, but it is the best
and will make the software work with multiple machines.</para> and will make the software work with multiple machines.</para>
</listitem>
<para><emphasis remap=bf>2)</emphasis> Use a proxy. The <listitem>
<para>Use a proxy. The
application may support socks5 for example, or (as in the application may support socks5 for example, or (as in the
<quote>cvsup</quote> case) may have a <quote>passive</quote> <quote>cvsup</quote> case) may have a <quote>passive</quote>
option that avoids ever requesting that the peer open option that avoids ever requesting that the peer open
connections back to the local machine.</para> connections back to the local machine.</para>
</listitem>
<para><emphasis remap=bf>3)</emphasis> Redirect everything to <listitem>
<para>Redirect everything to
the internal machine using <literal>nat addr</literal>. This the internal machine using <literal>nat addr</literal>. This
is the sledge-hammer approach.</para> is the sledge-hammer approach.</para>
</listitem>
</orderedlist>
</answer> </answer>
</qandaentry> </qandaentry>
@ -9933,9 +9945,9 @@ ATDT1234567</programlisting>
</question> </question>
<answer> <answer>
<para>FCS stands for <emphasis remap=bf>F</emphasis>rame <para>FCS stands for <literal>F</literal>rame
<emphasis remap=bf>C</emphasis>heck <literal>C</literal>heck
<emphasis remap=bf>S</emphasis>equence. Each ppp packet <literal>S</literal>equence. Each ppp packet
has a checksum attached to ensure that the data being has a checksum attached to ensure that the data being
received is the data being sent. If the FCS of an incoming received is the data being sent. If the FCS of an incoming
packet is incorrect, the packet is dropped and the HDLC FCS packet is incorrect, the packet is dropped and the HDLC FCS
@ -9990,7 +10002,7 @@ ATDT1234567</programlisting>
router. MacOS and Windows 98 (and maybe other Microsoft OSs) router. MacOS and Windows 98 (and maybe other Microsoft OSs)
send TCP packets with a requested segment size too big to fit send TCP packets with a requested segment size too big to fit
into a PPPoE frame (MTU is 1500 by default for ethernet) into a PPPoE frame (MTU is 1500 by default for ethernet)
<emphasis remap=bf>and</emphasis> have the <quote>don't <emphasis>and</emphasis> have the <quote>don't
fragment</quote> bit set (default of TCP) and the Telco router fragment</quote> bit set (default of TCP) and the Telco router
is not sending ICMP <quote>must fragment</quote> back to the is not sending ICMP <quote>must fragment</quote> back to the
www site you are trying to load. (Alternatively, the router is www site you are trying to load. (Alternatively, the router is
@ -10038,12 +10050,12 @@ ATDT1234567</programlisting>
<literal>Save as Auto Configure</literal>, and click <literal>Save as Auto Configure</literal>, and click
<literal>Make Active</literal>.</para> <literal>Make Active</literal>.</para>
<para>The latest version of <emphasis remap=bf>ppp</emphasis> <para>The latest version of <application>ppp</application>
(2.3 or greater) has an <command>enable tcpmssfixup</command> (2.3 or greater) has an <command>enable tcpmssfixup</command>
command that will automatically adjust the MSS to an appropriate command that will automatically adjust the MSS to an appropriate
value. This facility is enabled by default. If you're stuck value. This facility is enabled by default. If you're stuck
with an older version of <emphasis remap=bf>ppp</emphasis>, you with an older version of <application>ppp</application>, you
may want to look at the <emphasis remap=bf>tcpmssd</emphasis> may want to look at the <application>tcpmssd</application>
port.</para> port.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -10056,7 +10068,7 @@ ATDT1234567</programlisting>
<answer> <answer>
<para>If all else fails, send as much information as you can, <para>If all else fails, send as much information as you can,
including your config files, how you're starting including your config files, how you're starting
<emphasis remap=bf>ppp</emphasis>, the relevant parts of your <application>ppp</application>, the relevant parts of your
log file and the output of the log file and the output of the
<command>netstat -rn</command> command (before and after connecting) to <command>netstat -rn</command> command (before and after connecting) to
the <email>freebsd-questions@FreeBSD.org</email> mailing list the <email>freebsd-questions@FreeBSD.org</email> mailing list
@ -10670,7 +10682,7 @@ raisechar=^^</programlisting>
<qandaentry> <qandaentry>
<question id="zmodem-tip"> <question id="zmodem-tip">
<para>How can I run zmodem with <para>How can I run zmodem with
<emphasis remap=tt>tip</emphasis>?</para> <application>tip</application>?</para>
</question> </question>
<answer> <answer>
@ -10840,7 +10852,7 @@ raisechar=^^</programlisting>
necessary and the transition made.</para> necessary and the transition made.</para>
<para>In FreeBSD's case, our shared library mechanism is based <para>In FreeBSD's case, our shared library mechanism is based
more closely on Sun's <emphasis remap=tt>SunOS</emphasis>-style more closely on Sun's <application>SunOS</application>-style
shared library mechanism and, as such, is very easy to use. shared library mechanism and, as such, is very easy to use.
However, starting with 3.0, FreeBSD officially supports However, starting with 3.0, FreeBSD officially supports
<acronym>ELF</acronym> binaries as the default format. Even <acronym>ELF</acronym> binaries as the default format. Even
@ -10967,9 +10979,9 @@ raisechar=^^</programlisting>
<warning> <warning>
<para>The <option>-R</option> option does a <para>The <option>-R</option> option does a
<acronym>RECURSIVE</acronym> <acronym>RECURSIVE</acronym>
<emphasis remap=tt>chmod</emphasis>. Be careful about &man.chmod.1;. Be careful about
specifying directories or symlinks to directories to specifying directories or symlinks to directories to
<emphasis remap=tt>chmod</emphasis>. If you want to <command>chmod</command>. If you want to
change the permissions of a directory referenced by a change the permissions of a directory referenced by a
symlink, use &man.chmod.1; symlink, use &man.chmod.1;
without any options and follow the symlink without any options and follow the symlink
@ -10992,7 +11004,7 @@ raisechar=^^</programlisting>
<qandaentry> <qandaentry>
<question id="login-8char"> <question id="login-8char">
<para>Why are login names <emphasis remap=bf>still</emphasis> <para>Why are login names <emphasis>still</emphasis>
restricted to 8 characters?</para> restricted to 8 characters?</para>
</question> </question>
@ -11036,7 +11048,7 @@ raisechar=^^</programlisting>
<answer> <answer>
<para>Yes, starting with version 3.0 you can using BSDI's <para>Yes, starting with version 3.0 you can using BSDI's
<emphasis remap=tt>doscmd</emphasis> DOS emulation which has <application>doscmd</application> DOS emulation which has
been integrated and enhanced. Send mail to <ulink been integrated and enhanced. Send mail to <ulink
URL="mailto:freebsd-emulation@FreeBSD.org">The FreeBSD URL="mailto:freebsd-emulation@FreeBSD.org">The FreeBSD
emulation discussion list</ulink> if you're interested in emulation discussion list</ulink> if you're interested in
@ -11074,7 +11086,7 @@ raisechar=^^</programlisting>
<para><ulink URL="http://www.grex.org/">Grex</ulink> provides a <para><ulink URL="http://www.grex.org/">Grex</ulink> provides a
site very similar to M-Net including the same bulletin board site very similar to M-Net including the same bulletin board
and interactive chat software. However, the machine is a Sun and interactive chat software. However, the machine is a Sun
4M and is running SunOS.</para> 4M and is running SunOS</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -11463,11 +11475,11 @@ raisechar=^^</programlisting>
<quote>-CURRENT</quote>.</para> <quote>-CURRENT</quote>.</para>
<para>Right now, <quote>-CURRENT</quote> is the 5.0 development <para>Right now, <quote>-CURRENT</quote> is the 5.0 development
stream and the <emphasis remap=bf>4-STABLE</emphasis> branch, stream and the <literal>4-STABLE</literal> branch,
<symbol>RELENG_4</symbol>, forked off from <symbol>RELENG_4</symbol>, forked off from
<quote>-CURRENT</quote> in Mar 2000.</para> <quote>-CURRENT</quote> in Mar 2000.</para>
<para>The <emphasis remap=bf>2.2-STABLE</emphasis> branch, <para>The <literal>2.2-STABLE</literal> branch,
<symbol>RELENG_2_2</symbol>, departed -CURRENT in November <symbol>RELENG_2_2</symbol>, departed -CURRENT in November
1996, and has pretty much been retired.</para> 1996, and has pretty much been retired.</para>
</answer> </answer>
@ -11609,7 +11621,7 @@ doc-all</programlisting>
</question> </question>
<answer> <answer>
<para>Yes, you can do this <emphasis remap=tt>without</emphasis> <para>Yes, you can do this <literal>without</literal>
downloading the whole source tree by using the <ulink downloading the whole source tree by using the <ulink
URL="../handbook/synching.html#CTM">CTM facility.</ulink></para> URL="../handbook/synching.html#CTM">CTM facility.</ulink></para>
</answer> </answer>
@ -11782,7 +11794,7 @@ ${RELEASEDIR}/tarballs/bindist/bin_tgz.)</programlisting>
<para>This depends on whether or not you plan on making the <para>This depends on whether or not you plan on making the
driver publicly available. If you do, then please send us a driver publicly available. If you do, then please send us a
copy of the driver source code, plus the appropriate copy of the driver source code, plus the appropriate
modifications to <emphasis remap=tt>files.i386</emphasis>, a modifications to <filename>files.i386</filename>, a
sample configuration file entry, and the appropriate sample configuration file entry, and the appropriate
&man.MAKEDEV.8; &man.MAKEDEV.8;
code to create any special files your device uses. If you do code to create any special files your device uses. If you do
@ -11962,13 +11974,13 @@ Cc: current@FreeBSD.org</programlisting>
<para> To make sure you capture a crash dump, you need edit <para> To make sure you capture a crash dump, you need edit
<filename>/etc/rc.conf</filename> and set <filename>/etc/rc.conf</filename> and set
<emphasis remap=tt>dumpdev</emphasis> to point to your swap <literal>dumpdev</literal> to point to your swap
partition. This will cause the <command>rc(8)</command> scripts partition. This will cause the <command>rc(8)</command> scripts
to use the <command>dumpon(8)</command> command to enable crash to use the <command>dumpon(8)</command> command to enable crash
dumps. You can also run <command>dumpon(8)</command> manually. dumps. You can also run <command>dumpon(8)</command> manually.
After a panic, the crash dump can be recovered using After a panic, the crash dump can be recovered using
<command>savecore(8)</command>; if <emphasis <command>savecore(8)</command>; if
remap=tt>dumpdev</emphasis> is set in <literal>dumpdev</literal> is set in
<filename>/etc/rc.conf</filename>, the <command>rc(8)</command> <filename>/etc/rc.conf</filename>, the <command>rc(8)</command>
scripts will run <command>savecore(8)</command> automatically scripts will run <command>savecore(8)</command> automatically
and put the crash dump in and put the crash dump in
@ -12036,8 +12048,8 @@ Cc: current@FreeBSD.org</programlisting>
<para>The ELF toolchain does not, by default, make the symbols <para>The ELF toolchain does not, by default, make the symbols
defined in an executable visible to the dynamic linker. defined in an executable visible to the dynamic linker.
Consequently <function>dlsym()</function> searches on handles Consequently <function>dlsym()</function> searches on handles
obtained from calls to <emphasis remap=tt>dlopen(NULL, obtained from calls to <function>dlopen(NULL,
flags)</emphasis> will fail to find such symbols.</para> flags)</function> will fail to find such symbols.</para>
<para>If you want to search, using <function>dlsym()</function>, <para>If you want to search, using <function>dlsym()</function>,
for symbols present in the main executable of a process, you for symbols present in the main executable of a process, you
@ -12105,10 +12117,10 @@ SECTIONS
<para>Then reconfig and rebuild your kernel. You will probably <para>Then reconfig and rebuild your kernel. You will probably
have problems with <command>ps(1)</command>, have problems with <command>ps(1)</command>,
<command>top(1)</command> and the like; <emphasis remap=tt>make <command>top(1)</command> and the like; <command>make
world</emphasis> should take care of it (or a manual rebuild of world</command> should take care of it (or a manual rebuild of
<emphasis remap=tt>libkvm</emphasis>, <emphasis <filename>libkvm</filename>,
remap=tt>ps</emphasis> and <emphasis remap=tt>top</emphasis> <command>ps</command> and <command>top</command>
after copying the patched <filename>pmap.h</filename> to after copying the patched <filename>pmap.h</filename> to
<filename>/usr/include/vm/</filename>.</para> <filename>/usr/include/vm/</filename>.</para>

230
en_US.ISO_8859-1/books/faq/book.sgml
View file

@ -14,7 +14,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor> <corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.193 2001/05/14 22:57:35 dd Exp $</pubdate> <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.194 2001/05/15 00:24:18 dd Exp $</pubdate>
<copyright> <copyright>
<year>1995</year> <year>1995</year>
@ -3669,7 +3669,7 @@ quit</programlisting>
<para> <para>
<note> <note>
<para>You can not use a <para>You can not use a
<emphasis remap=bf>dangerously dedicated</emphasis> disk <literal>dangerously dedicated</literal> disk
with an HP Netserver. See <link linkend="dedicate">this with an HP Netserver. See <link linkend="dedicate">this
note</link> for more info.</para> note</link> for more info.</para>
</note></para> </note></para>
@ -3954,7 +3954,7 @@ quit</programlisting>
<literal>2e8</literal>, and the fourth serial port does too. <literal>2e8</literal>, and the fourth serial port does too.
Due to a bug (feature?) in the &man.sio.4; Due to a bug (feature?) in the &man.sio.4;
driver it will touch this port even if you don't have the driver it will touch this port even if you don't have the
fourth serial port, and <emphasis remap=bf>even</emphasis> if fourth serial port, and <emphasis>even</emphasis> if
you disable sio3 (the fourth port) which normally uses this you disable sio3 (the fourth port) which normally uses this
address.</para> address.</para>
@ -5237,7 +5237,7 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
math co-processor, right? Wrong! :-) The math co-processor, right? Wrong! :-) The
<devicename>npx0</devicename> is <devicename>npx0</devicename> is
<emphasis>MANDATORY</emphasis>. Even if you don't have a <emphasis>MANDATORY</emphasis>. Even if you don't have a
mathematic co-processor, you <emphasis remap=bf>must</emphasis> mathematic co-processor, you <emphasis>must</emphasis>
include the <devicename>npx0</devicename> device.</para> include the <devicename>npx0</devicename> device.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -5289,12 +5289,12 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
</question> </question>
<answer> <answer>
<para><emphasis remap=bf>Q.</emphasis> When I compile a kernel <para>When I compile a kernel
with multi-port serial code, it tells me that only the first with multi-port serial code, it tells me that only the first
port is probed and the rest skipped due to interrupt conflicts. port is probed and the rest skipped due to interrupt conflicts.
How do I fix this?</para> How do I fix this?</para>
<para><emphasis remap=bf>A.</emphasis> The problem here is that <para>The problem here is that
FreeBSD has code built-in to keep the kernel from getting FreeBSD has code built-in to keep the kernel from getting
trashed due to hardware or software conflicts. The way to fix trashed due to hardware or software conflicts. The way to fix
this is to leave out the IRQ settings on all but one port. Here this is to leave out the IRQ settings on all but one port. Here
@ -5650,18 +5650,18 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
</question> </question>
<answer> <answer>
<para><emphasis remap=bf> Digital UNIX</emphasis> UFS CDROMs can <para><literal>Digital UNIX</literal> UFS CDROMs can
be mounted directly on FreeBSD. Mounting disk partitions from be mounted directly on FreeBSD. Mounting disk partitions from
Digital UNIX and other systems that support UFS may be more Digital UNIX and other systems that support UFS may be more
complex, depending on the details of the disk partitioning for complex, depending on the details of the disk partitioning for
the operating system in question.</para> the operating system in question.</para>
<para><emphasis remap=bf> Linux</emphasis>: 2.2 and later have <para><literal>Linux</literal>: 2.2 and later have
support for <emphasis remap=bf>ext2fs</emphasis> partitions. support for <literal>ext2fs</literal> partitions.
See &man.mount.ext2fs.8; See &man.mount.ext2fs.8;
for more information.</para> for more information.</para>
<para><emphasis remap=bf> NT</emphasis>: A read-only NTFS driver <para><literal>NT</literal>: A read-only NTFS driver
exists for FreeBSD. For more information, see this tutorial by exists for FreeBSD. For more information, see this tutorial by
Mark Ovens at Mark Ovens at
<ulink URL="http://ukug.uk.freebsd.org/~mark/ntfs_install.html"> <ulink URL="http://ukug.uk.freebsd.org/~mark/ntfs_install.html">
@ -5699,7 +5699,7 @@ C:\="DOS"</programlisting>
<para>For 2.2.x systems this procedure assumes that DOS, NT, <para>For 2.2.x systems this procedure assumes that DOS, NT,
FreeBSD, or whatever have been installed into their respective FreeBSD, or whatever have been installed into their respective
fdisk partitions on the <emphasis remap=bf>same</emphasis> fdisk partitions on the <emphasis>same</emphasis>
disk. This example was tested on a system where DOS &amp; NT disk. This example was tested on a system where DOS &amp; NT
were on the first fdisk partition, and FreeBSD on the second. were on the first fdisk partition, and FreeBSD on the second.
FreeBSD was also set up to boot from its native partition, not FreeBSD was also set up to boot from its native partition, not
@ -6503,7 +6503,7 @@ rewrite: ruleset 0 returns: $# uucp-dom $@ if-bus $: foo \
the rest.</para> the rest.</para>
<para>If you've got a dynamically assigned IP number and use a <para>If you've got a dynamically assigned IP number and use a
dialup <emphasis remap=bf>ppp</emphasis> connection to the dialup <application>ppp</application> connection to the
internet, you will probably be given a mailbox on your ISPs internet, you will probably be given a mailbox on your ISPs
mail server. Lets assume your ISPs domain is mail server. Lets assume your ISPs domain is
<hostid role="domainname">myISP.com</hostid>, and that your user name is <hostid role="domainname">myISP.com</hostid>, and that your user name is
@ -7365,7 +7365,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
<filename>/dev/sysmouse</filename>. All mouse events received <filename>/dev/sysmouse</filename>. All mouse events received
from the real mouse device are written to the sysmouse device from the real mouse device are written to the sysmouse device
via moused. If you wish to use your mouse on one or more via moused. If you wish to use your mouse on one or more
virtual consoles, <emphasis remap=bf>and</emphasis> use X, see virtual consoles, <emphasis>and</emphasis> use X, see
<xref linkend="moused" remap="another section"> and set up <xref linkend="moused" remap="another section"> and set up
moused.</para> moused.</para>
@ -7844,7 +7844,7 @@ ttyvb "/usr/libexec/getty Pc" cons25 off secure</programlisting>
URL="http://www.FreeBSD.org/cgi/man.cgi?manpath=xfree86&amp;query=startx"> URL="http://www.FreeBSD.org/cgi/man.cgi?manpath=xfree86&amp;query=startx">
startx</ulink>, the permissions on startx</ulink>, the permissions on
<filename>/dev/console</filename> will <filename>/dev/console</filename> will
<emphasis remap=tt>not</emphasis> get changed, resulting in <emphasis>not</emphasis> get changed, resulting in
things like <ulink things like <ulink
URL="http://www.FreeBSD.org/cgi/man.cgi?manpath=xfree86&amp;query=xterm"> URL="http://www.FreeBSD.org/cgi/man.cgi?manpath=xfree86&amp;query=xterm">
xterm -C</ulink> and <ulink xterm -C</ulink> and <ulink
@ -8740,7 +8740,7 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
<listitem> <listitem>
<para>Place heavily triggered rules earlier in the rule <para>Place heavily triggered rules earlier in the rule
set than those rarely used (<emphasis remap=bf>without set than those rarely used (<emphasis>without
changing the permissiveness of the firewall</emphasis>, changing the permissiveness of the firewall</emphasis>,
of course). You can see which rules are used most often of course). You can see which rules are used most often
by examining the packet counting statistics with by examining the packet counting statistics with
@ -8970,10 +8970,10 @@ Znyx (2.2.x) ZX312, ZX314, ZX342, ZX345, ZX346, ZX348
<programlisting>set log Phase Chat Connect Carrier lcp ipcp ccp command</programlisting> <programlisting>set log Phase Chat Connect Carrier lcp ipcp ccp command</programlisting>
<para>This command may be typed at the <para>This command may be typed at the
<emphasis remap=bf>ppp</emphasis> command prompt or it may be <application>ppp</application> command prompt or it may be
entered in the <filename>/etc/ppp/ppp.conf</filename> entered in the <filename>/etc/ppp/ppp.conf</filename>
configuration file (the start of the configuration file (the start of the
<emphasis remap=bf>default</emphasis> section is the best <literal>default</literal> section is the best
place to put it). Make sure that place to put it). Make sure that
<filename>/etc/syslog.conf</filename> (see &man.syslog.conf.5;) contains the lines</para> <filename>/etc/syslog.conf</filename> (see &man.syslog.conf.5;) contains the lines</para>
@ -9038,7 +9038,7 @@ default 10.0.0.2 UGSc 0 0 tun0
running an old version of &man.ppp.8; running an old version of &man.ppp.8;
that doesn't understand the word <literal>HISADDR</literal> that doesn't understand the word <literal>HISADDR</literal>
in the ppp.conf file. If your version of in the ppp.conf file. If your version of
<emphasis remap=bf>ppp</emphasis> is from before FreeBSD <application>ppp</application> is from before FreeBSD
2.2.5, change the</para> 2.2.5, change the</para>
<programlisting>add 0 0 HISADDR</programlisting> <programlisting>add 0 0 HISADDR</programlisting>
@ -9080,7 +9080,7 @@ default 10.0.0.2 UGSc 0 0 tun0
file. This is only necessary if you have a dynamic IP address file. This is only necessary if you have a dynamic IP address
or don't know the address of your gateway. If you're using or don't know the address of your gateway. If you're using
interactive mode, you can type the following after entering interactive mode, you can type the following after entering
<emphasis remap=tt>packet mode</emphasis> (packet mode is <literal>packet mode</literal> (packet mode is
indicated by the capitalized <acronym>PPP</acronym> in the indicated by the capitalized <acronym>PPP</acronym> in the
prompt):</para> prompt):</para>
@ -9111,8 +9111,8 @@ add 0 0 HISADDR</programlisting>
closed due to a timeout. It is possible to put this command in closed due to a timeout. It is possible to put this command in
the <filename>ppp.conf</filename> file, or to type it at the the <filename>ppp.conf</filename> file, or to type it at the
prompt in interactive mode. It is also possible to adjust it on prompt in interactive mode. It is also possible to adjust it on
the fly while the line is active by connecting to <emphasis the fly while the line is active by connecting to
remap=bf>ppp</emphasis>s server socket using <application>ppp</application>s server socket using
&man.telnet.1; or &man.pppctl.8;. &man.telnet.1; or &man.pppctl.8;.
Refer to the Refer to the
&man.ppp.8; man &man.ppp.8; man
@ -9267,15 +9267,19 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
would wait for the peer to initiate the Line Control Protocol would wait for the peer to initiate the Line Control Protocol
(LCP). Many ISPs will not initiate negotiations and expect (LCP). Many ISPs will not initiate negotiations and expect
the client to do so. To force the client to do so. To force
<emphasis remap=bf>ppp</emphasis> to initiate the LCP, use the <application>ppp</application> to initiate the LCP, use the
following line:</para> following line:</para>
<programlisting>set openmode active</programlisting> <programlisting>set openmode active</programlisting>
<para><emphasis remap=bf>Note</emphasis>: It usually does no <para>
<note>
<para>It usually does no
harm if both sides initiate negotiation, so openmode is now harm if both sides initiate negotiation, so openmode is now
active by default. However, the next section explains when active by default. However, the next section explains when
it <emphasis remap=bf>does</emphasis> do some harm.</para> it <emphasis>does</emphasis> do some harm.</para>
</note>
</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -9349,44 +9353,44 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
<answer> <answer>
<para>There is currently an implementation mis-feature in <para>There is currently an implementation mis-feature in
<emphasis remap=bf>ppp</emphasis> where it doesn't associate <application>ppp</application> where it doesn't associate
LCP, CCP &amp; IPCP responses with their original requests. As LCP, CCP &amp; IPCP responses with their original requests. As
a result, if one <emphasis remap=bf>ppp</emphasis> a result, if one <application>ppp</application>
implementation is more than 6 seconds slower than the other implementation is more than 6 seconds slower than the other
side, the other side will send two additional LCP configuration side, the other side will send two additional LCP configuration
requests. This is fatal.</para> requests. This is fatal.</para>
<para>Consider two implementations, <para>Consider two implementations,
<emphasis remap=bf>A</emphasis> and <emphasis <hostid>A</hostid> and
remap=bf>B</emphasis>. <emphasis remap=bf>A</emphasis> starts <hostid>B</hostid>. <hostid>A</hostid> starts
sending LCP requests immediately after connecting and <emphasis sending LCP requests immediately after connecting and
remap=bf>B</emphasis> takes 7 seconds to start. When <emphasis <hostid>B</hostid> takes 7 seconds to start. When
remap=bf>B</emphasis> starts, <emphasis remap=bf>A</emphasis> <hostid>B</hostid> starts, <hostid>A</hostid>
has sent 3 LCP REQs. We're assuming the line has ECHO switched has sent 3 LCP REQs. We're assuming the line has ECHO switched
off, otherwise we'd see magic number problems as described in off, otherwise we'd see magic number problems as described in
the previous section. <emphasis remap=bf>B</emphasis> sends a the previous section. <hostid>B</hostid> sends a
REQ, then an ACK to the first of <emphasis REQ, then an ACK to the first of
remap=bf>A</emphasis>'s REQs. This results in <emphasis <hostid>A</hostid>'s REQs. This results in
remap=bf>A</emphasis> entering the <acronym>OPENED</acronym> <hostid>A</hostid> entering the <acronym>OPENED</acronym>
state and sending and ACK (the first) back to <emphasis state and sending and ACK (the first) back to
remap=bf>B</emphasis>. In the meantime, <emphasis <hostid>B</hostid>. In the meantime,
remap=bf>B</emphasis> sends back two more ACKs in response to <hostid>B</hostid> sends back two more ACKs in response to
the two additional REQs sent by <emphasis remap=bf>A</emphasis> the two additional REQs sent by <hostid>A</hostid>
before <emphasis remap=bf>B</emphasis> started up. <emphasis before <hostid>B</hostid> started up.
remap=bf>B</emphasis> then receives the first ACK from <hostid>B</hostid> then receives the first ACK from
<emphasis remap=bf>A</emphasis> and enters the <hostid>A</hostid> and enters the
<acronym>OPENED</acronym> state. <emphasis <acronym>OPENED</acronym> state.
remap=bf>A</emphasis> receives the second ACK from <emphasis <hostid>A</hostid> receives the second ACK from
remap=bf>B</emphasis> and goes back to the <emphasis <hostid>B</hostid> and goes back to the
remap=bf>REQ-SENT</emphasis> state, sending another (forth) REQ <literal>REQ-SENT</literal> state, sending another (forth) REQ
as per the RFC. It then receives the third ACK and enters the as per the RFC. It then receives the third ACK and enters the
<acronym>OPENED</acronym> state. In the meantime, <emphasis <acronym>OPENED</acronym> state. In the meantime,
remap=bf>B</emphasis> receives the forth REQ from <emphasis <hostid>B</hostid> receives the forth REQ from
remap=bf>A</emphasis>, resulting in it reverting to the <hostid>A</hostid>, resulting in it reverting to the
<emphasis remap=bf>ACK-SENT</emphasis> state and sending <literal>ACK-SENT</literal> state and sending
another (second) REQ and (forth) ACK as per the RFC. <emphasis another (second) REQ and (forth) ACK as per the RFC.
remap=bf>A</emphasis> gets the REQ, goes into <emphasis <hostid>A</hostid> gets the REQ, goes into
remap=bf>REQ-SENT</emphasis> and sends another REQ. It <literal>REQ-SENT</literal> and sends another REQ. It
immediately receives the following ACK and enters immediately receives the following ACK and enters
<acronym>OPENED</acronym>.</para> <acronym>OPENED</acronym>.</para>
@ -9394,7 +9398,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
getting nowhere and gives up.</para> getting nowhere and gives up.</para>
<para>The best way to avoid this is to configure one side to be <para>The best way to avoid this is to configure one side to be
<emphasis remap=bf>passive</emphasis> - that is, make one side <literal>passive</literal> - that is, make one side
wait for the other to start negotiating. This can be done wait for the other to start negotiating. This can be done
with the</para> with the</para>
@ -9406,12 +9410,12 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
<programlisting>set stopped N</programlisting> <programlisting>set stopped N</programlisting>
<para>command to limit the amount of time that <para>command to limit the amount of time that
<emphasis remap=bf>ppp</emphasis> waits for the peer to begin <application>ppp</application> waits for the peer to begin
negotiations. Alternatively, the</para> negotiations. Alternatively, the</para>
<programlisting>set openmode active N</programlisting> <programlisting>set openmode active N</programlisting>
<para>command (where <emphasis remap=bf>N</emphasis> is the <para>command (where <replaceable>N</replaceable> is the
number of seconds to wait before starting negotiations) can be number of seconds to wait before starting negotiations) can be
used. Check the manual page for details.</para> used. Check the manual page for details.</para>
</answer> </answer>
@ -9425,11 +9429,11 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
<answer> <answer>
<para>Prior to version 2.2.5 of FreeBSD, it was possible that <para>Prior to version 2.2.5 of FreeBSD, it was possible that
your link was disabled shortly after connection due to your link was disabled shortly after connection due to
<emphasis remap=bf>ppp</emphasis> mis-handling Predictor1 <application>ppp</application> mis-handling Predictor1
compression negotiation. This would only happen if both sides compression negotiation. This would only happen if both sides
tried to negotiate different Compression Control Protocols tried to negotiate different Compression Control Protocols
(CCP). This problem is now corrected, but if you're still (CCP). This problem is now corrected, but if you're still
running an old version of <emphasis remap=bf>ppp</emphasis>, running an old version of <application>ppp</application>,
the problem can be circumvented with the line</para> the problem can be circumvented with the line</para>
<programlisting>disable pred1</programlisting> <programlisting>disable pred1</programlisting>
@ -9465,7 +9469,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
</question> </question>
<answer> <answer>
<para>There is no way for <emphasis remap=bf>ppp</emphasis> to <para>There is no way for <application>ppp</application> to
automatically determine that a direct connection has been automatically determine that a direct connection has been
dropped. This is due to the lines that are used in a dropped. This is due to the lines that are used in a
null-modem serial cable. When using this sort of connection, null-modem serial cable. When using this sort of connection,
@ -9482,7 +9486,7 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
<para>Why does ppp dial for no reason in -auto mode</para> <para>Why does ppp dial for no reason in -auto mode</para>
</question><answer> </question><answer>
<para>If <emphasis remap=bf>ppp</emphasis> is dialing <para>If <application>ppp</application> is dialing
unexpectedly, you must determine the cause, and set up Dial unexpectedly, you must determine the cause, and set up Dial
filters (dfilters) to prevent such dialing.</para> filters (dfilters) to prevent such dialing.</para>
@ -9497,8 +9501,8 @@ deny pred1 deflate deflate24 protocomp acfcomp shortseq vj</programlisting>
<para>You can now disable dialing under these circumstances. <para>You can now disable dialing under these circumstances.
Usually, this sort of problem arises due to DNS lookups. To Usually, this sort of problem arises due to DNS lookups. To
prevent DNS lookups from establishing a connection (this will prevent DNS lookups from establishing a connection (this will
<emphasis remap=bf>not</emphasis> prevent <emphasis>not</emphasis> prevent
<emphasis remap=bf>ppp</emphasis> from passing the packets <application>ppp</application> from passing the packets
through an established connection), use the following:</para> through an established connection), use the following:</para>
<programlisting>set dfilter 1 deny udp src eq 53 <programlisting>set dfilter 1 deny udp src eq 53
@ -9563,7 +9567,7 @@ CCP: Received Terminate Ack (1) state = Req-Sent (6)</programlisting>
via syslogd.</para> via syslogd.</para>
<para>The ppp specification says that an MRU of 1500 should <para>The ppp specification says that an MRU of 1500 should
<emphasis remap=bf>always</emphasis> be accepted as a minimum, <emphasis>always</emphasis> be accepted as a minimum,
despite any LCP negotiations, therefore it is possible that despite any LCP negotiations, therefore it is possible that
should you decrease the MTU to less than 1500, your ISP will should you decrease the MTU to less than 1500, your ISP will
transmit packets of 1500 regardless, and you will tickle this transmit packets of 1500 regardless, and you will tickle this
@ -9602,7 +9606,7 @@ CCP: Received Terminate Ack (1) state = Req-Sent (6)</programlisting>
\"\" ATZ OK-ATZ-OK ATDT\\T TIMEOUT 60 CONNECT \\c \\n"</programlisting> \"\" ATZ OK-ATZ-OK ATDT\\T TIMEOUT 60 CONNECT \\c \\n"</programlisting>
<para>Here, we get our CONNECT, send nothing, then expect a <para>Here, we get our CONNECT, send nothing, then expect a
line-feed, forcing <emphasis remap=bf>ppp</emphasis> to read line-feed, forcing <application>ppp</application> to read
the whole CONNECT response.</para> the whole CONNECT response.</para>
</answer> </answer>
@ -9618,7 +9622,7 @@ CCP: Received Terminate Ack (1) state = Req-Sent (6)</programlisting>
interpret strings such as interpret strings such as
<literal>set phone "123 456 789"</literal> correctly (and <literal>set phone "123 456 789"</literal> correctly (and
realize that the number is actually only realize that the number is actually only
<emphasis remap=bf>one</emphasis> argument. In order to specify <emphasis>one</emphasis> argument. In order to specify
a <literal>"</literal> character, you must escape it using a a <literal>"</literal> character, you must escape it using a
backslash (<literal>\</literal>).</para> backslash (<literal>\</literal>).</para>
@ -9667,9 +9671,9 @@ ATDT1234567</programlisting>
dump core. Because ppp runs with an effective user id of 0, dump core. Because ppp runs with an effective user id of 0,
the operating system will not write ppps core image to disk the operating system will not write ppps core image to disk
before terminating it. If, however ppp before terminating it. If, however ppp
<emphasis remap=bf>is</emphasis> actually termating due to a is actually termating due to a
segmentation violation or some other signal that normally segmentation violation or some other signal that normally
causes core to be dumped, <emphasis remap=bf>and</emphasis> causes core to be dumped, <emphasis>and</emphasis>
you're sure you're using the latest version (see the start of you're sure you're using the latest version (see the start of
this section), then you should do the following:</para> this section), then you should do the following:</para>
@ -9719,18 +9723,18 @@ ATDT1234567</programlisting>
<answer> <answer>
<para>This was a known problem with <para>This was a known problem with
<emphasis remap=bf>ppp</emphasis> set up to negotiate a <application>ppp</application> set up to negotiate a
dynamic local IP number with the peer in auto mode. It is dynamic local IP number with the peer in auto mode. It is
fixed in the latest version - search the man page for fixed in the latest version - search the man page for
<emphasis remap=bf>iface</emphasis>.</para> <literal>iface</literal>.</para>
<para>The problem was that when that initial program calls <para>The problem was that when that initial program calls
&man.connect.2;, the IP number of the tun interface is &man.connect.2;, the IP number of the tun interface is
assigned to the socket endpoint. The kernel creates the first assigned to the socket endpoint. The kernel creates the first
outgoing packet and writes it to the tun device. <emphasis outgoing packet and writes it to the tun device.
remap=bf>Ppp</emphasis> then reads the packet and establishes a <application>ppp</application> then reads the packet and establishes a
connection. If, as a result of <emphasis connection. If, as a result of
remap=bf>ppp</emphasis>s dynamic IP assignment, the interface <application>ppp</application>s dynamic IP assignment, the interface
address is changed, the original socket endpoint will be address is changed, the original socket endpoint will be
invalid. Any subsequent packets sent to the peer will usually invalid. Any subsequent packets sent to the peer will usually
be dropped. Even if they aren't, any responses will not route be dropped. Even if they aren't, any responses will not route
@ -9739,8 +9743,8 @@ ATDT1234567</programlisting>
<para>There are several theoretical ways to approach this <para>There are several theoretical ways to approach this
problem. It would be nicest if the peer would re-assign the problem. It would be nicest if the peer would re-assign the
same IP number if possible <emphasis remap=tt>:-)</emphasis> same IP number if possible <literal>:-)</literal>
The current version of <emphasis remap=bf>ppp</emphasis> does The current version of <application>ppp</application> does
this, but most other implementations don't.</para> this, but most other implementations don't.</para>
<para>The easiest method from our side would be to never change <para>The easiest method from our side would be to never change
@ -9748,7 +9752,7 @@ ATDT1234567</programlisting>
packets so that the source IP number is changed from the packets so that the source IP number is changed from the
interface IP to the negotiated IP on the fly. This is interface IP to the negotiated IP on the fly. This is
essentially what the <literal>iface-alias</literal> option in essentially what the <literal>iface-alias</literal> option in
the latest version of <emphasis remap=bf>ppp</emphasis> is the latest version of <application>ppp</application> is
doing (with the help of doing (with the help of
&man.libalias.3; and ppp's <option>-nat</option> switch) - &man.libalias.3; and ppp's <option>-nat</option> switch) -
it's maintaining all previous interface addresses and NATing it's maintaining all previous interface addresses and NATing
@ -9756,7 +9760,7 @@ ATDT1234567</programlisting>
<para>Another alternative (and probably the most reliable) would <para>Another alternative (and probably the most reliable) would
be to implement a system call that changes all bound sockets be to implement a system call that changes all bound sockets
from one IP to another. <emphasis remap=bf>Ppp</emphasis> would from one IP to another. <application>ppp</application> would
use this call to modify the sockets of all existing programs use this call to modify the sockets of all existing programs
when a new IP number is negotiated. The same system call could when a new IP number is negotiated. The same system call could
be used by dhcp clients when they are forced to re-bind() their be used by dhcp clients when they are forced to re-bind() their
@ -9766,7 +9770,7 @@ ATDT1234567</programlisting>
brought up without an IP number. Outgoing packets would be brought up without an IP number. Outgoing packets would be
given an IP number of 255.255.255.255 up until the first given an IP number of 255.255.255.255 up until the first
SIOCAIFADDR ioctl is done. This would result in fully binding SIOCAIFADDR ioctl is done. This would result in fully binding
the socket. It would be up to <emphasis remap=bf>ppp</emphasis> the socket. It would be up to <application>ppp</application>
to change the source IP number, but only if it's set to to change the source IP number, but only if it's set to
255.255.255.255, and only the IP number and IP checksum would 255.255.255.255, and only the IP number and IP checksum would
need to change. This, however is a bit of a hack as the kernel need to change. This, however is a bit of a hack as the kernel
@ -9821,7 +9825,9 @@ ATDT1234567</programlisting>
<para>If the port numbers aren't consistent, there are three <para>If the port numbers aren't consistent, there are three
more options:</para> more options:</para>
<para><emphasis remap=bf>1)</emphasis> Submit support in <orderedlist>
<listitem>
<para>Submit support in
libalias. Examples of <quote>special cases</quote> can be found libalias. Examples of <quote>special cases</quote> can be found
in <filename>/usr/src/lib/libalias/alias_*.c</filename> in <filename>/usr/src/lib/libalias/alias_*.c</filename>
(<filename>alias_ftp.c</filename> is a good prototype). This (<filename>alias_ftp.c</filename> is a good prototype). This
@ -9834,16 +9840,22 @@ ATDT1234567</programlisting>
<para>This is the most difficult solution, but it is the best <para>This is the most difficult solution, but it is the best
and will make the software work with multiple machines.</para> and will make the software work with multiple machines.</para>
</listitem>
<para><emphasis remap=bf>2)</emphasis> Use a proxy. The <listitem>
<para>Use a proxy. The
application may support socks5 for example, or (as in the application may support socks5 for example, or (as in the
<quote>cvsup</quote> case) may have a <quote>passive</quote> <quote>cvsup</quote> case) may have a <quote>passive</quote>
option that avoids ever requesting that the peer open option that avoids ever requesting that the peer open
connections back to the local machine.</para> connections back to the local machine.</para>
</listitem>
<para><emphasis remap=bf>3)</emphasis> Redirect everything to <listitem>
<para>Redirect everything to
the internal machine using <literal>nat addr</literal>. This the internal machine using <literal>nat addr</literal>. This
is the sledge-hammer approach.</para> is the sledge-hammer approach.</para>
</listitem>
</orderedlist>
</answer> </answer>
</qandaentry> </qandaentry>
@ -9933,9 +9945,9 @@ ATDT1234567</programlisting>
</question> </question>
<answer> <answer>
<para>FCS stands for <emphasis remap=bf>F</emphasis>rame <para>FCS stands for <literal>F</literal>rame
<emphasis remap=bf>C</emphasis>heck <literal>C</literal>heck
<emphasis remap=bf>S</emphasis>equence. Each ppp packet <literal>S</literal>equence. Each ppp packet
has a checksum attached to ensure that the data being has a checksum attached to ensure that the data being
received is the data being sent. If the FCS of an incoming received is the data being sent. If the FCS of an incoming
packet is incorrect, the packet is dropped and the HDLC FCS packet is incorrect, the packet is dropped and the HDLC FCS
@ -9990,7 +10002,7 @@ ATDT1234567</programlisting>
router. MacOS and Windows 98 (and maybe other Microsoft OSs) router. MacOS and Windows 98 (and maybe other Microsoft OSs)
send TCP packets with a requested segment size too big to fit send TCP packets with a requested segment size too big to fit
into a PPPoE frame (MTU is 1500 by default for ethernet) into a PPPoE frame (MTU is 1500 by default for ethernet)
<emphasis remap=bf>and</emphasis> have the <quote>don't <emphasis>and</emphasis> have the <quote>don't
fragment</quote> bit set (default of TCP) and the Telco router fragment</quote> bit set (default of TCP) and the Telco router
is not sending ICMP <quote>must fragment</quote> back to the is not sending ICMP <quote>must fragment</quote> back to the
www site you are trying to load. (Alternatively, the router is www site you are trying to load. (Alternatively, the router is
@ -10038,12 +10050,12 @@ ATDT1234567</programlisting>
<literal>Save as Auto Configure</literal>, and click <literal>Save as Auto Configure</literal>, and click
<literal>Make Active</literal>.</para> <literal>Make Active</literal>.</para>
<para>The latest version of <emphasis remap=bf>ppp</emphasis> <para>The latest version of <application>ppp</application>
(2.3 or greater) has an <command>enable tcpmssfixup</command> (2.3 or greater) has an <command>enable tcpmssfixup</command>
command that will automatically adjust the MSS to an appropriate command that will automatically adjust the MSS to an appropriate
value. This facility is enabled by default. If you're stuck value. This facility is enabled by default. If you're stuck
with an older version of <emphasis remap=bf>ppp</emphasis>, you with an older version of <application>ppp</application>, you
may want to look at the <emphasis remap=bf>tcpmssd</emphasis> may want to look at the <application>tcpmssd</application>
port.</para> port.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -10056,7 +10068,7 @@ ATDT1234567</programlisting>
<answer> <answer>
<para>If all else fails, send as much information as you can, <para>If all else fails, send as much information as you can,
including your config files, how you're starting including your config files, how you're starting
<emphasis remap=bf>ppp</emphasis>, the relevant parts of your <application>ppp</application>, the relevant parts of your
log file and the output of the log file and the output of the
<command>netstat -rn</command> command (before and after connecting) to <command>netstat -rn</command> command (before and after connecting) to
the <email>freebsd-questions@FreeBSD.org</email> mailing list the <email>freebsd-questions@FreeBSD.org</email> mailing list
@ -10670,7 +10682,7 @@ raisechar=^^</programlisting>
<qandaentry> <qandaentry>
<question id="zmodem-tip"> <question id="zmodem-tip">
<para>How can I run zmodem with <para>How can I run zmodem with
<emphasis remap=tt>tip</emphasis>?</para> <application>tip</application>?</para>
</question> </question>
<answer> <answer>
@ -10840,7 +10852,7 @@ raisechar=^^</programlisting>
necessary and the transition made.</para> necessary and the transition made.</para>
<para>In FreeBSD's case, our shared library mechanism is based <para>In FreeBSD's case, our shared library mechanism is based
more closely on Sun's <emphasis remap=tt>SunOS</emphasis>-style more closely on Sun's <application>SunOS</application>-style
shared library mechanism and, as such, is very easy to use. shared library mechanism and, as such, is very easy to use.
However, starting with 3.0, FreeBSD officially supports However, starting with 3.0, FreeBSD officially supports
<acronym>ELF</acronym> binaries as the default format. Even <acronym>ELF</acronym> binaries as the default format. Even
@ -10967,9 +10979,9 @@ raisechar=^^</programlisting>
<warning> <warning>
<para>The <option>-R</option> option does a <para>The <option>-R</option> option does a
<acronym>RECURSIVE</acronym> <acronym>RECURSIVE</acronym>
<emphasis remap=tt>chmod</emphasis>. Be careful about &man.chmod.1;. Be careful about
specifying directories or symlinks to directories to specifying directories or symlinks to directories to
<emphasis remap=tt>chmod</emphasis>. If you want to <command>chmod</command>. If you want to
change the permissions of a directory referenced by a change the permissions of a directory referenced by a
symlink, use &man.chmod.1; symlink, use &man.chmod.1;
without any options and follow the symlink without any options and follow the symlink
@ -10992,7 +11004,7 @@ raisechar=^^</programlisting>
<qandaentry> <qandaentry>
<question id="login-8char"> <question id="login-8char">
<para>Why are login names <emphasis remap=bf>still</emphasis> <para>Why are login names <emphasis>still</emphasis>
restricted to 8 characters?</para> restricted to 8 characters?</para>
</question> </question>
@ -11036,7 +11048,7 @@ raisechar=^^</programlisting>
<answer> <answer>
<para>Yes, starting with version 3.0 you can using BSDI's <para>Yes, starting with version 3.0 you can using BSDI's
<emphasis remap=tt>doscmd</emphasis> DOS emulation which has <application>doscmd</application> DOS emulation which has
been integrated and enhanced. Send mail to <ulink been integrated and enhanced. Send mail to <ulink
URL="mailto:freebsd-emulation@FreeBSD.org">The FreeBSD URL="mailto:freebsd-emulation@FreeBSD.org">The FreeBSD
emulation discussion list</ulink> if you're interested in emulation discussion list</ulink> if you're interested in
@ -11074,7 +11086,7 @@ raisechar=^^</programlisting>
<para><ulink URL="http://www.grex.org/">Grex</ulink> provides a <para><ulink URL="http://www.grex.org/">Grex</ulink> provides a
site very similar to M-Net including the same bulletin board site very similar to M-Net including the same bulletin board
and interactive chat software. However, the machine is a Sun and interactive chat software. However, the machine is a Sun
4M and is running SunOS.</para> 4M and is running SunOS</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -11463,11 +11475,11 @@ raisechar=^^</programlisting>
<quote>-CURRENT</quote>.</para> <quote>-CURRENT</quote>.</para>
<para>Right now, <quote>-CURRENT</quote> is the 5.0 development <para>Right now, <quote>-CURRENT</quote> is the 5.0 development
stream and the <emphasis remap=bf>4-STABLE</emphasis> branch, stream and the <literal>4-STABLE</literal> branch,
<symbol>RELENG_4</symbol>, forked off from <symbol>RELENG_4</symbol>, forked off from
<quote>-CURRENT</quote> in Mar 2000.</para> <quote>-CURRENT</quote> in Mar 2000.</para>
<para>The <emphasis remap=bf>2.2-STABLE</emphasis> branch, <para>The <literal>2.2-STABLE</literal> branch,
<symbol>RELENG_2_2</symbol>, departed -CURRENT in November <symbol>RELENG_2_2</symbol>, departed -CURRENT in November
1996, and has pretty much been retired.</para> 1996, and has pretty much been retired.</para>
</answer> </answer>
@ -11609,7 +11621,7 @@ doc-all</programlisting>
</question> </question>
<answer> <answer>
<para>Yes, you can do this <emphasis remap=tt>without</emphasis> <para>Yes, you can do this <literal>without</literal>
downloading the whole source tree by using the <ulink downloading the whole source tree by using the <ulink
URL="../handbook/synching.html#CTM">CTM facility.</ulink></para> URL="../handbook/synching.html#CTM">CTM facility.</ulink></para>
</answer> </answer>
@ -11782,7 +11794,7 @@ ${RELEASEDIR}/tarballs/bindist/bin_tgz.)</programlisting>
<para>This depends on whether or not you plan on making the <para>This depends on whether or not you plan on making the
driver publicly available. If you do, then please send us a driver publicly available. If you do, then please send us a
copy of the driver source code, plus the appropriate copy of the driver source code, plus the appropriate
modifications to <emphasis remap=tt>files.i386</emphasis>, a modifications to <filename>files.i386</filename>, a
sample configuration file entry, and the appropriate sample configuration file entry, and the appropriate
&man.MAKEDEV.8; &man.MAKEDEV.8;
code to create any special files your device uses. If you do code to create any special files your device uses. If you do
@ -11962,13 +11974,13 @@ Cc: current@FreeBSD.org</programlisting>
<para> To make sure you capture a crash dump, you need edit <para> To make sure you capture a crash dump, you need edit
<filename>/etc/rc.conf</filename> and set <filename>/etc/rc.conf</filename> and set
<emphasis remap=tt>dumpdev</emphasis> to point to your swap <literal>dumpdev</literal> to point to your swap
partition. This will cause the <command>rc(8)</command> scripts partition. This will cause the <command>rc(8)</command> scripts
to use the <command>dumpon(8)</command> command to enable crash to use the <command>dumpon(8)</command> command to enable crash
dumps. You can also run <command>dumpon(8)</command> manually. dumps. You can also run <command>dumpon(8)</command> manually.
After a panic, the crash dump can be recovered using After a panic, the crash dump can be recovered using
<command>savecore(8)</command>; if <emphasis <command>savecore(8)</command>; if
remap=tt>dumpdev</emphasis> is set in <literal>dumpdev</literal> is set in
<filename>/etc/rc.conf</filename>, the <command>rc(8)</command> <filename>/etc/rc.conf</filename>, the <command>rc(8)</command>
scripts will run <command>savecore(8)</command> automatically scripts will run <command>savecore(8)</command> automatically
and put the crash dump in and put the crash dump in
@ -12036,8 +12048,8 @@ Cc: current@FreeBSD.org</programlisting>
<para>The ELF toolchain does not, by default, make the symbols <para>The ELF toolchain does not, by default, make the symbols
defined in an executable visible to the dynamic linker. defined in an executable visible to the dynamic linker.
Consequently <function>dlsym()</function> searches on handles Consequently <function>dlsym()</function> searches on handles
obtained from calls to <emphasis remap=tt>dlopen(NULL, obtained from calls to <function>dlopen(NULL,
flags)</emphasis> will fail to find such symbols.</para> flags)</function> will fail to find such symbols.</para>
<para>If you want to search, using <function>dlsym()</function>, <para>If you want to search, using <function>dlsym()</function>,
for symbols present in the main executable of a process, you for symbols present in the main executable of a process, you
@ -12105,10 +12117,10 @@ SECTIONS
<para>Then reconfig and rebuild your kernel. You will probably <para>Then reconfig and rebuild your kernel. You will probably
have problems with <command>ps(1)</command>, have problems with <command>ps(1)</command>,
<command>top(1)</command> and the like; <emphasis remap=tt>make <command>top(1)</command> and the like; <command>make
world</emphasis> should take care of it (or a manual rebuild of world</command> should take care of it (or a manual rebuild of
<emphasis remap=tt>libkvm</emphasis>, <emphasis <filename>libkvm</filename>,
remap=tt>ps</emphasis> and <emphasis remap=tt>top</emphasis> <command>ps</command> and <command>top</command>
after copying the patched <filename>pmap.h</filename> to after copying the patched <filename>pmap.h</filename> to
<filename>/usr/include/vm/</filename>.</para> <filename>/usr/include/vm/</filename>.</para>