Early Computers

Evolution of Operating Systems

No Operating Systems y Monitors y Simple Batch Systems y Multiprogrammed Batch Systems. y Time Sharing Systems
y

No Operating Systems
Each Program directly interfaced with the hardware. y One Person used the computer at a time. y Job Scheduling was done with the help of clipboard. y Library of commonly used procedures were the first start of OS.
y

EARLY SYSTEMS

Single user, programmer and operator y Manual loading from front panel control y Do whatever you want : halt program, examine register, change memory content
y

Problems : y Difficult to use y Gross waste of computing power, block time booking y Job set up time Development needed : y Device driver, compiler, high level languages

SIMPLE MONITOR
Avoid expensive CPU idle most of the time, get high utilization rate y Professional operator y Batching of jobs
y

Program errors/job failure : y operator takes memory/registers dump and start next job y waste of CPU time during the transition from one job to the next Development needed : y Automatic job sequencing y Resident Monitor y Evolution of control cards (JCL): To distinguish between jobs, and between data and program y Batch systems

Memory layout for a resident monitor

Simple Batch Systems

User Submitted Job (written on punched cards) to the computer. y The OS would copy the input data to o disk. y When a job completed, the OS would select one of the jobs from the disk and run it. y Printed output from the job was written to the disk. When the program terminated, the output file was copied to printer.
y

UNIUNI- PROGRAMMING (Single Program Execution)

Offline operation to compensate difference between CPU and I/O device speed y SPOOLING (Simultaneous Peripheral Operation On-line) y use disk as buffer y while computing one job, the computer will read in another job and print the third job y overlap I/O for a no. of jobs
y

Multi Programming
Ability to load a no. of programs with CPU switching from one another y Several programs had to be kept in RAM at the same time, each protected from the other. y The OS had to be able to switch user environment to another. y Relied on hardware that support I/O interrupts and DMA.
y

Requires: y protection for different users (memory & files), y concurrency control y memory management policies y process scheduling

Scheduling
Key to multi-programming y Long term y Medium term y Short term y I/O
y

Long Term Scheduling

y

Determines which programs are submitted for processing i.e. controls the degree of multi-programming Once submitted, a job becomes a process for the short term scheduler (or it becomes a swapped out job for the medium term scheduler)

Medium Term Scheduling

Part of the swapping function y Usually based on the need to manage multi-programming y If no virtual memory, memory management is also an issue
y

Desirable Hardware Features

y

Memory Protection
Do not allow the memory area containing the monitor to be altered.

Timer
Prevents a job from monopolizing the system. An interrupt occurs when time expires

y y

Privileged instructions
Executed only by the monitor

Interrupts
Provides flexibility for controlling user programs

TIME SHARING
Using multiprogramming to handle multiple interactive jobs. y Processors time is shared among multiple users. y Multiple users simultaneously access the system through terminals y A new control language was required for interactive work.
y

REALREAL-TIME SYSTEM
Characterized by processing activity triggered by external events y The processing of each task must be completed within a rigid time constraints y Responsiveness to the environment is more important than the utilization of resources y Usually used to monitor production lines, control continuous processes, etc.
y

DISTRIBUTED SYSTEMS
Loosely coupled system y separate memory , OS connected via communication link or bus y Total transparency to user y Jobs can be performed in different systems determined by the system y File locations are determined by the system
y

Adv. : y better price/performance than mainframes y if one machine crashes, the system as a whole can still survive y computing power can be added in small increments Disadv. : y little commercial software exists as present y network may cause problems y easy access and subjected to secure threats & attack

Multi Processing
Systems with more than one processor require : y interprocessor communication y more complicated process scheduling y parallel processing synchronization Tightly coupled system y sharing the computer bus, the clock, memory and peripherals y single O.S.

Clusters y multiple O.S. Massive Parallel (MPP) Systems y large no. of processors y super computers y transputers y Used for fault tolerant, backup & standby, load sharing

Memory Organization
Early computers did not have cache or Virtual Memory. Cache has little impact on the OS. y Some early machines had two types of RAM. The OS moved jobs between the fast and the slow RAMS
y y

(Pakaya hai.)

Virtual Memory
The IBM/370 introduced Virtual memory. y Intel 386 provided virtual memory support y The OS has to move pages between RAM and disk y The OS has to maintain the page tables and addressing environment.
y

HISTORICAL DEVELOPMENT
PAST MAINFRAME 1950 No software Compilers Resident Monitors Batch 1960 Time- sharing Multi-user (Multics, OS/360) 1970 Multi- processing MINI MICRO

1980 Networking 1990 Distributed Systems

No software Compilers Resident Monitors Time-sharing No software Multi-user (Unix) Compilers Resident Monitors Single User (CP/M, DOS) Networking Mulit-tasking Distributed Multi-user (Workstations)

FUTURE
Fully Distributed Systems y Embedded Systems y Massive Parallel Processors, National Grip Systems
y

(KUCH BHI DAAL)

Windows and UNIXAAge UNIXAAge