[comp.unix.questions] anonymous FTP from System V

RSILVERMAN@eagle.wesleyan.edu (Richard Silverman) (03/08/89)

	Does anyone have experience setting up anonymous FTP on a System
V machine?  I am working on an AT&T 3B2 under version 3.1, and am having
some difficulty.  The home directory for the ftp login is /usr/ftp, and that
tree looks like this:

directories	files
-----------	------------
ftp/bin		ls sh
ftp/etc		group passwd
ftp/shlib	libc_s
ftp/pub

The protections are fine (for argument's sake, I made them all 777).  I can
log in as 'anonymous' just fine, but when I try to get a directory, ftp returns
the error "data socket not created (0.0.0.0,0)".  I can perform the steps
that the manual says ftp goes through myself without problems: chroot to
the home directory and run ls.  Any help will be very much appreciated,

                                                Richard Silverman

arpa:	rsilverman@eagle.wesleyan.edu           Wesleyan University
bitnet:	rsilverman@wesleyan                     Middletown, CT
CIS:	[72727,453]                             06457

scott@rdahp.UUCP (Scott Hammond) (03/10/89)

In article <18583@adm.BRL.MIL> RSILVERMAN@eagle.wesleyan.edu (Richard Silverman) writes:
>
>	Does anyone have experience setting up anonymous FTP on a System
>V machine?  I am working on an AT&T 3B2 under version 3.1, and am having
>some difficulty....

I've never seen quite the problem you describe, but I know of a similar
problem.  When using anon ftp on a 3B2 with SysV3.1 and WIN3B/1.1, I
would log in as you did, but trying to look at the directory never
produced a response, or I should say the response was always as if there
was nothing in the directory at all. 

Well anyway, the "fix" which I accidentally discovered was to place in
the ftp bin directory an "ls" from a 3b15 running SysV2.1.2.  Worked
just fine.  The AT&T solution was to buy the upgrade to WIN3B. 

Your problem reminds me of a protected (chroot) environment a friend
created for tftpd, so that a Proteon router on campus could do an
auto-boot from it.  The thing he originally overlooked but later
discovered was that he had to have a tftp/dev directory with a network
device(s) in it.  Don't know if this might apply to your situation or
not.

--
Scott Hammond,  R & D Associates, Marina del Rey, CA  (213) 822-1715
: {sdcrdcf,zardoz}!rdahp!scott
:  rdahp!scott@sm.unisys.com
:  scott@harris.cis.ksu.edu