Operating Systems History & Approaches. Computer Systems Laboratory Sungkyunkwan University

Transcription

1 Operating Systems History & Approaches Jin-Soo Kim Computer Systems Laboratory Sungkyunkwan University

2 Pre-Multics Era (1) OS/360 A batch processing OS developed by IBM for System/360 mainframe computers (announced in 1964). A family of three control programs. The single task PCP (Primary Control Program) processed jobs sequentially. MFT (Multiprogramming li i with iha Fixed number of Tasks) added d multitasking, but only allowed a fixed number of concurrent tasks. MVF (Multiprogramming with a Variable number of Tasks) allowed varying numbers of tasks. OS/360 introduced IBM s batch-scripting language JCL (Job Control Language). g OS/360 was amongst the earliest OS to make direct access storage devices (DASD) a prerequisite for its operation. Evolution: MFT OS/VS1, MVT OS/VS2 MVS 2

3 Pre-Multics Era (2) CTSS (Compatible Time-Sharing System) Developed by MIT in 1961 for the IBM 709. One of the first time-sharing operating systems Compatible with the standard batch processing OS, the Fortran Monitor System (FMS). FMS in background, and programs compiled for FMS batch in foreground time-sharing environment Using virtual machines The system with the first computerized text formatting utility and inter-user electronic mail. A facility called RUNCOM for CTSS took a collection of commands contained in a file and executed ecuted them. This is the direct ancestor of the Unix shell script. 3

4 Multics (1) Multics Multiplexed Information and Computing Service A time-shared, multi-processor mainframe computing utility Originally started by MIT, GE, and Bell Labs for GE- 645, a 36-bit system, in Bell Labs quit in 1969 and built Unix. GE s computer business, including Multics, was taken over by Honeywell in Last system shutdown on 10/31/2000. / 4

5 Multics (2) Multics innovations Hierarchical file system. File / directory / path name / working directory Access Control Lists (ACLs). Long names on entries. Multiple l names on entries. Symbolic links. Storage quotas. Removable devices. The backup procedures. Lots of developments in management of virtual memory including segmentation and paging. 5

6 Multics (3) Multics innovations (cont d) Separating the command shell from the OS kernel. Dynamic linking. Implementation of an OS in a high level language (PL/1) Management of shared memory. Mapping of logical disk volumes onto physical volumes. Many developments in the area of secure computer systems. Multics was rated B2 by the NCSC in A subsequent system (based on the Multics experience) built by Honeywell was the first computer system ever rated A1. 6

7 Multics (4) Multics innovations (cont d) Multics Relational Data Store (MRDS) in The first commercial relational DBMS. The MRDS query language was similar to early SQL. Concurrent access to a database by multiple processes was supported. The database could be backed up in its entirety. Spreadsheets were developed on the Multics platform. Multics supports BCPL, BASIC, APL, FORTRAN, LISP, C, COBOL, ALGOL 68, and Pascal. Many optimizations for the LISP language through work on the Multics MACLISP compiler. 7

8 Unix (1) When BTL (Bell Telephone Laboratories) withdrew from the Multics project, they needed to rewrite an operating system in order to play space war on another smaller machine (a DEC PDP-7 with 4K memory for user programs). The result was a system which a punning colleague called UNICS (UNiplexed Information and Computing Services) an emasculated Multics ; no one recalls whose idea the change to UNIX was. -- Peter H. Salus, A Quarter Century of Unix, Addision-Wesley, It was the summer of '69. In fact, my wife went on vacation to my family's place in California... I allocated a week each to the operating system, the shell, the editor, and the assembler to reproduce itself, and during the month she was gone, it was totally rewritten in a form that looked like an operating system, with tools that were sort of known, you know, assembler, editor, and shell... Yeh, essentially one person for a month. -- Ken Thompson 8

9 Unix (2) Unix Features Hierarchical file systems Special files: uniform I/O, naming, and protection. Removable file systems via mount/umount t i-node Process control fork(), exec(), wait(), exit() Pipes for inter-process communication Shells Standard I/O and I/O redirection Filters Command separators Shell scripts Signals 9

10 Unix (3) 10

11 Multics vs. Unix (1) Timing Multics: The system was made available for general use in Unix: 1969 Present Fourth Edition (1973): rewritten in C. Sixth Edition (1975): available outside of Bell Labs. Design approach Multics: Top-down Clear goals drive design and primitives. Unix: Bottom-up Primitives define functionality (No predefined goals), while retaining simplicity and elegance. 11

