Operating Systems

Announcement

∗ [Apr/12] Final exams of 2013, 2014, and 2015 are posted.

∗ [Feb/27] Midterm solution posted.

∗ [Feb/20] Practice midterm (I), Practice midterm (II), and Practice midterm (III) are posted.

∗ [Jan/4] Please send your group information to yuan at eecg.utoronto.ca by the end of Jan. 8th. Use the subject "ECE344 group information", and make sure to include your UTORids.

∗ [Jan/4] Welcome to ECE 344!

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 distributed 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 (4th Edition), Andrew Tanenbaum and Herbert Bos, Prentice Hall. 2014

Additional: Operating Systems: Principles and Practice, Second Edition, Thomas Anderson and Michael Dahlin, Recursive Books, Ltd.

Course Information

The lecture and lab times and office hours are shown below:

Lecture Times: Tue./Wed./Fri. 1-2pm (BA1190)

Lab Times: Mon 9-12am, Fri 9-12am, 3-5pm (GB243)

Office Hours: Wed. 8:30-9:00AM (SF2002E)

Midterm exam: Feb. 24th, 1:00 - 3:00 PM (Location: HA 403)

Course Policies

Grading:
Final exam: 45%
Midterm exam: 25%
Lab assignment: 30% (3%, 7%, 9%, 11% respectively for each lab assignment)
Bonus points for answering questions on Piazza: every instructor endorsed answer will get 1 bonus point, 2 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.