ESIX: cu does not detect dropped line.

[Kayvan Sylvan]

In article <KAYVAN.90Nov22013215 at mrspoc.Transact.COM> Kayvan Sylvan writes:
>I have the ESIX 5.3.2 D on a 386 with 4 Meg of RAM and a Fujitsu
>M2263E ESDI drive in it. It runs great!!
>I have a Telebit Trailblazer Plus modem hooked into COM1.
>In Devices, I have all the ``line'' references ending with ",M" and
>that should enforce the modem control.
> 
>The problem: When I use cu to dial into another system, when I log out
>and the line is dropped, cu sits there still waiting for input. It's
>almost as if the modem control does not work. I have to do "~." to get
>back to the shell.

Okay, here's the solution (mentioned in the back of the release
notes).

The modem control device has a minor number that's 128 more than the
corresponding one with no modem control.

Here's my devices:

crw-rw-rw-   1 root     root       3,  0 Nov 25 16:56 /dev/tty00
crw-rw-rw-   1 root     root       3,  1 Nov 25 16:56 /dev/tty01
crw--w--w-   1 uucp     uucp       3,128 Nov 25 16:56 /dev/ttym00

You have to manually create /dev/ttym00 by doing:

	mknod /dev/ttym00 c 3 128

This creates the device entry which you will then use in your uucp
Devices and your /etc/inittab file.

If you don't want all of this to be wiped out the next time you
reconfigure your kernel, also change /etc/conf/cf.d/inittab.base.

In addition to inittab.base, I had to add the following to
/etc/conf/bin/idmkenv since sometimes when I remake the kernel,
idmknod seems to like to wipe out /dev/ttym00 (I'm sure there's a
better solution to this one, but I haven't found it).

============================== cut here ==============================
#
# Make the modem control device after idmknod wipes it out.
#
if [ ! -r /dev/ttym00 ]
then
	mknod /dev/ttym00 c 3 128
	chmod 666 /dev/ttym00
fi
============================== cut here ==============================

			---Kayvan