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?

Christopher Davis (ckd@EFF.ORG)
Thu, 16 Jan 1992 15:43:31 -0500


Date:         Thu, 16 Jan 1992 15:43:31 -0500
From:         Christopher Davis <ckd@EFF.ORG>
Subject:      Re: How hard is ftp?
In-Reply-To:  diderot@HITL.WASHINGTON.EDU's message of 16 Jan 92 18:24:05 GM

[good ftp hints & tips deleted]
 
 TE> 2.  When you "ftp"...make sure you have some system that will
 TE> help you remember where you've been.  What I do...is that
 TE> I always start my "ftp" from a directory I create that is
 TE> a customization of the ip address.  I also make a little
 TE> address file with the ip address and info that I keep in that
 TE> directory.  For example:
 
 TE> EFF is my directory for the eff.org.  I always ftp to eff.org
 TE> from that directory.  I have an eff.address file, etc.
 
Please note that IP addresses and machines do change.  One spreading
convention is the use of "ftp.dom.ain" as an alias for the main ftp
machine.  This allows the machines to be moved, replaced, and so forth
without affecting people who are using the alias.
 
Right now, ftp.eff.org is merely an alias for eff.org (192.88.144.3).
This will be changing soon; we have a few new machines coming in soon,
donated by Sun Microsystems.  At that point, we'll move ftp to one of
the new machines (we don't even know what we'll name it yet).
'ftp.eff.org' will still work.  192.88.144.3 will definitely *not* be
the right machine, though.
 
 TE> 3.  Another good idea is to execute the "bin" command before you
 TE> transfer files.
 
Some ftp clients support a "default" entry in the .netrc file, to allow
automatic settings changes.
 
Here's my .netrc:
 
----tear here----
default
macdef init
binary
hash
prompt
 
login anonymous password ckd@eff.org
----tear here----
 
The 'default' indicates that this entry will be used by default.  (Since
I have no other entries, that means any time I don't use 'ftp -n'.)  The
'macdef init' defines a macro 'init' which is automatically run when
connecting.  That sets binary mode, turns on hash printing, and turns
off prompting for 'mget' commands.  the default login and password for
anonymous ftp are also given.
 
Usually, .netrc will not be used unless it is inaccessible to group &
other.  Make sure to 'chmod 600 .netrc' and *NEVER* keep real passwords
in it, only 'anonymous' passwords like I did above.
 
 TE> Since that basic prompts don't give you a hint as to what directory
 TE> you're in...don't panic if you get a message that says that the
 TE> file you are looking for doesn't exist.  Always make sure you're
 TE> at the right level.
 
 TE> "ls" will list what's in that directory...ususually in a stream of
 TE> files.  "ls -CF" will make that listing go by screen.
 
Another useful command is 'pwd' which Prints your Working Directory,
allowing you to get an idea of where you are.  (This command is also
available in the "regular" Unix shells, but in this case, tells you the
working directory at the other end of the ftp, not your local
directory.)
 
Christopher Davis <ckd@eff.org>   |  OBLIGATORY SEMI-POLITICAL COMMENT:
System Manager & Postmaster       | "[The CIX] might be a conspiracy of
Electronic Frontier Foundation    |  lizard-like aliens here to steal our
+1 617 864 0665    NIC: [CKD1]    |  water, but I doubt it."


[CNI Home Page]