|
Lines 3034-3040
Link Here
|
| 3034 |
compile <filename>ls.c</filename> into |
3034 |
compile <filename>ls.c</filename> into |
| 3035 |
<filename>ls.o</filename>. If you then run <quote>make |
3035 |
<filename>ls.o</filename>. If you then run <quote>make |
| 3036 |
buildworld</quote> again, and the compile fails in the same |
3036 |
buildworld</quote> again, and the compile fails in the same |
| 3037 |
place then this is a broken build -- try updating your sources |
3037 |
place then this is a broken build — try updating your sources |
| 3038 |
and try again. If the compile fails elsewhere then this is |
3038 |
and try again. If the compile fails elsewhere then this is |
| 3039 |
almost certainly hardware.</para> |
3039 |
almost certainly hardware.</para> |
| 3040 |
|
3040 |
|
|
Lines 3713-3719
Link Here
|
| 3713 |
the &man.hosts.5; and &man.named.8; manual pages for more |
3713 |
the &man.hosts.5; and &man.named.8; manual pages for more |
| 3714 |
information. If this is on the global Internet, the problem |
3714 |
information. If this is on the global Internet, the problem |
| 3715 |
may be that your server's resolver is not functioning |
3715 |
may be that your server's resolver is not functioning |
| 3716 |
correctly. To check, try to look up another host--say, |
3716 |
correctly. To check, try to look up another host — say, |
| 3717 |
<hostid>www.yahoo.com</hostid>. If it does not work, that is |
3717 |
<hostid>www.yahoo.com</hostid>. If it does not work, that is |
| 3718 |
your problem.</para> |
3718 |
your problem.</para> |
| 3719 |
|
3719 |
|
|
Lines 9748-9754
Link Here
|
| 9748 |
using port address <literal>0x3f8</literal>, and has a |
9748 |
using port address <literal>0x3f8</literal>, and has a |
| 9749 |
16550A-type UART chip. The second uses the same kind of chip |
9749 |
16550A-type UART chip. The second uses the same kind of chip |
| 9750 |
but is on irq 3 and is at port address <literal>0x2f8</literal>. |
9750 |
but is on irq 3 and is at port address <literal>0x2f8</literal>. |
| 9751 |
Internal modem cards are treated just like serial ports---except |
9751 |
Internal modem cards are treated just like serial ports — except |
| 9752 |
that they always have a modem <quote>attached</quote> to the |
9752 |
that they always have a modem <quote>attached</quote> to the |
| 9753 |
port.</para> |
9753 |
port.</para> |
| 9754 |
|
9754 |
|
|
Lines 9956-9962
Link Here
|
| 9956 |
The terminal type for this port is |
9956 |
The terminal type for this port is |
| 9957 |
<literal>dialup</literal>. The port is |
9957 |
<literal>dialup</literal>. The port is |
| 9958 |
<literal>on</literal> and is |
9958 |
<literal>on</literal> and is |
| 9959 |
<literal>insecure</literal>---meaning |
9959 |
<literal>insecure</literal> — meaning |
| 9960 |
<username>root</username> logins on the port are not |
9960 |
<username>root</username> logins on the port are not |
| 9961 |
allowed. For dialin ports like this one, use the |
9961 |
allowed. For dialin ports like this one, use the |
| 9962 |
<devicename>ttyd<replaceable>X</replaceable></devicename> |
9962 |
<devicename>ttyd<replaceable>X</replaceable></devicename> |
|
Lines 10049-10055
Link Here
|
| 10049 |
|
10049 |
|
| 10050 |
<qandaentry> |
10050 |
<qandaentry> |
| 10051 |
<question id="hayes-unsupported"> |
10051 |
<question id="hayes-unsupported"> |
| 10052 |
<para>My stock Hayes modem is not supported---what |
10052 |
<para>My stock Hayes modem is not supported — what |
| 10053 |
can I do?</para> |
10053 |
can I do?</para> |
| 10054 |
</question> |
10054 |
</question> |
| 10055 |
|
10055 |
|
|
Lines 10061-10067
Link Here
|
| 10061 |
file.</para> |
10061 |
file.</para> |
| 10062 |
|
10062 |
|
| 10063 |
<para>The Hayes driver is not smart enough to recognize some of |
10063 |
<para>The Hayes driver is not smart enough to recognize some of |
| 10064 |
the advanced features of newer modems---messages like |
10064 |
the advanced features of newer modems — messages like |
| 10065 |
<literal>BUSY</literal>, <literal>NO DIALTONE</literal>, or |
10065 |
<literal>BUSY</literal>, <literal>NO DIALTONE</literal>, or |
| 10066 |
<literal>CONNECT 115200</literal> will just confuse it. You |
10066 |
<literal>CONNECT 115200</literal> will just confuse it. You |
| 10067 |
should turn those messages off when you use &man.tip.1; |
10067 |
should turn those messages off when you use &man.tip.1; |