jasonf@cetemp.Eng.Sun.COM (Jason Freund) (09/20/90)
I'm no expert on FTPing, but for those of you completely in the
dark, here's my interpretation of how to get started: (No flames, please)
If I you find anything grossly innaccurate and misleading, please post.
First see if your machine has the FTP command: TYPE "ftp". You should get
the prompt "ftp> " or something like that. TYPE "bye" to exit.
If you don't get the prompt, look for the path to the ftp command
with "whereis ftp". It should be in /usr/ucb/ftp.
If that worked, try "ftp"ing to another computer, preferably one with amiga
stuff on it, like a.cs.uiuc.edu (128.174.252.1).
"a.cs.uiuc.edu" is the name of a host computer like mine,
cetemp.Corp.sun.com.
128.174.252.1 is UNIX's node address for that computer.
TYPE "ftp 128.174.252.1" (it is better to use the #.#.#.# format
instead of a.b.c.d)
If that worked you should get something like "Connecting to ...."
If you connect, it should ask you for your user name.
TYPE "anonymous" (since you just want to visit and
download some stuff and you don't have an account there).
"anonymous" works on all public ftp sites.
Any password (except RETURN works in most cases). So TYPE in
anything for the password.
If you don't connect and you get "Host unreachable..." or something
then you need to ask your system administrator how to set
up ftp in your account. Sometimes schools or businesses will
have a special "gateway" for security purposes to restrict
ftp-ing in and out. In that case, you'd need to get an
account on their gateway machine to get access to the outside
world.
You should be logged into another machine.
Your shell now has a limited vocabulary like "ls", "cd",
and all of the really basic essentials.
Look around for a file you want.
To download it, you need to TYPE:
"hash" -- Makes "#" marks on screen so you can see how fast
download is going. Optional.
"binary" -- If the file you want to get is not pure ascii
text, you need to type "binary" to set some mark
to "I"
"get <filename>" -- puts that file in your current directory.
("put <filename>" "uploads" a file to your host
machine -- make sure you put it in the "incoming
directory).
Many files have a ".Z" or another extension. you need to type "sh -c <file>"
and "uudecode <file>" to unarchive and decompress most stuff.
If you unarchive something and find a "Makefile", just TYPE "make"
Here are some sample ftp sites with amiga stuff:
a.cs.uiuc.edu (128.174.252.1)
abcd20.larc.nasa.gov (Xanth)
ux1.cso.uiuc.edu
a.cs.uiuc.edu
mars.ee.msstate.edu
uafcseg.uark.edu
ftp.ecs.clarkston.edu
alfred.carleton.ca
pilot.njin.net (only has ftp list)
trantor.umd.edu
Jason Freund, Sun Microsystems, jasonf@cetemp.Corp.sun.com <== summer address
Deprtmnt of Computer Science, Univ California, Davis. freund@sakura.ucdavis.edu
Quantum Link: JasonF5, Compu$erve: 72007,244, 690 Erie Dr, Sunnyvale, CA 94087
-------------------------------------------------------------------------------
STOLEN QUOTES -- Please give the authors credit if you know who they are!
"To understand recursion, you need to understand recursion."
"Wow! Virtual memory! Now I'm gonna build me a REALLY big ram disk!"
"My other computer is a SUN3/50." "E. Pluribus UNIX" -- authors unkown frazier@oahu.cs.ucla.edu (Greg Frazier) (09/20/90)
In article <142740@sun.Eng.Sun.COM> jasonf@cetemp.Eng.Sun.COM (Jason Freund) writes: > If you connect, it should ask you for your user name. > TYPE "anonymous" (since you just want to visit and > download some stuff and you don't have an account there). > "anonymous" works on all public ftp sites. > Any password (except RETURN works in most cases). So TYPE in > anything for the password. Just a comment here - most sites want you to type in your <userID>@<site> for the password, i.e. login(frazier): anonymous password: frazier@cs.ucla.edu Of course, you will not be able to see the <userID>@<site> - but then, you knew that. -- "They thought to use and shame me but I win out by nature, because a true freak cannot be made. A true freak must be born." K. Dunn, _Geek_Love_ Greg Frazier frazier@CS.UCLA.EDU !{ucbvax,rutgers}!ucla-cs!frazier
jerry@truevision.com (Jerry Thompson) (09/20/90)
OK, for those of us without an Internet connection, how do we get files? -- Jerry Thompson | // checks ___________ | "I'm into S&M, "What I want to know is, have | \\ // and | | | | Sarcasm and you ever seen Claude Rains?" | \X/ balances /_\ | /_\ | Mass Sarcasm."
tadguy@abcfd01.larc.nasa.gov (Tad Guy) (09/21/90)
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.
GELSON%SBU.UFRGS.ANRS.BR@uicvm.uic.edu (Gelson Dias Santos) (09/21/90)
<jerry@truevision.com> writes: >OK, for those of us without an Internet connection, how do we get files? What network are you using? I am on BITNET, and to FTP files I use a gateway called BITFTP@PUCC.BITNET . Of couse, it's batch (I send a mail and wait for an answer) but it work! ================================================================================ ***** # Gelson Dias Santos # /\/\ ** # BITNET: GELSON@SBU.UFRGS.ANRS.BR # Please, don't look my / \-------\* # HOME: Av. Bento Goncalves 948/12 # grammar/spelling errors. ! 0 0 ! _ ! # Porto Alegre - RS CEP:90620 # I am learning english ! ! ^^ ! ( ! # Brazil # \_()_/ _( ) #============================================================= (__(____(_____) # Alguem ai fala portugues? # =======================================================
hill@evax.arl.utexas.edu (Col. Ames and Pixel) (09/22/90)
I vote we include it (Jasons "How To FTP") in the monthly posting.
--
adam hill Everybody lies about sex.
hill@evax.arl.utexas.edu BOING!4Ever Rub HER feet!
It's better to copulate than never
AmigaDos2.0 - A VW with $10,000 in options. --Robert A. Heinlein