1. Introduction to Operating Systems
Prof. Scott Brandt
Computer Science Department
Jack Baskin School of Engineering

2. Course Description
This course covers the fundamentals of operating systems, including:
Processes, interprocess communication, synchronization, scheduling,
Memory management, swapping, virtual memory, page replacement algorithms, segmentation,
File systems, security, input/output, interrupts, device management, ....

3. If there is time... Communications protocols,
If we find we have extra time, we will cover issues in distributed operating systems, including:
Communications protocols,
Synchronization, serializability, atomicity,
Remote procedure call,
Distributed file systems,
Cryptography and fault tolerance

4. Required Reading
G. Nutt, Operating Systems: A Modern Approach, Second Edition, Addison-Wesley, 2000, ISBN

5. Suggested Reading
A. Silberschatz, P. Galvin, and G. Gagne, Applied Operating Systems Concepts, Wiley, 2000.
M. McKusick, K. Bostic, M. Karels, and J. Quarterman, The Design and Implementation of the 4.4 BSD Operating System, Addison-Wesley, 1996.

6. Examinations
Two quizzes each worth 5% of your grade at weeks three and seven.
Two examinations worth 20% and 30% of your grade
A midterm examination around week five, and
A comprehensive final examination.

7. Programming Assignments
We will use the Nachos operating system simulator.
You will write four programs, together worth 40% of your grade.
You will have four grace days for the quarter to spend as you wish,
After that 10% of the points for the assignment will be deducted per day.

8. Academic Honesty
You are expected to adhere to the highest ethical standards.
All work you submit must be your own.
Plagiarism of any form is unacceptable.
You must give credit where it is due.

9. Consequences of Cheating
A letter will be sent to the Department, to the School of Engineering and to the student’s Provost.
The student will fail the course.

10. IEEE Code of Ethics
We, the members of the IEEE, … commit ourselves to the highest ethical and professional conduct and agree:
To seek, accept, and offer honest criticism of technical work, to acknowledge and correct errors, and to credit properly the contributions of others.

11. ACM Code of Ethics
Computing professionals are obligated to protect the integrity of intellectual property. Specifically, one must not take credit for other's ideas or work, even in cases where the work has not been explicitly protected by copyright, patent, et cetera.

12. What does this mean?
You can collaborate on the programming project as part of a defined group.
All members of the group (two or three) are graded equally.
Any other collaboration must be limited, and credit given to the other student.
You can’t look at, modify, or copy anyone else’s code.
You may not collaborate on examinations.

13. Gilligan’s Island Rule
You may discuss the project.
You must not take notes.
You must take a 30 minute break before coding (perhaps watching Gilligan’s Island).