Xref: utzoo comp.dcom.modems:2781 comp.sys.att:4594
Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!think!redsox!campbell
From: campbell@redsox.UUCP (Larry Campbell)
Newsgroups: comp.dcom.modems,comp.sys.att
Subject: Re: MORE 6386 UUCP WOES ...
Keywords: cu, Hayes Modem, tty, asy, sio, modem control
Message-ID: <490@redsox.UUCP>
Date: 23 Oct 88 03:35:34 GMT
References: <319@argon.UUCP> <2096@cuuxb.ATT.COM> <727@wsccs.UUCP> <16509@onfcanim.UUCP> <1988Oct21.033839.1412@ixpierre.uucp>
Reply-To: campbell@redsox.UUCP (Larry Campbell)
Organization: The Boston Software Works, Inc.
Lines: 19

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.

VenturCom provided this feature in VENIX/86, a V7-based UNIX port
for 8086 machines.  I don't know if their current SV port supports
this, but I doubt it, since it's based on 386/ix.

The lack of this simple feature is INCREDIBLY ANNOYING, guys.  Are you
listening, AT&T (and Interactive and SCO and Altos and DEC and...)?
-- 
Larry Campbell                          The Boston Software Works, Inc.
campbell@bsw.com                        120 Fulton Street
wjh12!redsox!campbell                   Boston, MA 02146