Computer Science Department
Computer Science Department
Introduction to operating systems including memory organization, I/O control, multitasking, process control, coordination, and resource management.
The class is structured around a lecture format; however, class discussions, questions and participation are strongly encouraged.
"The labs were awesome (although wickedly hard), the homework was applicable, and the tests seemed to test knowledge over memorization/logic." - Neil Pring - Fall08
| When: | Lecture: 12:30 - 1:45 T-Th ; Lab (opt): 3-5 Wed |
|---|---|
| Where: | Lecture: 160 Computer Science ; Lab (opt) Wed 3-5: Comoputer Science Linux Lab |
| Instructor: | Fritz Sieker (WHOD) |
| Email: fsieker AT cs.colostate.edu | |
| Office: Computer Science 256 | |
| Office Hours: T/TH 2-5; most Wed afternoons; whenever my door is open, and by appointment. During office hours I will commonly be in the Lab. | |
| Phone: TBD | |
| GTA: | TBD |
| Email:TBD AT cs.colostate.edu | |
| Office: TBD | |
| Office Hours: TBD; by email or by appointment | |
| Phone: TBD |
Operating Systems Concepts (7th edition), Silberschatz, Galvin, and Gagne Wiley, 2005.
| Week | Date | Subject |
| 1 | Jan 19 | Introduction / Organization (chapt 1 and 2) |
| 2 | Jan 26 | Processes / Synchronization (chapt 3 and 6) |
| 3 | Feb 2 | Processes / Synchronization (cont) |
| 4 | Feb 9 | Deadlock (chapt 7) |
| 5 | Feb 16 | Scheduling (chapt 5) |
| 6 | Feb 23 | Implementation |
| 7 | Mar 2 | TBD/Exam (Mar 5) - tentative |
| 8 | Mar 9 | Memory Management (chapt 8 and 9) |
| 9 | Mar 16 | Spring Break |
| 10 | Mar 23 | Memory Management - continued (chapt 8 and 9) |
| 11 | Mar 30 | Virtual Memory (chapt 9) |
| 12 | Apr 6 | Mass Storage (chapt 12) |
| 13 | Apr 13 | TBD/Exam (April 16) - tentative |
| 14 | Apr 20 | File Systems (chapt 10, 11) |
| 15 | Apr 27 | File Systems - continued (chapt 10, 11) |
| 16 | May 4 | TBD |
| 17 | May 11 | Finals week - CS 370 final Monday May 11th 9:10 AM |
| Homework | 10% |
|---|---|
| Labs | 30% |
| Exams | 60% |
| Exam | Date | Points | Avg | Max | Min | StdDev |
|---|---|---|---|---|---|---|
| Exam 1 | - | - | - | - | - | - |
| Exam 2 | - | - | - | - | - | - |
| Final | May 11 | - | - | - | - | - |
I encourage you to talk with other students about your assignments
and questions, but make sure you do your own homework.
You may not copy another student's program (either with
or without their knowledge) or write code for them. Please read the
departmental policy statement regarding incompletes, cheating, and
class attendance. This policy statement is in the file ~info/student-info . We will follow
the guidelines outlined in these documents.
Homeworks are written assignments that are to be done individually. They
are submitted electronically, Please use a common format (word, pdf, ...) to
make it easier to view and grade you work.
Assignment Submission
Each lab/homework assignment must be submitted electronically by
midnight on the given due date for that assignment. Instructions for checkin in
assignments may be found
here.
Late Policy: There is a penalty of 10% per day
for late work (to a maximum of 50%).
Assignments
Assignments consist of labs and homework. Labs are programming assignments.
They may be done individually, or with a single partner. The amount of
work does not require partnering. However, you may find it usefull to partner
with another student. If you partner with someone for a lab, please put the
names of both of you on the assignment and please submit only a
single copy of your work for grading. You will both recieve the same
grade for the lab.
| Assignment | Points | Description | Assigned | Due | Avg | Min | Max | StdDev |
|---|---|---|---|---|---|---|---|---|
| HW0 | 5 | Submission Process | Jan 20 | Jan 27 | - | 0 | 5 | - |