IntroductionCS-3013 C-term CS-3013, Operating Systems C-term 2008 Hugh C. Lauer Adjunct Professor (Slides include materials from Operating System Concepts, 7 th ed., by Silbershatz, Galvin, & Gagne and from Modern Operating Systems, 2 nd ed., by Tanenbaum)

IntroductionCS-3013 C-term Outline for Today Logistics and Details of this Course Introductions Discussion – What is an Operating System? Project Assignment Virtual Machines Introduction to Concurrency

IntroductionCS-3013 C-term Why an Operating Systems course? WPI CS requirements “Core area” for both grads and undergrads Understanding of inner workings of “systems” Exposure to diversity of operating systems OS-related assignments you may see in real life:– –“Design and develop an operating system to do THIS” (not probable) –“Select an operating system for an application that will do THAT” (probable) –“Design and develop this application on THAT system to exploit its special features” (likely)

IntroductionCS-3013 C-term This Course Two 2-hour classes per week, 7 weeks 8:00 AM to 9:50 AM January 11 – February 26 (Nearly) identical to first half of CS-502 First graduate course in Operating Systems Concentrated reading and project work Introducing the newly upgraded Fossil Lab

IntroductionCS-3013 C-term Textbook and Web Text Book: –(required) Operating Systems Concepts, 7 th edition, by Silberschatz, Galvin, and Gagne, John Wiley and Sons, 2005 –(required) Linux Kernel Design, 2 nd edition, by Robert Love, Novell Press, 2005 –(supplemental) Modern Operating Systems, 2 nd edition, by Andrew S. Tanenbaum, Prentice Hall, 2001 Course Information: –

IntroductionCS-3013 C-term Prerequisites Prerequisites: –C/C++ programming –Data structures –Computer Organization –Unix/Linux user experience and access Reading assignment –Silbershatz Chapters 1 and 2 Especially §2.8 about virtual machines

IntroductionCS-3013 C-term More on Prerequisites No time to try to “pick up” C programming Java-only programmers will find it challenging C++-only programmers may also find it challenging Time required 15+ hours per week average, 7 weeks total Computing resources Fossil Lab Room B17, Fuller ID card operates lock; separate login account and password Web-based Turnin system for projects

IntroductionCS-3013 C-term Schedule & Logistics Schedule –Atwater Kent – Room 223 –8:00 AM to 9:50 AM –One 5 minute break –28 classes –One mid-term exam and one final exam –One or more unannounced quizzes 4 Programming Projects –1-2 weeks each Mobile Phones, pagers and other similar devices OFF during class Avoid food and drink in class –If absolutely necessary, please be QUIET and inconspicuous Office Hours –by appointment –or immediately after class Contacts cs.wpi.edu –Adjunct office phone:– (508) (shared) Teaching assistants –Li, Feng – Fuller 317 Rick Skowyra Josh Nedelka (SA)

IntroductionCS-3013 C-term Exams and Quizzes Mid-term exam approx February 1 Final exam, February 26, 8:00 AM Exam rules –One hour –May include lecture material introduced earlier that same class –Closed book, one 8½ x 11 sheet of prepared notes (2 sides) –Bring calculator One or more unannounced quizzes –Closed book, no notes –Calculator may be useful

IntroductionCS-3013 C-term Grading –Exams & quizzes – 40% –Programming Projects – 40% –Class participation and written homework – 20% Unless otherwise noted, assignments are to be completed individually, not groups Late Policy – 10% per day –But contact Professor for extenuating circumstances WPI Academic Honesty policy

IntroductionCS-3013 C-term Ground Rule #1 There are no “stupid” questions. It is a waste of your time and the class’s time to proceed when you don’t understand the basic terms. If you don’t understand it, someone else probably doesn’t it, either.

IntroductionCS-3013 C-term Ground Rule #2 Help each other to understand. Even if a project is specified as individual, ask your friends/colleagues about stuff you don’t understand. It is a waste of your time try to figure out some obscure detail on your own when there are lots of resources around.

