- Catch up with renaming of cuaa->cuad, ttyiN->ttyN.init, ttylN->ttyN.lock
in FreeBSD 6.0 - Catch up with renaming of /etc/rc.serial to /etc/rc.d/serial in FreeBSD 5.1 - Reword two sections to give 6.0 relevant instructions first
This commit is contained in:
Pav Lucistnik
parent
a5e969edc0
commit
e2f759c9d6
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=26628
1 changed files with 47 additions and 48 deletions
|
|
@ -473,11 +473,15 @@
|
|||
|
||||
<listitem>
|
||||
<para>Call-out ports are named
|
||||
<filename>/dev/cuaa<replaceable>N</replaceable></filename>.
|
||||
<filename>/dev/cuad<replaceable>N</replaceable></filename>.
|
||||
You usually do not use the call-out port for terminals, just
|
||||
for modems. You may use the call-out port if the serial cable
|
||||
or the terminal does not support the carrier detect
|
||||
signal.</para>
|
||||
|
||||
<note><para>Call-out ports are named
|
||||
<filename>/dev/cuaa<replaceable>N</replaceable></filename> in
|
||||
&os; 5.X and older.</para></note>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
|
@ -532,29 +536,22 @@ sio3 at 0x2e8-0x2ef irq 9 on isa
|
|||
sio3: type 16550A</screen>
|
||||
|
||||
<para>If your kernel does not recognize all of your serial
|
||||
ports, you will probably need to configure a custom FreeBSD
|
||||
kernel for your system. For detailed information on
|
||||
configuring your kernel, please see <xref
|
||||
linkend="kernelconfig">.</para>
|
||||
ports, you will probably need to configure your kernel
|
||||
in the <filename>/boot/device.hints</filename> file. You can
|
||||
also comment-out or completely remove lines for devices you do not
|
||||
have.</para>
|
||||
|
||||
<para>On &os; 4.X you have to edit your kernel configuration file.
|
||||
For detailed information on configuring your kernel, please see <xref
|
||||
linkend="kernelconfig">. The relevant device lines would look like
|
||||
this:</para>
|
||||
|
||||
<para>The relevant device lines for your kernel configuration
|
||||
file would look like this, for FreeBSD 4.X:</para>
|
||||
|
||||
<programlisting>device sio0 at isa? port IO_COM1 irq 4
|
||||
device sio1 at isa? port IO_COM2 irq 3
|
||||
device sio2 at isa? port IO_COM3 irq 5
|
||||
device sio3 at isa? port IO_COM4 irq 9</programlisting>
|
||||
|
||||
|
||||
<para>and like this, for FreeBSD 5.X:</para>
|
||||
|
||||
<programlisting>device sio</programlisting>
|
||||
|
||||
<para>You can comment-out or completely remove lines for devices
|
||||
you do not have in the case of FreeBSD 4.X; for
|
||||
FreeBSD 5.X you have to edit your
|
||||
<filename>/boot/device.hints</filename> file to configure your
|
||||
serial ports. Please refer to the &man.sio.4; manual page for
|
||||
<para>Please refer to the &man.sio.4; manual page for
|
||||
more information on serial ports and multiport boards configuration.
|
||||
Be careful if you are using a configuration
|
||||
file that was previously used for a different version of
|
||||
|
|
@ -585,13 +582,21 @@ device sio3 at isa? port IO_COM4 irq 9</programlisting>
|
|||
<filename>/dev</filename> directory. The <devicename>sio</devicename>
|
||||
devices are accessed through the
|
||||
<filename>/dev/ttyd<replaceable>N</replaceable></filename> (dial-in)
|
||||
and <filename>/dev/cuaa<replaceable>N</replaceable></filename>
|
||||
and <filename>/dev/cuad<replaceable>N</replaceable></filename>
|
||||
(call-out) devices. FreeBSD also provides initialization devices
|
||||
(<filename>/dev/ttyid<replaceable>N</replaceable></filename> and
|
||||
<filename>/dev/cuaia<replaceable>N</replaceable></filename>) and
|
||||
(<filename>/dev/ttyd<replaceable>N</replaceable>.init</filename> and
|
||||
<filename>/dev/cuad<replaceable>N</replaceable>.init</filename> on
|
||||
&os; 6.X,
|
||||
<filename>/dev/ttyid<replaceable>N</replaceable></filename> and
|
||||
<filename>/dev/cuaid<replaceable>N</replaceable></filename> on
|
||||
&os; 5.X and older) and
|
||||
locking devices
|
||||
(<filename>/dev/ttyld<replaceable>N</replaceable></filename> and
|
||||
<filename>/dev/cuala<replaceable>N</replaceable></filename>). The
|
||||
(<filename>/dev/ttyd<replaceable>N</replaceable>.lock</filename> and
|
||||
<filename>/dev/cuad<replaceable>N</replaceable>.lock</filename> on
|
||||
&os; 6.X,
|
||||
<filename>/dev/ttyld<replaceable>N</replaceable></filename> and
|
||||
<filename>/dev/cuald<replaceable>N</replaceable></filename> on
|
||||
&os; 5.X and older). The
|
||||
initialization devices are used to initialize communications port
|
||||
parameters each time a port is opened, such as
|
||||
<literal>crtscts</literal> for modems which use
|
||||
|
|
@ -654,10 +659,10 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen>
|
|||
<title>Serial Port Configuration</title>
|
||||
|
||||
<indexterm><primary><devicename>ttyd</devicename></primary></indexterm>
|
||||
<indexterm><primary><devicename>cuaa</devicename></primary></indexterm>
|
||||
<indexterm><primary><devicename>cuad</devicename></primary></indexterm>
|
||||
|
||||
<para>The <devicename>ttyd<replaceable>N</replaceable></devicename> (or
|
||||
<devicename>cuaa<replaceable>N</replaceable></devicename>) device is the
|
||||
<devicename>cuad<replaceable>N</replaceable></devicename>) device is the
|
||||
regular device you will want to open for your applications. When a
|
||||
process opens the device, it will have a default set of terminal I/O
|
||||
settings. You can see these settings with the command</para>
|
||||
|
|
@ -672,7 +677,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen>
|
|||
and <option>XON/XOFF</option> flow control by default for
|
||||
<devicename>ttyd5</devicename>, type:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>stty -f /dev/ttyid5 clocal cs8 ixon ixoff</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>stty -f /dev/ttyd5.init clocal cs8 ixon ixoff</userinput></screen>
|
||||
|
||||
<indexterm>
|
||||
<primary>rc files</primary>
|
||||
|
|
@ -693,7 +698,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen>
|
|||
device. For example, to lock the speed of
|
||||
<devicename>ttyd5</devicename> to 57600 bps, type:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>stty -f /dev/ttyld5 57600</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>stty -f /dev/ttyd5.lock 57600</userinput></screen>
|
||||
|
||||
<para>Now, an application that opens
|
||||
<devicename>ttyd5</devicename> and tries to change the speed of
|
||||
|
|
@ -1318,7 +1323,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
<filename>/sbin/init</filename> what <filename>tty</filename> devices
|
||||
should have <command>getty</command> processes running on them.
|
||||
Lastly, you can place port initialization commands in the
|
||||
<filename>/etc/rc.serial</filename> script.</para>
|
||||
<filename>/etc/rc.d/serial</filename> script.</para>
|
||||
|
||||
<para>There are two schools of thought regarding dial-up modems on &unix;.
|
||||
One group likes to configure their modems and systems so that no matter
|
||||
|
|
@ -1539,7 +1544,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title><filename>/etc/rc.serial</filename></title>
|
||||
<title><filename>/etc/rc.d/serial</filename></title>
|
||||
<indexterm>
|
||||
<primary>rc files</primary>
|
||||
<secondary><filename>rc.serial</filename></secondary>
|
||||
|
|
@ -1548,7 +1553,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
|
|||
<para>High-speed modems, like V.32, V.32bis, and V.34 modems,
|
||||
need to use hardware (<filename>RTS/CTS</filename>) flow
|
||||
control. You can add <command>stty</command> commands to
|
||||
<filename>/etc/rc.serial</filename> to set the hardware flow
|
||||
<filename>/etc/rc.d/serial</filename> to set the hardware flow
|
||||
control flag in the FreeBSD kernel for the modem
|
||||
ports.</para>
|
||||
|
||||
|
|
@ -1556,10 +1561,10 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
|
|||
<varname>crtscts</varname> on serial port #1's
|
||||
(<devicename>COM2</devicename>) dial-in and dial-out initialization
|
||||
devices, the following lines could be added to
|
||||
<filename>/etc/rc.serial</filename>:</para>
|
||||
<filename>/etc/rc.d/serial</filename>:</para>
|
||||
<programlisting># Serial port initial configuration
|
||||
stty -f /dev/ttyid1 crtscts
|
||||
stty -f /dev/cuaia1 crtscts</programlisting>
|
||||
stty -f /dev/ttyd1.init crtscts
|
||||
stty -f /dev/cuad1.init crtscts</programlisting>
|
||||
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
|
@ -1870,28 +1875,22 @@ AT&B2&W</programlisting>
|
|||
</indexterm>
|
||||
<para>Make what is called a <quote>direct</quote> entry in your
|
||||
<filename>/etc/remote</filename> file. For example, if your modem is
|
||||
hooked up to the first serial port, <filename>/dev/cuaa0</filename>,
|
||||
hooked up to the first serial port, <filename>/dev/cuad0</filename>,
|
||||
then put in the following line:</para>
|
||||
|
||||
<programlisting>cuaa0:dv=/dev/cuaa0:br#19200:pa=none</programlisting>
|
||||
<programlisting>cuad0:dv=/dev/cuad0:br#19200:pa=none</programlisting>
|
||||
|
||||
<para>Use the highest bps rate your modem supports in the br capability.
|
||||
Then, type <command>tip cuaa0</command> and you will be connected to
|
||||
Then, type <command>tip cuad0</command> and you will be connected to
|
||||
your modem.</para>
|
||||
|
||||
<para>If there is no <filename>/dev/cuaa0</filename> on your system, do
|
||||
this:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /dev</userinput>
|
||||
&prompt.root; <userinput>sh MAKEDEV cuaa0</userinput></screen>
|
||||
|
||||
<para>Or use <command>cu</command> as <username>root</username> with the
|
||||
following command:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cu -l<replaceable>line</replaceable> -s<replaceable>speed</replaceable></userinput></screen>
|
||||
|
||||
<para><replaceable>line</replaceable> is the serial port
|
||||
(e.g.<filename>/dev/cuaa0</filename>) and
|
||||
(e.g.<filename>/dev/cuad0</filename>) and
|
||||
<replaceable>speed</replaceable> is the speed
|
||||
(e.g.<literal>57600</literal>). When you are done entering the AT
|
||||
commands hit <keycap>~.</keycap> to exit.</para>
|
||||
|
|
@ -1917,9 +1916,9 @@ AT&B2&W</programlisting>
|
|||
<filename>/etc/remote</filename> file. For example:</para>
|
||||
|
||||
<programlisting>tip115200|Dial any phone number at 115200 bps:\
|
||||
:dv=/dev/cuaa0:br#115200:at=hayes:pa=none:du:
|
||||
:dv=/dev/cuad0:br#115200:at=hayes:pa=none:du:
|
||||
tip57600|Dial any phone number at 57600 bps:\
|
||||
:dv=/dev/cuaa0:br#57600:at=hayes:pa=none:du:</programlisting>
|
||||
:dv=/dev/cuad0:br#57600:at=hayes:pa=none:du:</programlisting>
|
||||
|
||||
<para>Then you can do things like:</para>
|
||||
|
||||
|
|
@ -1929,7 +1928,7 @@ tip57600|Dial any phone number at 57600 bps:\
|
|||
use a generic <literal>cu</literal> entry:</para>
|
||||
|
||||
<programlisting>cu115200|Use cu to dial any number at 115200bps:\
|
||||
:dv=/dev/cuaa1:br#57600:at=hayes:pa=none:du:</programlisting>
|
||||
:dv=/dev/cuad1:br#57600:at=hayes:pa=none:du:</programlisting>
|
||||
|
||||
<para>and type:</para>
|
||||
|
||||
|
|
@ -1960,7 +1959,7 @@ tip57600|Dial any phone number at 57600 bps:\
|
|||
muffin|muffin.deep13.com|Frank's machine:\
|
||||
:cm=CONNECT muffin\n:tc=deep13:
|
||||
deep13:Gizmonics Institute terminal server:\
|
||||
:dv=/dev/cuaa2:br#38400:at=hayes:du:pa=none:pn=5551234:</programlisting>
|
||||
:dv=/dev/cuad2:br#38400:at=hayes:du:pa=none:pn=5551234:</programlisting>
|
||||
|
||||
<para>will let you type <command>tip pain</command> or <command>tip
|
||||
muffin</command> to connect to the hosts pain or muffin, and
|
||||
|
|
@ -1980,7 +1979,7 @@ deep13:Gizmonics Institute terminal server:\
|
|||
<programlisting>big-university:\
|
||||
:pn=\@:tc=dialout
|
||||
dialout:\
|
||||
:dv=/dev/cuaa3:br#9600:at=courier:du:pa=none:</programlisting>
|
||||
:dv=/dev/cuad3:br#9600:at=courier:du:pa=none:</programlisting>
|
||||
|
||||
<para>Then, list the phone numbers for the university in
|
||||
<filename>/etc/phones</filename>:</para>
|
||||
|
|
|
|||
Loading…
Reference in a new issue