SlideShare a Scribd company logo
Chapter 2: Operating-SystemChapter 2: Operating-System
StructuresStructures
2.2 Silberschatz, Galvin and GagneOperating System Concepts
Chapter 2: Operating-SystemChapter 2: Operating-System
StructuresStructures
Operating System Services
User Operating System Interface
System Calls
Types of System Calls
System Programs
Operating System Design and Implementation
Operating System Structure
Virtual Machines
Operating System Generation
System Boot
2.3 Silberschatz, Galvin and GagneOperating System Concepts
ObjectivesObjectives
To describe the services an operating system provides to users,
processes, and other systems
To discuss the various ways of structuring an operating system
To explain how operating systems are installed and customized
and how they boot
2.4 Silberschatz, Galvin and GagneOperating System Concepts
Operating System ServicesOperating System Services
One set of operating-system services provides functions that are
helpful to the user:
User interface - Almost all operating systems have a user interface (UI)
 Varies between Command-Line (CLI), Graphics User Interface (GUI),
Batch
Program execution - The system must be able to load a program into
memory and to run that program, end execution, either normally or
abnormally (indicating error)
I/O operations - A running program may require I/O, which may involve
a file or an I/O device.
File-system manipulation - The file system is of particular interest.
Obviously, programs need to read and write files and directories, create
and delete them, search them, list file Information, permission
management.
2.5 Silberschatz, Galvin and GagneOperating System Concepts
Operating System Services (Cont.)Operating System Services (Cont.)
One set of operating-system services provides functions that are
helpful to the user (Cont):
Communications – Processes may exchange information, on the same
computer or between computers over a network
 Communications may be via shared memory or through message
passing (packets moved by the OS)
Error detection – OS needs to be constantly aware of possible errors
 May occur in the CPU and memory hardware, in I/O devices, in user
program
 For each type of error, OS should take the appropriate action to
ensure correct and consistent computing
 Debugging facilities can greatly enhance the user’s and
programmer’s abilities to efficiently use the system
2.6 Silberschatz, Galvin and GagneOperating System Concepts
Operating System Services (Cont.)Operating System Services (Cont.)
Another set of OS functions exists for ensuring the efficient operation of the
system itself via resource sharing
Resource allocation - When multiple users or multiple jobs running
concurrently, resources must be allocated to each of them
 Many types of resources - Some (such as CPU cycles,mainmemory,
and file storage) may have special allocation code, others (such as I/O
devices) may have general request and release code.
Accounting - To keep track of which users use how much and what kinds
of computer resources
Protection and security - The owners of information stored in a
multiuser or networked computer system may want to control use of that
information, concurrent processes should not interfere with each other
 Protection involves ensuring that all access to system resources is
controlled
 Security of the system from outsiders requires user authentication,
extends to defending external I/O devices from invalid access attempts
 If a system is to be protected and secure, precautions must be
instituted throughout it. A chain is only as strong as its weakest link.
2.7 Silberschatz, Galvin and GagneOperating System Concepts
User Operating System Interface -User Operating System Interface -
CLICLI
CLI allows direct command entry
 Sometimes implemented in kernel, sometimes by systems
program
 Sometimes multiple flavors implemented – shells
 Primarily fetches a command from user and executes it
