|
Lines 385-391
Link Here
|
| 385 |
initialization devices are used to initialize communications port |
385 |
initialization devices are used to initialize communications port |
| 386 |
parameters each time a port is opened, such as |
386 |
parameters each time a port is opened, such as |
| 387 |
<literal>crtscts</literal> for modems which use |
387 |
<literal>crtscts</literal> for modems which use |
| 388 |
<literal>CTS/RTS</literal> signaling for flow control. The locking |
388 |
<literal>RTS/CTS</literal> signaling for flow control. The locking |
| 389 |
devices are used to lock flags on ports to prevent users or programs |
389 |
devices are used to lock flags on ports to prevent users or programs |
| 390 |
changing certain parameters; see the manual pages &man.termios.4;, |
390 |
changing certain parameters; see the manual pages &man.termios.4;, |
| 391 |
&man.sio.4;, and &man.stty.1; for |
391 |
&man.sio.4;, and &man.stty.1; for |
|
Lines 1487-1493
Link Here
|
| 1487 |
the FreeBSD system through the console and issue a <command>ps |
1487 |
the FreeBSD system through the console and issue a <command>ps |
| 1488 |
ax</command> to see if FreeBSD is trying to run a |
1488 |
ax</command> to see if FreeBSD is trying to run a |
| 1489 |
<command>getty</command> process on the correct port. You should see |
1489 |
<command>getty</command> process on the correct port. You should see |
| 1490 |
a lines like this among the processes displayed:</para> |
1490 |
lines like these among the processes displayed:</para> |
| 1491 |
|
1491 |
|
| 1492 |
<screen> 114 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd0 |
1492 |
<screen> 114 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd0 |
| 1493 |
115 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd1</screen> |
1493 |
115 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd1</screen> |