TI Column Logo
November 1995

More about FTP

In the June issue I discussed various options for using FTP -- file transfer protocol -- to copy files from someone else's machine to yours or vice-versa. This month I want to share some feedback I received from that column.

EASIER WITH WINDOWS.   I commented that the newer FTP icons that exist on many Mac- or Windows-based systems make the job of using FTP much easier than it used to be when one used the basic FTP command that is part of the Unix operating system. Several Unix users reminded me that X-Windows, which runs under Unix, offers the same convenience. I agree. Let me just add that if you are buying a new computer system or upgrading your present one, and if you are not familiar with electronic communications tools, e-mail, FTP, etc., the window style of environment will make your life a lot easier. For example, obtaining a copy of a file is as easy as dragging the file's icon from the window containing the remote list of files into the window containing the local list of files.

E-MAIL FTP.   Several readers responded to my request for information on FTP sites that support the use of e-mail messages to request file transfers. This technique enables users who cannot use FTP but who can send e-mail messages to be able to transfer files between machines.

BITFTP.   Bob McGann writes, "One source I've used for months with little or no problems is the BITFTP facility out of Princeton University. They've been able to transfer many files to my Compuserve account and are able to split files as needed to accommodate Compuserve's limitation on block sizes. To get an initial help file, send an e-mail message to 'BITFTP@pucc.princeton.edu' with 'help' as the body. The subject can be left blank. You will receive about six pages of information on how to construct the e-mail messages needed to command the BITFTP interface. The help file is fairly concise and I don't think many people will have a hard time understanding it."

My thanks to Bob McGann and also Brice Wightman and Santiago Fisher for the Princeton site tip. I followed their suggestions and sent for the help file. Since the Princeton site offers a service that enables you to access other sites via e-mail, I will quote here the example from that help file and explain how to use this service:

  FTP nis.nsf.net
  USER anonymous
  cd introducing.the.internet    
  get intro.to.ip
  get network.gold
  get where.to.start
  get zen.ps
  get zen.txt
  QUIT


This example illustrates nine lines that you can enter as the body of your message to "bitftp@pucc.princeton.edu".

The first line contains the command "ftp site" and is the instruction to connect to and open an FTP session on a remote site (nis.nsf.net in the example). Alternatively, to connect to the IEEE FTP server use the command "FTP ftp.ieee.org".

The second line is the log-in command for a site which offers anonymous FTP log-in service. If you want to FTP from a site where you have obtained log-in permission -- for example with a log-in ID "freD" and password "Xy5#", then the second line would be "USER freD Xy5#".

The third line is to change to a subdirectory called "introducing.the.internet". The next five lines are commands to get (or copy) the five files that are in that subdirectory. The last line is the quit command to leave the FTP session. The commands to change directories and get files imply that you know the names of the files you want and in which directory they are stored. There is often an index file in the log-in directory that lists file names and paths. On the IEEE FTP server the file is named "info-index.paths".

As this is such a very useful service it is often busy, so expect delays ranging from minutes to several days! There are other commands you can use to list files, or change the transfer mode or the size of the files that are sent (long files are subdivided for mailing). These are described in the help file.

FTP SITES.   To get a list of sites that offer anonymous FTP log-ins, send an e-mail message to "bitftp@pucc.princeton.edu" with "FTPLIST" on the first line of your message.

FROM GERMANY.   Ralf Widera writes: "I can provide you with some addresses of FTP servers that are also accessible via e-mail. All of them provide a help function if you place 'help' in the subject or body of your message. Most of them send the help anyway, if they receive a message they do not understand:
* ftpmail@decwrl.dec.com
* archive-server@Germany.EU.net
* ftpmail@ftp.uni-stuttgart.de
* mail-server@cs.tu-berlin.de
* archive-server@ibr.cs.tu-bs.de
* mailserver@LEO.ORG

"The server at 'ftpmail@ftp.uni-stuttgart.de' allows not only access to a local FTP server, but can also open any FTP server. You only have to send the commands in the body of the message. Again, the 'help' is very useful for that. I know that most of the above addresses are in Germany but U.S. members can try 'ftpmail@decwrl.dec.com'."

IEEE LOGOS.   Some time ago, I wrote that IEEE logos are available via FTP from IEEE (The Institute, July 1995). Many of you have experienced difficulties in getting them. It seems that IEEE staff removed the files without telling me. When I checked to see why, I found out that there was a reason that relates to trademark issues. Bill Hagen is our manager of IEEE copyrights and trademarks. He and Tom Brisco, our director of electronic communications, are working on a long-term solution that will likely involve an electronic catalog of logos and formats and a mechanism for obtaining the logos. Before too long, we expect that IEEE members will have electronic access to selected IEEE servers that will not be accessible to nonmembers. In the meantime, any IEEE member who needs an IEEE logo for a valid reason as an IEEE volunteer should contact Bill Hagen at "w.hagen@ieee.org".


Robert T.H. (Bob) Alden is the chair of the IEEE Electronic Communications Coordinating Committee, and a former IEEE vice president.   In his other life, he is the director of the Power Research Laboratory at McMaster University in Hamilton, Ontario, Canada.   He welcomes your input via .

extracted from the IEEE website www.theinstitute.ieee.org
by Bob Alden