Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!BRL.MIL!andy
From: andy@BRL.MIL ("Ronald D. Anderson", IBD)
Newsgroups: comp.sys.sgi
Subject: tty-to-tty testing
Message-ID: <9104250933.aa26475@IBD.BRL.MIL>
Date: 25 Apr 91 13:33:06 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 27

|> From: Henrik Klagges <math.fu-berlin.de!opal!fauern!NewsServ!sunmanager!uh311ae@uunet.uu.net>
|> Organization: Technische Universitaet Muenchen, Germany
|> 
|> Hello !
|> I just wonder why there is a need for hardware handshakers (ttyf's).
|> I have no problem running the standard 4DGifts kermit at 19200. I 
|> couldn`t try 38k because I don't have a 2nd 38k thing.
|>  BTW, if I want to make SGI-SGI serial line transfer, would I have to
|> switch wires in the serial line ? Recently, I had some nice "Panic:....
|> 

for testing kermit baud rates and ttyf's, try defining two of the sgi serial
i/o ports as having the same rates and characterisitcs (ttyf, etc.).
then (a) cable together with null-modem signal swapping (rx-to-tx, tx-to-rx,
etc.); (b) start kermit on the first tty and set it up to receive;
(c) start kermit again from a second window on the other tty, where you can
now send files to the first tty.  this scheme can be set up between two
distinct machines, or can be done over two tty's on the same machine.
(the second option is OK for testing the hardware and software links, but
has little other usefulness.)

a note:  don't try sending/receiving from two windows that reside in the
same subdirectory, unless you are sure to put the (sent) file under a
different filename.

this is also a convenient way to test the uucp setup on a single local
machine before connecting to a remote system.