Week 2 - Operating System Structures
Week 2 - Operating System Structures
SYSTEM
STRUCTURE
S
REMINDERS
Prelim
Examination
March 23,
2023
To describe the services that the OS
provides to users, processes and
OBJECTIVES other systems
USER INTERFACES
SYSTEM CALL
PROGRAM
SERVICES
COMMAND
INTERPRETE
• There are two-way to do it:
RS • The command interpreter itself contains the
code to execute the command
• The command interpreter does not
understand the command in any way and
merely uses the command to identify the file
to be loaded into memory and executed.
• Users employ a mouse-based window and
menu system characterized by a:
• Desktop
GRAPHICA
L USER
• Icons
INTERFAC • Folders
ES • Mobile Systems like smartphones and
tablets used touchscreen interfaces
instead of mouse due to impracticality.
• The choice of whether to use a command-line or GUI interface is mostly one
of personal preference
SYSTEM CALLS
SOURCE FILE DESTINATION FILE
open ()
User
Mode
SYSTEM CALL INTERFACE
Kernel
Mode open()
Implementation of
open() system call
.
.
.
return
TYPES OF
SYSTEM CALLS
• Process Control
• File Manipulation
• Device Manipulation
• Information Maintenance
• Communications
• Protection
• File Management
• Status Information
• File Modification
SYSTEM
PROGRAMS
• Programming Language Support
• Program Loading and execution
• Communication
• Background Services
SANITY
BREAK
We will resume by:
10:00 am
• Design Goals
• Mechanisms and Policies
OS Design
• Implementation
• Define Goals and Specification
LAYER 3
LAYER 2
LAYER 1
LAYER 0
MICROKERNELS
USER MODE
APPLICATION
PROGRAM FILE SYSTEM DEVICE DRIVER
MESSAGES MESSAGES
KERNEL MODE
INTERPROCESS MEMORY
CPU SCHEDULING
COMMUNICATION MANAGEMENT
MICROKERNEL
HARDWARE
MODULES
Scheduling
Classes
Loadable
File Systems
System Calls
Core
Kernel
Executable Device and
Formats Bus Drivers
STREAM Miscellaneou
Modules s Modules
• Most modern operating systems are actually not one pure
model
• Hybrid combines multiple approaches to address
performance, security, usability needs
• Linux and Solaris kernels in kernel address space, so
monolithic, plus modular for dynamic loading of
HYBRID functionality
Get If the process is generated successfully, get the process id and print it