
======
As I was saying earlier - it would be easier and quicker if you 
could e-mail the ps file of the report and the abstract in ascii text -
under separate cover - to csweb@cs.

I will also need a hard copy of the report for our files.
(you can leave it in my mailbox - if you want)

=======


Using the Anonymous FTP Facility.
---------------------------------

An anonymous ftp facility is now available for faculty members to distribute
technical reports, and any other files which need to be made public.
The faculty committee working on this has decided that the standard
formats for technical reports should be either LaTeX source, TeX source,
Troff source, or Postscript.

Each faculty member now has a directory on "cs" which the path
Now, merv.
usr/ftp/pub/local/shasha. 

---------------------------------------------------------------------------

Step 1: Gather together all of your files in a single subdirectory and make
a tar file of that directory.

Since it is a pain in the neck for users to ftp multiple source files
from an anonymous ftp archive, a standard convention used is to gather

Example: You have created a tex document called zippers.tex, generated
a dvi file called zippers.dvi which you would like to propogate along
with the tex source itself, and you have included a README file which
you would like to distribute. You create a subdirectory called zippers
by typing:

	% mkdir zippers

then copy all the files to that directory, and then create the tar
file zippers.tar by typing:

	% tar cvf zippers.tar ./zippers

It is usually advisable, although not required, to compress this file
(particularly if it is large) by typing:

	% compress zippers.tar

This will create the file zippers.tar.Z and remove the original zippers.tar.


Step 2: Put the file into your ftp directory.

Ftp into cs using your regular user name (you type the stuff that is
underlined:

Nowadays, log into merv then
cd usr/ftp/pub/local/shasha
and then do the ftp.
	     ----------------------------
	ftp> binary
	     ------
	200 Type set to I.
	ftp> put zippers.tar.Z
		 -------------
	200 PORT command successful.
	150 Binary data connection for zippers.tar.Z (128.122.140.11,1953).
	226 Binary Transfer complete.
	local: zippers.tar.Z remote: zippers.tar.Z
	1882 bytes sent in 0.0026 seconds (7.1e+02 Kbytes/s)
	ftp> quit
	     ----
	221 Goodbye
	%

Step 3: Send mail to Karen Christie

If the file is an "authorized" CSD technical report, send mail to
Victoria Macaulay asking her to link your file to the official
technical report list. Here's what to send to Victoria:

	Karen,

	Could you please create a technical report for me. The file
	is in /usr/ftp/pub/local/shasha/zippers.tar.Z. Please let
	me know what technical report number you have assigned to this
	paper.

It seems that it is now /pub/local/shasha

	Thanks,
	Matthew

Step 4: Victoria creates a link to your file and sends you the following
	mail:

	Matthew,

	You have been assigned technical report number 125. You can tell
	all interested parties that they can log into cs using anonymous
	ftp and then change their directory to pub/tech-reports, and
	get the file tr0125.tar.Z.

	Victoria





The two files temptuning.text and temptuning.figs
contain the text and figure slides respectively.
They are both in uuencoded postscript format.


Thanks very much for your interest. 

The two files temptuning.text and temptuning.figs
contain the text and figure slides respectively.
They are both in uuencoded postscript format.

Please obtain the lecture notes by performing the following steps:
1. ftp into cs.nyu.edu (ip address is 128.122.140.24)
2. type anonymous in response to login
3. type your id as the password
4. cd to pub/local/shasha
5. get temptuning.text
6. get temptuning.figs
7. apply uudecode to these two files.
8 print them out as regular postscript files.

If you have any problems, please let me know.
Best regards,
Dennis

If you have any problem, please let me know.
Thank you for your interest,
Dennis

