ted@imsvax.UUCP (Ted Holden) (10/12/86)
There have been several postings on this topic lately. The cu routine should be a last resort in UNIX to non-UNIX communications situations. Someone using a small UNIX system as a make-believe terminal via cu will probably have to modify the port driver for the port being used, i.e. set usart values to match those of the target machine, turn echoing off (since most other computers don't like something which they regard as a terminal echoing back at them) while somehow still making sure that stuff going TO the target machine can be seen on the user console...... especially with PCs, using the PC as the terminal is a lot easier, lots of good programs to do that around.
perl@rdin.UUCP (Robert Perlberg) (10/17/86)
I have never had any trouble using cu(1) for accessing a variety of
different machines and operating systems. I can't even see any reason
why you would have any trouble with cu. All it does is send and
receive characters. As for modifying the serial drivers, you
apparently haven't heard of the ioctl function or the stty command. Cu
does not echo back received characters. Perhaps you haven't been
disabling the getty(8) on the outgoing line? Cu has a -h (half duplex)
option that controls whether cu does local echoing. I've even been
able to use a PC through cu by doing a CTTY COM1: on the PC. Some
programs won't play nice, like BASICA and LOTUS, but that's not cu's
fault.
Robert Perlberg
Resource Dynamics Inc.
New York
{philabs|delftcc}!rdin!perl