∗ [Apr/21] Final Exam posted.
∗ [Apr/15] Quiz 3 solution.
∗ [Mar/11] Quiz 2 solution posted.
∗ [Mar/2] Quiz 2 posted.
∗ [Feb/22] Sign up for lab groups here
∗ [Feb/11] Quiz 1 solution posted.
∗ [Feb/2] Quiz 1 posted.
∗ [Jan/22] Past exams posted.
∗ [Jan/10] Welcome to ECE 344!
In this course discuss the principles in the design and implementation of operating systems software. Topics include: Introduction to operating systems concepts, process management, memory management, file systems for both hard drive and SSD, virtualization, and distributed operating systems. The laboratory exercises will require implementing a simple, but functional operating system from ground up.
This site provides instructor's lecture notes and all lab-related information.
All lectures, tutorials, and practice sessions are delivered via Zoom; the Zoom links can be found at UofT Quercus.
Course announcements and the course discussion is on the Piazza web site.
Course grades are available at the UofT Quercus.
Suggested textbook (not required)
Modern Operating Systems (4th Edition), Andrew Tanenbaum and Herbert Bos, Prentice Hall. 2014
Operating Systems: Three Easy Pieces, Remzi H. Arpaci-Dusseau and Andrea C. Arpaci-Dusseau.
The lecture and lab times and office hours are shown below:
Lecture Times: Mon. 13-15, Thu 16-17
Lab times (when TAs will be available): Tue. 13:00-14:00, Thu. 12:00-13:00
Office Hours: Friday 10:00-11:00
Quiz 1: Tuesday 2/2, 10 - 11AM
Quiz 2: Tuesday 3/2, 10 - 11AM
Tuesday 3/23, 10 - 11AMThursday 3/25, 4-5PM
Quizzes: Each quiz will be 45 minutes long, with 15 additional minutes provided for uploading your answers.
Final exam: 30
3 Quizzes: 45 (equally weighted)
Lab assignment: 25 (3, 10, 12 respectively for each lab assignment)
Bonus: there is an optional 4th lab assignment that worths 10 bonus marks
Grace tokens: each student has 3 grace tokens. Each token can be used for an automatic 24 hour extension for one lab assignment.
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.