IntroductionCS-3013 C-term Programming Projects Project work based on OpenSUSE Linux 10.3 Each student will get a “virtual machine” What is a virtual machine? ( §2.8 in Silbershatz) Build, modify, install Linux kernel on your virtual machine Debug, analyze, crash Restore, try again

IntroductionCS-3013 C-term Fossil Lab (Free Open-Source Software Laboratory) Newly upgraded 30 Dell 2.4 GHz Core Duo PCs, 2 gigabytes RAM One Fossil server, 340 gigabytes of user storage Gigabit local area network; isolated from campus Virtual Machines Stored on Fossil server May be run on any Fossil PC –VMware Workstation May be suspended, resumed, restored, etc.

IntroductionCS-3013 C-term Fossil Lab (continued) This is the first class to use the newly upgraded Fossil Lab Expect teething troubles, miscues, etc. This is the first class to use virtual machines in the Fossil Lab Ditto However, we have used virtual machines for CS- 502 for three terms

IntroductionCS-3013 C-term What is a Virtual Machine? An application that simulates a computer with enough fidelity and performance to mimic an actual hardware system Concept originated in 1960s, and has been used occasionally in large systems Established in mainstream of enterprise systems by VMware in early 2000s.

IntroductionCS-3013 C-term Definitions Host system:– The hardware and operating system that supports the virtualization application E.g., the Windows PC in the Fossil Lab E.g., a departmental server Guest system:– The virtual hardware and the operating system that is being simulated E.g., OpenSUSE Linux 10.3 for this course

IntroductionCS-3013 C-term Using a Virtual Machine Use VMware Workstation in Fossil Lab Create a clone of master virtual machine P:\cs3013\c08\VirtualMachine May be suspended, resumed, moved to another PC, etc. Indistinguishable from real hardware on network and display in most behaviors Alternative Run your virtual machine on your own PC using free VMware Player or your own VMware Workstation license

IntroductionCS-3013 C-term Questions?

IntroductionCS-3013 C-term Outline for Today Logistics and Details of this Course Introductions Discussion – What is an Operating System? Project Assignment Virtual Machines Introduction to Concurrency

IntroductionCS-3013 C-term Instructor — Hugh C. Lauer Adjunct Professor Ph. D. Carnegie-Mellon –Dissertation “Correctness in Operating Systems” Lecturer: University of Newcastle upon Tyne, UK Approximately 30 years in industry in USA Research topics –Operating Systems –Proofs of Correctness –Computer Architecture –Networks and Distributed Computing –Real-time networking –3D Volume Rendering –Surgical Simulation and Navigation –…

IntroductionCS-3013 C-term Systems Experience IBM Corporation University of Newcastle Systems Development Corporation Xerox Corporation (Palo Alto) Software Arts, Inc. Apollo Computer Eastman Kodak Company Mitsubishi Electric Research Labs (MERL) Real-Time Visualization Founded and spun out from MERL Acquired by TeraRecon, Inc. SensAble Technologies, Inc. Dimensions Imaging, Inc. (new start-up)

IntroductionCS-3013 C-term VolumePro™ Interactive volume rendering of 3D data such as MRI scans CT scans Seismic scans Two generations of ASICs, boards, software VolumePro 500 – 1999 VolumePro 1000 – 2001 CTO, Chief Architect of VolumePro million gate, high-performance ASIC 10 9 Phong-illuminated samples per second

IntroductionCS-3013 C-term Sample images from VolumePro

IntroductionCS-3013 C-term Operating Systems I have known IBSYS (IBM 7090) OS/360 (IBM 360) TSS/360 (360 mod 67) Michigan Terminal System (MTS) CP/CMS & VM 370 MULTICS (GE 645) Alto (Xerox PARC) Pilot (Xerox STAR) CP/M MACH Apollo DOMAIN Unix (System V & BSD) Apple Mac (v.1 – v.9) MS-DOS Windows NT, 2000, XP various embedded systems Linux …

