Partner: naze pwebb

Testing procedure:

We wrote 3 testing scripts for our program, which work as follows:

Test1:

This is a basic test which makes sure many of the system calls work correctly.
This was ran in 3 different disk sizes (5, 100, 1000) to verify that the 
basic commands work.

Test2:
This test is ran after Test1 to verify that all of the data was preserved on
the disk after quitting the first time.  Once again, it was ran on the same 3 sized.

errors:
Here just about every command was a bad command.  This was to check that all
errors and exceptions were handled properly with bad commands.  Same 3 sizes.

filldisk:
Used only with a 5 block disk, this test attempted to write 13 blocks.
Like the errors test, wanted to make sure that no uncaught exceptions were thrown.

We were able to implement all 11 possible action on the filesystem.  They all 
appear to work well, and we included a significant amount of error-checking 
to prevent problems caused by unexpected input or other bugs.

We were unable to incorporate symlinks in our algorithms to walk through the 
directory tee.