CS 537 Introduction to Operating Systems
Lecture 2, Spring 1998
Instructor and TAs
Office: 7361 Computer Science
Office hours: 3-4pm Tuesday
TA: Shankar Pasupathy
TA: Mei-Guei Shie
Office: CS 3310
Office hours: Monday 1-3pm
Watch this space for the latest updates.
Last updated: Mon Jan 19 12:18:18 CST 1998
- Jan 19 1998
- Class schedule is available now.
- Dec 24 1997
- Course home page is set up.
CS 537 is an introduction course to operating system implementation and
related system software.
Topics covered include: process management, concurrency and synchronization,
process scheduling, main-memory management, file system and I/O management,
a brief introduction to networking and distributed systems, and protection
Lecture: 1:00pm-2:15pm, Tuesday and Thursday, 1221 Computer Science
Discussion: 2:30pm, Thursday, 1325 Computer Science
The discussion section is very important.
The primary focus of the discussion meetings will be topics related to the
(including introduction to the
Java programming language), but time will also be available for answering any
questions you have regarding points raised in the the lectures or the
Operating Systems Concepts (Fifth Edition)
by Abraham Silberschatz and Peter Galvin
The Java Programming Language
by Ken Arnold and James Gosling,
Professor Marv Solomon have written a tutorial,
Java for C++ Programmers.
lots of additional helpful materials about Java are available on the WEB.
The following references have been collected locally for fast access.
For copyright reasons, the local copies are only accecessable
from Computer Sciences Department
Public versions can be found at
In this course there will be five excercises, five programming assignments,
a midterm and a final exam (scheduled on 7:45am, Fri. May 15).
The midterm and final exams will each count for 21% of your grade.
Five excercises will each count for 1%.
The first programming assignment will count for 5%. The remaining four
projects will count for 12% each.
All excercises and the first assignment should be done individually. Projects
two through five require students to work in pairs. Both members of a pair
will receive the same grade on a project. Students can switch partners
between projects. Feel free to discuss projects with anyone, but you
must not share code with anyone but your partner.
Assignments are due at the start of class on the date listed on the handout.
Over the entire semester,
three late days
You can use these late days on different assignments (e.g., one day on each
of three assignments) or all three days on one assignment.
Other than these three days,
absolutely no late work will be accepted.
Late days cannot be used on any assignment
that is due during the last week
Programming assignments will be done with partners.
Each group of two will work independently from other groups.
Cheaters will receive the maximum penalties, which include receiving an
"F" grade for the course
and having this marked on your transcript.
Copyright © 1998 by Pei Cao. All rights reserved.