IntroductionCS-3013 C-term Other Two seminal contributions to computer science Duality hypothesis for operating system structures (with Roger Needham) First realization of opaque types in type-safe programming languages (with Ed Satterthwaite) 21 US patents issued Computer architecture Software reliability Networks Computer graphics & volume rendering

IntroductionCS-3013 C-term Outline for Today Logistics and Details of this Course Introductions Discussion – What is an Operating System? Introduction to Concurrency Project Assignment Virtual Machines Term Project Assignment

IntroductionCS-3013 C-term Class Discussion What is an Operating System? (Laptops closed, please!)

IntroductionCS-3013 C-term What is an Operating System? Characteristics –Large, complex set of programs –Long-lived, evolutionary –Worked on by many people over many years Functions –Creates abstractions –Multiplexes concurrent activities –Manages resources –Mediates access to hardware devices –Provides a variety of services to users and applications –…–…

IntroductionCS-3013 C-term Definition – Abstraction The distillation of a complex mechanism into a simple, conceptual model User of abstraction does not need to worry about details Implementer of abstraction does not need to worry about how user will use it (within limits)

IntroductionCS-3013 C-term Abstraction The most important word in this course!

IntroductionCS-3013 C-term What is an operating system? (cont’d) Abstractions:– –Processes, threads, and concurrent computation –Virtual memory. For managing memory –Files. Persistent storage of information –Sockets & connections for network communication Controls I/O & peripherals Implements security and accessibility Definition — Same as judicial definition of pornography “I cannot define it, but I sure can recognize one when I see it!”

IntroductionCS-3013 C-term What is an Operating System Hardware Interfaces – Registers, etc. OS Kernel Prog. ToolsServicesUI/Shell XYZ OfficeMedia PlayerBusiness Appl. CPUI/O Controllers Traditional OS Practical OS

IntroductionCS-3013 C-term Computer System Organization

IntroductionCS-3013 C-term Operating System Organization Kernel System Libraries (user space) Utilities, tools, other stuff

IntroductionCS-3013 C-term Operating System Organization (continued) Kernel System Libraries (user space) Utilities, tools, other stuff Drivers & modulesFile Systems

IntroductionCS-3013 C-term Major OS Issues structure: how is the OS organized? sharing: how are resources shared across users? naming: how are resources named (by users or programs)? security: how is the integrity of the OS and its resources ensured? protection: how is one user/program protected from another? performance: how do we make it all go fast? reliability: what happens if something goes wrong – hardware or software extensibility: can we add new features? communication: how do programs exchange information concurrency: how are parallel activities created and controlled? scale: what happens as demands or resources increase? persistence: how do you make data last longer than program executions? distribution: how do multiple computers interact with each other? accounting: how do we keep track of resource usage, and charge for it?

IntroductionCS-3013 C-term Operating Systems Large, complex programs Typically –Long-lived –Frequently extended and updated –Worked on by many developers –Used and, maybe abused by a variety of users with varying expertise and expectations Essential to create an acceptable computing environment to create and execute other programs that achieve business or personal goals

IntroductionCS-3013 C-term Kinds of operating systems Stand-alone machines – no OS Simple batch monitors Concurrent I/O and programs Time-sharing, multiple users, interactive Servers, non-stop systems, transaction processing PC’s, workstations Multiple processor systems Real-time systems Embedded systems

IntroductionCS-3013 C-term Kinds of operating systems (1) Stand-alone machines – no OS –Manually scheduled “jobs,” reset between jobs –Early business computers E.g., IBM 1401/1460 –Early mini-computers E.g., PDP1, PDP5, PDP8, etc. Simple batch monitors –Simple “monitor routine” switches between jobs –Input loaded onto tape or other media off-line –Output to tape is punched and/or printed off-line –Typical university computing centers IBM 7090, Univac, etc.

IntroductionCS-3013 C-term Kinds of operating systems (2) Concurrent I/O and programs –SPOOL-ing (Simultaneous Peripheral Operation On Line) Allows direct input & output –Multiple programs resident in memory at once Keeps processor busy –On-line file storage –Some support for terminals, telecommunications –Early business computers E.g., IBM 7070, IBM 360 & 370 –Scientific computing E.g., Control Data 6600, IBM 360/91

