1. Introduction to Operating Systems Prof. Darrell Long Computer Science Department Jack Baskin School of Engineering

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

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

4. Required Reading 4 Andrew S. Tanenbaum, Modern Operating Systems, Prentice Hall, 2001, ISBN: 0130313580.

5. Suggested Reading 4 Abraham Silberschatz, Peter B. Galvin and Greg Gagne, Operating System Concepts, Seventh Edition, John Wiley & Sons, 2005. 4 Marshall Kirk McKusick and George V. Neville- Neil, The Design and Implementation of the FreeBSD Operating System, Addison-Wesley Professional, 2004. 4 Edward G. Coffman and Peter J. Denning, Operating Systems Theory, Prentice-Hall: Englewood Cliffs, 1973.

6. Examinations 4 Weekly exercises worth 10% of the total grade. 4 Four programming assignments worth 40% combined. 4 Two examinations worth 50% of your grade –A midterm examination around week five worth 20%, and –A comprehensive final examination worth 30%.

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

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

9. Consequences 4 A letter will be sent to the Department, to the School of Engineering and to your Provost and you will fail the course.

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

11. ACM Code of Ethics 4 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? 4 You can collaborate on the programming project as part of a defined group. –All members of the group (one or two) are graded equally. –The first assignment you must complete alone. 4 Any other collaboration must be limited, and credit given to the other student. 4 You may not collaborate on examinations.

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

14. What about the Simpsons rule? 4 This is Simpson’s rule: 4 But you can watch the Simpsons instead (if you can’t find Gilligan’s Island).

15. Secrets to Success in CS 111 4 Start projects early –Write your design document before writing any code Spend less time writing and more time thinking. 4 The best time to get help is as soon as possible –Waiting until the last minute won’t leave enough time for us to help you, –It’s better to finish early and take the last day off.

16. Design Documents 4 Indicates the changes that you need to make to DLX/OS to implement the assignment. –Identify algorithms, –Identify locations in DLX/OS where code will be added or changed. 4 This is a high-level design document, and does not contain intricate implementation details. 4 Must be done before you begin coding the assignment.