Xref: utzoo news.admin:14514 comp.mail.uucp:6601 Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!elroy.jpl.nasa.gov!sdd.hp.com!samsung!umich!ox.com!msen.com!emv From: emv@msen.com (Ed Vielmetti) Newsgroups: news.admin,comp.mail.uucp Subject: Re: BITFTP Message-ID: Date: 20 May 91 19:53:03 GMT References: Sender: usenet@ox.com (Usenet News Administrator) Organization: MSEN, Inc. Ann Arbor MI Lines: 24 In-Reply-To: peter@ficc.ferranti.com's message of Mon, 20 May 91 17:37:54 GMT In article peter@ficc.ferranti.com (Peter da Silva) writes: > And also naturally there would be an interface to the > raw "OPEN, CD, GET" commands if you're dealing with a sufficiently > goofy remote system that expressing things in terms of one-liners is > not adequate to the task. Like SIMTEL? Or does rftp know about SIMTEL's <> stuff in your model? my model rftp knows about simtel20 and its syntax, also it knows about the half dozen IBM VM systems on the net that don't have a proper way to fetch files out of subdirectories from the initial prompt. e.g. nis.nsf.net, where a single GET command doesn't work, you have to CD and GET. Just a few special cases, FTP'ing is generally predictable and standard enough to work well without much prior knowlege of the remote site. this rftp would also know that 99 44/100% of what's on simtel (behind horrible syntax and MILNET gateways) also lives on wuarchive.wustl.edu and whatever other official shadow archive systems there are for it. thus the Australian version of it would point to all of local Australian caches. --Ed