[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

4208.0. "How does a VMS user FTP?" by WILARD::BARRETT (I must not waste pixels) Wed Oct 17 1990 02:20

    How does an a user on an ENET VMS node FTP? I've heard that there is a
    way to send an email that causes the requested file to be emailed back
    to you (I assume in a SHAR format).
    
    Can someone that knows about all this post the process and the location
    of Amiga Archives? If the archive list is too long (as I suspect),
    the method of obtaining the complete list so a search command for
    "amiga" will do.
    
    Thanks!
    
    Keith
T.RTitleUserPersonal
Name
DateLines
4208.1Some starting info from UsenetBOMBE::MOOREAmiga: Real computing on a PC budgetWed Oct 17 1990 06:40198
Article 66020 of comp.sys.amiga:
Path: shlump.nac.dec.com!rust.zso.dec.com!bacchus.pa.dec.com!deccrl!decvax.dec.com!mcnc!mephisto!ncar!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!abcfd20.larc.nasa.gov!tadguy
From: tadguy@abcfd01.larc.nasa.gov (Tad Guy)
Newsgroups: comp.sys.amiga
Subject: Re: How to FTP, by Jason Freund
Message-ID: <TADGUY.90Sep20135518@abcfd20.larc.nasa.gov>
Date: 20 Sep 90 18:55:18 GMT
References: <142740@sun.Eng.Sun.COM> <414@epicb.com>
Sender: news@abcfd20.larc.nasa.gov (USENET File Owner)
Organization: NASA/Langley Research Center, Hampton, VA
Lines: 183
In-Reply-To: jerry@truevision.com's message of 20 Sep 90 13:23:20 GMT

In article <414@epicb.com> jerry@truevision.com (Jerry Thompson) writes:
> OK, for those of us without an Internet connection, how do we get files?

You must be a New User; this has been posted before...

	...tad


        BITFTP -- Princeton BITNET FTP Server

BITFTP provides a mail interface to the FTP portion
of the IBM TCP/IP product ("FAL") running on the
Princeton VM system, to allow BITNET/NetNorth/EARN users
to ftp files from sites on the Internet.

BITFTP currently accepts requests only via RFC822-format
mail, IBM NOTE-format mail, PROFS-format messages, or
files with no headers at all.  BITFTP currently returns
the requested files as NETDATA-format files or as mail files
containing UUENCODED data.  If you specify "UUENCODE" or
"NETDATA" on your "FTP" command, BITFTP will attempt to
use that format.  If you do not specify the format, BITFTP
will attempt to select the appropriate format for your node.
BITFTP attempts to send NETDATA-format files through the gateway
from EARN into Janet via the NIFTP facility at Rutherford Lab.

If BITFTP sends you a file you cannot read, THE FIRST THING
TO DO is to make sure that you specified ASCII if the file
should contain textual material or that you specified BINARY
if the file should contain binary data, executable programs,
tar files, or the like.  VMS users should specify BINARY F 512
and should use RECEIVE/BINARY to receive the NETDATA-format
binary files BITFTP sends them.

If BITFTP sends you a uuencoded file that you cannot
uudecode, the first thing to do is to translate all occurrences of
0x7E in the file to 0x5E and then try uudecoding again.  (Some
gateways are changing 5Es to 7Es when the files pass through them.)

To use BITFTP, send mail containing your ftp commands to
"BITFTP@PUCC".  The first command to BITFTP must be "FTP"
or "HELP".

The recommended syntax for ftp requests is:

FTP hostname NETDATA    --or--    FTP hostname UUENCODE
USER username password
<other ftp subcommands>
QUIT

After the hostname on the FTP command, you may specify
"UUENCODE" or "NETDATA" to tell BITFTP the format in which
you wish to receive files.

(If the username is "anonymous", no password is required;
BITFTP will use your userid and nodeid as the password.)

Note that on many systems passwords are case-sensitive;
that is, the password may be required to be in lower case
or mixed case or upper case.  (The same is true of directory
and file names.)

The following is an example of an ftp request:

FTP  f.ms.uky.edu  NETDATA
USER  anonymous
CD  /pub/msdos/Games
DIR
BINARY
GET  robotron.arc  msdos.robotron
QUIT

To request a list of some of the hosts that allow anonymous ftp,
send BITFTP mail or a message containing only the command "FTPLIST".
Note that there is no guarantee that BITFTP can access
all the hosts in this list.

BITFTP implements a subset of the ftp subcommands provided
in the IBM TCP/IP and uses the same syntax.  Therefore, you
may find it useful to obtain the "IBM TCP/IP for VM Command
Reference Manual", IBM order number GC09-1204.

The currently supported subcommands are:

  ACCT        -- to send host-dependent account information.
    format:   ACCT account-information

  ASCII       -- to change the file transfer type to ASCII.
    format:   ASCII

  BINARY      -- to change the file transfer type to image.
    format:   BINARY <FIXED record-len> <VARIABLE>

  CD          -- to change the working directory.
    format:   CD directory

  CLOSE       -- to disconnect from the foreign host.
    format:   CLOSE

  DIR         -- to get a list of directory entries.
    format:   DIR

  EBCDIC      -- to change the file transfer type to EBCDIC
    format:   EBCDIC

  GET         -- to get a file from the foreign host.
    format:   GET foreignfile <localfile>

              If you specify "localfile", it must be in
              the forms "filename.filetype" or "filename",
              and the filename and filetype may each be no
              more than 8 characters long and may not contain
              periods.

  LOCSTAT     -- to display local status information.
    format:   LOCSTAT

  LS          -- to list the files in a directory.
    format:   LS <name>

  PWD         -- to print the working directory.
    format:   PWD

  QUIT        -- to disconnect from the foreign host.
    format:   QUIT

  STATUS      -- to retrieve status information from a foreign host.
    format:   STATUS <name>

  SYSTEM      -- to get the name of the foreign host's operating system.
    format:   SYSTEM

  TYPE        -- to specify Image, ASCII, or EBCDIC file transfer.
    format:   TYPE <I|A|E>

The files you request will be sent to you in NETDATA format or
UUENCODED inside mail files.

You will also receive a mail file containing a log of your
ftp session.  In that mail file, entries prefixed by ">" are
your original commands; those prefixed by ">>" are your
commands as interpreted by BITFTP and passed to TCPIP; those
prefixed by ">>>" are your commands as interpreted by TCPIP and
passed to the remote host; those prefixed by "<<<" are messages
from the remote host; and those prefixed by ">>>>" are completion
messages from BITFTP.

If BITFTP is unable to connect to the host you specify,
it will send you mail after the first attempt, but will keep
trying at intervals over three days.  The only additional mail
files you will receive will be when the connection is made
successfully or when BITFTP gives up after three days.

The load on BITFTP is often very heavy, and network
backlogs are often so great that it may take several days
for a file to get to you once BITFTP sends it, so please be
patient and don't send multiple requests for the same file.
If your system allows you to send interactive messages, you
can inquire about BITFTP's backlog by sending the query
"How are you?", e.g., on a VM system:

   TELL BITFTP AT PUCC How are you?


This service is currently under development and is far from
complete.  Current plans for improvements include:

1.  Acknowledgments via MSG when mail is received and when
    processing has been completed.

2.  A much more complete HELP facility.

Questions about BITFTP and suggestions for improvements
should be directed to Melinda Varian, MAINT@PUCC on BITNET or
MAINT@pucc.princeton.edu on the Internet.

The author gratefully acknowledges the use of the FTP
SUBCOM interface written by David Nessl, the SENDJANI EXEC
written by Alan Flavell, the uuencoding utility written by
John Fisher, and the RFC822 parsing routine written by Eric
Thomas.  NOTE:  If you have any complaints or suggestions
about the way any of these routines work in BITFTP, please
send them to MAINT@PUCC (Melinda Varian), not to the authors.


4208.2More info...BOMBE::MOOREAmiga: Real computing on a PC budgetWed Oct 17 1990 07:294
    See also topic 3339.* for further discussion and examples.

    There is supposedly a reverse chronological list of files (/FILES.Z),
    updated nightly, on abcfd20.
4208.3More please...CSSE32::SMITHReality, just a visible imagination?Thu Oct 18 1990 19:256
Ok, sounds simple enough.  But, how does one find out what the different FTP
systems are?  I mailed a DIR request to NM%DECWRL::"bitftp@pucc.princeton.edu"
but what other FTP sites are there.


...Ed
4208.4ELMST::MCAFEESteve McAfeeThu Oct 18 1990 19:4911
One place to find them is to look in the comp_sys_amiga notesfile on
FRSOLD::.  Do a dir/title="ftp".  If a list of sites comes over
usenet again I'll post it here.

By the way, in my experience these areas are noway near as complete
as the ones we have here on tape::, wjg::, etc.  In fact, they are
usually not as up-to-date.  Anything really good usually makes it
here sooner or later through the kindness of others in this notesfile.
We all know who they are :-) (Ed, Paul, John, etc).

