🚀 go-pugleaf

In article <1991May17.202220.9531@uu.psi.com> schoff@uu.psi.com (Martin Schoffstall) writes:
>In article <MDDB7-A@xds13.ferranti.com> peter@ficc.ferranti.com (Peter da Silva) writes:
>>
>>"uux uupsi!rftp sprite.berkeley.edu:~ftp/mx.tar.Z (ficc!~/from-uupsi)"
>>
>...
>But lets go back to your rftp, what you need to do is create the
>code and make it work across 2 dozen platforms and it will be
>as explosive as CNews use.  So get the community to work the
>spec and write the code and we're off, minimum portability would be

Oh, rot.  The proposed program would only need to work on host "uupsi"
and would be simple to write.  Your customers would only need to issue
a uux command, and that could be bundled into a symbol shell script.

If you wanted to implement it easily, you could grab the "expect"
package, which has been posted on the net, and have it run the anonymous
FTP session.  You'd have to write almost no code.

>Your biggest and most controversial design decision will be to
>decide if this works one hop or multiple hops.

No controversy at all.  One hop only.  Otherwise it would be another
way for UUCP sites to get a free lunch.  The "rftp" command would
retrieve the first argument by anonymous FTP and then transfer the
result by uucp to the second argument.  By building on top of "expect",
a competent programmer could get it working without much trouble.


-- 
--
Joe Buck
jbuck@janus.berkeley.edu	 {uunet,ucbvax}!janus.berkeley.edu!jbuck