How to turn in your assignment

prep

If you have an OCE account, you must run the prep command to get to
your space allocation for this class.  This command also sets up certain
environment variables which are specific to this class.  To run the prep
command, simply type   prep cs100s

turnin

The turnin program can be found in /software/common/bin/turnin, which
should be in your standard default path.  There is a man page and a 
help page which describe how to use the turnin program, which should
explain everything you could ever wish to know about turnin.
Please note that turnin will only submit *one* file per student; that
is, if you run turnin more than once for a given assignment, turnin will
overwrite what you have already submitted.  Thus, if you wish to submit
more than one file (as will be required for this and all subsequent
assignments), you must package those files together with the tar command
and submit the tar package with the turnin program.  Additional 
information on tar can be found in the turnin help pages, and in the
tar man and help pages.

You can use either of two forms to turnin a tar package.  Say you
wish to turnin everything in the directory hw1.dir.  You can use the 
command:
	tar cvf - hw1.dir | turnin -c cs100s
which will package everythin in hw1.dir into a tar package and send
that package through the turnin program without making any additional
files in your directory.  Alternatively, you can run the following
sequence of commands:
	tar cvf hw1.tar hw1.dir
	tar tvf hw1.tar                 //this gives a table-of-contents
	turnin -c cs100s hw1.tar
which will package the files in hw1.dir into a file called hw1.tar,
list the contents of the tar file so you can see that everything
you expect is in there, and then finally submit that tar file through
turnin.

In your turnin package, the only types of files we want are *.C,
*.h, makefile, and any documentation files.  Please do not hand in
executables, *.o files, or anything ending in ~ or % (i.e. editor
files).  Remember to include user and logic manuals for the programs
(as separate files) and any README files if appropriate.