Association of Research Libraries; <http://www.arl.org/>EDUCAUSE; <http://www.educause.edu/>
   
CNI - Coalition for Networked Information; <http://www.cni.org/>
 
About CNI
Task Force Meetings
Conferences
Presentations and Publications
Projects
CNI Collaborations
Site Map
Google

www.cni.org
the web

Information about CNI RSS news feed.

 
cni-directories: Re: How hard is ftp?

Re: How hard is ftp?

toni (diderot@HITL.WASHINGTON.EDU)
Thu, 16 Jan 1992 10:24:05 PST


Date:         Thu, 16 Jan 1992 10:24:05 PST
From:         toni <diderot@HITL.WASHINGTON.EDU>
Subject:      Re: How hard is ftp?

There are a number of conventions that you should know about to
successfully "ftp".
 
1.  ReadMe, README, READ_ME files...take a look at them first.
They usually contain information that will give you a
hint to what's in the database.
 
You don't have to "get" that file.  Just type :
 
get README |less
 
and the file will be printed out, but not transferred.
 
Sometimes, if the file is comprehensive...I do get the
readme file.  But, always rename it with an indication to
where it comes from ...so its not generic.
 
2.  When you "ftp"...make sure you have some system that will
help you remember where you've been.  What I do...is that
I always start my "ftp" from a directory I create that is
a customization of the ip address.  I also make a little
address file with the ip address and info that I keep in that
directory.  For example:
 
EFF is my directory for the eff.org.  I always ftp to eff.org
from that directory.  I have an eff.address file, etc.
 
3.  Another good idea is to execute the "bin" command before you
transfer files.
 
4.  Look for INDEX files in directories...to give you information
about what is in that directory.
 
5.  directory names are ususally self-explanatory.  There are some
that have become universal...like "pubs".
 
Since that basic prompts don't give you a hint as to what directory
you're in...don't panic if you get a message that says that the
file you are looking for doesn't exist.  Always make sure you're
at the right level.
 
"ls" will list what's in that directory...ususually in a stream of
files.  "ls -CF" will make that listing go by screen.
 
***"Knowledge is the true organ of sight, not the eyes."--Panchatantra***
***Toni Emerson                            diderot@hitl.washington.edu***
***Human Interface Technology Lab                                     ***
***University of Washington, FJ-15                                    ***
***Seattle, WA  98195                      ******************************


[CNI Home Page]