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

- Fix dashes

Browse source 
PR:         	docs/124137
Submitted by:	pgj
Approved by:	gabor (mentor)
This commit is contained in:
Gabor Pali 2008-05-31 08:44:51 +00:00
parent 6b1037215c
commit ac839cf1a3
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=32094
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -3034,7 +3034,7 @@ quit</programlisting>
compile <filename>ls.c</filename> into compile <filename>ls.c</filename> into
<filename>ls.o</filename>. If you then run <command>make <filename>ls.o</filename>. If you then run <command>make
<maketarget>buildworld</maketarget></command> again, and the compile fails in the same <maketarget>buildworld</maketarget></command> again, and the compile fails in the same
place then this is a broken build -- try updating your sources place then this is a broken build &mdash; try updating your sources
and try again. If the compile fails elsewhere then this is and try again. If the compile fails elsewhere then this is
almost certainly hardware.</para> almost certainly hardware.</para>
@ -3713,7 +3713,7 @@ chip1@pci0:31:5: class=0x040100 card=0x00931028 chip=0x24158086 rev=0x02
the &man.hosts.5; and &man.named.8; manual pages for more the &man.hosts.5; and &man.named.8; manual pages for more
information. If this is on the global Internet, the problem information. If this is on the global Internet, the problem
may be that your server's resolver is not functioning may be that your server's resolver is not functioning
correctly. To check, try to look up another host--say, correctly. To check, try to look up another host &mdash; say,
<hostid>www.yahoo.com</hostid>. If it does not work, that is <hostid>www.yahoo.com</hostid>. If it does not work, that is
your problem.</para> your problem.</para>
@ -9748,7 +9748,7 @@ sio1: type 16550A</programlisting>
using port address <literal>0x3f8</literal>, and has a using port address <literal>0x3f8</literal>, and has a
16550A-type UART chip. The second uses the same kind of chip 16550A-type UART chip. The second uses the same kind of chip
but is on irq 3 and is at port address <literal>0x2f8</literal>. but is on irq 3 and is at port address <literal>0x2f8</literal>.
Internal modem cards are treated just like serial ports---except Internal modem cards are treated just like serial ports &mdash; except
that they always have a modem <quote>attached</quote> to the that they always have a modem <quote>attached</quote> to the
port.</para> port.</para>
@ -9956,7 +9956,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
The terminal type for this port is The terminal type for this port is
<literal>dialup</literal>. The port is <literal>dialup</literal>. The port is
<literal>on</literal> and is <literal>on</literal> and is
<literal>insecure</literal>---meaning <literal>insecure</literal> &mdash; meaning
<username>root</username> logins on the port are not <username>root</username> logins on the port are not
allowed. For dialin ports like this one, use the allowed. For dialin ports like this one, use the
<devicename>ttyd<replaceable>X</replaceable></devicename> <devicename>ttyd<replaceable>X</replaceable></devicename>
@ -10049,7 +10049,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
<qandaentry> <qandaentry>
<question id="hayes-unsupported"> <question id="hayes-unsupported">
<para>My stock Hayes modem is not supported---what <para>My stock Hayes modem is not supported &mdash; what
can I do?</para> can I do?</para>
</question> </question>
@ -10061,7 +10061,7 @@ device sio7 at isa? port 0x2b8 tty flags 0x781 irq 7 vector siointr</programlist
file.</para> file.</para>
<para>The Hayes driver is not smart enough to recognize some of <para>The Hayes driver is not smart enough to recognize some of
the advanced features of newer modems---messages like the advanced features of newer modems &mdash; messages like
<literal>BUSY</literal>, <literal>NO DIALTONE</literal>, or <literal>BUSY</literal>, <literal>NO DIALTONE</literal>, or
<literal>CONNECT 115200</literal> will just confuse it. You <literal>CONNECT 115200</literal> will just confuse it. You
should turn those messages off when you use &man.tip.1; should turn those messages off when you use &man.tip.1;