CS 350 - Assignment Information

Assignment Policies:

• Slip Days - Submitting an assignment after the deadline.
• Group Policies - So you want to break-up...
• Assignment Pick-up: Marked assignments can be picked up during the IA's office hours, during the first two weeks after they have been marked. After two weeks they can be picked up from the instructor's office until the end of the term. Unclaimed assignments will be shredded at the end of the term.
• Assignment marking reappraisal requests:
  
  If there is a problem with the marking your assignment, you may request that your assignment be reappraised. To do this:
  • Print and fill out a reappraisal form, on which you should describe (briefly) what the problem is.
  • Drop your form off with the course instructor after lecture or during office hours.
  For each assignment there will be a deadline for reappraisal requests.

Readings and Reference Material:

• CVS
  • Using CVS
  • Setting Up CVS for use with OS/161
  • Sharing an OS/161 CVS Repository (for group work)
• Debugging OS/161 with GDB
• An Introduction to Programming with Threads, by Andrew Birrell
• MIPS R3000 Software Reference Manual
• ELF (Executable and Linking Format) Specification
• GDB Online Documentation from www.gnu.org

OS/161 Information

OS/161 Essentials

• OS/161 and tools FAQ (Frequently Asked Questions)
  Be sure to read this if/when you experience problems installing or runnning OS 161 or the other tools for this class (including installing on a personal machine).
• OS/161 Installation Guide for the student.cs computing environment
• OS/161 Installation Guide for other machines (FOLLOW THESE INSTRUCTIONS FOR WORKING FROM HOME)
• Working with OS/161 (how to build, run, and debug OS/161 kernels)
• The sys161 manual. This information is also available in the sys161 source code distribution.

Other Useful Stuff

• Browseable OS/161 source code
• Browseable OS/161 man pages
• Other OS/161 links
  • A paper about OS/161 from SIGCSE 2002.
  • The OS/161 home page at Harvard.

Submitting Your Work and Checking Your Submission

• This page has information on how to submit your work and how to check that your submitted code compiles on the machines that we use for marking.

Assignment Specifications:

Do not leave assignments until the last week. Start early!
Remember: late assignments receive a grade of 0%.

Assignment 0

• Due Date: Wednesday Sept 18 (noon)
• NO SLIP DAYS
• Assignment 0 is to be done individually.
• Assignment 0 description.
• OS/161 and tools FAQ (Frequently Asked Questions)
  Be sure to read this if/when you experience problems installing or runnning OS 161 or the other tools for this class (including installing on a personal machine).

Assignment 1

• Due Date: Wednesday Oct 9 (noon)
• Assignment 1 is to be done individually.
• Slip days may be used.
• Assignment 1 description.
• Assignment 1 hints.
• Assignment 1 marking report.
• Assignment 1 test scripts (NEW: Now available)
• Mark reappraisal deadline: November 11

Assignment 1b

• Due Date: Thursday Oct 17 (noon) (Note date changed from Tues Oct 15)
• NO SLIP DAYS
• Assignment 1b is to organize and register your project group.
  To do so, you should follow the instructions in the Assignment 1b description.

Assignment 2

• Due Date: Friday Nov 8 (noon)
• Slip days may be used.
• Assignment 2 description.
• Assignment 2 hints. (Read this before starting the assignment)
• Chart of system calls used by testbin programs (PDF). (A bit old but may be helpful for your testing)
• Assignment 2 marking report.
• Assignment 2 test scripts
• Mark reappraisl deadline: Tuesday December 10

Assignment 3

• Due Date: Friday Nov 29 (noon)
• Slip days may be used.
• Assignment 3 description.
• Assignment 3 hints.
• Paging Flowchart (NEW: may have minor inaccuracies)
• Assignment 3 marking report. (Now available)
• Assignment 3 test scripts. (Now available)
• Mark reappraisl deadline: as soon as possible, and no later than Friday, January 10th