1 / 32

CS 423 – Operating Systems Design Lecture 1 - Introduction

CS 423 – Operating Systems Design Lecture 1 - Introduction. Roy Campbell Spring 2008. Overview. Course information (personnel, policy, schedule, misc.) What is OS? What does it do? History of OS Summary. Instructor. Roy Campbell PhD University of Newcastle upon Tyne Research:

deidra
Télécharger la présentation

CS 423 – Operating Systems Design Lecture 1 - Introduction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS 423 – Operating Systems DesignLecture 1 - Introduction Roy Campbell Spring 2008 CS 423 - Spring 2008

  2. Overview • Course information (personnel, policy, schedule, misc.) • What is OS? What does it do? • History of OS • Summary CS 423 - Fall 2007

  3. Instructor • Roy Campbell • PhD University of Newcastle upon Tyne • Research: • Distributed Operating Systems (Distributed Services, Reflective Systems, Adhoc Configuration), • Object-Oriented Operating systems (Parallelism, O-O Design, File Systems, Persistent Objects, Fault-Tolerance, Security, Real-time, Root Kits • Pervasive/Ubiquitous Systems (Naming, Discovery, Configuration, Fault-Tolerance, Events, Active Spaces, Rooms, Buildings), • Security (Corba SECIOP, Policies, Denial of Service, Authentication, Access Control, Security Assessment) • Streaming Video (QoS, Adaptation, Protocols) CS 423 - Fall 2007

  4. Office Assistants: Anda Ohlsson (ohlsson@cs.uiuc.edu) for Roy Campbell Teaching Assistants: Jeffrey Naisbitt Class Website http://www.cs.uiuc.edu/class/sp08/cs423/ Newsgroup: uiuc.class.cs423 and uiuc.class.cs423.announce Two newsgroups – one for discussion on machine problems, one for announcements Overview CS 423 - Fall 2007

  5. Required Readings for cs423 • Required Textbook: • Modern Operating Systems, Andrew Tanenbaum, Prentice Hall, second edition, 2001 • Understanding the LINUX Kernel, Bovet and Cesati, O’Reilly, third edition, 2006 (kernel 2.6) CS 423 - Fall 2007

  6. Course Prerequisites • CS 241 – MUST • There will be a test similar to exams of cs241 (take-home exam) • If you can finish more than 80% of the exam, you should be fine in the class • If you cannot finish the exam with 70% and lower, then it means that you should consider sitting in cs241 or taking it first • Evaluation exam will be given on 1/16 CS 423 - Fall 2007

  7. Facilities and Office Hours • Laboratory Facilities • CSIL-linux clusters, 216 SC, • Office hours: available in web page • RC: Tue/Thu, 9-10am, Office: 3120 SC • JN: Wed/Fri, 1-2pm, Office: 1100 SC CS 423 - Fall 2007

  8. Principles System concepts OS design Some theory Rationale Practice Goals Understand OS decisions Basis for future learning Get hands dirty About this course… CS 423 - Fall 2007

  9. Fast pace Hard material 4 MPs (programming) 2 Homework 1 Midterm and 1 Final (Comprehensive) Exam But…. Students survived past cs423! Expect (Some) Pain CS 423 - Fall 2007

  10. Grading • Final exam: 35% • Mid-exam: 20% • 2 Homework: 10% • 4 MPs: 35% (depending on the difficulty each MP will have different weight • 1st MP – 7% • 2nd MP – 8% • 3rd MP – 10% • 4th MP – 10% CS 423 - Fall 2007

  11. Grading policy • Gradebook system: http://compass.uiuc.edu • Late policy for MPs and Homework Assignments • No Late Policy, but there will be 3Bonus Days • It is your responsibility! • Check announcements in lectures, newsgroups, or web pages • MPs will be done in Groups of 2-3 students • MPs done on vmware server CS 423 - Fall 2007

  12. Group Setup • Setup Groups between 1/14 and 1/23 • Email to the TA Jeff (naisbitt@uiuc.edu ) your group formation • David Andersen (system admin) will setup accounts on the vmware server. • Between 1/23 and 25 the TA (Jeff) will inform each group their login and password to start to work on the vmware server. • The instructions about working on the vmware server will be also posted on web as well as mailed to each group. CS 423 - Fall 2007

  13. Re-grading policy • Students have 1 week (after the grade for a Homework/MP/exam is released into gradebook) to request for re-grading • Re-grading requests need to be in writing to the TA • After the re-grading period, no re-grading request will be granted for this Homework/MP/exam. CS 423 - Fall 2007

  14. Cheating Policy • Academic integrity • Your homework and exams must be your own - we have a zero tolerance policy towards cheating of any kind and any student who cheats will get a failing grade in the course. • Both the cheater and the student who aided the cheater will be held responsible for the cheating • Machine problems will be graded per group, i.e., each member gets the same number of points. CS 423 - Fall 2007

  15. Lecture Format • Help you understand important and hard OS concepts • Lectures do not cover everything • Not all questions in homework or exams are from lectures • Students responsibility • Attend lectures • Read textbooks • Homework, MP, Exam • Periodically check web page, Read/utilize newsgroup CS 423 - Fall 2007

  16. MPs (Deadlines) • Q&A Session before each MP due date • MP releases and Q&A Session dates will be announced • on the course web page/newsgroup CS 423 - Fall 2007

  17. Homework & Exams • Announcement in web page • No makeup homework • No makeup exams unless with documented medical emergency CS 423 - Fall 2007

  18. ¼ Unit Project: graduate students • Final grade is decided upon ¾ unit performance • ¼ unit project: pass or fail • Individual or group of two • Choices • Implementation project • Animation project • Survey • Proposal due: 2/8, Friday, 5pm, by email to rhc@uiuc.edu • Details in web page CS 423 - Fall 2007

  19. “Code” that: Sits between programs & hardware Sits between different programs Sits betweens different users But what does it do? to provide an orderly and controlled allocation of the processors, memories and I/O devices among the various programs competing for them Real Life Example: Government What Is an OS? CS 423 - Fall 2007

  20. Resources Allocation Protection Reclamation Virtualization Services Abstraction Simplification Convenience Standardization What Is an OS? Makes computers simpler CS 423 - Fall 2007

  21. Resources Allocation Protection Reclamation Virtualization Finite resources Competing demands Examples: CPU Memory Disk Network What Is an OS? Government Limited budget,Land,Oil,Gas, CS 423 - Fall 2007

  22. Resources Allocation Protection Reclamation Virtualization You can’t hurt me I can’t hurt you Implies some degree of safety & security What Is an OS? Government Law and order CS 423 - Fall 2007

  23. Resources Allocation Protection Reclamation Virtualization The OS gives The OS takes away Voluntary at run time Implied at termination Involuntary Cooperative What Is an OS? Government Income Tax CS 423 - Fall 2007

  24. Resources Allocation Protection Reclamation Virtualization illusion of infinite, private resources Memory versus disk Timeshared CPU More extreme cases possible (& exist) What Is an OS? Government Social security CS 423 - Fall 2007

  25. History of Operating Systems (1) • First generation 1945 – 1955 • vacuum tubes, plug boards (no OS) • Second generation 1955 – 1965 • transistors, batch systems • Third generation 1965 – 1980 • ICs and multiprogramming • Fourth generation 1980 – present • personal computers, hand-held devices, sensors CS 423 - Fall 2007

  26. History of Operating System (1945-55) Early batch system • bring cards to 1401 • read cards to tape • put tape on 7094 which does computing • put tape on 1401 which prints output CS 423 - Fall 2007

  27. History of Operating Systems (1955-65) • Structure of a typical JCL job – 2nd generation • Single user • Programmer/User as the operator • Secure, but inefficient use of expensive resources • Low CPU utilization-slow mechanical I/O devices CS 423 - Fall 2007

  28. History of Operating Systems (1965-80) • Multiprogramming system • Three jobs in memory – 3rd generation • Spooling - use disk as a very large buffer for input/output devices • Polling/Interrupts, Timesharing CS 423 - Fall 2007

  29. The Operating System Zoo (1980-present) • Mainframe operating systems • Server operating systems • Multiprocessor operating systems • Personal computer operating systems • Real-time operating systems • Embedded operating systems • Smart card operating systems CS 423 - Fall 2007

  30. Historical Comparison CS 423 - Fall 2007

  31. Summary • Course overview • Policy and requirement • What is OS? • OS history • Next lecture: system overview (chapter 1.4-1.6 – review of cs241 concepts) CS 423 - Fall 2007

  32. After this lecture… • Reading assignment: chapter 1 • Browse the web site • Subscribe to newsgroup • Login to csil machines • Setup Groups: 1/14-1/23(email to Jeff about group formation) • Think about what are the criteria to evaluate an OS? CS 423 - Fall 2007

More Related