CS111 - Spring 2004

Instructions on how to turn in Project #2:

Project #2 due Thursday, May 6th, by 22:00 (10:00pm)

We will be using electronic submission for this project. You may have used electronic submit in some of your previous classes. In order to use it, you will have to copy the files to your seas account. If you do not have a seas account, and you are an engineering student, you can can apply for one here. If you are not an engineering student, you can apply at the SEASnet Office. Account requests take 1 business day to processes. Since this announcement is within 2 business days of the due date e-mail your TA if there is a problem getting an account.

From your SEASnet account, run submit cs111 <file1> <file2> <file3>. You can not submit the same file twice. If you need to resubmit, append -number to the file. For example: to resubmit the README file, submit README-1; to resubmit it again submit README-2.

Do not submit MS Word files. (or KWord, or Openoffice, or anything other then plain text)

You will need to submit the following files.Please use the names listed below (including case). If you do not, points may be deducted.

  1. readme.txt (Maximum of 500 words)
    1. The exact command line needed to compile your test program.
    2. Last minute info, what works, what doesn't work.
    3. Brief documentation.
    4. Other: assumptions you made, etc.
  2. partners.txt
    1. Each partner's name.
    2. Your TA's name.
  3. journal.txt A journal of who did what parts of the project and how long each part tool.
  4. kernelchanges.diff (Look at the kernel hacking tips for information about generating a diff)
    Points may be deducted if your diff does not apply cleanly to a stock 2.4.26 tree. Points may also be deducted if the size of the diff is over 12Kbytes; if it is, most probably you're submitting something you don't need to.
  5. bzImage (a copy of your compiled kernel).
  6. userprogram.c (and any support files needed)
  7. transcript.txt (As stated in the project description, your test program must demonstrate several things.)
    1. The successful clean compilation of your test program. This means compiling with the -Wall option.
    2. A successful call -- print the results: pid with largest number of open file descriptors, number of file descriptors it has open, and the largest process descriptor seen in any of the input processes.
    3. A failed call due to a null pointer. Print the return value, and the value of errno.
    4. A failed call due to an out of range memory access. Print the return value, and the value of errno.

Notes about script files:

When the script command is running do not edit files with vi or other editors because it may mess up the script file.
To produce a script file execute the command:
script -a transcript.txt [Return]
Type exit to exit the script when done.
Do not use the extension .c for the script files! You may overwrite your C programs and lose them forever!