1&6(&6(3ULQFLSOHVRI2SHUDWLQJ3ULQFLSOHVRI2SHUDWLQJ6\VWHPV6\VWHPV)DOO)DOOLecture 1: Course IntroductionLecture 1: Course IntroductionGeoffrey M. VoelkerGeoffrey M. VoelkerSeptember 19, 2001 CSE 120 -- Lecture 1 -- Course Intro 2/HFWXUH2YHUYLHZ/HFWXUH2YHUYLHZ● Class overview● What is an operating system?● Operating system modules, interfaces, structure2September 19, 2001 CSE 120 -- Lecture 1 -- Course Intro 3&6(&ODVV2YHUYLHZ&6(&ODVV2YHUYLHZ● Course material taught through class lectures, textbook readings, and handouts● Course assignments are ◆ Homework questions from the book◆ Three large programming projects● Discussion sections are a forum for asking questions◆ Primarily about lecture material and homework◆ But also “guest” discussions from the project TAs◆ Will have mailing list and online discussion forums, tooSeptember 19, 2001 CSE 120 -- Lecture 1 -- Course Intro 4+RPHZRUNV+RPHZRUNV● There will be approximately five homeworks throughout the quarter◆ Reinforce lecture material…no better practice● Collaboration vs. cheating◆ I encourage you to 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 by me3September 19, 2001 CSE 120 -- Lecture 1 -- Course Intro 51DFKRV1DFKRV● 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» This is not an understatement● You will do three projects using Nachos (more later)◆ Concurrency and synchronization ◆ Multiprogramming◆ Virtual memory ● You will work in groups of four on the projects◆ Start identifying partners nowSeptember 19, 2001 CSE 120 -- Lecture 1 -- Course Intro 6/DEV/DEV● We will have access to two labs in the AP&M basement◆ uAPE: sparc/Solaris◆ OSTL: x86/Linux (access is combo controlled)● You can use either platform for your project◆ Or even your home machine◆ Helps if everyone in your group is using the same platform4September 19, 2001 CSE 120 -- Lecture 1 -- Course Intro 7([DPV([DPV● Midterm◆ Thursday, October 25◆ Covers first half of class● Final◆ Friday, December 7◆ Covers second half of class plus selected material from first half» I will be explicit about the material covered● Crib sheet◆ You can bring one double-sided 8.5x11” page of notes to each exam to assist you in answering the questions◆ Note: Not a substitute for thinkingSeptember 19, 2001 CSE 120 -- Lecture 1 -- Course Intro 8*UDGLQJ*UDGLQJ● Homeworks: 20%◆ Think of these collectively as a take-home midterm● Midterm: 20%● Final: 25%● Projects: 35%5September 19, 2001 CSE 120 -- Lecture 1 -- Course Intro 9+RZ+RZ1RW1RW7R3DVV&6(7R3DVV&6(● Do not come to lecture◆ It’s too early, 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 (differencebetween an A and a C)September 19, 2001 CSE 120 -- Lecture 1 -- Course Intro 10+RZ+RZ1RW1RW7R3DVV7R3DVV● Do not ask questions in lecture, office hours, or email◆ It’s 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◆ Some groups last time learned that starting early meant finishing all of the project on time…and some didn’t6September 19, 2001 CSE 120 -- Lecture 1 -- Course Intro 11&6(&RXUVH0DWHULDO&6(&RXUVH0DWHULDO● This course addresses classic OS concepts◆ The services provided by the OS◆ OS implementation on modern hardware◆ Co-evolution of hardware and software◆ Techniques for implementing software systems that are» Large and complex» Long-lived and evolving» Concurrent» Performance-critical● System software tends to be mysterious● Our goal is to reveal all mysteriesSeptember 19, 2001 CSE 120 -- Lecture 1 -- Course Intro 12)XQGDPHQWDO26,VVXHV)XQGDPHQWDO26,VVXHV● 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 features?7September 19, 2001 CSE 120 -- Lecture 1 -- Course Intro 13)XQGDPHQWDO26,VVXHV)XQGDPHQWDO26,VVXHV◆ Concurrency: how to control parallel activities?◆ Performance: how to make efficient use of resources, reduce OS overhead?◆ Scale and growth: how to handle increased demand?◆ Compatibility: can we ever do anything new?◆ Distribution: how to coordinate remote operations?◆ Accountability: how to charge for/restrict use of resources?● And the principles in this course are the design methods/approaches/solutions to these issuesSeptember 19, 2001 CSE 120 -- Lecture 1 -- Course Intro 14:KDWLVDQRSHUDWLQJV\VWHP":KDWLVDQRSHUDWLQJV\VWHP"● The operating system is the software layer between user applications and the hardware● The OS is “all the code that you didn’t have to write” to implement your applicationOperating
View Full Document
Unlocking...