– Sometimes commands built-in, sometimes just names of
programs
» If the latter, adding new features doesn’t require shell
modification
2.8 Silberschatz, Galvin and GagneOperating System Concepts
User Operating System Interface -User Operating System Interface -
GUIGUI
User-friendly desktop metaphor interface
Usually mouse, keyboard, and monitor
Icons represent files, programs, actions, etc
Various mouse buttons over objects in the interface cause
various actions (provide information, options, execute function,
open directory (known as a folder)
Invented at Xerox PARC
Many systems now include both CLI and GUI interfaces
Microsoft Windows is GUI with CLI “command” shell
Apple Mac OS X as “Aqua” GUI interface with UNIX kernel
underneath and shells available
Solaris is CLI with optional GUI interfaces (Java Desktop, KDE)
2.9 Silberschatz, Galvin and GagneOperating System Concepts
System CallsSystem Calls
Programming interface to the services provided by the OS
Typically written in a high-level language (C or C++)
Mostly accessed by programs via a high-level Application
Program Interface (API) rather than direct system call use
Three most common APIs are Win32 API for Windows, POSIX API
for POSIX-based systems (including virtually all versions of UNIX,
Linux, and Mac OS X), and Java API for the Java virtual machine
(JVM)
Why use APIs rather than system calls?
(Note that the system-call names used throughout this text are
generic)
2.10 Silberschatz, Galvin and GagneOperating System Concepts
Example of System CallsExample of System Calls
System call sequence to copy the contents of one file to another file
2.11 Silberschatz, Galvin and GagneOperating System Concepts
Example of Standard APIExample of Standard API
Consider the ReadFile() function in the
Win32 API—a function for reading from a file
A description of the parameters passed to ReadFile()
HANDLE file—the file to be read
LPVOID buffer—a buffer where the data will be read into and written
from
DWORD bytesToRead—the number of bytes to be read into the buffer
LPDWORD bytesRead—the number of bytes read during the last read
LPOVERLAPPED ovl—indicates if overlapped I/O is being used
2.12 Silberschatz, Galvin and GagneOperating System Concepts
System Call ImplementationSystem Call Implementation
Typically, a number associated with each system call
System-call interface maintains a table indexed according to
these numbers
The system call interface invokes intended system call in OS kernel
and returns status of the system call and any return values
The caller need know nothing about how the system call is
implemented
Just needs to obey API and understand what OS will do as a
result call
Most details of OS interface hidden from programmer by API
 Managed by run-time support library (set of functions built
into libraries included with compiler)
2.13 Silberschatz, Galvin and GagneOperating System Concepts
API – System Call – OS RelationshipAPI – System Call – OS Relationship
2.14 Silberschatz, Galvin and GagneOperating System Concepts
Standard C Library ExampleStandard C Library Example
C program invoking printf() library call, which calls write() system call
2.15 Silberschatz, Galvin and GagneOperating System Concepts
System Call Parameter PassingSystem Call Parameter Passing
Often, more information is required than simply identity of desired
system call
Exact type and amount of information vary according to OS and
call
Three general methods used to pass parameters to the OS
Simplest: pass the parameters in registers
 In some cases, may be more parameters than registers
Parameters stored in a block, or table, in memory, and address
of block passed as a parameter in a register
 This approach taken by Linux and Solaris
Parameters placed, or pushed, onto the stack by the program
and popped off the stack by the operating system
Block and stack methods do not limit the number or length of
parameters being passed
2.16 Silberschatz, Galvin and GagneOperating System Concepts
Parameter Passing via TableParameter Passing via Table
2.17 Silberschatz, Galvin and GagneOperating System Concepts
Types of System CallsTypes of System Calls
Process control
File management
Device management
Information maintenance
Communications
2.18 Silberschatz, Galvin and GagneOperating System Concepts
MS-DOS executionMS-DOS execution
(a) At system startup (b) running a program
2.19 Silberschatz, Galvin and GagneOperating System Concepts
FreeBSD Running Multiple ProgramsFreeBSD Running Multiple Programs
2.20 Silberschatz, Galvin and GagneOperating System Concepts
System ProgramsSystem Programs
System programs provide a convenient environment for program
development and execution. The can be divided into:
File manipulation
Status information
File modification
Programming language support
Program loading and execution
Communications
Application programs
Most users’ view of the operation system is defined by system
programs, not the actual system calls
2.21 Silberschatz, Galvin and GagneOperating System Concepts
Solaris 10 dtrace Following SystemSolaris 10 dtrace Following System
CallCall
2.22 Silberschatz, Galvin and GagneOperating System Concepts
System ProgramsSystem Programs
Provide a convenient environment for program development and execution
Some of them are simply user interfaces to system calls; others are
considerably more complex
File management - Create, delete, copy, rename, print, dump, list, and
generally manipulate files and directories
Status information
Some ask the system for info - date, time, amount of available memory,
disk space, number of users
Others provide detailed performance, logging, and debugging
information
Typically, these programs format and print the output to the terminal or
other output devices
Some systems implement a registry - used to store and retrieve
configuration information
2.23 Silberschatz, Galvin and GagneOperating System Concepts
System Programs (cont’d)System Programs (cont’d)
File modification
Text editors to create and modify files
Special commands to search contents of files or perform
transformations of the text
Programming-language support - Compilers, assemblers,
debuggers and interpreters sometimes provided
Program loading and execution- Absolute loaders, relocatable
loaders, linkage editors, and overlay-loaders, debugging systems
for higher-level and machine language
Communications - Provide the mechanism for creating virtual
connections among processes, users, and computer systems
Allow users to send messages to one another’s screens,
browse web pages, send electronic-mail messages, log in
remotely, transfer files from one machine to another
2.24 Silberschatz, Galvin and GagneOperating System Concepts
Operating System Design andOperating System Design and
ImplementationImplementation
Design and Implementation of OS not “solvable”, but some
approaches have proven successful
Internal structure of different Operating Systems can vary widely
Start by defining goals and specifications
Affected by choice of hardware, type of system
User goals and System goals
User goals – operating system should be convenient to use,
easy to learn, reliable, safe, and fast
System goals – operating system should be easy to design,
implement, and maintain, as well as flexible, reliable, error-free,
and efficient
2.25 Silberschatz, Galvin and GagneOperating System Concepts
Operating System Design and ImplementationOperating System Design and Implementation
(Cont.)(Cont.)
Important principle to separate
Policy: What will be done?
Mechanism: How to do it?
Mechanisms determine how to do something, policies decide what
will be done
The separation of policy from mechanism is a very important
principle, it allows maximum flexibility if policy decisions are to
be changed later
2.26 Silberschatz, Galvin and GagneOperating System Concepts
Simple StructureSimple Structure
MS-DOS – written to provide the most functionality in the least
space
Not divided into modules
Although MS-DOS has some structure, its interfaces and levels
of functionality are not well separated
2.27 Silberschatz, Galvin and GagneOperating System Concepts
MS-DOS Layer StructureMS-DOS Layer Structure
2.28 Silberschatz, Galvin and GagneOperating System Concepts
Layered ApproachLayered Approach
The operating system is divided into a number of layers (levels),
each built on top of lower layers. The bottom layer (layer 0), is the
hardware; the highest (layer N) is the user interface.
With modularity, layers are selected such that each uses functions
(operations) and services of only lower-level layers
2.29 Silberschatz, Galvin and GagneOperating System Concepts
Layered Operating SystemLayered Operating System
2.30 Silberschatz, Galvin and GagneOperating System Concepts
UNIXUNIX
UNIX – limited by hardware functionality, the original UNIX operating
system had limited structuring. The UNIX OS consists of two
separable parts
Systems programs
The kernel
 Consists of everything below the system-call interface and
above the physical hardware
 Provides the file system, CPU scheduling, memory
management, and other operating-system functions; a large
number of functions for one level
2.31 Silberschatz, Galvin and GagneOperating System Concepts
UNIX System StructureUNIX System Structure
2.32 Silberschatz, Galvin and GagneOperating System Concepts
Microkernel System StructureMicrokernel System Structure
Moves as much from the kernel into “user” space
Communication takes place between user modules using message
passing
Benefits:
Easier to extend a microkernel
Easier to port the operating system to new architectures
More reliable (less code is running in kernel mode)
More secure
Detriments:
Performance overhead of user space to kernel space
communication
2.33 Silberschatz, Galvin and GagneOperating System Concepts
Mac OS X StructureMac OS X Structure
2.34 Silberschatz, Galvin and GagneOperating System Concepts
ModulesModules
Most modern operating systems implement kernel modules
Uses object-oriented approach
Each core component is separate
Each talks to the others over known interfaces
Each is loadable as needed within the kernel
Overall, similar to layers but with more flexible
2.35 Silberschatz, Galvin and GagneOperating System Concepts
Solaris Modular ApproachSolaris Modular Approach
2.36 Silberschatz, Galvin and GagneOperating System Concepts
Virtual MachinesVirtual Machines
A virtual machine takes the layered approach to its logical
conclusion. It treats hardware and the operating system
kernel as though they were all hardware
A virtual machine provides an interface identical to the
underlying bare hardware
The operating system creates the illusion of multiple
processes, each executing on its own processor with its own
(virtual) memory
2.37 Silberschatz, Galvin and GagneOperating System Concepts
Virtual Machines (Cont.)Virtual Machines (Cont.)
The resources of the physical computer are shared to create the
virtual machines
CPU scheduling can create the appearance that users have
their own processor
Spooling and a file system can provide virtual card readers and
virtual line printers
A normal user time-sharing terminal serves as the virtual
machine operator’s console
2.38 Silberschatz, Galvin and GagneOperating System Concepts
Virtual Machines (Cont.)Virtual Machines (Cont.)
(a) Nonvirtual machine (b) virtual machine
Non-virtual Machine Virtual Machine
2.39 Silberschatz, Galvin and GagneOperating System Concepts
Virtual MachinesVirtual Machines (Cont.)(Cont.)
The virtual-machine concept provides complete protection of system
resources since each virtual machine is isolated from all other virtual
machines. This isolation, however, permits no direct sharing of
resources.
A virtual-machine system is a perfect vehicle for operating-systems
research and development. System development is done on the
virtual machine, instead of on a physical machine and so does not
disrupt normal system operation.
The virtual machine concept is difficult to implement due to the effort
required to provide an exact duplicate to the underlying machine
2.40 Silberschatz, Galvin and GagneOperating System Concepts
VMware ArchitectureVMware Architecture
2.41 Silberschatz, Galvin and GagneOperating System Concepts
The Java Virtual MachineThe Java Virtual Machine
2.42 Silberschatz, Galvin and GagneOperating System Concepts
Operating System GenerationOperating System Generation
Operating systems are designed to run on any of a class of
machines; the system must be configured for each specific
computer site
SYSGEN program obtains information concerning the specific
configuration of the hardware system
Booting – starting a computer by loading the kernel
Bootstrap program – code stored in ROM that is able to locate the
kernel, load it into memory, and start its execution
2.43 Silberschatz, Galvin and GagneOperating System Concepts
System BootSystem Boot
Operating system must be made available to hardware so
hardware can start it
Small piece of code – bootstrap loader, locates the kernel,
loads it into memory, and starts it
Sometimes two-step process where boot block at fixed
location loads bootstrap loader
When power initialized on system, execution starts at a fixed
memory location
 Firmware used to hold initial boot code
End of Chapter 2End of Chapter 2

More Related Content

PDF
Operation system structure
PPTX
PPT
MELJUN CORTES operating_system_structure
PDF
Studying a decade of Linux system calls
PPT
Introduction to System Calls
PPT
Structure of operating system
PPT
WinCE
PPT
Unix.system.calls
Operation system structure
MELJUN CORTES operating_system_structure
Studying a decade of Linux system calls
Introduction to System Calls
Structure of operating system
WinCE
Unix.system.calls

What's hot (20)

PPTX
services and system calls of operating system
PPT
PPT
System call
PPTX
Unit 1 ppt
PDF
Ch2 operating-system structures
PPTX
System calls
PDF
Ch2
PPTX
System call
PPT
OPERATING SYSTEMS - INTRODUCTION
PDF
System calls
DOCX
Unix system calls
PDF
Operating System - Unit I - Introduction
PDF
System Calls
PPT
Installing driver
PDF
Part 04 Creating a System Call in Linux
PPT
OPERATING SYSTEMS DESIGN AND IMPLEMENTATION
PPTX
System program
PPTX
Windows Architecture Explained by Stacksol
services and system calls of operating system
System call
Unit 1 ppt
Ch2 operating-system structures
System calls
Ch2
System call
OPERATING SYSTEMS - INTRODUCTION
System calls
Unix system calls
Operating System - Unit I - Introduction
System Calls
Installing driver
Part 04 Creating a System Call in Linux
OPERATING SYSTEMS DESIGN AND IMPLEMENTATION
System program
Windows Architecture Explained by Stacksol
Ad

Viewers also liked (15)

PPT
MOBILE APPs DEVELOPMENT PLATFORMS
PPT
15.Security
PPT
9.Virtual Memory
PPT
1.introduction
DOC
HR QUESTIONS, INTERVIEW QUESTIONS
PDF
On-Demand Multicast Routing Protocol
PPT
Social Media and Web 2.0 for Emergency Medicine – the Luddiot’s guide
PPT
14.Protection
ODP
Adhoc routing protocols
PPTX
Ad network mediation guideline
PPT
5.CPU Scheduling
PPT
16.Distributed System Structure
PPT
wireless communication and networking Chapter 1
PDF
DSDV VS AODV
PPT
WAP- Wireless Application Protocol
MOBILE APPs DEVELOPMENT PLATFORMS
15.Security
9.Virtual Memory
1.introduction
HR QUESTIONS, INTERVIEW QUESTIONS
On-Demand Multicast Routing Protocol
Social Media and Web 2.0 for Emergency Medicine – the Luddiot’s guide
14.Protection
Adhoc routing protocols
Ad network mediation guideline
5.CPU Scheduling
16.Distributed System Structure
wireless communication and networking Chapter 1
DSDV VS AODV
WAP- Wireless Application Protocol
Ad

Similar to 2.Operating System Structures (20)

PPT
OS-ch02-part-1-2024.ppt
PDF
Prujisjkkbshshshshususueu7sis hshsyysususuus
PPT
Operating System- Structures of Operating System
PPTX
ch2- os.pptx
PPTX
Operating System Chapter Two Process Related Concepts
PDF
Operating System - Unit I - Operating System Structures
PPTX
Operating system structures
PDF
ch2_EN_BK.pdf
PPT
operating Systems Structures and functions
PPT
Operating-System Structures
PPT
PPT
ch2.ppt
PPT
PPT
ch2.ppt
PPT
PPT
process and threads in operating systems
PPT
chapter 2 operating systems galvin slides
PPT
operating system introduction to os1.ppt
OS-ch02-part-1-2024.ppt
Prujisjkkbshshshshususueu7sis hshsyysususuus
Operating System- Structures of Operating System
ch2- os.pptx
Operating System Chapter Two Process Related Concepts
Operating System - Unit I - Operating System Structures
Operating system structures
ch2_EN_BK.pdf
operating Systems Structures and functions
Operating-System Structures
ch2.ppt
ch2.ppt
process and threads in operating systems
chapter 2 operating systems galvin slides
operating system introduction to os1.ppt

More from Senthil Kanth (18)

PPT
Wireless Communication and Networking by WilliamStallings Chap2
PPT
WML Script by Shanti katta
PPT
What is WAP?
PPT
Introduction to Mobile Application Development
PPT
Markup Languages
PPT
Introduction to wireless application protocol (wap)ogi
PPT
XML Programming WML by Dickson K.W. Chiu PhD, SMIEEE
PPT
Wireless Application Protocol WAP by Alvinen
DOC
HR QUESTIONS
TXT
STOCK APPLICATION USING CORBA
DOC
RSA alogrithm
PDF
Zone Routing Protocol (ZRP)
PPT
13.IO systems
PPT
12.mass stroage system
PPT
11.file system implementation
PPT
10.file system interface
PPT
7.Dead Locks
PPT
6.Process Synchronization
Wireless Communication and Networking by WilliamStallings Chap2
WML Script by Shanti katta
What is WAP?
Introduction to Mobile Application Development
Markup Languages
Introduction to wireless application protocol (wap)ogi
XML Programming WML by Dickson K.W. Chiu PhD, SMIEEE
Wireless Application Protocol WAP by Alvinen
HR QUESTIONS
STOCK APPLICATION USING CORBA
RSA alogrithm
Zone Routing Protocol (ZRP)
13.IO systems
12.mass stroage system
11.file system implementation
10.file system interface
7.Dead Locks
6.Process Synchronization

Recently uploaded (20)

PPTX
Tissue processing ( HISTOPATHOLOGICAL TECHNIQUE
PDF
A systematic review of self-coping strategies used by university students to ...
PDF
3rd Neelam Sanjeevareddy Memorial Lecture.pdf
PDF
grade 11-chemistry_fetena_net_5883.pdf teacher guide for all student
PDF
Module 4: Burden of Disease Tutorial Slides S2 2025
PDF
Chinmaya Tiranga quiz Grand Finale.pdf
PDF
Computing-Curriculum for Schools in Ghana
PPTX
IMMUNITY IMMUNITY refers to protection against infection, and the immune syst...
PDF
Chapter 2 Heredity, Prenatal Development, and Birth.pdf
PPTX
Pharma ospi slides which help in ospi learning
PPTX
Cell Structure & Organelles in detailed.
PDF
01-Introduction-to-Information-Management.pdf
PDF
FourierSeries-QuestionsWithAnswers(Part-A).pdf
PDF
RMMM.pdf make it easy to upload and study
PDF
Black Hat USA 2025 - Micro ICS Summit - ICS/OT Threat Landscape
PDF
Supply Chain Operations Speaking Notes -ICLT Program
PPTX
Presentation on HIE in infants and its manifestations
PPTX
202450812 BayCHI UCSC-SV 20250812 v17.pptx
PPTX
Cell Types and Its function , kingdom of life
PPTX
Institutional Correction lecture only . . .
Tissue processing ( HISTOPATHOLOGICAL TECHNIQUE
A systematic review of self-coping strategies used by university students to ...
3rd Neelam Sanjeevareddy Memorial Lecture.pdf
grade 11-chemistry_fetena_net_5883.pdf teacher guide for all student
Module 4: Burden of Disease Tutorial Slides S2 2025
Chinmaya Tiranga quiz Grand Finale.pdf
Computing-Curriculum for Schools in Ghana
IMMUNITY IMMUNITY refers to protection against infection, and the immune syst...
Chapter 2 Heredity, Prenatal Development, and Birth.pdf
Pharma ospi slides which help in ospi learning
Cell Structure & Organelles in detailed.
01-Introduction-to-Information-Management.pdf
FourierSeries-QuestionsWithAnswers(Part-A).pdf
RMMM.pdf make it easy to upload and study
Black Hat USA 2025 - Micro ICS Summit - ICS/OT Threat Landscape
Supply Chain Operations Speaking Notes -ICLT Program
Presentation on HIE in infants and its manifestations
202450812 BayCHI UCSC-SV 20250812 v17.pptx
Cell Types and Its function , kingdom of life
Institutional Correction lecture only . . .

2.Operating System Structures

  • 1. Chapter 2: Operating-SystemChapter 2: Operating-System StructuresStructures
  • 2. 2.2 Silberschatz, Galvin and GagneOperating System Concepts Chapter 2: Operating-SystemChapter 2: Operating-System StructuresStructures Operating System Services User Operating System Interface System Calls Types of System Calls System Programs Operating System Design and Implementation Operating System Structure Virtual Machines Operating System Generation System Boot
  • 3. 2.3 Silberschatz, Galvin and GagneOperating System Concepts ObjectivesObjectives To describe the services an operating system provides to users, processes, and other systems To discuss the various ways of structuring an operating system To explain how operating systems are installed and customized and how they boot
  • 4. 2.4 Silberschatz, Galvin and GagneOperating System Concepts Operating System ServicesOperating System Services One set of operating-system services provides functions that are helpful to the user: User interface - Almost all operating systems have a user interface (UI)  Varies between Command-Line (CLI), Graphics User Interface (GUI), Batch Program execution - The system must be able to load a program into memory and to run that program, end execution, either normally or abnormally (indicating error) I/O operations - A running program may require I/O, which may involve a file or an I/O device. File-system manipulation - The file system is of particular interest. Obviously, programs need to read and write files and directories, create and delete them, search them, list file Information, permission management.
  • 5. 2.5 Silberschatz, Galvin and GagneOperating System Concepts Operating System Services (Cont.)Operating System Services (Cont.) One set of operating-system services provides functions that are helpful to the user (Cont): Communications – Processes may exchange information, on the same computer or between computers over a network  Communications may be via shared memory or through message passing (packets moved by the OS) Error detection – OS needs to be constantly aware of possible errors  May occur in the CPU and memory hardware, in I/O devices, in user program  For each type of error, OS should take the appropriate action to ensure correct and consistent computing  Debugging facilities can greatly enhance the user’s and programmer’s abilities to efficiently use the system
  • 6. 2.6 Silberschatz, Galvin and GagneOperating System Concepts Operating System Services (Cont.)Operating System Services (Cont.) Another set of OS functions exists for ensuring the efficient operation of the system itself via resource sharing Resource allocation - When multiple users or multiple jobs running concurrently, resources must be allocated to each of them  Many types of resources - Some (such as CPU cycles,mainmemory, and file storage) may have special allocation code, others (such as I/O devices) may have general request and release code. Accounting - To keep track of which users use how much and what kinds of computer resources Protection and security - The owners of information stored in a multiuser or networked computer system may want to control use of that information, concurrent processes should not interfere with each other  Protection involves ensuring that all access to system resources is controlled  Security of the system from outsiders requires user authentication, extends to defending external I/O devices from invalid access attempts  If a system is to be protected and secure, precautions must be instituted throughout it. A chain is only as strong as its weakest link.
  • 7. 2.7 Silberschatz, Galvin and GagneOperating System Concepts User Operating System Interface -User Operating System Interface - CLICLI CLI allows direct command entry  Sometimes implemented in kernel, sometimes by systems program  Sometimes multiple flavors implemented – shells  Primarily fetches a command from user and executes it – Sometimes commands built-in, sometimes just names of programs » If the latter, adding new features doesn’t require shell modification
  • 8. 2.8 Silberschatz, Galvin and GagneOperating System Concepts User Operating System Interface -User Operating System Interface - GUIGUI User-friendly desktop metaphor interface Usually mouse, keyboard, and monitor Icons represent files, programs, actions, etc Various mouse buttons over objects in the interface cause various actions (provide information, options, execute function, open directory (known as a folder) Invented at Xerox PARC Many systems now include both CLI and GUI interfaces Microsoft Windows is GUI with CLI “command” shell Apple Mac OS X as “Aqua” GUI interface with UNIX kernel underneath and shells available Solaris is CLI with optional GUI interfaces (Java Desktop, KDE)
  • 9. 2.9 Silberschatz, Galvin and GagneOperating System Concepts System CallsSystem Calls Programming interface to the services provided by the OS Typically written in a high-level language (C or C++) Mostly accessed by programs via a high-level Application Program Interface (API) rather than direct system call use Three most common APIs are Win32 API for Windows, POSIX API for POSIX-based systems (including virtually all versions of UNIX, Linux, and Mac OS X), and Java API for the Java virtual machine (JVM) Why use APIs rather than system calls? (Note that the system-call names used throughout this text are generic)
  • 10. 2.10 Silberschatz, Galvin and GagneOperating System Concepts Example of System CallsExample of System Calls System call sequence to copy the contents of one file to another file
  • 11. 2.11 Silberschatz, Galvin and GagneOperating System Concepts Example of Standard APIExample of Standard API Consider the ReadFile() function in the Win32 API—a function for reading from a file A description of the parameters passed to ReadFile() HANDLE file—the file to be read LPVOID buffer—a buffer where the data will be read into and written from DWORD bytesToRead—the number of bytes to be read into the buffer LPDWORD bytesRead—the number of bytes read during the last read LPOVERLAPPED ovl—indicates if overlapped I/O is being used
  • 12. 2.12 Silberschatz, Galvin and GagneOperating System Concepts System Call ImplementationSystem Call Implementation Typically, a number associated with each system call System-call interface maintains a table indexed according to these numbers The system call interface invokes intended system call in OS kernel and returns status of the system call and any return values The caller need know nothing about how the system call is implemented Just needs to obey API and understand what OS will do as a result call Most details of OS interface hidden from programmer by API  Managed by run-time support library (set of functions built into libraries included with compiler)
  • 13. 2.13 Silberschatz, Galvin and GagneOperating System Concepts API – System Call – OS RelationshipAPI – System Call – OS Relationship
  • 14. 2.14 Silberschatz, Galvin and GagneOperating System Concepts Standard C Library ExampleStandard C Library Example C program invoking printf() library call, which calls write() system call
  • 15. 2.15 Silberschatz, Galvin and GagneOperating System Concepts System Call Parameter PassingSystem Call Parameter Passing Often, more information is required than simply identity of desired system call Exact type and amount of information vary according to OS and call Three general methods used to pass parameters to the OS Simplest: pass the parameters in registers  In some cases, may be more parameters than registers Parameters stored in a block, or table, in memory, and address of block passed as a parameter in a register  This approach taken by Linux and Solaris Parameters placed, or pushed, onto the stack by the program and popped off the stack by the operating system Block and stack methods do not limit the number or length of parameters being passed
  • 16. 2.16 Silberschatz, Galvin and GagneOperating System Concepts Parameter Passing via TableParameter Passing via Table
  • 17. 2.17 Silberschatz, Galvin and GagneOperating System Concepts Types of System CallsTypes of System Calls Process control File management Device management Information maintenance Communications
  • 18. 2.18 Silberschatz, Galvin and GagneOperating System Concepts MS-DOS executionMS-DOS execution (a) At system startup (b) running a program
  • 19. 2.19 Silberschatz, Galvin and GagneOperating System Concepts FreeBSD Running Multiple ProgramsFreeBSD Running Multiple Programs
  • 20. 2.20 Silberschatz, Galvin and GagneOperating System Concepts System ProgramsSystem Programs System programs provide a convenient environment for program development and execution. The can be divided into: File manipulation Status information File modification Programming language support Program loading and execution Communications Application programs Most users’ view of the operation system is defined by system programs, not the actual system calls
  • 21. 2.21 Silberschatz, Galvin and GagneOperating System Concepts Solaris 10 dtrace Following SystemSolaris 10 dtrace Following System CallCall
  • 22. 2.22 Silberschatz, Galvin and GagneOperating System Concepts System ProgramsSystem Programs Provide a convenient environment for program development and execution Some of them are simply user interfaces to system calls; others are considerably more complex File management - Create, delete, copy, rename, print, dump, list, and generally manipulate files and directories Status information Some ask the system for info - date, time, amount of available memory, disk space, number of users Others provide detailed performance, logging, and debugging information Typically, these programs format and print the output to the terminal or other output devices Some systems implement a registry - used to store and retrieve configuration information
  • 23. 2.23 Silberschatz, Galvin and GagneOperating System Concepts System Programs (cont’d)System Programs (cont’d) File modification Text editors to create and modify files Special commands to search contents of files or perform transformations of the text Programming-language support - Compilers, assemblers, debuggers and interpreters sometimes provided Program loading and execution- Absolute loaders, relocatable loaders, linkage editors, and overlay-loaders, debugging systems for higher-level and machine language Communications - Provide the mechanism for creating virtual connections among processes, users, and computer systems Allow users to send messages to one another’s screens, browse web pages, send electronic-mail messages, log in remotely, transfer files from one machine to another
  • 24. 2.24 Silberschatz, Galvin and GagneOperating System Concepts Operating System Design andOperating System Design and ImplementationImplementation Design and Implementation of OS not “solvable”, but some approaches have proven successful Internal structure of different Operating Systems can vary widely Start by defining goals and specifications Affected by choice of hardware, type of system User goals and System goals User goals – operating system should be convenient to use, easy to learn, reliable, safe, and fast System goals – operating system should be easy to design, implement, and maintain, as well as flexible, reliable, error-free, and efficient
  • 25. 2.25 Silberschatz, Galvin and GagneOperating System Concepts Operating System Design and ImplementationOperating System Design and Implementation (Cont.)(Cont.) Important principle to separate Policy: What will be done? Mechanism: How to do it? Mechanisms determine how to do something, policies decide what will be done The separation of policy from mechanism is a very important principle, it allows maximum flexibility if policy decisions are to be changed later
  • 26. 2.26 Silberschatz, Galvin and GagneOperating System Concepts Simple StructureSimple Structure MS-DOS – written to provide the most functionality in the least space Not divided into modules Although MS-DOS has some structure, its interfaces and levels of functionality are not well separated
  • 27. 2.27 Silberschatz, Galvin and GagneOperating System Concepts MS-DOS Layer StructureMS-DOS Layer Structure
  • 28. 2.28 Silberschatz, Galvin and GagneOperating System Concepts Layered ApproachLayered Approach The operating system is divided into a number of layers (levels), each built on top of lower layers. The bottom layer (layer 0), is the hardware; the highest (layer N) is the user interface. With modularity, layers are selected such that each uses functions (operations) and services of only lower-level layers
  • 29. 2.29 Silberschatz, Galvin and GagneOperating System Concepts Layered Operating SystemLayered Operating System
  • 30. 2.30 Silberschatz, Galvin and GagneOperating System Concepts UNIXUNIX UNIX – limited by hardware functionality, the original UNIX operating system had limited structuring. The UNIX OS consists of two separable parts Systems programs The kernel  Consists of everything below the system-call interface and above the physical hardware  Provides the file system, CPU scheduling, memory management, and other operating-system functions; a large number of functions for one level
  • 31. 2.31 Silberschatz, Galvin and GagneOperating System Concepts UNIX System StructureUNIX System Structure
  • 32. 2.32 Silberschatz, Galvin and GagneOperating System Concepts Microkernel System StructureMicrokernel System Structure Moves as much from the kernel into “user” space Communication takes place between user modules using message passing Benefits: Easier to extend a microkernel Easier to port the operating system to new architectures More reliable (less code is running in kernel mode) More secure Detriments: Performance overhead of user space to kernel space communication
  • 33. 2.33 Silberschatz, Galvin and GagneOperating System Concepts Mac OS X StructureMac OS X Structure
  • 34. 2.34 Silberschatz, Galvin and GagneOperating System Concepts ModulesModules Most modern operating systems implement kernel modules Uses object-oriented approach Each core component is separate Each talks to the others over known interfaces Each is loadable as needed within the kernel Overall, similar to layers but with more flexible
  • 35. 2.35 Silberschatz, Galvin and GagneOperating System Concepts Solaris Modular ApproachSolaris Modular Approach
  • 36. 2.36 Silberschatz, Galvin and GagneOperating System Concepts Virtual MachinesVirtual Machines A virtual machine takes the layered approach to its logical conclusion. It treats hardware and the operating system kernel as though they were all hardware A virtual machine provides an interface identical to the underlying bare hardware The operating system creates the illusion of multiple processes, each executing on its own processor with its own (virtual) memory
  • 37. 2.37 Silberschatz, Galvin and GagneOperating System Concepts Virtual Machines (Cont.)Virtual Machines (Cont.) The resources of the physical computer are shared to create the virtual machines CPU scheduling can create the appearance that users have their own processor Spooling and a file system can provide virtual card readers and virtual line printers A normal user time-sharing terminal serves as the virtual machine operator’s console
  • 38. 2.38 Silberschatz, Galvin and GagneOperating System Concepts Virtual Machines (Cont.)Virtual Machines (Cont.) (a) Nonvirtual machine (b) virtual machine Non-virtual Machine Virtual Machine
  • 39. 2.39 Silberschatz, Galvin and GagneOperating System Concepts Virtual MachinesVirtual Machines (Cont.)(Cont.) The virtual-machine concept provides complete protection of system resources since each virtual machine is isolated from all other virtual machines. This isolation, however, permits no direct sharing of resources. A virtual-machine system is a perfect vehicle for operating-systems research and development. System development is done on the virtual machine, instead of on a physical machine and so does not disrupt normal system operation. The virtual machine concept is difficult to implement due to the effort required to provide an exact duplicate to the underlying machine
  • 40. 2.40 Silberschatz, Galvin and GagneOperating System Concepts VMware ArchitectureVMware Architecture
  • 41. 2.41 Silberschatz, Galvin and GagneOperating System Concepts The Java Virtual MachineThe Java Virtual Machine
  • 42. 2.42 Silberschatz, Galvin and GagneOperating System Concepts Operating System GenerationOperating System Generation Operating systems are designed to run on any of a class of machines; the system must be configured for each specific computer site SYSGEN program obtains information concerning the specific configuration of the hardware system Booting – starting a computer by loading the kernel Bootstrap program – code stored in ROM that is able to locate the kernel, load it into memory, and start its execution
  • 43. 2.43 Silberschatz, Galvin and GagneOperating System Concepts System BootSystem Boot Operating system must be made available to hardware so hardware can start it Small piece of code – bootstrap loader, locates the kernel, loads it into memory, and starts it Sometimes two-step process where boot block at fixed location loads bootstrap loader When power initialized on system, execution starts at a fixed memory location  Firmware used to hold initial boot code
  • 44. End of Chapter 2End of Chapter 2