CSE 120 Principles of Operating Systems Fall 2005 Lecture 1 Course Introduction Alex C Snoeren Lecture 1 Overview Class overview What is an operating system Operating systems and hardware Operating systems and applications September 22 2005 CSE 120 Lecture 1 Course Intro 2 Personnel Instructor Alex C Snoeren Discussion TA Barath Raghavan Office hours Thursdays 1 2pm or by appointment Discussion Mon 11 11 50am in HSS 1330 Office hours TBD Homework grader Project TA Jose Garcia Lab hours TBD email Project grader September 22 2005 CSE 120 Lecture 1 Course Intro 3 CSE 120 Class Overview Course material taught through class lectures textbook readings and handouts Course assignments are Discussion sections are a forum for asking questions Homework questions mostly from the book Three large programming projects in groups Lecture material and homework Additional OS topics e g how does an OS boot Other forums Mailing list cse120 cs ucsd edu Discussion board http webboard ucsd edu September 22 2005 CSE 120 Lecture 1 Course Intro 4 Homeworks There will be 4 5 homeworks throughout the quarter Reinforce lecture material no better practice Collaboration vs cheating You should discuss homework problems with others You can learn a lot from each other But there is a distinction between collaboration and cheating Rule of thumb Discuss together in library walk home and write up answers independently Cheating is copying from other student s homeworks or solution sets searching for answers on the Web etc Suspicious homeworks will be flagged for review September 22 2005 CSE 120 Lecture 1 Course Intro 5 Textbook Silberschatz Galvin and Gagne Operating System Concepts John Wiley and Sons 7th Edition ISBN 0471 69466 6 September 22 2005 CSE 120 Lecture 1 Course Intro 6 Nachos Project September 22 2005 CSE 120 Lecture 1 Course Intro 7 Nachos Nachos is an instructional operating system It is a user level operating system and a machine simulator Not unlike the Java runtime environment Will become abundantly clear or not so clear very soon Programming environment will be C on Unix Linux Solaris The projects will require serious time commitments Waiting until the last minute is not an option You will do three projects using Nachos Concurrency and synchronization Multiprogramming Virtual memory You will work in groups of 1 4 on the projects Start identifying partners now September 22 2005 CSE 120 Lecture 1 Course Intro 8 Labs We will use the uAPE B230 lab in the basement of the CSE EBU3B building Solaris running on Sun sparc machines You can also use your home machine The same project source will work on Linux but not Windows Graders will test on uAPE machines Be sure to test your projects there as well September 22 2005 CSE 120 Lecture 1 Course Intro 9 Exams Midterm Tuesday October 25th Covers first half of class Final Tuesday December 6th Covers second half of class selected material from first part Prof Snoeren will be explicit about the material covered No makeup exams Unless dire circumstances we all want to start vacation early Crib sheet You can bring one double sided 8 5x11 page of notes to each exam to assist you in answering the questions Not a substitute for thinking September 22 2005 CSE 120 Lecture 1 Course Intro 10 Grading Homeworks 20 Think of these collectively as a take home midterm Midterm 20 Final 30 Projects 30 September 22 2005 CSE 120 Lecture 1 Course Intro 11 How Not To Pass CSE 120 Do not come to lecture It s nice out the slides are online and the material is in the book anyway Lecture material is the basis for exams and directly relates to the projects Do not do the homework It s only 20 of the grade Excellent practice for the exams and some homework problems are exercises for helping with the project 20 is actually a significant fraction of your grade difference between an A and a C September 22 2005 CSE 120 Lecture 1 Course Intro 12 How Not To Pass 2 Do not ask questions in lecture office hours or email Professor is scary I don t want to embarrass myself Asking questions is the best way to clarify lecture material at the time it is being presented Office hours and email will help with homeworks projects Wait until the last couple of days to start a project We ll have to do the crunch anyways why do it early The projects cannot be done in the last couple of days Repeat The projects cannot be done in the last couple of days Some groups last time learned that starting early meant finishing all of the projects on time and some didn t September 22 2005 CSE 120 Lecture 1 Course Intro 13 Class Web Page http www cs ucsd edu classes fa05 cse120 Serves many roles Course syllabus and schedule updated as quarter progresses Lecture slides Announcements Homework handouts Project handouts tons of info on Nachos start now September 22 2005 CSE 120 Lecture 1 Course Intro 14 Questions Before we start the material any questions about the class structure contents etc September 22 2005 CSE 120 Lecture 1 Course Intro 15 Why Operating Systems Why are we making you sit here today having to suffer through a core course in operating systems Understand what you use Understanding how an OS works helps you develop apps System functionality performance efficiency etc Pervasive abstractions It s not like everyone will become OS developers after all Concurrency Threads and synchronization are common modern programming abstractions Java NET etc Complex software systems Many of you will go on to work on large software projects OSes serve as examples of an evolution of complex systems September 22 2005 CSE 120 Lecture 1 Course Intro 16 CSE 120 Course Material This course addresses classic OS concepts Services provided by the OS OS implementation on modern hardware Co evolution of hardware and software Techniques for implementing software systems that are System software tends to be mysterious Large and complex Long lived and evolving Concurrent Performance critical Virtual memory Wazzat Our goal is to reveal all mysteries September 22 2005 CSE 120 Lecture 1 Course Intro 17 Fundamental OS Issues The fundamental issues questions in this course are Structure how is an operating system organized Sharing how are resources shared among users Naming how are resources named by users and programs Protection how are users programs protected from each other Security how can information access flow be restricted Communication how to exchange data Reliability and fault tolerance how to mask failures Extensibility how to add new
View Full Document
Unlocking...