Xref: utzoo comp.sys.att:5203 comp.unix.questions:11054
Path: utzoo!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!purdue!haven!rutgers!att!mtuxo!mtgzz!avr
From: avr@mtgzz.att.com (a.v.reed)
Newsgroups: comp.sys.att,comp.unix.questions
Subject: Re: Terminal emulator for 6386 under UNIX(r)
Summary: Here's how to do it
Keywords: 6386, UNIX, cu
Message-ID: <4877@mtgzz.att.com>
Date: 12 Jan 89 00:11:01 GMT
References: <9877@drutx.ATT.COM> <4861@mtgzz.att.com> <563@mccc.UUCP>
Distribution: comp
Organization: AT&T, Middletown NJ
Lines: 38

In article <563@mccc.UUCP>, pjh@mccc.UUCP (Pete Holsberg) writes:
> In article <4861@mtgzz.att.com> avr@mtgzz.att.com (a.v.reed) writes:
> =
> =In article <9877@drutx.ATT.COM>, csr@drutx.ATT.COM (Steve Roush) writes:
> =>    For strictly interactive use, I use "cu". ....
> =>   I do not know of any UNIX programs outside of AT&T that allow scripting
> => of sessions as can be done under DOS.
> =
> =Oh yes you do, unless you've never heard of "tee".
> =Here is how you use tee to "script" a cu session:
> 
> I wondewr if the original poster wasn't talking about writing scripts
> that "drive" cu, the way that MSDOS programs such as ProYAM and ProComm
> have scripts that make the call, log you on, download messages, upload
> files, etc., without human intervention.  I's certainly like to see how
> to do that.

Fair enough - I was thinking of the (clearly redundant) BSD "script".
Here is what you want from standard UNIX tools. Let "dialog.cu" be a
shell script to do your thing. It "read"s from cu and "echo"s to it,
and after doing its job lets you continue by doing

	cat -u < $TTY &
	exec cat -u > $TTY

Start your session like this:

	TTY=`tty`
	export TTY
	mknod tocu p
	mknod fromcu p
	dialog.cu <fromcu >tocu &
	cu <tocu >fromcu

You can be more elaborate and check the fifos first and remove them
afterward etc., but I think the above should be enough to get you
started.
			Adam Reed (avr@mtgzz.ATT.COM)