CMH117@PSUVM.BITNET (Charles Hannum) (10/13/89)
I figured this out several weeks ago, but haven't had a chance to post it yet. To download from Simtel20 to VM, you must do the following: FTP> Type I FTP> Quote TYPE L 8 Note: The L in the line above ***MUST*** be capitalized. Otherwise, case does not matter. The problem with this is that MGET and MPUT don't work. Tough luck. +-------------------------------------------------------------+ | Mr. Cole's Axiom: | | The sum of the intelligence on the planet is a constant; | | the population is growing. | +-------------------------------------------------------------+ | My name? Hannum ... Charles Hannum. You can reach me at: | | Bitnet ..... CMH117@PSUVM | | C9H@PSUECL | | Internet ... cmh117@psuvm.psu.edu | | c9h@psuecl.psu.edu | +-------------------------------------------------------------+
karn@ka9q.bellcore.com (Phil Karn) (10/16/89)
In article <89285.230458CMH117@PSUVM.BITNET> CMH117@PSUVM.BITNET (Charles Hannum) writes: >I figured this out several weeks ago, but haven't had a chance to post it yet. >To download from Simtel20 to VM, you must do the following: > > FTP> Type I > FTP> Quote TYPE L 8 > >Note: The L in the line above ***MUST*** be capitalized. Otherwise, case does >not matter. > >The problem with this is that MGET and MPUT don't work. Tough luck. Just to expand on this a little....the reason MGET and MPUT from a BSD client to a TOPS-20 server don't work is because the remote server will return an error message in response to the NLST command. It complains that you must be in ascii mode to do an NLST. I dunno whether this is strictly the fault of the server or of the client, but the problem could be fixed on either end. The TOPS-20 server could be a little more lenient by always executing the NLST command as though it were in ascii mode. Alternatively, the BSD client could keep track of the TYPE commands issued to the server and issue temporary "TYPE A" commands around NLST and LIST commands when the server is otherwise in TYPE I state. My own FTP client does the latter because I got annoyed by LIST output from BSD systems appearing on my MS-DOS screen without carriage returns. Phil
dik@cwi.nl (Dik T. Winter) (10/16/89)
(Reference lost because of editing problems;if you want to know why, send mail) > I dunno whether this is strictly the fault of the server or of the client, > but the problem could be fixed on either end. The TOPS-20 server could be a > little more lenient by always executing the NLST command as though it were > in ascii mode. I think simtel changed, but I am not sure. If I am right currently an NLST will work if in non-ascii mode; but I could not check (too many anonymous users). > Alternatively, the BSD client could keep track of the TYPE > commands issued to the server and issue temporary "TYPE A" commands around > NLST and LIST commands when the server is otherwise in TYPE I state. I do not know the exact definition of TYPE A. Is it 7 bit, 8 bit or what? If 7 bit, you do not want to do your NLST in ascii (check you Mac). > > My own FTP client does the latter because I got annoyed by LIST output from > BSD systems appearing on my MS-DOS screen without carriage returns. The problem with the LIST output is due to your client not properly formatting the output. When in a BSD ftp to a Mac try an ls. If you are unlucky your terminal is locked. But this is a more general problem. What should a client do when the filename-space on the server is very different from that on the client? In my opinion the client should format the output for LIST such that inputting an item to GET is retranslated to the original item. Also when doing a GET the client ought to translate filenames that are invalid on the clients machine. (Ever tried to get a file where the name contains an embedded slash on a unix machine?) -- dik t. winter, cwi, amsterdam, nederland INTERNET : dik@cwi.nl BITNET/EARN: dik@mcvax
rick@UUNET.UU.NET (Rick Adams) (10/16/89)
Its the clients fault. The current BSD client does this correctly. (current being the one I am running...) It will be released in a week or two as soon as a finish adding the "mnewer" command which gets files newer than a specifed date (unfortunately it needs a cooperating server, but I'll supply that too!0 --rick
braden@VENERA.ISI.EDU (10/17/89)
>The problem with this is that MGET and MPUT don't work. Tough luck.
Just to expand on this a little....the reason MGET and MPUT from a BSD
client to a TOPS-20 server don't work is because the remote server will
return an error message in response to the NLST command. It complains that
you must be in ascii mode to do an NLST.
The Host Requirements Working Group struggled with this issue, and reached
what seemed to be an acceptable decision. See section 4.1.2.7 of RFC-1123.
Bob Braden