usenet@cps3xx.UUCP (Usenet file owner) (08/27/89)
>FTP: grape.ecs.clarkson.edu [128.153.13.196], user anonymous, password guest.
It seems that your ftp in incompatible with the ftp here. It lets me
log in with anonymous and guest, but then I get these messages that I
need to logon with user and pass. In addition, it doesn't seem to take
the ls or get or bin commands. get 00readme was fruitless. Can you
please help? (Note that I have almost no ability here to get ftp
updated, and our ftp works great everyplace else.) Thanks. Ken
In the rare case that original ideas Kenneth J. Hendrickson N8DGN
are found here, I am responsible. Owen W328, E. Lansing, MI 48825
Internet: hendrick@frith.egr.msu.edu UUCP: ...!frith!hendricknelson@sun.soe.clarkson.edu (Russ Nelson) (08/27/89)
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 :-)
tgoodman@bbn.com (Todd Goodman) (08/28/89)
In article <NELSON.89Aug27003535@sun.clarkson.edu> nelson@clutx.clarkson.edu writes: >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. > > [ Explanation of grape's ftp server deleted for brevity ] > >And, sure enough, many FTP clients don't implement >continuation lines. I have no sympathy for the users of these FTP >clients. While it's true that continuation lines are in the RFC, don't you think it's a little harsh to have no sympathy for the USERS? In most cases the users have little to do with the IMPLEMENTION of their FTP clients. It's the implementors perhaps who deserve to be strung up. :-) > >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. As an unfortunate user of one of these broken FTP clients I did just that. However, it should be mentioned that this FTP client seems to be for 4.3 BSD (which SunOS 3.5 is not). It is very easy to get working in 4.2 BSD though, there are a few changes in ftp.c to make and a couple of functions to write (the hostent structure only returns one h_addr, not a list of them and strcasecmp() and strncasecmp() need to be worked written). > >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 :-) Well, SunOS 3.5 FTP clients don't understand continuation lines (unless we don't have something configured correctly here, in which case I'm sure many people will let me know). You may have been including SunOS as BSD Unix at any rate. This certainly is not meant as a complaint to you since I HIGHLY appreciate the service you provide (for free too! :-) ). +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+ | Todd Goodman, BBN Communications, Inc. tgoodman@bbn.com | | Disclaimer: I never speak for anyone but myself. | +=-=-=-=-=-=-=-=-=-=-=-= "Right theory, wrong universe." =-=-=-=-=-=-=-=-=-=-=+
nelson@sun.soe.clarkson.edu (Russ Nelson) (08/28/89)
In article <44846@bbn.COM> tgoodman@bbn.com (Todd Goodman) writes:
However, it should be mentioned that this FTP client seems to be for 4.3 BSD
(which SunOS 3.5 is not).
Hmmmm... I didn't realize that.
It is very easy to get working in 4.2 BSD though,
there are a few changes in ftp.c to make and a couple of functions to write
(the hostent structure only returns one h_addr, not a list of them and
strcasecmp() and strncasecmp() need to be worked written).
I'm sure that Rick Adams would be interested in your changes. ... Well,
he *might* be interested in them, anyway. He's rick@uunet.uu.net.
Well, SunOS 3.5 FTP clients don't understand continuation lines
(unless we don't have something configured correctly here, in which
case I'm sure many people will let me know). You may have been
including SunOS as BSD Unix at any rate.
Yes, SunOS's FTP client is a major offender. And no, I didn't realize that
SunOS isn't BSD Unix.
--
--russ (nelson@clutx [.bitnet | .clarkson.edu])|(70441.205@compuserve.com)|
(Russ.Nelson@f360.n260.z1.fidonet.org)|(BH01@GEnie.com :-)ked@garnet.berkeley.edu (Earl H. Kinmonth) (08/28/89)
In article <NELSON.89Aug27164509@sun.clarkson.edu> nelson@clutx.clarkson.edu writes: >In article <44846@bbn.COM> tgoodman@bbn.com (Todd Goodman) writes: [problems with ftp on various machines not working with grape. suggestion to pull ftp from uunet.] I ran into the problem of ftp on a Sun not working with grape. It also had problems (not fatal) with simtel20. I pulled the ftp from uunet and got it working in about an hour. The process can be described as simple only if you have a reasonable amount of experience with various **IX systems and can guess relatively rapidly where alternatives to missing include files and library items might be found. It is no plug and play operation. I suspect I'm one of the few specialists on modern Japanese history who could have done it. :) Indeed, there were enough changes that I suspect even a few **IX adepts would have problems, not even counting the fact that (a) the code was not in the directory I was told to look and (b) there were at least two sets of ftp source to be found. Unless the grape ftp code that breaks SUN ftp offers some very great advantage to the grape moderator and some equally great advantage to the majority of grape users, even if it is completely kosher by ftp standards, it is a pain in the arse.
bobmon@iuvax.cs.indiana.edu (RAMontante) (08/28/89)
nelson@clutx.clarkson.edu <NELSON.89Aug27003535@sun.clarkson.edu> : - -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. I can't resist a quick flame, directed at the "power users" in general --- As an Unfortunate User with a limited disk quota on a system that is constantly nagging people about 99.9% disk utilization, it is really difficult for me to justify keeping (and paying for) personal variants of all the system software in my own account. I could spend all my time trying to tell the sysadmins what software to upgrade and how, but "mind your own business and leave me alone" gets to be an uninteresting response after awhile.