|
Princeton
University
|
Computer Science 318
|
Fall 2012 |
Directory
General Information | Schedule
| Projects | Policies
Projects
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 co-developed with colleagues at University of Tromso in Norway and have been used in other institutions such as Yale.
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 some pseudocode, a flowchart, or whatever else you think appropriate in order to demonstrate your plans. Depending on the project, we might also want you to provide running code, or answer questions. Your design review will be graded from 0 to 5. To conduct a graded design review, each working group or student will meet with a TA for 10 minutes one week 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.
The following list the projects:
Project 1: Bootloader
|
|
|
9/18 |
|
|
9/20 |
|
|
9/24 |
Design review |
|
9/25 |
Precept 2 |
|
9/30 |
Project due |
|
Project 2: Non-preemptive
kernel Lab TAs: Amy Ousterhout, and Leonardo Stedile, Sat 3-5pm, Sun 8-10pm) |
|
|
10/2 |
|
|
10/8 |
Design review |
|
10/9 |
Precept 2 |
|
10/14 |
Project due |
|
Project 3: Preemptive
kernel Lab TAs: Michael Franklin, Ilias Glechaskiel,
Sat 3-5pm, Sun 3-5pm & 8-10pm) |
|
|
10/16 |
|
|
10/22 |
Design review |
|
10/23 |
Precept 2 |
|
11/5 |
Project due |
Project 4: IPC and device driver
|
|
|
11/6 |
|
|
11/12 |
Design review |
|
11/13 |
Precept 2 |
|
11/18 |
Project due |
Project 5: Virtual memory(TA: Aaron Blankstein;
Lab TAs: Michael Franklin, Ilias Glechaskiel, Sat 3-5pm, Sun 3-5pm & 8-10pm) |
|
|
11/20 |
|
|
11/26 |
Design review |
|
11/27 |
Precept 2 |
|
12/2 |
Project due |
Final project: File system
|
|
|
12/6 |
Precept 1 |
|
1/15 |
Project due |
Project Development Environments
You can either develop your projects in our lab or on your personal computers or laptops.
PCs in 010 Friends Center
You can use the Linux PCs in the 010 lab in Friends Center (so called Fishbowl). All the projects in this course should be placed on a USB flash memory stick and perform final tests on the PCs in the Fishbowl lab. The lab in Friend 010 is reserved for COS 318 students during the whole semester. When working on the projects, it is helpful to test your implementation using Bochs simulator during the development phase. After your projects run successfully on a simulator, you should test it on a PC in this lab before submitting to the dropbox.
Since there are only about 20 PCs in this lab, the lab may be crowded at times. You can always use ssh to remotely access these machines. Please share these machines for final tests.
VirtualBox on Windows or Mac PCs
If you have a PC or a laptop
that uses x86 CPU and your machine runs either Microsoft
Windows and Mac OS, you can use the VirtualBox
environment to develop your projects with the Bochs
simulator and debugger.
We have created a VirtualBox virtual machine image of the Linux OS in the
fishbowl lab for you. You can
download it here. The file is a bit smaller than
2GB. You may want to connect your
machine to a good access point on the campus network to reduce the download
time. You also want to make sure
your machine has enough storage space before downloading it. You also need some disk storage extra
space to run VirtualBox. You must test the final results of your projects on a PC in
the Fishbowl lab, by booting from your USB memory stick.
Instructions
1.
Download VirtualBox.
VirtualBox works for both Windows and Mac OS.
2.
Download
the provided virtual machine image, and unzip it.
3.
Add a
new machine to VirtualBox using "labpc-virtual.vbox" (on a Mac, ⌘A). You may
want to do some configurations before running, such as seting
the quota of memory and video memory. If your PC runs a 32-bit OS, you may need
to enable
Intel VT-x and/or AMD-V virtualization hardware extensions in BIOS.
4.
Log
in to the system by username: "student", password:
"cos318".
5.
Get
the start code to work. You can use bochs and bochsdbg as the same as in the fishbowl machines.
[student@labpc-virtual your_code_directory$ bochs
[student@labpc-virtual your_code_directory$ ~/318/bin/bochsdbg
COS 318: Operating Systems
Princeton University
Department of Computer Science