Lecture
Operators and operating systems
Machines take over in batches ( data paper cards tapes moved around fed to reader)
Machines began to take over seeting the program counter to a new job, collecting the output, fetching memory... but it was still one job at a time.
one user, one program, one computer
dedicated -> just one job ( game typesetting)
-> programme know all details disk access
-> practically no op. sys needed
unix (mostly) to the desktop
|
|__ mainframe migrate
> several program
> networking
> GUIs
An operating system should have kernel (shell, sheield access to hardware, referee sharing); untilities (repair, maintain machine, list files, format disk)
one user, one program, one computer
dedicated -> just one job ( game typesetting)
-> programme know all details disk access
-> practically no op. sys needed
unix (mostly) to the desktop
|
|__ mainframe migrate
> several program
> networking
> GUIs
An operating system should have kernel (shell, sheield access to hardware, referee sharing); untilities (repair, maintain machine, list files, format disk)
No comments:
Post a Comment