We will be using Pintos for this semester's projects. This page applies to all sections of CS 3204. Read more about important updates to the Pintos code or documentation since Aug 22.
| Project | Help Session | Groups Formed By | Due Date | Time Left | Project | Design Document |
|---|---|---|---|---|---|---|
| 0 | none | N/A | Sep 2, 11:59pm | 2007-09-02 23:59:59 GMT-04:00 | Individual | N/A |
| 1 |
We Sep 5, 6-8pm Williams 120 Slides: pdf ppt |
Sep 5 | Sep 24, 11:59pm | 2007-09-24 23:59:59 GMT-04:00 | Group | Individual* |
| 2 |
Th Sep 27, 7-9pm RAND 129 Slides: pdf ppt |
Sep 28 | Oct 16, 11:59pm | 2007-10-16 23:59:59 GMT-04:00 | Group | Individual* |
| 3 (MS) | Design Milestone | N/A | Oct 24 11:59pm (no extensions) |
2007-10-20 23:59:59 GMT-04:00 | Group | Group |
| 3 |
Th Oct 18, 6-8pm MCB 210 Slides: pdf ppt |
Oct 21 | Nov 7, 11:59pm | 2007-11-07 23:59:59 GMT-04:00 | Group | Group |
| 4 |
Mo Nov 12, 6-8pm PAM 1001 Slides: pdf ppt |
Nov 13 | Dec 5, 11:59pm | 2007-12-05 23:59:59 GMT-04:00 | Group | Group |
Project 0 is an individual project. The remaining projects require group work.
For the group projects, you must have committed to a group by the date indicated. You may not switch groups during the project for which you have committed. You may form groups of either 2 or 3 students, even across sections.
Important Note: Barring extenuating circumstances, we will not accept a project submission from you unless we have received notification from you that you have formed a group.
Send information about which groups have formed to cs3204-staff@cs.vt.edu. Here is a list of available students. We will keep this list up-to-date.
(*) For some group projects, we ask that you prepare an individual design document. Members of a group are allowed to discuss the content of this document, but copying is not allowed. Each group member must have created their design document independently.
1. In the 'pintos/src' directory, issue the command tar cvzf project0-yourpid.tgz * Note: the "pintos" directory is wherever you keep a working copy of Pintos. It does not need to be named "pintos". 2. If you are using one of the machines in McB124, open the web browser and log on to curator to submit your project0-yourpid.tgz file. To make submissions from elsewhere, copy the file project0-yourpid.tgz to your local machine and submit it to the curator.Note: Please issue a "make clean" command before submitting projects 1 through 4. Your .tgz file should be between 300 and 400 KB big, not larger.
The Curator is located at this URL.
Honor Code Pledge: This honor code pledge must be included in the source file for project 0. Please include it as part of the design template documents for projects 1 through 4, see below.
Project 0 - A list of common mistakes.
All of the remaining four projects are posted here together. If you want to think ahead while you write your code, feel free—in fact, we recommend it. But keep in mind that until the deadline for the current project, the details of the future projects are subject to change.
The use of a CVS repository is required for these projects.
You should read everything below before attempting any of the projects:
You'll want to read these once you start work on the projects. Their advice can save you a lot of time:
Bracketed notations in Pintos source code comments can be looked up in the Bibliography.