Xref: utzoo comp.dcom.modems:2787 comp.sys.att:4606
Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!mcvax!hp4nl!ctisbv!pim
From: pim@ctisbv.UUCP (Pim Zandbergen)
Newsgroups: comp.dcom.modems,comp.sys.att
Subject: Re: MORE 6386 UUCP WOES ...
Keywords: cu, Hayes Modem, tty, asy, sio, modem control
Message-ID: <538@ctisbv.UUCP>
Date: 24 Oct 88 19:01:41 GMT
Article-I.D.: ctisbv.538
References: <319@argon.UUCP> <2096@cuuxb.ATT.COM> <727@wsccs.UUCP> <16509@onfcanim.UUCP> <1988Oct21.033839.1412@ixpierre.uucp>
Reply-To: pim@ctisbv.UUCP (Pim Zandbergen)
Organization: CTI Software BV, The Hague, The Netherlands
Lines: 50

In article <1988Oct21.033839.1412@ixpierre.uucp> woods@ixpierre.UUCP (Greg A. Woods) writes:
>
>Does anyone besides Microport and Sun support simple bi-directional
>port usage by having a device driver which will prevent a getty's open
>on the modem control device from completing whenever the no wait
>device is open?  Does anyone have a version of asy(7) for 386/ix that
>does this?  Why does AT&T seem to instist on keeping the uugetty
>hack?  I see no reason for it given a fully functional modem that
>adheres to the RS-232 spec. and an intelligent device driver.

Correct me if I'm wrong, but isn't the current release of 386/ix
based on System V release 3.1 ? In that case you only need
the modem control device to use your modem bidirectionally.

System V release 3.1 and up enables uucico and cu to open
the modem control device with O_NDELAY specified, set CLOCAL
while dialing and unset CLOCAL after a connection has been made.

This is what you specify in Devices:
ACU tty00,M - 2400 hayes \T	# open tty00 with O_NDELAY

This is what you specify in Dialers:
hayes	=,-,	"" \M\dAT\r\c OK\r \EATDT\T\r\c CONNECT \m\c
where:
\M means: set CLOCAL
\m means: unset CLOCAL

This way, you can program your modem to be as verbose as possible,
because all RINGS etc. will be ignored when DCD is low.

You still will need uugetty, because getty would wake up as soon
as DCD will raise when a dialout connection has been made. Uugetty
won't, because it checks the LCK.. files. But the only minor
problem I see in using uugetty in this scheme is having to press
<return> to get a login prompt.

BTW, I made ct work using this scheme, even though the man pages
tell me ct won't work with intelligent modems.

However, it takes the following to put in /etc/inittab:
00:234:respawn:sh -c 'sleep 60; exec /usr/lib/uucp/uugetty -rt 60 tty00 2400'

The 'sleep 60' is required by ct in order to call back before
uugetty respawns. I don't know why this is necessary (ct makes
valid LCK.. files) but it is.
-- 
--------------------+------------------------------------+---------------------
Pim Zandbergen      | CTI Software BV                    | Phone: +31 70 542302 
pim@ctisbv.UUCP     | Laan Copes van Cattenburch 70      | Fax:   +31 70 512837
..!mcvax!ctisbv!pim | 2585 GD The Hague, The Netherlands | Telex: 32133 CTI NL