- steve
4208.5More FTP/UUCP info neededMCDONL::BARRETTI must not waste pixelsThu Oct 18 1990 20:1422
    (I usually hate it when other say this, but...) "forgive my
    ignorance here, but I have some minor questions.
    
    When you get a file, I assume it's in a SHAR format, correct?
    Where is the "accepted" UNSHAR for VMS and/or Amiga that handles
    these files? After going throught the FF disks, I learned that they
    all have quirks and some don't work well with each other's files. What
    works best with the FTP'd files (or does any of this matter)?
    
    Second question concerns direct UUCP access. When choosing a "feeder"
    from the registered node map, I assume the next step is to contact that
    person/postmaster and ask for permission/access -- right? Am I also
    correct in assuming that there isn't a "standard" password and that
    just knowning a site's info and modem phone number isn't enough?
    I'm having a problem in that there are only 2 registered USENET
    nodes in my local calling area (according to the USENET posting
    for connecticut). I've sent several email to both asking for
    info/help/permission and havn't gotten any responses. Am I missing
    something or is it just that I should keep looking/trying?
    
    
    Thanks! Keith
4208.6SHAR.EXECRISTA::CAPRICCIOSmilin' Joe FissionThu Oct 18 1990 20:3711
4208.7Well Known storesWELSWS::FINNISThu Oct 18 1990 21:4673
    
    The Invisible man strikes again..
    
    
    
	Some well known stores.....
	If you Know of any more I'll be interested.....

	What I really really want is an Encyclpedia


Name                   Tz  IP-Address(es)  Files
------------------------------------------------------------------------------
a.cs.uiuc.edu          c   128.174.252.1   /pub/amiga/
                           128.174.237.2
