Introduction to OS (414)HOWEVER…Class OutlineSchedule of Classes and ExamsOperating SystemsBrief HistoryHistory (cont)Networking!Microsoft WorldUnix WorldOS StructureOS FunctionsSlide 13Slide 14Slide 15Modular ApproachLanguageLanguage (cont)Slide 19System ProgramsMore on LanguagesIntro to OS CUCS MosséIntroduction to OS (414)•Why take this class? Why with Mosse?–it’s mandatory –it’s a great class–it’s a great prof–it’s easy (NOT!!!! do not fool thyself!)–it’s good for you•Life is not life anymore while this class is going on. Be careful! Specially if you’re taking also 415…Intro to OS CUCS MosséHOWEVER…•A new and improved 414 will be offered in the spring–MUCH SMALLER enrollment–New instructor (from UC Berkeley) with new ideas (that is, new blood)–Coupled with 415 (mandatory)–Kind of an honors “thing”Intro to OS CUCS MosséClass Outline•Book: Silberschatz and Galvin•Intro to OSs (including Real-Time OSs)•Processes (definition, synchronization, management)•Memory (virtual memory, memory allocation)•IO (disks, sensors, actuators, keyboards, etc)•InterProcess Communication (networking, data transmission, etc)•Fault Tolerance, Real-Time and Security (time permitting)Intro to OS CUCS MosséSchedule of Classes and Exams•Assignments 25% of grade: about every 2.5 weeks•First Prelim 25% of grade: Oct 3•Second Prelim 25% of grade: Nov 30•Final Exam 25% of grade : Dec ??•Potential pop quizzes and class participation may carry 5% of grade for extra creditIntro to OS CUCS MosséOperating Systems•Manages different resources (CPU, mem, disk, etc)•Improves performance (response time, throughput, etc)•Allows portability, enables easier programming (no need to know what the underlying hardware)•Interface between the hardware and the rest of the machine… editors, compilers, user programs, etc•Standard interface is typically done in two ways:–system calls: control goes to the Operating System– library calls: control remains with the UserIntro to OS CUCS MosséBrief History•First Generation of computers had no OS: single-user. All coding done directly in machine language, memory resident code (no other resources to manage)•Second Generation has basic OS: batch processing. Read input (tape/cards), process, output to tape or print•Third Generation improved life: multiprogramming! Careful partitioning of memory space (4-12KB), drums and disks added for reading cards and spooling outputs (Simultaneous Peripherals Operations On-Line)•Time-sharing created several virtual machinesIntro to OS CUCS MosséHistory (cont)•Fourth Generation: PCs and workstations. Cheaper, faster, more user-friendly (Thank Macs for interfaces!)•UNIX precursor MULTICS (MULTIplexed Information and Computing Services) was the first “modern” OS. Bell+MIT+GE (MULTICS --> units --> Unix)•Berkeley improved on it: paging, virtual memory, file systems, signals (interrupts), networking!Intro to OS CUCS MosséNetworking!•Networked OSs are connected through a network, but user needs to know the name/type/location of everything•Distributed OSs (e.g., Amoeba, Mach, Locus) provide transparency to user, yielding one huge virtual machine!•Specialized OSs are built for specific purposes: routing engines (Networking), lisp machines (AI), time constrained applications (Real-Time), Internet (WWW servers), massively parallel uses (supercomputers), etc•All these are coming together, hard to identify boundaries anymore. It’s the nineties!Intro to OS CUCS MosséMicrosoft World•Excellent marketing, some good products•OSs started with DOS (Disk OS), no nothing, just very simple commands!•Windows 3.1 was a huge jump (based on decades-old technology initially developed at Xerox then Macs)•Windows 95 (released in 96) improved tremendously the state-of-the-affairs for MS, but still unreliable•Windows NT approaches Unix distributions, with more user-friendly interface.Intro to OS CUCS MosséUnix World•Created at AT&T, re-written/improved by Berkeley•ATT had majority control and good support (reliable OS)•OSF (Open SW Foundation, now Open Group) is a consortium of several companies to standardize UNIX•Different subgroups (syscalls, shells, RT, etc)•Standardization is with respect to interfaces and not implementation of primitives. Impln is left to the implr•Modern applications are time constrained (tel, video, etc)•Real-Time playing an increasingly important roleIntro to OS CUCS MosséOS Structure•Interface can be done atany level (depends onlevel of security of OS)•Interface with the lowerlevel layer gets translated•Machine dependent language used for accessing hardware•Main advantage of direct resource access is efficiency•Main advantage of indirect access is portability•Completely layered OS? Why or why not?USEROSHardwareDev DriversIntro to OS CUCS MosséOS Functions•Controls and manages resources (disks, memory, CPU, …); sends/receives control commands and data•Allows multiprogramming (several programs “at the same time” in the same resource)•Carries out communication between processes (inter and intra processor)•Manages interrupt handlers for HW and SW interrupts•Provides protection and security to processes•Prioritizes requests and manages multiple resources in a single machine (eg multiprocessors or CPU IO reqs)Intro to OS CUCS MosséOS Functions•OS manages resources, including management of–processes (creation, deletion, suspension, comm, synch)–main memory (usage, alloc/de-alloc, which processes get it)–2ary storage (disk scheduling, alloc/de-alloc, swapping, files)–IO interfaces and devices (eg, keyboard, caching, memory)–protection (authorization, file and memory protection, etc)–InterProcess Communication (intra- and inter-machines)–Command interpretation (shells to Xlate user to OS). Typically includes the user interface that the OS uses.Intro to OS CUCS MosséOS Structure•Hardware at the bottom layer•Accessing the lower layer thruthe higher layers•DOS programs can access HW•Unix has controllers and devdrivers (DD) controlling devices•system calls are the interfacebetween user and OS (DDs)•libraries and system programs invoke
View Full Document
Unlocking...