IntroductionCS-3013 C-term Kinds of operating systems (3) Time-sharing, multiple users, interactive –Many concurrent users “logged on” –Interactive editing and computing –Self submission of batch jobs –Protection among users, protection among jobs –Fair allocation of resources –All university computing centers since about 1970 E.g., MULTICS, IBM 360/67, DEC PDP-10, PDP-20 –Advanced minicomputers DEC, Data General, Prime, etc. Unix

IntroductionCS-3013 C-term Kinds of operating systems (4) Servers, non-stop systems, transaction processing –Banking, airline reservation –Online databases –Many very short “transactions” –Tandem, Stratus, Sequoia –Unix, Linux, Solaris, HP-UX –Windows Server 2000, 2003 –Oracle, SAP (?)

IntroductionCS-3013 C-term Kinds of operating systems (5) PC’s, workstations –CP/M, DOS, MS-DOS –Apollo Domain –Unix, Solaris, HP-UX –Mac OS –Windows 95, 98, Me –Windows 2000, XP –Linux Multiple processor systems –Beowulf clusters –Unix, Solaris, HP-UX, Linux server systems

IntroductionCS-3013 C-term Kinds of operating systems (6) Real-time systems –SAGE (North American air defense) –Process control (steel mills, refineries, etc.) –Large and small; computers you never heard of –VxWorks, etc. Embedded systems –Auto ignition –Cell phone, PDA –Appliances –…–…

IntroductionCS-3013 C-term OS History – Unix & Linux Unix –Descendant of Multics –First “C” version in 1973 (DEC PDP-11) Timesharing for < 10 users on 32K Memory Many Unix versions at Bell Labs – different goals Source code made available to Universities – BSD –Posix (start 1981) defines standard Unix system calls –AT&T licensing!

IntroductionCS-3013 C-term OS History - Linux Open Source – Linux.org First Version 1991, Linus Torvalds, processor –v.01, limited devices, no networking, –with proper Unix process support! 1994, v1.0 –networking (Internet) –enhanced file system –many devices, dynamic kernel modules

IntroductionCS-3013 C-term OS History - Linux 1996, v2.0 –multiple architectures, multiple processors –threads, memory management …. Gnome UI – introduced in 1999 Recent –V million lines of code –7-10 million users –Growth by 25%/year through 2003 –Growing use in business server market Note: development convention –Odd numbered minor versions “development” –Even numbered minor versions “stable”

IntroductionCS-3013 C-term OS History – Windows NT/2000/XP Key designer – David Cutler also designed VAX/VMS 1988, v1 - Win32 API – “microkernel” 1990, v3.1- Server and Workstation versions 1996, v4 –Win95 interface –Graphics to kernel –More NT licenses sold than all Unix combined –Microkernel de-emphasized

IntroductionCS-3013 C-term OS History – Windows NT/2000/XP Windows 2000 – NT5.0 –Multi-user (with terminal services) –Professional - desktop –Server and Advanced Server - Client-server application servers –Datacenter Server - Up to 32 processors, 64 GB RAM Windows XP –Windows 2000 code base –Revised UI –EOL for DOS/Windows line

IntroductionCS-3013 C-term OS History – Windows NT/2000/XP Microsoft has 80% to 90% of OS market Wintel – Windows + X86 WinNT 4.x is 12 million lines of code Win2000 is 18 million lines of code Windows XP – approaching 10 8 lines of code Windows Vista – early 2007

IntroductionCS-3013 C-term OS and Hardware OS mediates programs’ access to hardware –Computation – CPU –Storage – volatile (memory) and persistent (disk) –Networks – NIC, protocols –I/O devices – sound cards, keyboards, displays

IntroductionCS-3013 C-term Four fundamental Abstractions Processes & threads This course Virtual memory This course Files & persistent storage CS-4513, Distributed Systems Sockets & connections CS-4514, Computer Networks

IntroductionCS-3013 C-term Break