Instructor: Announcement
∗ [Mar/14] Lab Assignment 3 is released. Due date: April 12, 5 pm. Please start early!
∗ [Mar/3] Midterm Solution is posted.
∗ [Feb/14] Lab Assignment 2 is released. Due date: March 15, 5 pm. Please start early!
∗ [Jan/31] Lab Assignment 1 is released. Due date: Feb 15, 5 pm. Please start early!
∗ [Jan/24] No lecture on February 14th, Thursday. The instructor is away for a conference. Work on your project!
Course Description
The goal of this course is to have students understand and appreciate the principles in the design and implementation of operating systems software. Topics include: Introduction to operating systems concepts, process management, memory management, file systems, virtualization, and smart-phone operating systems. The laboratory exercises will require implementing a simple operating system.
This site provides instructor's lecture notes and all lab-related information.
Course announcements and the course discussion is on the Piazza web site.
Course grades are available at the UoT portal site.
Textbook
Main: Modern Operating Systems (3rd Edition), Andrew Tanenbaum, Prentice Hall. 2008
Additional: Operating Systems: Principles and Practice, Beta Edition, Thomas Anderson and Michael Dahlin, Recursive Books, Ltd. 2012
Course Information
The lecture and lab times and office hours are shown below:
Lecture Times: Mon 2-4pm (MC252), Thu 2-3pm (LM161)
Lab Times: January 24th to April 12th, Thu 3-6pm (GB251 and SF2102), Fri 9-12am (GB243)
Office Hours: Mon 4-5pm (SF2002E)
Midterm exam: February 25, 2013, Monday, 2-4PM, GB405 and GB412
Course Policies
Grading:Final exam: 50%
Midterm exam: 25%
Lab assignment: 25% (3%, 6%, 8%, 8% respectively for each lab assignment)
Bonus points for answering questions on Piazza: every instructor endorsed answer will get 2 bonus points, 4 bonus points maximum.
Missed Labs: Missed labs will be made up on a case-by-case basis. Please have appropriate documentation (i.e. doctor's note, etc...)
Cheating: Each group should work independently. You may confer with each other, but your work should be your own. You should understand your code well enough to describe it to the TA and make simple changes to it when asked to.
Course Feedback
Please provide anonymous course feedback by posting anonymous notes on Piazza.