fiasco@infoserv.com (Rich Gircys) (11/16/90)
First, thanks to the many responses on Interactive bi-dir setup. What
I'm posting here is hopefully a useful summary as I'm sure this problem
will continue for others. And for those that requested the Esix bi-dir
setup, it's in the mail; if you don't get it, email me and we'll try again.
Interactive bi-dir suggestions/answers included:
1) Use uugetty.
This might be the answer on some machines, but doesn't appear to
have anything to do with the 386ix solution.
2) Use the latest/updated Interactive Unix OS. It fixes earlier problems.
The following is a terse description of how to make a bi-dir port
under Interactive:
o Get Interactive's X5 and X6 fixes installed, or use ISC 2.2 (newest
version?)
o Once that's done, follow this sample setup example:
Systems entry:
comtst Any Direct 19200 - "" \r in:--in: nuucp word: ....
Devices entry:
Direct /dev/ttyd0 - 19200 direct \D
Dialers entry
direct
inittab entry:
00:2345:respawn:/etc/getty -t 60 /dev/ttyd0 19200
Also, the dialers entry will probably need a \M to set
CLOCAL mode (i.e ignore modem control) and once your connection
is established (after you get the CONNECT) add a \m to turn the
modem control back on.
Use caution in useing this terse summary; I'm sure you'll want to check
the documentation. But I think you got the basic answer: a bidir port
under standard Interactive is possible. Many people have done it.
3) Use the FAS (Final Async Solution) driver. FAS is a PD package. I'd
like to try FAS instead of feeding good money to Interactive.
If anybody knows where to get FAS, please let me know. I checked the
uunet archives and they don't have it. Is there a good archive site
for other Unix source in general? (hopefully NOT requiring anon ftp,
which I currently don't have).
Thanks in advance,
rich