Fill paragraphs.
This commit is contained in:
parent
d11f41b8c5
commit
11f46b8e37
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10264
1 changed files with 27 additions and 24 deletions
|
|
@ -17,7 +17,7 @@
|
|||
|
||||
<corpauthor>The FreeBSD Documentation Project</corpauthor>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.248 2001/08/09 07:19:11 dd Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.249 2001/08/09 07:20:16 dd Exp $</pubdate>
|
||||
|
||||
<copyright>
|
||||
<year>1995</year>
|
||||
|
|
@ -3623,12 +3623,14 @@ quit</programlisting>
|
|||
but the activity that the compiler is carrying out changes
|
||||
each time.</para>
|
||||
|
||||
<para>For example, suppose you are running <quote>make buildworld</quote>, and
|
||||
the compile fails while trying to compile <filename>ls.c</filename> in to <filename>ls.o</filename>. If
|
||||
you then run <quote>make buildworld</quote> again, and the compile fails in
|
||||
the same place then this is a broken build -- try updating your
|
||||
sources and try again. If the compile fails elsewhere then this
|
||||
is almost certainly hardware.</para>
|
||||
<para>For example, suppose you are running <quote>make
|
||||
buildworld</quote>, and the compile fails while trying to
|
||||
compile <filename>ls.c</filename> in to
|
||||
<filename>ls.o</filename>. If you then run <quote>make
|
||||
buildworld</quote> again, and the compile fails in the same
|
||||
place then this is a broken build -- try updating your sources
|
||||
and try again. If the compile fails elsewhere then this is
|
||||
almost certainly hardware.</para>
|
||||
|
||||
<para>What you should do:</para>
|
||||
|
||||
|
|
@ -7074,12 +7076,13 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
|
|||
|
||||
<screen>&prompt.root; <userinput>sysctl kern.securelevel</userinput></screen>
|
||||
|
||||
<para>You cannot lower the security level; you have to boot
|
||||
to single mode to install the kernel, or change the
|
||||
security level in <filename>/etc/rc.conf</filename> then reboot. See
|
||||
the &man.init.8; man page for details on securelevel, and
|
||||
see <filename>/etc/defaults/rc.conf</filename> and the
|
||||
&man.rc.conf.5; man page for more information on rc.conf.</para>
|
||||
<para>You cannot lower the security level; you have to boot to
|
||||
single mode to install the kernel, or change the security
|
||||
level in <filename>/etc/rc.conf</filename> then reboot. See
|
||||
the &man.init.8; man page for details on securelevel, and see
|
||||
<filename>/etc/defaults/rc.conf</filename> and the
|
||||
&man.rc.conf.5; man page for more information on
|
||||
rc.conf.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
|
|
@ -9740,17 +9743,17 @@ ATDT1234567</programlisting>
|
|||
<literal>iface</literal>.</para>
|
||||
|
||||
<para>The problem was that when that initial program calls
|
||||
&man.connect.2;, the IP number of the tun interface is
|
||||
assigned to the socket endpoint. The kernel creates the first
|
||||
outgoing packet and writes it to the tun device.
|
||||
<application>ppp</application> then reads the packet and establishes a
|
||||
connection. If, as a result of
|
||||
<application>ppp</application>'s dynamic IP assignment, the interface
|
||||
address is changed, the original socket endpoint will be
|
||||
invalid. Any subsequent packets sent to the peer will usually
|
||||
be dropped. Even if they are not, any responses will not route
|
||||
back to the originating machine as the IP number is no longer
|
||||
owned by that machine.</para>
|
||||
&man.connect.2;, the IP number of the tun interface is assigned
|
||||
to the socket endpoint. The kernel creates the first outgoing
|
||||
packet and writes it to the tun device.
|
||||
<application>ppp</application> then reads the packet and
|
||||
establishes a connection. If, as a result of
|
||||
<application>ppp</application>'s dynamic IP assignment, the
|
||||
interface address is changed, the original socket endpoint will
|
||||
be invalid. Any subsequent packets sent to the peer will
|
||||
usually be dropped. Even if they are not, any responses will
|
||||
not route back to the originating machine as the IP number is
|
||||
no longer owned by that machine.</para>
|
||||
|
||||
<para>There are several theoretical ways to approach this
|
||||
problem. It would be nicest if the peer would re-assign the
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue