Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!alberta!myrias!dragos!ruiu
From: ruiu@dragos.uucp (dragos)
Newsgroups: comp.unix.misc
Subject: Re: crc as child of cu
Message-ID: <1990Oct31.080825.7709@dragos.uucp>
Date: 31 Oct 90 08:08:25 GMT
References: <554@lrark.UUCP>
Reply-To: ruiu@dragos.UUCP (dragos)
Distribution: na
Organization: Orbital Mind Control Lasers, Inc.
Lines: 23

In article <554@lrark.UUCP> gars@lrark.UUCP (Gary Smith) writes about:

Problem: getting an xmodem-type program to run from cu.
System: SystemV/AT

The answer is you don't. The uPort cu is a generic SysVr2 cu and only lets
you spawn a process with the output redirected to the remote end instead
of both the output and the input.

On other, more modern systems tip/cu have ~ options to let you do this,
but you can't do it with what you have.

Solutions:

 If you are only calling other unix systems, live with ~t(ake) and ~p(ut),
 which is kind of gross.

 Use another program instead of cu to call out. My personal preference is 
 a program I got of the uPort BBS called "xcomm". Doubtless there are others
 around. Check your friendly neighborhood archive.
-- 
Dragos Ruiu (ruiu@dragos.uucp)  alberta!dragos!ruiu    Copyright(c) 1990
HP, Idacom division.