Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!agate!garnet.berkeley.edu!ked From: ked@garnet.berkeley.edu (Earl H. Kinmonth) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: FTP grape.ecs.clarkson.edu Message-ID: <1989Aug27.215905.16975@agate.uucp> Date: 27 Aug 89 21:59:05 GMT References: <4315@cps3xx.UUCP> <44846@bbn.COM> Sender: usenet@agate.uucp (USENET Administrator;;;;ZU44) Reply-To: ked@garnet.berkeley.edu (Earl H. Kinmonth) Organization: University of California, Berkeley Lines: 22 In article 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.