Also, if you want to receive any new articles which are distributed
automatically (which may take a while to find their way into the archives
at ftp.css.itd.umich.edu, but which will be filed immediately at TAMVM1),
just send a message to LISTSERV@TAMVM1.TAMU.EDU containing the text:
subscribe nat-1492 Your Name Here
(substituting your own name - *not* your email address). You'll be sent
confirmation of your subscription automatically, and instructions on how
to unsubscribe from the list.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
In <1992Oct5.063709.12600@gnosys.svle.ma.us> I wrote:
> ...
> To obtain articles via ftp, if your system supports the command, do the
> following:
> ftp ftp.css.itd.umich.edu
> or
> ftp 141.211.182.11
> (enter "anonymous" at the login prompt, and
> enter your own user-ID at the password prompt.)
> cd /poli/nativenet.d/1492.d
>
> Now you will be able to go to individual directories containing the
> actual files, as indicated by the following list...
What I forgot to say is that to actually retrieve files, you use the "get"
command, after going to the directory containing the files you want, by
means of the "cd" ("change directory") command, which works just like its
UNIX counterpart:
cd /poli/nativenet.d/1492.d/essay
get peopleshistory
cd ../event/current (".." means - go up a dir level)
get hgw-intro
get denver-action
cd ../../misc
get 1492-stories
cd ../myths
get wfp-intro
get 10-91
get 11-91
get 12-91
(etc.)
As an alternative, you can retrieve a number of files in a given directory
using the "mget" command, which accepts the syntax of UNIX "wildcard"
pattern-matching characters:
cd myths
mget *
or
cd printed
mget 500yrs-*
When using "mget" you'll be prompted to confirm retrieval of each file that
matches the wildcard pattern.
Remember, if you can deal with compressed files, which will transfer at about
twice the speed, you can get them from site redspread.css.itd.umich.edu under
an identical directory structure (/poli/nativenet.d/1492.d) as what's found
at the other site.
If you lack the ability to use FTP, you can retrieve materials either from
the LISTSERV archive for the NAT-1492 mailing list at site TAMVM1, using
the instructions indicated in my previous message - or you can use the "ftp-
mail" service (using the address "ftpmail@decwrl.dec.com" or "ftpmail@pa.dec
.com") described below:
How to get your ftp documents from the site via email
DEC offers a public service of sending ftp documents through
the mail. It takes about a day to process, and is
unforgiving of errors, but it definitely works, and can
easily be used by people without shell access or proper
types of connectivity.
If you want the full instruction sheet:
mail ftpmail@pa.dec.com (or "elm" or "pine" or "mush" or
subject: <return> whatever your mail system is called
help<ret> locally)
quit<ret>
<end message>
To actually get a document from the ftpmail site:
mail ftpmail@pa.dec.com
subject: <any--server ignores subject>
reply <your@address.here>
connect ftp.css.itd.umich.edu<ret> <-- assumes anonymous
ascii<ret>
chdir /poli/nativenet.d/1492.d<ret>
get <filename><ret> <-- you can request up to ten files
quit<ret>
<end message>
To get a current index of articles in the 1492 archive:
mail ftpmail@pa.dec.com
subject: <any>
reply <your@address.here>
connect ftp.css.itd.umich.edu<ret>
ascii<ret>
chdir /poli/nativenet.d/1492.d
get Index<ret>
quit<ret>
<end message>
That's all. You will get three messages back--one will be a
confirmation of your order. The second will be the
document[s] you requested. The third will be a transcript
of your session. The server will automatically divide all
documents into 50k chunks. If your mail system needs
smaller chunks, obtain the "help" instructions to learn more
commands. NOTE: All documents in /poli are ASCII text.
If you have problems with the service, contact:
ftpmail-request@pa.dec.com, and DO NOT send mail to the DEC postmaster.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Here is the full help file from the ftpmail site:
>>> $Id: help-text,v 1.4 1992/09/29 01:34:33 vixie Exp $
>>>
>>> commands are:
reply <MAILADDR> set reply addr, since headers are usually wrong
connect [HOST [USER [PASS]]] defaults to gatekeeper.dec.com, anonymous
ascii files grabbed are printable ascii
binary files grabbed are compressed or tar or both
chdir PLACE "get" and "ls" commands are relative to PLACE
(only one CHDIR per ftpmail session,
and it executes before any LS/DIR/GETs)
compress compress binaries using Lempel-Ziv encoding
compact compress binaries using Huffman encoding
uuencode binary files will be mailed in uuencode format
btoa binary files will be mailed in btoa format
chunksize SIZE split files into SIZE-byte chunks (def: 64000)
ls (or dir) PLACE short (long) directory listing
get FILE get a file and have it mailed to you
(max 10 GET's per ftpmail session)
quit terminate script, ignore rest of mail message
(use if you have a .signature or
are a VMSMAIL user)
>>> notes:
-> you should send complaints to the ftpmail-admin address. our
postmaster does not handle ftpmail problems and you can save her
the trouble of forwarding your complaints by just mailing them to
the right address. the "ftpmail-request" address is gone; don't
use it.
-> the "Subject:" of your request will be contained in the "Subject:"
of all of ftpmail's responses to you regarding that request. You
can therefore use it to "tag" different requests if you have more
than one outstanding at any given time.
-> you must give a "connect" command, default host is
gatekeeper.dec.com, default user is anonymous, default
password is your mail address.
-> binary files will not be compressed unless 'compress' or 'compact'
command is given; use this if at all possible, it helps a lot.
note that many files are already compressed. if you use any of
the binary-file qualifiers (compress, compact, uuencode, btoa)
without setting 'binary' first, your session will abort in error.
-> binary files will always be formatted into printable ASCII
with "btoa" or "uuencode" (default is "btoa"). if you don't
use the "binary" command, ftpmail will cheerfully try to mail
you the binary data, which will absolutely, positively fail.
-> all retrieved files will be split into chunks and mailed. the
size of the chunk is 64000 characters unless you change it with
the "chunksize" command. CompuServe users will need to set this
to 49000. there is no way to set it higher than 100000, so please
don't ask.
-> if you ask for more than 10 files in a session, you will receive
an error message and your entire request will be rejected.
-> VMS/DOS/Mac versions of uudecode, atob, compress and compact
are available, ask your LOCAL wizard about them if you can't
locate them (but try gatekeeper.dec.com in /archive/pub/VMS
if you're still using a VMS system.)
-> several mail unsplitters are hiding on gatekeeper.dec.com in
/pub/mail/ua/misc/unsplit. there is one in c, one in perl,
and one in VMS DCL.
-> there is no way to request only certain parts of a file and we
do not plan to add one in the near future, so please don't ask.
-> there is no way to delete things from the queue or to find out
the status of things in the queue, and we do not plan to add
either feature in the near future, so please don't ask.
>>> examples:
-> connect to gatekeeper.dec.com and get a root directory listing:
connect
ls
quit
-> connect to gatekeeper.dec.com and get the README.ftp file:
connect
get README.ftp
quit
-> connect to gatekeeper.dec.com and get the gnuemacs sources:
connect
binary
uuencode
chdir /pub/GNU
get emacs-18.58.tar.Z
quit
-> connect to ftp.uu.net as anonymous and get a root directory list:
connect ftp.uu.net
binary
chdir /index/master
get by-name.Z
quit
-- Ftpmail Submission Transcript --
<<< help
>>> Help is on the way.
-- End Of Ftpmail Transcript --
--
Gary S. Trujillo gst@gnosys.svle.ma.us
Somerville, Massachusetts {wjh12,bu.edu,spdcc,ima,cdp}!gnosys!gst