12 Multics vs. Unix (2) Development Multics: Well-organized: MIT Project MAC: Design is key strength. Bell Labs: Online update capabilities, robustness, scalability GE/Honeywell: Defense contractor, hardware page program module specification BEFORE coding. An unanticipated phase of design iterations was necessary due to gross discrepancies i between actual and expected performance.»design, build, evaluate, design, build, evaluate, $6M / year for five years. 150 Man-Years for design and system programming, another 50 Man-Years for improvements. 12

13 Multics vs. Unix (3) Development (cont d) Unix: Two Man-Years. Build/design i mixed at same time. Target users Multics: military, government agencies, NSA, Unix: Universities, research institutions, Protection Multics: Protection rings Unix: All or nothing (superuser model) 13

14 Multics vs. Unix (4) Resource utilization Multics: Memory: 256KWords/box (1 word = 36 bits) Paging device (Drum): 4MWords Disk: 136MB Unix: Old, unused PDP-7 Occupies 42KBytes on PDP-11/45 with 144KBytes of memory. PDP-11 has a 1MB disk used for file system storage and swapping. 14

15 Multics vs. Unix (5) Resource management Multics: Multiprocessor support from start. Transparent multi-level memory model: memory drum disk True memory-mapped mapped world view. Unix: Simple 3 segment view. Partial memory mapped model later. 15

16 Multics vs. Unix (6) Summary Multics: Too complicated, too costly hardware. Second system effect (by Fred Brooks, The Mythical Man-Month)» System one was successful (CTSS)» System two aims to correct all flaws from #1» Almost always fails. Unix: Low cost hardware University adoption Simplicity, elegance, and ease of use. 16

17 Operating System Structure (1) Monolithic The Big Mess - a single large software system. Local procedure calls are used to communicate among different components. API Advantages: performance Disadvantages: Monolithic Kernel Difficult to maintain and upgrade because of the interdependencies d i Hardware in the code. Operating system code runs at supervisor level in the same memory space so that any component of the system could corrupt data being used by other components. Unixware, Solaris, AIX, HP-UX, Linux, etc. 17

18 Operating System Structure (2) Layered A hierarchy of layers, each one constructed upon the one below it. The layered approach is modular; simplifies the extension and maintenance of the code base. THE (Dijkstra, 1968): 6 layers 18

19 Operating System Structure (3) Layered (cont d) Multics: 8 rings of protection The inner ones are more privileged than the outer ones. (The supervisor runs in ring 0) Calling a procedure in an inner ring requires a system call, where the parameters are carefully checked for validity. The ring mechanism is present at run time and enforced by the hardware.» The hardware made it possible to designate individual procedures (memory segments, actually) as protected against reading, writing, or executing. The ring mechanism can easily be extended to structure user subsystems. 19

20 Operating System Structure (4) Microkernel Move as much functionality as possible from the kernel into user space. Communication takes place between user modules using message passing. A request for an operating system service from an application is processed by the microkernel and forwarded to the appropriate server. The server handles the request est and passes the results back to the kernel, which forwards them to the calling application. i Client process Memory Server File Server Terminal Server Microkernel 20

21 Operating System Structure (5) Microkernel (cont d) The Mach kernel only includes: Thread scheduling Message passing Virtual memory Device driver code Microkernels Mach (CMU) OSF/1, NeXTSTEP, IBM OS/2, MkLinux, GNU Hurd, Microsoft Windows NT/XP, Mac OS X Chorus (INRIA, Chorus) Amoeba (Andrew Vrije Univ.) QNX L3/L4 (GMD, Jochen Univ. Karlsruhe) 21

22 Operating System Structure (6) Microkernel: Benefits Extensibility, Reliability, Simplicity, Maintainability, Flexibility Modular structure (easy to add services) Easing system design, implementation, and maintenance Failure isolation, enhancing debuggability and validation (small microkernel can be rigorously tested.) Coexistence of different APIs, file systems, and OS personalities. Portability Changes needed to port the system to a new processor is done in the microkernel not in the other services. Distributed system support Transparent access to network services, aiding and encouraging distribution. Object-oriented operating system Components are objects with clearly defined interfaces that can be interconnected to form software. 22

23 Operating System Structure (7) Linux Monolithic kernel + (layered) kernel modules System Calls Kernel extensions Monolithic Linux Kernel Device driver modules (cf.) Monolithic kernels vs. Microkernels: A debate between Linus Torvalds and Andrew Tanenbaum (1992) 23

24 Operating System Structure (8) Microsoft Windows NT/2000/XP Modified microkernels or hybrid kernels Keep some codes in kernel space to run them more quickly. 24

25 Operating System Structure (9) Mac OS X 25