Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!bloom-beacon!mintaka!yale!cs.utexas.edu!usc!ucsd!ucsdhub!hp-sdd!ncr-sd!ncrcae!cs-col!vause
From: vause@cs-col.Columbia.NCR.COM
Newsgroups: comp.sys.ncr
Subject: Re: uugetty and bi-directional calling
Message-ID: <1990Feb8.185539.25455@cs-col.Columbia.NCR.COM>
Date: 8 Feb 90 18:55:39 GMT
References: <48@texbell.swbt.com>
Reply-To: vause@cs-col.Columbia.NCR.COM (Sam Vause)
Organization: Corporate Customer Services NCR E&M Columbia, SC
Lines: 23

In article <48@texbell.swbt.com>  writes:
>Has anybody been able to get uugetty to work on outgoing uucico calls
>and on incoming non-uucico calls on the same modem?
>out most hardware possibilities.  Can anybody offer any suggestions?
>Mike Nolan                          (uunet!frith!upba!tssi!nolan)

Unfortunately, this is a situation where the documentation may not have
quite made it out with the software in sufficient degree of clarity.

"uugetty" is one of those programs which will work only with itself;
that is, one cannot *reliably* connect a getty with a uugetty.  Sometimes
it works, and most times not.

General rule:  uugetty to uugetty; nothin to getty... (understanding the
was the /etc/inittab file is structured).
					--sam
+---------------------------------------------------------------+
|Sam Vause, NCR Corporation, Customer Services - TOWER Support  |
|3325 Platt Springs Road, West Columbia, SC 29169 (803) 791-6953|
|                                vause@cs-col.Columbia.NCR.COM  |
|                         ...!uunet!ncrlnk!ncrcae!cs-col!vause  |
|                ...!ucbvax!sdcsvax!ncr-sd!ncrcae!cs-col!vause  |
+---------------------------------------------------------------+