Assignment Information

Assignment Policies:

• Slip Days - Submitting an assignment after the deadline.
• Assignment Pick-up: Marked assignments will be posted to Markus and can also 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.
• 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 when 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, read this if you experience problems when running or installing OS/161.
• Browseable OS/161 man pages, including system call details.
• The sys161 manual, including hardware, running and debugging information.

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: Friday, January 17 (11:30pm)
• Slip days may be used.
• Assignment 0 description.
• Assignment 0 hints. (Read this for useful assignment tips)

Assignment 1

• Due Date: Monday, February 3 (11:30pm)
• 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: Monday, February 24 (11:30pm)
• 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: Monday, March 16 Monday, March 23 (11:30pm)
• 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: Wednesday, April 1 (11:30pm)
• Slip days may be used.
• Assignment 3 description.
• Assignment 3 hints. (Read this before starting the assignment)
• Assignment 3 marking report.

---

Quizzes:

All the quizzes should be completed electronically on Learn. Quizzes will open at 8:00 am on the due date and remain open for twelve hours (8:00 am - 8:00 pm). You will be able to attempt each quiz only once and will have 30 minutes to finish it once you start answering it.

The dates of the 10 quizzes are:

1. Friday, January 10: Threads
2. Friday, January 17: Threads/Sync
3. Friday, January 24: Sync
4. Friday, January 31: Procs
5. Friday, February 7: VM 1
6. Friday, February 14: VM 2
7. Friday, February 28: VM 3/Scheduling
8. Friday, March 13: Scheduling/IO
9. Friday, March 20 March 27: IO
10. Friday, March 27 April 3: Filesys

Note: these dates and topics are subject to change to account for the actual lecture progress.