EVOLUTION OF OPERATING SYSTEM

The History of OS is linked with the development of various computer generations, which were marked by

Change in Hardware Technology Need for Faster Processing Power Resource sharing between multiple users Networking capabilities

Operating systems and computer architecture have a great deal of influence on each other.

THE ZEROTH GENERATION

Referred to the period of development of computing Emergence of the electronic digital computers in 1940s Electronic Discrete Variable Automatic Computer(EDVAC) first to fully implement the idea of the stored program and serial execution of instructions without benefit of an actual operating system Programs were written in machine language and contained code for initiating operation of the computer itself

THE FIRST GENERATION (1951-1956)

Beginning of commercial computing. Some of its limitations were;

Application programs were run one at a time and were translated with absolute computer addresses run from these pre assigned storage addresses set by the translator no provision for moving a program to a different location in storage

These inefficiencies led to the development of the mono

programmed operating system, The OS consisted of

a permanently resident kernel in main storage, a job scheduler a number of utility programs kept in secondary storage.

The systems were designed to be operated as batch processing system, but in sequential manner Several problems

inefficient use of system resources Weak system protection

THE SECOND GENERATION (1956-1964)

(Batch Operating Systems)

Continued with mono programmed batch processing operating systems, but various other innovations in it The most significant innovations introduction of the data channel

addressed the problem of excessive central processor delay due to waiting for input/output operations process input/output operations asynchronously allowed some I/O to be buffered

Introduction of Interrupt from data channel to CPU Introduction of interval clocks OS can regain control of exceptionally long or indefinitely looping program Researchers began to experiment with multiprogramming and multiprocessing, e.g. Compatible Time Sharing System (CTSS)

THE THIRD GENERATION (1964-1979)

(Multiprogramming and Time Sharing Systems)

Officially began in April 1964 with IBMs announcement of its IBM OS /360 system Introduction and adoption of multiprogramming More sophisticated I/O buffering

E.g. the HASP (Houston Automatic Spooling) system that accompanied the IBM OS/360 system Taking fuller advantage of the computers data channel, I/O capabilities

Introduction of two new systems programs

a system reader - to move input jobs from cards to disk a system writer - to move job output from disk to printer, tape, or cards

Time sharing and resource utilization Concurrent operation of three programs required that additional features and complexity be added to the OS. An increase in system throughput and resource utilization

THE FOURTH GENERATION (1980 2000S)

(Personal Computers and Workstations)

Characterized by the development of OS for personal computer and the workstation. In 1981 IBM introduced its first computer for the home user with MS-DOS 1.0 as OS , and in 1984 Apple introduced the Macintosh with Mac OS. Concept of "virtual computers" - the open shop type of environment where each user occupies an entire computer for the duration of a jobs execution. OS supporting GUIs, the mouse and hand held devices. Operating system augmented with communication capabilities that enable users to remotely log into any system on the network and transfer information among machines that are connected to the network. Network connectivity eventually led to the development of the Internet

UNIX OS EVOLUTION

ANDRIOD ARCHITECTURE

KEY CONSTRAINTS FOR MOBILE OS MULTI-TASKING

Mobile devices don't have the luxury of swap space, so have fairly hard limits on memory use. We did not want to require that users close applications when "done" with them. Such a usage pattern does not work well in a mobile environment, where usage tends to involve repeated brief contact with a wide variety of applications throughout the day. Application switching on a mobile device is extremely critical; we target significantly less than 1 second to launch a new application. This is especially important when the user is switching between a few applications, such as switching to look at a new SMS message while watching a video, and then returning to that video The available APIs must be sufficient for writing the built-in Google applications. This means background music playback, data syncing, GPS navigation, and application downloading must be implemented with the same APIs that are available to third party developers.

LIFESYCLE OF ANDRIOD APPLICATION

Lifescycle - The steps that an application goes through from starting to finishing An Android application is a collection of activities, an activity correlates to a screen or form that is presented to the user. Each application runs in its own process. Processes are started and stopped as needed to run an apps components. Processes may be killed to reclaim needed resources.

ACTIVITY MANAGEMENT

Eg. a. Live wallpapers are a service started by Android when selected by the user. b. Sync adapters introduced in Android 2.0 are services that are run in the background when a particular data sync needs to be performed.