Princeton University
Computer Science Department

Computer Science 318
Operating Systems

Jaswinder P. Singh

Fall 2017

General Information | Schedule | Projects | Policies


We believe that the only way to master the knowledge of operating systems is to build a real operating system kernel. The six projects in this course are designed to do exactly that. At the end of the class, you will have a small, real operating system kernel. This set of projects were adapted from assignments used at Yale University, and were made in close association with professors at the institution.

Students will be paired as working groups for the first five projects. You will be regrouped after three projects in order to give you a chance to work with another person for the next two projects. You will be working alone on the last project.

Each project has two grading phases: design review and final submission. The goal of design review is to help you start early and our TAs can point out potential mistakes as early as possible. We want to make sure that you can finish the project before it's due so you have time to catch and resolve design errors and avoid frustrating last minute debugging. We don't mind mistakes at this stage; we encourage them. For design review, you should have seriously thought about all aspects of the project so you have a clear idea of what you are going to do. It is a good idea to have started some coding at this stage and for you to have investigated what tools will be necessary and have them working. When you meet with one of us TAs, please have prepared to answer the assigned questions. Your design review will be graded from 0 to 5 points. To conduct a graded design review, each working group or student will meet with a TA for 10 minutes no later than five days before the project is due.

The final submission will be done online, following the specific instructions in each project description. You should include a small README file with your project submission. You should concisely describe your design and implementation. Also, you need to describe what parts work and what parts don't; and how to compile and run your program (if you are not using the Makefile we provided). You don't have to repeat anything you presented in the design review. The TA who is in charge of the project will grade the project without correcting your code. It is your responsibility to figure out how to correct your code by comparing your implementations with the released solutions.

Normally, we will give the same grade to both students in a working group. If one of the students feel that the other student did more work and deserve more credits, please inform the TA who is in charge of the project by e-mail.


Tools Guide

Project 1: Bootloader and Physical Memory Management

Monday, 9/18 - 7:30pm-8:20pm x86 Assembly and Kernel debugging tutorial
Monday, 9/25 - 7:30pm-8:20pm Precept
Monday, 9/25 - 3:00pm-7:00pm Design review, Friend 010
Sunday, 10/01 at 11:55pm Project due

Project 2: Containers and Virtual Memory Management

Monday, 10/02 - 7:30pm-8:20pm Precept
Monday, 10/09 - 3:00pm-7:00pm Design review, Friend 010
Sunday, 10/15 at 11:55pm Project due

Project 3: Process Management and Trap Handling

Monday, 10/16 - 7:30pm-8:20pm Precept
Monday, 10/23 - 3:00pm-7:00pm Design review, Friend 010
Sunday, 11/05 at 11:55pm Project due

Project 4: Multicore and Preemption

Monday, 11/06 - 7:30pm-8:20pm Precept
Monday, 11/13 - 3:00pm-7:00pm Design review, Friend 010
Sunday, 11/19 at 11:55pm Project due

Project 5: File Systems

Monday, 11/27 - 7:30pm-8:20pm Precept
Monday, 12/04 - 3:00pm-7:00pm Design review, Friend 010
Sunday, 12/10 at 11:55pm Project due

Project 6: Advanced Projects

Dean's Date, 01/16 at 5pm Project due