CS 350 - Operating Systems

Assignment Information

Assignment Policies:

• Slip Days - Submitting an assignment after the deadline.
• Assignment Pick-up: Marked assignments will be posted to Crowdmark with the exception of A0. Marks for A0 will be posted to this website and can be viewed by clicking on the "Marks Online" link from the main page.
• 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:
  • Fill out a reappraisal form, on which you should describe (briefly) what the problem is.
  • Email or drop your form off with the course instructor after lecture or during office hours.
  For each assignment there is a deadline of two weeks after the marks are made available for reappraisal requests.

Reference Material:

• git
  • Git Magic.
  • Git Reference.
  • Git Manual.
  • Git Tutorial.
  • Links to the Pro Git Book, references, vidoes and more.
• Subversion (SVN)
  • Apache Subversion documentation.
• GDB Online Documentation
• MIPS R3000 Software Reference Manual
• ELF (Executable and Linking Format) Specification
• An Introduction to Programming with Threads, by Andrew Birrell

OS/161 Information

OS/161 Essentials

• 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
• Debugging OS/161 with GDB
• 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).
• Manuals
  • Browseable OS/161 man pages.
  • The sys161 manual. This information is also available in the sys161 source code distribution.

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

• Overview of cs350_submit - how to submit your work and check that it will compile for marking.

Assignment Specifications:

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

Descriptions of assignments will be made available as the term progresses.

Assignment 0

• Due Date: Wednesday, May 10 (12:00 Noon)
• Slip days may be used.
• Assignment 0 description.
• Assignment 0 hints. (Read this for useful assignment tips)

Assignment 1

• Due Date: Wednesday, May 31st (12:00 Noon)
• Slip days may be used.
• Assignment 1 description.
• Assignment 1 hints. (Read this before starting the assignment)
• Assignment 1 marking report.

Assignment 2a

• Due Date: Friday June 16th (12:00 Noon)
• Slip days may be used.
• Assignment 2a description.
• Assignment 2a hints. (Read this before starting the assignment)
• Assignment 2a marking report.

Assignment 2b

• Due Date: Wednesday, July 5th (12:00 Noon)
• Slip days may be used.
• Assignment 2b description.
• Assignment 2b 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 2b marking report.

Assignment 3

• Due Date: Monday, July 24 (12:00 Noon)
• Only 2 slp days may be used
• Slip days may be used.
• Assignment 3 description.
• Assignment 3 hints. (Read this before starting the assignment)
• Assignment 3 marking report.