To install

1) unpack the archive (tar xzf taper-6.2.tar.gz)
2) edit Makefile 
	There are several options - read the taper.txt for details
	about which ones to set etc..

	Also, change the directories if you want to install in
	different directories
3) do a 'make clean; make all'
4) do a 'make install' to install files in correct locations
5) to start taper:
    
       taper -T [tape_type]
       
   [tape_type] = zftape or ftape or scsi or file or removable

6) to make a statically linked version of taper for use in emergency
   rescue disks, do 'make taper-static' and the resulting file 
   (taper-static) will not require any libraries to be on-line when
   running.

READ THIS!!!!!!!!!!!!
---------------------
I know that very few of you will read the full documentation. That
is fine as long as taper works for you. 

Howver, if you run into problems, please read the documentation before
firing off your e-mail editor and asking me. A lot of your questions
will be answered in the relatively short FAQ, saving you from having
to read the entire documentation.

I do not mind receiving mail - in fact, a lot of suggestions, bug
fixes, improvements came from people mailing me - but only
after you have read the docs and not found the solution in them.

I have to waste a lot of time answering questions
that I didn't need to - although you may think that it will only
take a quick second to answer to question, it actually takes a while -
I read your message, type the answer, send it off and
then archive the message - about 5 minutes in all. Multiple this
by 8 messages a day (average), this means 40 minutes of wasted time - 
time I could spend developing taper, especially seeing this is
a sideline and must fit it around my work etc..

What I object to is people being lazy and not reading documentation
and then expecting me to help them.

Because my time is now even more limited, if your question is
answered in the FAQ or documentation, I will only send you a rather
terse one line message "Read the FAQ" or "Read the documentation".
Sorry, but you have to at least try and help yourself.

If you find that some aspect of the documentation is not clear,
by all means, e-mail me a tell me and I'll try and clarify it
in a later version.

If you have a bug to report, please read the BUGS file for
the sort of information I need.

I did a quick survey on the e-mail I received regarding taper from
August through November and the results are quite amazing:

	over 65% (67.2%) of mail was about a question directly 
                         answered in the FAQ
	over 20% (22.6%) of mail was about a question directly 
			 answered in the taper.txt file
	remaining	 was about bug fixes and useful suggestions
			 etc..

Yusuf
27JAN96
