Turning in your lab project work (Operating Systems and Concurrency)

For both Operating Systems and Concurrency you will be doing substantial projects. It is important that you write a report documenting your work. While you may think your code is self-explanatory, this is rarely the case.

• Do the work as specified in the Kernel Projects for Linux textbook (and as amended during class) OR as specified in the Project chapters of the Unix Systems Programming textbook.
• Turn in your work as a single tar file of a single directory using the submit program. Your work will include the following:
  1. Turn in your codes. This includes:
     • your codes (changes to the kernel or your application program)
     • your test code: how you tested your new kernel feature or your application
     • any other code changes (eg makefiles, header files, etc.)
  2. Turn in evidence of your tests
  3. Turn in a 1-2 page lab report in a README text file that specifies
     • what you did
     • what system files you altered (if any) and why
     • what functions you've defined and what role they have in your solution
     • how the results of your test are to be interpreted. (EG, what happens when you give it an illegal address! how you know that your program is working)

Basically your report should tell the story of what your goal was, how you accomplished it, and how you know you succeeded. If you didn't quite succeed, this is also an opportunity to reflect on what went wrong.