Lab 2 is due Friday 5/13/05 at 5:00:00AM PST. Begin the submission process at least 30 minutes early, because the timestamps I go by are what the CourseWeb system says, browsers can crash, networks can stall, etc.

Be sure to include a README file with the following:

• Both lab partner's names, email addresses, and ID numbers.
• A brief write-up describing your approach and details about your implementation, and details about any challenge problems you choose to implement.
• The status of the implementation, any known drawbacks, any unimplemented features, etc. This one is especially important and should match the behavior I see when testing the code. Make sure you discuss what tests may lead to a race condition in your code and WHY.
• IMPORTANT: write build instructions for your code! Document where each of your included source files goes in the kernel source tree.

Write this in a file in PLAINTEXT, HTML, or PDF format. NO MS WORD DOCUMENTS!! Put the README file in a directory with the kernel source code files you've modified (e.g. barrier.c, entry.S, etc.), and your user-space test code WITH Makefile. DO NOT submit the entire source tree, only the files you've modified! Tar and gzip the directory (see details below). Rename the resulting tarball to your names, like:

first_last1_first_last2_lab2.tar.gz

You should test the tarball file to make sure it includes all of your code, Makefile, and README you need BEFORE you submit the file. ONE person per team should then submit the tarball file through CourseWeb. If you are working with a partner from Section 1, they should submit your code on their CourseWeb page.

Submissions after 5/13/05 at 5:00:00AM will be considered late and consume one of your free late days per 24 hours. You have a maximum of three late days for the quarter, so if you already used any late days on lab 1, you have less than 3 remaining for this and future labs.

Lab submissions will be tested on the CS111 partition in the 4405 BH Linux lab, so make sure your code compiles and runs there. I should be able to extract the tarball file and follow your build instructions without making any modifications to your code.

If you have any questions about the submission instructions, please ask me ASAP. Don't wait until Friday at 3AM.

Using TAR and GZIP:

TAR creates a single file containing one or more files. GZIP compresses a file. You can use them together as follows:

Create a .tar file containing all of the files you wish to submit. Be careful not to overwrite any of your code files when doing this (backing up is always a good idea):

$tar -cvf my_file.tar file1 file2 file3 ...

This creates a file 'my_file.tar' that contains file1, file2, file3, and so on. You can also tar an entire directory:

$tar -cvf my_file.tar my_dir/

You can extract files from the tar file by running:

$tar -xvf my_file.tar

Second, GZIP the .tar file:

$gzip my_file.tar

This creates a compressed file 'my_file.tar.gz'. You can uncompress the file with:

$gunzip my_file.tar.gz

As always, see "$man tar" and "$man gzip" for more info.

updated 5/12/05