Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!sun-barr!cs.utexas.edu!uunet!image.soe.clarkson.edu!news From: nelson@sun.soe.clarkson.edu (Russ Nelson) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: FTP grape.ecs.clarkson.edu Message-ID: Date: 27 Aug 89 04:39:09 GMT References: <4315@cps3xx.UUCP> Sender: news@sun.soe.clarkson.edu Reply-To: nelson@clutx.clarkson.edu Organization: Clarkson University, Postdam NY Lines: 32 In-reply-to: usenet@cps3xx.UUCP's message of 26 Aug 89 19:17:24 GMT In article <4315@cps3xx.UUCP> usenet@cps3xx.UUCP (Usenet file owner) writes: >FTP: grape.ecs.clarkson.edu [128.153.13.196], user anonymous, password guest. It seems that your ftp is incompatible with the ftp here. Right. Can you please help? (Note that I have almost no ability here to get ftp updated, and our ftp works great everyplace else.) Thanks. Well, yes and no. Perhaps a word of explanation is in order here. I have chosen to make use of continuation lines in my version of Phil Karn (KA9Q)'s TCP/IP. You'll find continuation lines documented in the RFC that defines the File Transfer Protocol (FTP). However, just because it's in the documentation doesn't mean that it's actually implemented. And, sure enough, many FTP clients don't implement continuation lines. I have no sympathy for the users of these FTP clients. If you are one of the unfortunate users of these broken FTP clients, then you can (and *should*, most emphatically), FTP to uunet.uu.net, cd to /networking, and get ftp.tar.Z. Uncompress and untar it, compile it, and install it as globally as you can. The only broken FTP clients that I know of are BSD Unix clients. If there are any others then I will reconsider my use of continuation lines. Until then, go back one paragraph and re-read. -- --russ (nelson@clutx [.bitnet | .clarkson.edu])|(70441.205@compuserve.com)| (Russ.Nelson@f360.n260.z1.fidonet.org)|(BH01@GEnie.com :-)