cseg.uark.edu          c   130.184.64.202  /amiga/ (login 'bbs' => bbs)
etana.tut.fi           +2  128.214.1.1     /amiga/ (ff#158-320)
 (or funet.fi)
f.ms.uky.edu           e   128.163.128.6   /alt.sources.amiga/
                                           /comp.sources.amiga/
                                           /pub/amiga/
                                           /incoming/Amiga/
geomag.gly.fsu.edu     e   128.186.10.2    /pub/pics/IFFpics/
                                           /pub/pics/hampics/
                                           /pub/pics/gifs/
ix1.cc.utexas.edu      c   128.83.1.21     /microlib/amiga/
ix2.cc.utexas.edu      c   128.83.1.29     /microlib/amiga/
j.cc.purdue.edu        e   128.210.9.2     /comp.binaries.amiga/
                                           /comp.sources.amiga/
louie.udel.edu         e   128.175.1.3     /pub/amiga/
                                           /pub/ka9q/
                                           /Amiga.incoming/
mrcnext.cso.uiuc.edu   c   128.174.73.105  /amiga/      (ff#189-320)
mtsg.ubc.ca            p   128.189.103.1   PC6:         (not a UNIX machine!)
plains.nodak.edu       c   134.129.111.64  /pub/amiga/
rusmv1.rus.uni-stuttgart.de
                       +1  129.69.1.12     /soft/amiga
swan.ulowell.edu       e   129.63.224.1    /amiga/
                           129.63.1.1
tolsun.oulu.fi         +2  128.214.5.6     /pub/amiga/ (login 'box' => bbs)
                                           /pub/amiga3/
                                           /pub/amiga4/
                                           /pub/amiga5/
topaz.rutgers.edu      e   128.6.4.194     /pyr-public/text/mg2/sys/amiga/
trantor.umd.edu        e   128.8.10.14     /info-amiga/    (ff#001-300)
tukki.jyu.fi           +2  128.214.7.5     /pub/amiga/
 (or jyu.fi)
tut.cis.ohio-state.edu e   128.146.8.60    /pub/amigo/
ucbvax.berkeley.edu    p   128.32.133.1    /pub/amiga/
                           128.32.130.12   /pub/SKsh/
                           128.32.149.36   /pub/dillon/
                           128.32.137.3       
ucsd.ucsd.edu          p   128.54.16.1     /hamradio/karn/
 (or ucsd.edu)                             /amiga
                                           /midi/sofware/amiga/
uhccux.uhcc.hawaii.edu p-2 128.171.1.101   /amiga/Amiga/
                           128.171.7.2
ummts.cc.umich.edu     e   35.1.1.43       PC6:
uunet.uu.net           e   192.48.96.2     /amiga-sources/
uxc.cso.uiuc.edu       c   128.174.5.50    /utils/cshar/
uxe.cso.uiuc.edu       c   128.174.5.54    /amiga/      (ff#001-188)
wuarchive.wustl.edu    c   128.252.135.4   /systems/amiga/comp.binaries.amiga/
                                           /systems/amiga/comp.sources.amiga/
                                           /usenet/comp.binaries.amiga/
                                           /usenet/comp.sources.amiga/
xanth.cs.odu.edu       e   128.82.8.1      /usenet/comp.binaries.amiga/
                           128.82.4.1      /usenet/comp.sources.amiga/
                                           /amiga/
    
    
    
    
    			-Pete-
4208.8And ...WELSWS::FINNISThu Oct 18 1990 21:484
    For Xanth read  abcfd20.larc.nasa.gov  
    
    
    			-Pete-  :-)
4208.9Very fresh FTP site info...BOMBE::MOOREAmiga: Real computing on a PC budgetFri Oct 19 1990 00:49433
Article 35427 of comp.sys.amiga:
Path: sousa.enet.dec.com!shlump.nac.dec.com!decuac!haven!aplcen!uakari.primate.wisc.edu!sdd.hp.com!wuarchive!emory!gatech!burdell!juan
From: juan@burdell.gatech.edu (Juan Orlandini)
Newsgroups: comp.sys.amiga
Subject: monthly (ahem) ftp site list post.
Message-ID: <278@mephisto.edu>
Date: 18 Oct 90 20:54:19 GMT
Sender: news@gatech.edu
Reply-To: juan@burdell.UUCP (Juan Orlandini)
Organization: ICS Lab
Lines: 419


(I have lots of things to change on this list, and it's on my queue of 
 things to do. I will post an updated version multo pronto.)


------------------------------------------------------------------------------
                    AMIGA SOFTWARE SOURCES (October 9, 1990)

The following is a list of mail-servers, BBS services, and anonymous Internet
FTP sites that I know, and which provide a large selection of Amiga software.

This list is a couple of months late. I have no excuse other than I have been
very busy and have had some disk problems. I'll be back on schedule beginning
next month. Sorry folks.

***OLD NEWS***
***OLD NEWS*** 

I have created an anonymous ftp account on my machine. I have some extra disk
space now, and would enjoy greatly if people would begin using it to upload
and download amiga, mac, and pc stuff. Please use the incoming directory to
put new stuff in.
     The machine is called burdell.gatech.edu (130.207.3.207). Please
restrict ftp'ing between 1700 and 0600 EST. 
***NEWS***
***NEWS***

Please keep me informed about any new sites, mail-archives, IP-addresses, and
directories, as well as the ones which have been removed, changed, or
manipulated (enough to make this list "old").  I'd appreciate it. Since during
these days I'm very busy, I have little time to read newsgroups. Therefore,
please do *email* your suggestions/corrections to me. I may not see your
posting. Also, if you email me something, which does not show up in the next
version of the list, please don't get mad about it. My mind was probably doing
something else... Remind me again...

You will see a section below which is titled "CHANGES THIS MONTH". Lines in
that section may start with !, -, or +. They mean "changed", "removed", and
"added", respectively.

This month there are no changes. My machine had a severe disk problem with
the partition that kept my mail messages. That is where I deposit all the
new info on sites and suggestions. Sorry about that. If you sent me some
mail regarding this list, and I have not accted upon it, it is because of
this. Please send me a note again, and I will put it in next months list.

The "TZ" column shows the timezone of that site. This might not be very
important to people in the US, but since the sites shouldn't be used 0600-1800
local time weekdays so as not to bog things down, people in Europe should be
helped by this. "e,c,m,p" means eastern, central, mountain & pacific,
respectively.  Sites ending with .fi is in Finland (Greenwich+2).

My plan is to extend the list of mail servers and UUCP ftp sites etc., in
order to enable people without access to Internet to have some sort of
software source.  If you operate such a server or site, please send me couple
of lines describing how people can connect to it, or send requests, what kind
of programs you have, whether it is also accessible via Internet anonymous
ftp, if yes what the IP-address is, what the directories are etc.  Include any
information you think would be appropriate.  I will add those instructions to
the end of this list, and won't be able to check their validity (is there
someone willing to make that test for me?).  Internet anonymous ftp sites will
be checked as before.  Still, I may miss some directories or removed sites
since I don't have infinite supply of time to spend on this list. So, think
twice before flaming me...

Some of the Internet sites also provide BBS service. I marked them as such. To
connect to them as BBS, use 'telnet' instead of 'ftp'.

Thanks very much to many people who contributed to the creation and
maintenance of this list. It is in no way my original work (although I put
lotsa time into it). It is just a collection of information which wouldn't be
possible without those people.

Once more, thanks to all those that send me mail about new sites and
corrections. Without you, this list is impossible. I'm always glad to hear
from anyone, so mail away!

Juan Orlandini  (juan@ics.gatech.edu)

================= CHANGES THIS MONTH (since July 3, 1990) ===================

(read the little note I have above)

=============================== FTP/BBS SITES ================================

Name                   Tz  IP-Address(es)  Files
------------------------------------------------------------------------------
a.cs.uiuc.edu          c   128.174.252.1   /pub/amiga/
                           128.174.237.2
abcfd20.larc.nasa.gov  e   128.155.23.64   /usenet/comp.binaries.amiga/
                                           /usenet/comp.sources.amiga/
                                           /amiga/
                                           /incoming/amiga/  (Watch viruses!)
burdell.gatech.edu     e   130.207.3.207   /pub/amiga
cseg.uark.edu          c   130.184.64.202  /amiga/ (login 'bbs' => bbs)
drycas.club.cc.cmu.edu e   128.2.232.11    [ANONYMOUS.AMIGA-SIG] (a VMS system)
etana.tut.fi           +2  128.214.1.1     /amiga/ (ff#158-320)
 (or funet.fi)
f.ms.uky.edu           e   128.163.128.6   /alt.sources.amiga/
 (or ms.uky.edu)                           /comp.sources.amiga/
                                           /pub/amiga/   (ff#300-340)
                                           /incoming/Amiga/
funic.fu.fi            +2  128.214.6.100   /pub/amiga/
ix1.cc.utexas.edu      c   128.83.1.21     /microlib/amiga/
ix2.cc.utexas.edu      c   128.83.1.29     /microlib/amiga/
j.cc.purdue.edu        e   128.210.9.2     /comp.binaries.amiga/
                                           /comp.sources.amiga/
louie.udel.edu         e   128.175.1.3     /pub/amiga/
                                           /pub/ka9q/
                                           /pub/Amiga.incoming/ (Watch viruses)
mars.ee.msstate.edu    e   130.18.64.3     /files/Amiga.Comm/
                                           /files/Amiga.Games/
                                           /files/Amiga.Graphics/
                                           /files/Amiga.Misc/
ux1.cso.uiuc.edu       c   128.174.5.59    /amiga/      (ff#1-350)
mrcnext.cso.uiuc.edu   c   128.174.73.105  /amiga/      (ff#189-350)
mtsg.ubc.ca            p   128.189.103.1   PC6:         (not a UNIX machine!)
plains.nodak.edu       c   134.129.111.64  /pub/amiga/
rusmv1.rus.uni-stuttgart.de
                       +1  129.69.1.12     /soft/amiga
swan.ulowell.edu       e   129.63.224.1    /amiga/
                           129.63.1.1
tolsun.oulu.fi         +2  128.214.5.6     /pub/amiga/ (login 'box' => bbs)
                                           /pub/amiga3/
                                           /pub/amiga4/
                                           /pub/amiga5/
topaz.rutgers.edu      e   128.6.4.194     /pyr-public/text/mg2/sys/amiga/
trantor.umd.edu        e   128.8.10.14     /info-amiga/    (ff#001-350)
tukki.jyu.fi           +2  128.214.7.5     /pub/amiga/
 (or jyu.fi)
tut.cis.ohio-state.edu e   128.146.8.60    /pub/amigo/
ucbvax.berkeley.edu    p   128.32.133.1    /pub/SKsh/
                           128.32.130.12   /pub/dillon/
                           128.32.149.36   /pub/amiga/
                           128.32.137.3       
ucsd.ucsd.edu          p   128.54.16.1     /hamradio/karn/
 (or ucsd.edu)                             /pub/amiga
                                           /midi/sofware/amiga/
uhccux.uhcc.hawaii.edu p-2 128.171.1.101   /amiga/Amiga/
                           128.171.7.2
ummts.cc.umich.edu     e   35.1.1.43       PC6:
uunet.uu.net           e   192.48.96.2     /amiga-sources/
uxc.cso.uiuc.edu       c   128.174.5.50    /utils/cshar/
uxe.cso.uiuc.edu       c   128.174.5.54    /amiga/      (ff#001-188)
wolfen.cc.uow.edu.au   +10 130.130.0.1     /pub/amiga
                                           /pub/comp.sources.amiga
                                           /pub/comp.binaries.amiga
wuarchive.wustl.edu    c   128.252.135.4   /systems/amiga/comp.binaries.amiga/
                                           /systems/amiga/comp.sources.amiga/
                                           /usenet/comp.binaries.amiga/
                                           /usenet/comp.sources.amiga/

============================= AMIGA MAIL SERVERS =============================

---------------------------------- SERVER 1 ----------------------------------

Correspondence to: greg@noel.CTS.COM

Requests to: amiga-archive@ncr-sd.SanDiego.NCR.COM (Registered domain address)
             amiga-archive@ncr-sd.UUCP             (Psuedo-domain address)
             ...!ncr-sd!amiga-archive              (UUCP path)

Ncr-sd is not on the Internet; FTP access is not possible.  Anonymous UUCP is
not supported.

All lines of the incoming mail message are ignored except lines that begin
with either "path" or "send".  (For compatibility with other servers, "help"
and "index" are also recognized and are treated as equivalent to "send help"
and "send index".)

If a line saying "path route-from-us-to-you" is encountered, it will be used
for any subsequent mail.  If the path line is missing, the system will try to
determine the reply address; it's pretty good at guessing, but it's not
perfect.  Try it initially without the path line; if you don't get an answer
in a reasonable period, try again with one.  We run a full domain router, so
the route-from-me-to-you should be a domain address (or a UUCP psuedo-domain
address) if you have one.

Start with "send help" for information on how to get started.

The mail server is actually the beta test version of an archive server that I
hope to fill with Amiga sources and binaries.  If you are interested in
providing some feedback, try the requests "send help" and "send index" to see
how to use it.  I'd appreciate any help you can offer in getting this started.
There's only about 15MB of stuff so far, so I need to make arrangements to get
access to more of the comp.{sources,binaries}.amiga archives; anybody have
this in a form that I can conveniently get?


==============================================================================

------------------------------ Server 2 --------------------------------------

        Announcing MRCserv, a mailserver based at Mount Royal College.
 
        MRCserv is a MAIL ONLY based server.  Mount Royal is not on
        the Internet so FTP access is not supported.  Anonymous UUCP
        is also not supported.
 
        All commands to the server must be in the BODY of the message.
        The subject line is ignored.
 
        The address of the server is MRCserv@Janus.MtRoyal.AB.CA
 
        Mount Royal College is in Calgary, Alberta, Canada.  Our time
        zone is MST.  Please try and restrict your archive access to
        non-prime hours (primetime is 07:00 - 17:00).
 
        MRCserv is currenly in BETA test.  If you experence any problems
        please send e-mail to RMF@Janus.MtRoyal.AB.CA
 
|       There had been a fatal bug in the server in that it would inform
|       you of files being sent, but they never were (BETA 0.48)
 
|       A PATH command had been added.  It appears that the server had some
!       trouble with "!" addresses, so a path command became necessary.  The
|       server is pretty good usally in figuring out return-paths, hoever if
|       you don't receive a response from the server try again with a PATH
|       command.  Remember the PATH is from the SERVER to you.  If you are
|       using "!" paths please add the .UUCP domain name, ie. a!b!c!d!user.uucp
 
        Enjoy!
==============================================================
 
    MRCserv - Mount Royal College Mail Server (BETA 0.50)
    -----------------------------------------
 
    Commands:
        DIR       -   list a directory (equiv. to ls -l)
        LS        -   briefly list a directory
        DIR -d    -   list subdirectories only
        LS -d     -   briefly subdirectories only
|       DIR -s nn -   list files added to archinve in the last 'nn' days
|                     an optional parameter of 'directory specification
|                     can be added (ie dir -s 07 *.* )
|       LS -s nn  -   briefly list files added in last 'nn' days
        CD        -   change working directory
        GET       -   sends you one or more files
        HELP      -   sends you this help
        EXIT      -   finishes request
|       PATH      -   Path from MRCserv to you.  (if your using "!" paths make
|                     address ends with a .UUCP ie.  foo!bar.uucp)
        PUT       -   Put a file in the archive. (must be validated first).
|                     (currently not implemented)
 
    Extensions:
        ZOO     - ZOO file      ZUU     - UUencoded ZOO file
        ARC     - ARC file      AUU     - UUencoded ARC file
        LZH     - LHARC file    LUU     - UUencoded LHARC file
        LHW     - LhWarp file   DIR     - VMS directory file
        WRP     - Warp file     UUE     - UUencoded executable
|       ABC     - ABasiC file
 
    Wildcards and directory specifications are allowable with DIR and GET
    commands.  These follow standard VMS wildcard rules.
 
    Subdirectories can be accessed via the CD command.  For example, if
    you see a file with the extension .DIR (ie ARCHIVERS.DIR), CD to
    it by issuing the command CD [ARCHIVERS] (case insensitive, brackets are
    not required).  To move to the parent directory issue the command CD [-]
    (Brackets are required) To move to the root directory issue command
    CD [000000]
 
    Binary files (ZOO/ARC/LZH/EXE) will be uuencoded before being sent.
 
    Files larger then 100 blocks will be sent in multiple parts.  You
    will be informed of the number of parts in the server's response.  All
    files will be sent as separate messages (except HELP).
 
    In the reply sent by MRCserv, your commands are preceeded by a less-than
    sign "<".  MRCserv responses are preceeded by a greater-than sign ">".
 
    Original code written by Henry Bland - Henry@Daffy.FhHosp.AB.CA
    Modified and maintained by Russ Forster - RMF@Janus.MtRoyal.AB.CA
 
================================ END OF LIST =================================

From toka@tko-sony-12.hut.fi Fri Jun 15 14:58:00 1990
Return-Path: <toka@tko-sony-12.hut.fi>
Received: from santra.hut.fi ([130.233.224.1]) by burdell.gatech.edu (4.0/SMI-3.2)
	id AA01518; Fri, 15 Jun 90 14:57:31 EDT
From: toka@tko-sony-12.hut.fi@cc.gatech.edu
Received: from tko-sony-12.hut.fi by santra.hut.fi
	(5.61++/7.0/TeKoLa) id AA27527; Fri, 15 Jun 90 21:59:38 +0300
Received: by tko-sony-12.hut.fi (5.61++/6.8/S-TeKoLa)
	id AA06945; Fri, 15 Jun 90 21:59:15 +0300
Date: Fri, 15 Jun 90 21:59:15 +0300
Message-Id: <9006151859.AA06945@tko-sony-12.hut.fi>
To: juan@burdell.gatech.edu
Subject: Amiga  FTPsites
Status: RO


This was not on your list:

funic.funet.fi (aliased to nic.funet.fi (or was it the other way round?))
128.214.6.100

This is (or will be) the main FTP-server in Finland, where most services
will be moved. I think they are also working on a mailserver and some
other features. It is quite reliable, and is officially supported
by the Finnish-University-Network (or whatever) organisation FUNET.


/README:
----8<---

	Welcome to FUNIC.FUNET.FI

    This is s Sun4/330 with (19-Mar-90) 1.5GB disk space (660MB used).
It is owned by  Finnish Academic and Research Network Project FUNET,
and is located at Finnish State Computing Centre, near Helsinki, Finland.

  If you have better suggestions than 'FUNIC' (or 'HAMSTER') for naming this
node, please let us know. Also a good name for BITNET is welcomed.

This system has lots PD material on its FTPable areas. We have also plans for a
couple of info-server -like systems for maildelivery of remote files (few which
are monitored here).  BUT NOT YET!
(Details will be explained later when those systems are operational)

	This FTPSERVER has some special features which may help on grabbing
        files from here:

	<filename>.Z	Compress designated file while
			fetching from this system.
	<dirname>.tar	Make a TAR (using GNU tar-1.07) of dir.
	<filename>.tar	Make a TAR (- " -) of file.
	<dirname>.tar.Z Make a compressed tar of dir.
	<filename>.tar.Z Make a compressed tar of file.
                        (Why to tar a single file? To get its date & time
                        information too...)

	Note:	It isn't very useful to compress .arc, .zoo, .gif or
		.Z files.  Usually they just expand when compressed :-(
		(Why?  They all use similar compression schemes.)

	Note2:  This ftp server won't perform .tar or .tar.Z transfer
                (mentioned above) for top level directories.
		This is to avoid accidental loading of whole archive over
		the network to your disk.   Several hundred megabytes of
		.tar isn't very easy to handle.
                So .tar and/or .tar.Z will only work in some subdirectories.
                Of course, this restriction doesn't apply for regular files.

	Special command   'FIND regexpr'  (your average UNIX ftp client
accepts it like this:  'quote find gcc370')  to run regexpr matching
against files in archive.  Scans special file with UNIX regex(3) library
routines, which about implement ed (UNIX) style regexprs.

        When this server is complete the actual disk mount points will not be
seen.  Later on we hope to get some even more reasonable directory structure.

	This FTPSERVER counts the number of anonymous customers
currently on the system, and currently limits it to 16 simultaneous FOREIGN
anonymous users (so it doesn't show how many finns there are, also the
restriction of 16 simultaneous users doesn't apply for the finns).

        Note that we are located far away from USA. Our connection to USA
is only a 56 KBits/Sec satellite link (which is used by all the scandinavian
countries). Our main purpose is to be central repository for finnish users.
Lately trafic on that link has been TWICE as great to USA as it has been to
Finland, think about that...  (Feb-Apr -90)

	For GIF archive ( /pub/misc/gif ) you can send questions to
gif-adm@funic.funet.fi .  FUNIC just provides the disk space, people behind
'gif-adm' take care of the material.

	For other interest areas:  There is file  /etc/aliases  which
contains some comment informations from actual system mail alias database.
See if you can find proper contact person/mail alias from there.

	If you want the sources for this FTP server (derived from PD material)
look into /bin for ls and ftpd programs (GNU-tar and BSD-compress are
unmodified).

    Bugs/problems:
	Matti Aarnio	<mea@funic.funet.fi>
	(And if possible, preselect a mail alias from /etc/aliases
	 according to your problem.)


---8<----

/pub/amiga/ReadMe:
-----8<----
	Here we have amiga pd stuff

	zoofiles 	contains stuff from usenet (comp.bin.amiga, ...)

	fish	contain Fred Fish's pd-diskettes (not too new now)
		upto ff320

	misc	other stuff

	new	contains latest stuff from usenet (some of it)

	gcc-port	contains GNU CC port by vinsci@funic.funet.fi et. al.

	Lucky and happiness hoped by
					pl
------8<-----

Actually, there are fish disks 158-350 + some (rough guess) 30MB of other
stuff for the time being.

Also, I've heard a rumor that UX1.CSO.UIUC.EDU contains some amiga PD.
I haven't been able to verify it.

Tomi Kause	t36288v@puukko	"Mark my last words. They might be
Ti II		toka@niksula	 what I just said."


=======================================================================
Juan Orlandini                /// "Whe have not inherited this      ///
Super User At Large          ///  earth from our parents, but      ///
College of Computing     \\\///   rather borrowed it from our  \\\///
juan@cc.gatech.edu        \XX/    children." -- Unknown         \XX/
=======================================================================


4208.10FTP site info appreciatedCSSE32::SMITHReality, just a visible imagination?Fri Oct 19 1990 11:276
Wow, what a list...


Thanks a bunch

Ed
4208.11Observations...KALI::PLOUFFAhhh... cider!Fri Oct 19 1990 14:0834
    Re: purpose of BITFTP.
    
    Please understand that BITFTP is just the library clerk, so to speak. 
    There are at least several hundred announced FTP sites with an
    unbelievable wealth of files available, even though there is extensive
    duplication.  Unfortunately, it's up to you to find what you want.  The
    best source I have found is simply watching the Usenet Amiga newsgroup
    - there's a fairly regular posting of Amiga FTP sites.
    
    FTP is the Internet's equivalent to DECnet COPYing from a remote node. 
    However, only a handful of people at some of Digital's research labs
    have direct access to the Internet.  I would not expect this to change
    anytime soon.
    
    Beware that any version of SHAR will have problems with somebody's
    screwy version of shar archiving.  The VMS SHAR I have doesn't like
    filenames presented as './file.name' -- the prefix is redundant and is
    equivalent to the VMS form '[]file.name'   ...Also beware that at least
    one version of Amiga UUDECODE chokes on UUencoded files with an extra M
    added to the end of each line.  A good version (such as the one in
    Dillon's UUCP 1.06D) will ignore extra characters in a line.  BITFTP
    sends UUencoded files with this characteristic.
    
    Re: .5 UUCP connections
    
    Discussed in another topic, but here's a brief answer.  The rule for
    UUCP connections is that you have working software and find someone
    willing to connect to you.  Unfortunately, nobody has any obligation to
    give you a connection.  I suggest searching a little farther afield. 
    You might also try asking for help finding a connection rather than
    asking directly.  In this fashion I was able to find a willing host
    about 15 miles and a toll call away.
    
    Wes
4208.12WELSWS::FINNISThu Oct 25 1990 20:5311
    
    Re UUCP connection   
    			What sort of connect time do you experience ?
    
    	Is the host node that you connect to buffer the data ( Timezone
    delayed access etc..)
    
    	Mail me if this is off the thread 
    
    			.Pete.
    
4208.13Response is pretty goodDECWET::DAVISYou always get what you deserveThu Oct 25 1990 22:287
    Using bitftp@pucc.princeton.edu I usually get a reply in a minute or
    two depending on the machine I'm trying to connect to.  I got a reply
    from a machine from Germany in approx. 8 minutes.  That is pretty good. 
    Some days it takes a day or so.  Most times the response is pretty good
    although I haven't tried using "GET" on a file larger than 80K or so.
    
    m
4208.14A bit confusedPAMSRC::BARRETTThis is my brain on Notes.Tue Oct 30 1990 14:3317
        Some questions concerning getting UUCP up on my home Amiga.
    
    I'm currently trying to get a news feed. I've sent email to all
    the registered sites that are local phone calls to my area, but
    haven't received any responses. Is this normal? Also, does the amiga
    "call" the other system to get it's data, or does the other system call
    the amia and download it, or both? If the other system calls me, are
    there sites willing to provide this service (for free or pennies)
    if the call isn't local? And finally; does it make a difference
    if I'm looking for a mail site or a news feed? In other words,
    is it easier to get someone to agree to be a news feed than to also
    forward mail or does it make no difference?
    
    
    Thanks! Keith
    
4208.15UnixWJG::GUINEAUTue Oct 30 1990 15:3743
>        Some questions concerning getting UUCP up on my home Amiga.
>    
>    I'm currently trying to get a news feed. I've sent email to all
>    the registered sites that are local phone calls to my area, but
>    haven't received any responses. Is this normal? 

Yes, that's normal. Unix system administrators like to be treated special :-)
try using lots of nice compliments, on the order of "I grovel at your 
vast superiority and would be eternally in your debt if you would allow
the likes of me the honor of a news feed from your obviously magnificant system"

Never bash a system administrator.

Sometimes it helps to speak of any experience (good only) of setting up
and using uucp. This will make them feel better that you won't be wasting
thier time too often.


> Also, does the amiga
>    "call" the other system to get it's data, or does the other system call
>    the amia and download it, or both?

both or either. Usually you will call the site and pay the bill.


> If the other system calls me, are
>    there sites willing to provide this service (for free or pennies)
>    if the call isn't local?

Site dependant. Take what you can get.


> And finally; does it make a difference
>    if I'm looking for a mail site or a news feed? In other words,
>    is it easier to get someone to agree to be a news feed than to also
>    forward mail or does it make no difference?
    
News feeds are far more bandwidth consuming than mail (unless you mail
news articles to yourself :-). A mail link is most often easier to get
than a news feed. Try asking for mail, prove your competence and then beg
and plead gracefully for a news feed...

john    
4208.16OKMCDONL::BARRETTThis is my brain on Notes.Tue Oct 30 1990 22:4717
    Re: -1
    
    Thanks -- it appears that phone calls produce MUCH better results
    that email. It appears that I'll be able to get a feed.
    
    I'm going through all the documentation, but I'd like to ask a few
    more question:
    
    Do I simply PICK the node name I want for my system, or is there
    a more official method to this? What about duplicates?
    
    How does one go about getting themself in the appropriate
    comp.mail.maps file?
    
    How many of us DEC Amiga users are using UUCP?
    
    Keith (who is just starting to see a light)
4208.1711SRUS::MARKWaltzing with BearsWed Oct 31 1990 03:4117
	Yes, I've found phone calls to work much better, as well.

	To choose a name, you want a name that's less than eight characters.
It needs to be unique within the domain you belong to, which is probably the
.UUCP domain in your case.  The quickest way to test this is to have someone
who builds full paths from the map entries search their paths file for you, to
see if there are any nodes that have the name you'd like.  If so, try again, 
otherwise, you're all set.

	When you've got a name and a feed worked out, make a map entry for
your site.  You should have a sample entry from which to work.  If not, I
could post the format.  Then, send it to uucpmap@rutgers.edu, and it will
eventually show up in the map for your state.

Mark
me@stile.stonemarche.org    or   ...uunet!stile!me

4208.18Other stuff to try...FROCKY::BALZERChristian Balzer DTN:785-1029Wed Oct 31 1990 07:2924
    Re: UUCP
    
    I'm just uploading UUCP_Plus1.LZH and UUCP_Plus2.LZH as well as the
    latest release of BRNews to TAPE""::USER2:[UPLOAD].
    
    The AmigaUUCP Plus Package is based on Matt Dillons V1.06D and features
    a CNews port plus pathalias support for sendmail. It was written by
    Ingo Feulner, a fellow german Amiga developer. However beware of the
    sparse & german documentation... I've currently no time to translate
    this, so you're on your own here.
    
    If your host belongs to a Domain other than .UUCP, I would highly
    recommend you to ask the admin if you might join this domain. As stated
    in .17 your chances of finding a name for your system that you can
    relate to are much higher. ;-)
    
    Don't hesitate to ask here, time permitting I'll try to answer (I've
    been through all of this, including registering our own domain).
    
    <CB>   
    
    Domain address      : CB@brewhq.swb.de		
    Prefered from the US: ...!cbmvax!cbmger!brewas!CB
                             
4208.19DICKNS::MACDONALDVAXELN - Realtime Software PubsWed Oct 31 1990 12:022
    RE: .16  I use it on my Amiga    ... virgin!ubbs-nh!wa1omm!paul
    
4208.20WJG::GUINEAUWed Oct 31 1990 14:117
I used to use uucp. Haven't gotten it set back up yet. 

I was ryn!wjg-ami!guineau  and wanted to make my Ultrix machine at work
my dial up site (sdteng!wjg-ami!guineau) but we've moved since and it's 
now a toll call :-(

john
4208.21Pathname for Fish disks?DWOMV2::CAMPBELLDelaware AmiganThu Nov 01 1990 12:436
    
    Anyone know a pathname to find fish disks?  I'm looking for
    FF375 and FF378.
    
    Thankx,
    Dennis
4208.22HPSCAD::GATULISFrank Gatulis 297-6770Thu Nov 01 1990 16:118
    
    May be wrong but I don't think they're on line yet.
    
    If they were, I'd expect to find them in:
    
    TAPE::USER2:[AMIGA.FISH.Z350]FF37x.LZH
    
    
4208.23BOMBE::MOOREAmiga: Real computing on a PC budgetThu Nov 01 1990 19:072
    I think he's looking for an FTP path.  But they may not be online there
    yet either...
4208.24Fish found!!DWOMV2::CAMPBELLDelaware AmiganWed Nov 14 1990 05:58396
    
    Re: .21
    
    From the list in .9, I eventually got the following reply from a DIR
    mail request.
    
    
From:	26874::"BITFTP1@pucc.PRINCETON.EDU" "Princeton BITNET FTP Server" 13-NOV-1990 19:48:11.92
To:	dwomv2::campbell 
CC:	
Subj:	BITFTP REPLY 

 
19:33:52 > FTP ux1.cso.uiuc.edu UUENCODE
19:33:52 > USER anonymous dwomv2
19:33:52 >> OPEN UX1.CSO.UIUC.EDU
19:33:54 <<< 220 ux1.cso.uiuc.edu FTP server ($Header: ftpd.c 2.5 89/
             12/15 $) ready.
19:33:54 >> USER anonymous campbell@dwomv2.enet.dec.com
19:33:57 >>> USER anonymous
19:33:57 <<< 331 Guest login ok, send ident as password.
19:33:57 >>> PASS ********
19:33:57 <<< 230 Guest login ok, access restrictions apply.
 
19:33:58 > CD amiga/fish
19:33:58 >> CD amiga/fish
19:33:58 >>> CWD amiga/fish
19:33:59 <<< 250 CWD command successful.
 
19:33:59 > DIR
19:33:59 >> DIR ( DISK
19:34:07 >>> PORT 128,112,129,99,103,240
19:34:07 <<< 200 PORT command successful.
19:34:07 >>> LIST
19:34:08 <<< 150 Opening data connection for /bin/ls (ascii mode) (0
             bytes).
19:34:09 <<< 226 Transfer complete.
total 342
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff056
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff058
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff059
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff060
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff061
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff062
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff063
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff064
drwxrwxr-x  2 root     amiga         512 Mar 23  1989 ff065
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff066
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff067
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff068
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff069
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff070
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff071
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff072
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff073
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff074
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff075
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff076
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff077
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff078
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff079
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff081
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff082
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff083
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff084
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff085
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff086
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff087
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff089
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff090
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff091
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff092
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff093
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff094
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff095
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff096
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff097
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff098
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff099
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff100
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff101
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff102
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff103
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff104
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff105
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff106
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff107
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff108
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff109
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff110
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff111
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff112
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff113
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff114
drwxrwxr-x  2 root     amiga         512 Oct 27  1989 ff115
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff116
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff117
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff118
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff119
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff120
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff121
drwxrwxr-x  2 root     amiga         512 Dec  7  1988 ff122
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff123
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff124
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff125
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff126
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff127
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff128
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff129
drwxrwxr-x  2 root     amiga         512 Feb 24  1989 ff130
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff131
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff132
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff133
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff134
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff135
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff136
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff137
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff138
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff139
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff140
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff141
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff142
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff143
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff144
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff145
drwxrwxr-x  2 root     amiga         512 Sep  2  1988 ff146
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff147
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff148
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff149
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff150
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff151
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff152
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff153
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff154
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff155
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff156
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff157
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff158
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff159
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff160
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff161
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff162
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff163
drwxrwxr-x  2 root     amiga         512 Jun 10 18:40 ff164
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff165
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff166
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff167
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff168
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff169
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff170
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff171
drwxrwxr-x  2 root     amiga         512 Jan 27  1989 ff172
drwxrwxr-x  2 root     amiga         512 Jun 10 16:41 ff173
drwxrwxr-x  2 root     amiga         512 Feb 24  1989 ff174
drwxrwxr-x  2 root     amiga         512 Feb 24  1989 ff175
drwxrwxr-x  2 root     amiga         512 Feb 24  1989 ff176
drwxrwxr-x  2 root     amiga         512 Feb 24  1989 ff177
drwxrwxr-x  2 root     amiga         512 Feb 24  1989 ff178
drwxrwxr-x  2 root     amiga         512 Mar 23  1989 ff179
drwxrwxr-x  2 root     amiga         512 Mar 23  1989 ff180
drwxrwxr-x  2 root     amiga         512 Mar 23  1989 ff181
drwxrwxr-x  2 root     amiga         512 Mar 23  1989 ff182
drwxrwxr-x  2 root     amiga         512 Mar 23  1989 ff183
drwxrwxr-x  2 root     amiga         512 Mar 23  1989 ff184
drwxrwxr-x  2 root     amiga         512 Mar 23  1989 ff185
drwxrwxr-x  2 root     amiga         512 Mar 23  1989 ff186
drwxrwxr-x  2 root     amiga         512 Mar 23  1989 ff187
drwxrwxr-x  2 root     amiga         512 Mar 23  1989 ff188
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff189
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff190
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff191
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff192
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff193
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff194
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff195
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff196
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff197
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff198
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff199
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff200
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff201
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff202
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff203
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff204
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff205
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff206
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff207
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff208
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff209
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff210
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff211
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff212
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff213
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff214
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff215
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff216
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff217
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff218
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff219
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff220
drwxrwxr-x  2 hummel   amiga         512 Jun 10 16:43 ff221
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff222
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff223
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff224
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff225
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff226
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff227
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff228
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff229
drwxrwxr-x  2 hummel   amiga         512 Jun 10 16:48 ff230
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff231
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff232
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff233
drwxrwxr-x  2 hummel   amiga         512 Jul  6 13:53 ff234
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff235
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff236
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff237
drwxrwxr-x  2 hummel   amiga         512 Jun 10 16:49 ff238
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff239
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff240
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff241
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff242
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff243
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff244
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff245
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff246
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff247
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff248
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff249
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff250
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff251
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff252
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff253
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff254
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff255
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff256
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff257
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff258
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff259
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff260
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff261
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff262
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff263
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff264
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff265
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff266
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff267
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff268
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff269
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff270
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff271
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff272
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff273
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff274
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff275
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff276
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff277
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff278
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff279
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff280
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff281
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff282
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff283
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff284
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff285
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff286
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff287
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff288
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff289
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff290
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff291
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff292
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff293
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff294
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff295
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff296
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff297
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff298
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff299
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff300
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff301
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff302
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff303
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff304
drwxrwxr-x  2 hummel   amiga         512 Jun 10 16:50 ff305
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff306
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff307
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff308
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff309
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff310
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff311
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff312
drwxrwxr-x  2 hummel   amiga         512 May 21 22:14 ff313
drwxrwxr-x  2 hummel   amiga         512 May 24 01:05 ff314
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff315
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff316
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff317
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff318
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff319
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff320
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff321
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff322
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff323
drwxrwxr-x  2 hummel   amiga         512 Jun 10 16:52 ff324
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff325
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff326
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff327
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff328
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff329
drwxrwxr-x  2 hummel   amiga         512 Aug  7 13:08 ff330
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff331
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff332
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff333
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff334
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff335
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff336
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff337
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff338
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff339
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff340
drwxrwxr-x  2 hummel   amiga         512 May 24 01:07 ff341
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff342
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff343
drwxrwxr-x  2 hummel   amiga         512 May 24 05:48 ff344
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff345
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff346
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff347
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff348
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff349
drwxrwxr-x  2 hummel   amiga         512 May  6  1990 ff350
drwxrwxr-x  2 hummel   amiga         512 Sep 19 16:58 ff351
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:00 ff352
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:00 ff353
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:00 ff354
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:00 ff355
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:00 ff356
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:00 ff357
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:00 ff358
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:01 ff359
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:01 ff360
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:01 ff361
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:01 ff362
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:01 ff363
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:01 ff364
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:01 ff365
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:01 ff366
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:01 ff367
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:01 ff368
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:02 ff369
drwxrwxr-x  2 hummel   amiga         512 Sep 19 17:02 ff370
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:16 ff371
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:16 ff372
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:17 ff373
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:17 ff374
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:17 ff375
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:17 ff376
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:18 ff377
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:18 ff378
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:18 ff379
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:18 ff380
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:19 ff381
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:19 ff382
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:20 ff383
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:20 ff384
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:20 ff385
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:21 ff386
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:21 ff387
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:21 ff388
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:22 ff389
drwxrwxr-x  2 schwager amiga         512 Nov  7 15:22 ff390
drwxrwxr-x  2 schwager amiga         512 Nov 11 21:47 ff391
drwxrwxr-x  2 schwager amiga         512 Nov 11 21:48 ff392
drwxrwxr-x  2 schwager amiga         512 Nov 11 21:48 ff393
drwxrwxr-x  2 schwager amiga         512 Nov 11 21:48 ff394
drwxrwxr-x  2 schwager amiga         512 Nov 11 21:48 ff395
drwxrwxr-x  2 schwager amiga         512 Nov 11 21:48 ff396
drwxrwxr-x  2 schwager amiga         512 Nov 11 21:49 ff397
drwxrwxr-x  2 schwager amiga         512 Nov 11 21:49 ff398
drwxrwxr-x  2 schwager amiga         512 Nov 11 21:49 ff399
drwxrwxr-x  2 schwager amiga         512 Nov 11 21:49 ff400
 
19:34:09 > QUIT
19:34:10 >> CLOSE
19:34:11 >>> QUIT
19:34:11 <<< 221 Goodbye.
 
% ====== Internet headers and postmarks (see DECWRL::GATEWAY.DOC) ======
Received: by easynet.crl.dec.com; id AA09390; Tue, 13 Nov 90 19:44:50 -0500
Received: by crl.dec.com; id AA29158; Tue, 13 Nov 90 16:35:23 -0800
Message-Id: <9011140035.AA29158@crl.dec.com>
Received: from PUCC.PRINCETON.EDU by pucc.PRINCETON.EDU (IBM VM SMTP R1.2.2MX) with BSMTP id 0203; Tue, 13 Nov 90 19:34:16 EST
Received: by PUCC (Mailer R2.08A) id 8771; Tue, 13 Nov 90 19:34:25 EST
Date:     Tue, 13 Nov 1990 19:34:12 EST
From: Princeton BITNET FTP Server <BITFTP1@pucc.PRINCETON.EDU>
To: dwomv2::campbell
Subject:  BITFTP REPLY
4208.25FTP helpCSCOAC::KENDRIX_JWed Nov 14 1990 19:048
    re: .24
     
    Would someone be so kind as show me a sample 'ftp message' for ftping
    one of the listed fish disks?  I seem to be running afoul somehow or
    another.  
     
    JK
    
4208.26ELMST::MCAFEESteve McAfeeWed Nov 14 1990 19:3712
Take note that in .24 ff*** are directories.  You need to get a
listing of what is in each before you know what file to request.
One you know the file name (e.g. xyz.lzh)...

To: decwrl::"bitftp@pucc.bitnet"
Subject: ftp
--------
FTP ux1.cso.uiuc.edu UUENCODE
USER anonymous
CD /amiga/fish/ff400
GET xyz.lzh
QUIT
4208.27NMAIL is even better.STAR::ROBINSONWed Nov 14 1990 20:226
And using NMAIL is one nit better. Otherwise you may not know if the messege
died before leaving DEC. And NMAIL will keep trying for you.

nm%DECWRL::"bitftp@pucc.bitnet"

Dave
4208.28Only five!SNOC01::GADSBYCHRISChris GADSBY @SNO &lt;IPS SG&gt;Wed Nov 14 1990 22:533
    And your limited to five GETs per request.
    
    Chris
4208.29One tale of access...DWOMV2::CAMPBELLDelaware AmiganThu Nov 15 1990 03:14142
    One novice's experience:
    
    !!! First mail message sent to DECWRL::"bitftp@pucc.princeton.edu"
FTP ux1.cso.uiuc.edu UUENCODE
USER anonymous dwomv2
CD amiga/fish/ff378
DIR
QUIT

!!! FTP reply to above !!!
From:	26874::"BITFTP2@pucc.PRINCETON.EDU" "Princeton BITNET FTP Server" 14-NOV-1990 02:15:55.59
To:	dwomv2::campbell 
CC:	
Subj:	BITFTP REPLY 

 
01:55:27 > FTP ux1.cso.uiuc.edu UUENCODE
01:55:27 > USER anonymous dwomv2
01:55:27 >> OPEN UX1.CSO.UIUC.EDU
01:55:28 <<< 220 ux1.cso.uiuc.edu FTP server ($Header: ftpd.c 2.5 89/
             12/15 $) ready.
01:55:29 >> USER anonymous campbell@dwomv2.enet.dec.com
01:55:29 >>> USER anonymous
01:55:30 <<< 331 Guest login ok, send ident as password.
01:55:30 >>> PASS ********
01:55:30 <<< 230 Guest login ok, access restrictions apply.
 
01:55:31 > CD amiga/fish/ff378
01:55:31 >> CD amiga/fish/ff378
01:55:31 >>> CWD amiga/fish/ff378
01:55:31 <<< 250 CWD command successful.
 
01:55:32 > DIR
01:55:32 >> DIR ( DISK
01:55:33 >>> PORT 128,112,129,99,116,198
01:55:33 <<< 200 PORT command successful.
01:55:33 >>> LIST
01:55:34 <<< 150 Opening data connection for /bin/ls (ascii mode) (0
             bytes).
01:55:34 <<< 226 Transfer complete.
total 405
-rw-rw-r--  1 schwager amiga       86412 Nov  7 15:18 ANSIMaster.zoo
-rw-rw-r--  1 schwager amiga       11531 Nov  7 15:18 Adapt.zoo
-rw-rw-r--  1 schwager amiga        8658 Nov  7 15:18 DevRen.zoo
-rw-rw-r--  1 schwager amiga        6869 Nov  7 15:18 JoyLib.zoo
-rw-rw-r--  1 schwager amiga       79592 Nov  7 15:18 MachIII.zoo
-rw-rw-r--  1 schwager amiga       60738 Nov  7 15:18 MuchMore.zoo
-rw-rw-r--  1 schwager amiga       52276 Nov  7 15:18 MuchMorePoPa.zoo
-rw-rw-r--  1 schwager amiga        5479 Nov  7 15:18 Observer.zoo
-rw-rw-r--  1 schwager amiga       64955 Nov  7 15:18 TheGuru.zoo
-rw-rw-r--  1 schwager amiga       16617 Nov  7 15:18 c.zoo
-rw-rw-r--  1 schwager amiga       14665 Nov  7 15:18 ff378.zoo
 
01:55:35 > QUIT
01:55:35 >> CLOSE
01:55:35 >>> QUIT
01:55:36 <<< 221 Goodbye.
 
% ====== Internet headers and postmarks (see DECWRL::GATEWAY.DOC) ======
Received: by easynet.crl.dec.com; id AA15814; Wed, 14 Nov 90 02:14:06 -0500
Received: by crl.dec.com; id AA07873; Tue, 13 Nov 90 23:06:46 -0800
Message-Id: <9011140706.AA07873@crl.dec.com>
Received: from PUCC.PRINCETON.EDU by pucc.PRINCETON.EDU (IBM VM SMTP R1.2.2MX) with BSMTP id 2912; Wed, 14 Nov 90 02:05:40 EST
Received: by PUCC (Mailer R2.08A) id 4702; Wed, 14 Nov 90 01:55:50 EST
Date:     Wed, 14 Nov 1990 01:55:36 EST
From: Princeton BITNET FTP Server <BITFTP2@pucc.PRINCETON.EDU>
To: dwomv2::campbell


!!! then send a GET (Note, this example from a different directory, sorry)!!!
!!! Note that I carefully follow case in file name specification !!!
FTP ux1.cso.uiuc.edu UUENCODE
USER anonymous dwomv2
CD amiga/fish/ff375
GET TextPlus.zoo
QUIT

!!! and the FTP reply (plus five mail messages with the file, see 4274.4)!!!
!!! Extract mail with file segments to file1.uue, file2.uue...,filen.uue, !!!
!!! then edit to remove extraneous stuff.  Next, take *.uue and !!!
!!! append to one file (I did a anal/rms/fdl file1.uue to get a file1.fdl !!!
!!! and then did a convert/fdl=file1.fdl of my target file for the appends !!!
!!! to get the file characteristics to match), and then use UUDECODE on !!!
!!! finished file... result, one *.zoo file in following format:   !!!
!!!      Record format:      Variable length, maximum 512 bytes    !!!
!!! After using CVTARC u *.zoo *.slf to get a StreamLF format file, !!!
!!! you're ready to do a ZOO l *.slf to see what's in your *.zoo file !!!
!!! A CVTARC v *.slf *.ker will give you a KERMIT format file.     !!!


Subject:  BITFTP REPLY
From:	26874::"BITFTP4@pucc.PRINCETON.EDU" "Princeton BITNET FTP Server" 14-NOV-1990 00:16:59.39
To:	dwomv2::campbell 
CC:	
Subj:	BITFTP REPLY 

 
00:00:38 > FTP ux1.cso.uiuc.edu UUENCODE
00:00:38 > USER anonymous dwomv2
00:00:39 >> OPEN UX1.CSO.UIUC.EDU
00:00:40 <<< 220 ux1.cso.uiuc.edu FTP server ($Header: ftpd.c 2.5 89/
             12/15 $) ready.
00:00:40 >> USER anonymous campbell@dwomv2.enet.dec.com
00:00:41 >>> USER anonymous
00:00:41 <<< 331 Guest login ok, send ident as password.
00:00:41 >>> PASS ********
00:00:42 <<< 230 Guest login ok, access restrictions apply.
 
00:00:42 > CD amiga/fish/ff375
00:00:42 >> CD amiga/fish/ff375
00:00:43 >>> CWD amiga/fish/ff375
00:00:43 <<< 250 CWD command successful.
 
00:00:43 > GET TextPlus.zoo
00:00:44 >>>> Representation forced to IMAGE.
00:00:44 >>>> Representation forced to IMAGE.
00:00:44 >> GET TextPlus.zoo TEXTPLUS.ZOO.D ( REPLACE
00:00:52 >>> PORT 128,112,129,99,112,248
00:00:52 <<< 200 PORT command successful.
00:00:53 >>> RETR TextPlus.zoo
00:00:53 <<< 150 Opening data connection for TextPlus.zoo (binary mod
             e) (139249 bytes).
00:00:53 <<< 226 Transfer complete.
00:01:04 >>>> File "TextPlus.zoo" sent to you as "TEXTPLUS ZOO".
 
00:01:05 > QUIT
00:01:05 >> CLOSE
00:01:06 >>> QUIT
00:01:06 <<< 221 Goodbye.
 
% ====== Internet headers and postmarks (see DECWRL::GATEWAY.DOC) ======
Received: by easynet.crl.dec.com; id AA14284; Wed, 14 Nov 90 00:14:40 -0500
Received: by crl.dec.com; id AA05756; Tue, 13 Nov 90 21:03:22 -0800
Message-Id: <9011140503.AA05756@crl.dec.com>
Received: from PUCC.PRINCETON.EDU by pucc.PRINCETON.EDU (IBM VM SMTP R1.2.2MX) with BSMTP id 8939; Wed, 14 Nov 90 00:01:44 EST
Received: by PUCC (Mailer R2.08A) id 5522; Wed, 14 Nov 90 00:01:26 EST
Date:     Wed, 14 Nov 1990 00:01:07 EST
From: Princeton BITNET FTP Server <BITFTP4@pucc.PRINCETON.EDU>
To: dwomv2::campbell
Subject:  BITFTP REPLY
    
4208.30On a related issue - how about Fidonet??MEO78B::MANDERSONPhotographers do it in darkroomsTue Nov 20 1990 07:4123
Hi,

Has anyone sucessfully sent a message from the DEC network to
a Fidonet node?

In the genalogy notes file (note 78.24) was a writeup on sending to nodes
off the DEC network - which I tried but DECWRL:: came back with server
unknown (I was also trying to get some info off the USENET about genealogy
and got the same reply some maybe there is a DECWRL problem?).

According to the note, mail to me at a local Fidonet node (number
3:670/301) should be:

    DECWRL::Kevin Manderson@f301.n670.z3.fidonet.org


Any ideas,

regards
k


    
4208.31BOMBE::MOOREAmiga: Real computing on a PC budgetTue Nov 20 1990 07:544
    Try it as DECWRL::"Kevin Manderson@f301.n670.z3.fidonet.org"
                      ^                                        ^
                      |                                        |
                      +--------- quotes are required ----------+
4208.32Thanks, haven't had an error from DECWRL yetMEO78B::MANDERSONPhotographers do it in darkroomsTue Nov 20 1990 10:371
    
4208.33help with ftped filesSHARE::DOYLEWed Dec 04 1991 12:3514
    I've been trying to get the Amos Amoner disks from ftp, but the files
    give the following error after uudecodeing them...
    "no end line"
     Am I doing something wrong? I check the file and the end is as
    follows:
    
    '
    end 
    
     Do I need a newer version of uudecode?
    
    							Thanks..
    								Ed
    
4208.34Check the ends of the uuencoded filesDECWET::DAVISMark W. Davis 206.865.8749Wed Dec 04 1991 13:348
    Make sure that the files are 1) joined in the correct order, 2) the
    'header' (footer) at the end of the uuencoded file(s) are edited out. 
    When I first started ftp'ing files from Internet I always forgot to
    edit the last 10 or so lines from the uuencoded files, 3) make sure
    there is an end line in the last uuencoded file.
    
    mark
    
4208.35Problem solvedSHARE::DOYLEWed Dec 04 1991 15:085
    Ah!! I missed the footers!
    
    							Thanks 
    								Ed