5/12:
Class is over (except for your final project write-ups)
The course will center around two basic entities:
readings
and a
final project.
For most every class, you will have to read one or more papers (as assigned), which we will then discuss in class. You will also have to write a little review of each paper. The real key to the class will be your final project: a mini-research project on the topic of your choice. Though we will provide some suggestions, you are strongly encouraged to come up with a topic of your own (after all, that's what research is all about). More details will be available below in the weeks to come.
Mondays1/31 No Class 2/07 No Class 2/14 No Class (A#0 due) 2/21 No Class 2/28 No Class 3/06 Midterm Review 3/13 Spring Break 3/20 No Class 3/27 No Class 4/03 No Class 4/10 No Class 4/17 A#2: Project checkup due 4/24 TBA 5/01 A#3: Project presentation due 5/08 TBA |
Wednesdays2/02 Pilot, Optimistic Incremental 2/09 Impact of Structure 2/16 LFS, RAID 2/23 Lottery, Resource Containers (A#1 due) 3/01 Vax/VMS, Mach 3/08 Midterm Exam 3/15 Spring Break 3/22 RPC 3/29 Cluster-based... 4/05 NFS 4/12 Measurement of... 4/19 Implicit 4/26 Data Security 5/03 No class 5/10 The Final Lecture |
Fridays2/04 Disco 2/11 FFS 2/18 AutoRAID 2/25 Sched Activations 3/03 Multics VM 3/10 TBA 3/17 Spring Break 3/24 U-net 3/31 Locus 4/07 AFS 4/14 Coda 4/21 No class - work on project 4/28 Encryption 5/05 All-star Presentations 5/12 A#4: Project Write-up due |
Some additional papers are available in the
Auxiliary Reading List.
You are not expected to read these unless you wish to learn more about a specific topic.
Finally, a collection of advice papers is (partly) available in the
Advice Papers List.
I highly recommend that you read these papers on your own; however, you will not be held responsible for them in any way. I will try to make all of these available electronically.
You will have three basic responsibilities for the readings covered in the course:
1 - Read the assigned papers before class.
Without doing so, discussion is a little more difficult.
2 - Form a discussion group.
You should have about four people in your group, and discuss each paper sometime before class meets.
When you have formed a group, please send me email with a list of group members.
3 - Write-up each paper.
Your
individual
write-up should consist of three aspects of the paper you found to be most interesting, and also at least one aspect of the paper which you found to be least satisfying (a criticism). The write-up should
not
exceed half of a page in length. The write-up should focus on the
content
of the paper, not the
quality
of the writing.
Readings will probably be heavy up front, so make sure not to fall behind. That way, you will have more time towards to end of the semester to focus on your project.
A
project resources page
is also available.
The final project is the main focus of the course. You are expected to perform work which could eventually be suitable for publication in a major operating systems conference. In general, people should work in groups of two, though perhaps, for exceptionally difficult projects, three could be allowed. Though we will provide some suggestions for you to pick from, you are encouraged to think of a project on your own, which we can help to refine. Project write-ups will be similar in format to a conference submission, and all will be entered into a class-wide mini-conference. The best three papers will be presented to the class. More details are forthcoming.
Important Dates
|
Project Proposal
Status Meeting Talk Write-up (Call for Papers) |
2/23
4/17 5/1 5/12 |
Here are links to some previous class's projects:
Bart Miller's
and
Marvin Solomon's.
Assignment #0: Digital Picture
Assignment #1: Project Proposal
Assignment #2: Status Meeting
Assignment #3: Project Talk
Assignment #4: Project Write-up (Call for Papers)