1. Operating Systems CS381 Umar Saif umar@mit.edu

2. The Bureaucracy Not anointed by the Queen I am not a Sir! Call me Umar

3. The Bureaucracy  Instructor: Umar Saif  TAs:  TBA  19, 100 minute lectures  Assignments vs. project poll?  Instructor: Umar Saif  TAs:  TBA  19, 100 minute lectures  Assignments vs. project poll?

4. Why Bother?  We’ll not teach you operating systems textbooks  We’ll learn to engineer real- world complex systems  OS is one such system  You’ll leave with an intuitive sense for engineering real systems  We’ll not teach you operating systems textbooks  We’ll learn to engineer real- world complex systems  OS is one such system  You’ll leave with an intuitive sense for engineering real systems

5. Modus Operandi  System design is as much an art as it is science  We are using an internal MIT textbook (6.033 classnotes) from Jerry Saltzer and Frans Kaashoek  We’ll refer to a traditional textbook every so often  System design is as much an art as it is science  We are using an internal MIT textbook (6.033 classnotes) from Jerry Saltzer and Frans Kaashoek  We’ll refer to a traditional textbook every so often

6. Text Books  Silberschatz, Galvin and Gagne, ‘ Applied Operating System Concepts ’, 1 st Edition, 2000, John Wiley & Sons, Inc. ISBN 0-471-36508-4.  Principles of Computer System Design, MIT 6.033 Class Notes, Draft Release 4 by Jerome H. Saltzer and M. Frans Kaashoek, Department of EECS, MIT  Some handouts will be given to supplement the text.  Silberschatz, Galvin and Gagne, ‘ Applied Operating System Concepts ’, 1 st Edition, 2000, John Wiley & Sons, Inc. ISBN 0-471-36508-4.  Principles of Computer System Design, MIT 6.033 Class Notes, Draft Release 4 by Jerome H. Saltzer and M. Frans Kaashoek, Department of EECS, MIT  Some handouts will be given to supplement the text.

7. Grading 15% Quizzes 30 % Hands-on exercises 25% Midterm Exam 30% Final Exam (Comprehensive) 15% Quizzes 30 % Hands-on exercises 25% Midterm Exam 30% Final Exam (Comprehensive)

8. Grading  Announced quizzes  So that you prepare for them  Programming assignments carry the same weight as the finals  Engineers learn by kicking the sandbag  I am very lenient grader  Try and enjoy the course, don’t worry about grades  Announced quizzes  So that you prepare for them  Programming assignments carry the same weight as the finals  Engineers learn by kicking the sandbag  I am very lenient grader  Try and enjoy the course, don’t worry about grades

9. What we’ll learn 1 Operating System Concepts (What is an OS? Why is an OS Needed? Case study of the UNIX time-sharing OS.) 1Chapter 1 System Engineering (Indirection, Complexity, Modularity, I/O, Storage Structures, Storage Hierarchy, Protection Layers etc.) 2 Chapter 2 Operating System Structures (Clock Management (scheduling), Address-space-management (Memory), Abstraction (System Calls, Virtual Machines) etc.) Chapter 3

10. What we’ll learn

12. What is an OS?

13. What is an os  OS is needed to do three things:  abstraction  Security  multipelxing An OS securely abstracts and multiplexes hardware  OS is needed to do three things:  abstraction  Security  multipelxing An OS securely abstracts and multiplexes hardware

14. What is an OS  Abstraction, protection and multiplexing of:  Clock  RAM  Hard-disk  Network interface  Keyboard and display  peripherals  Abstraction, protection and multiplexing of:  Clock  RAM  Hard-disk  Network interface  Keyboard and display  peripherals