Napredni operativni sistemi

UNIX, Linux i Android

Prof. dr Dragan Stojanović

Katedra za računarstvo
Elektronski fakultet u Nišu

Napredni operativni sistemi

Prof. dr Dragan Stojanović Računarstvo i informatika
 UNIX, Linux, and Android

Chapter 10

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 History of UNIX and Linux
• UNICS
• PDP-11 UNIX
• Portable UNIX
• Berkeley UNIX
• Standard UNIX
• MINIX
• Linux

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Linux Goals

• Simplicity, elegance, consistency

• Power and flexibility
• Lack of useless redundancy

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Interfaces to Linux

Figure 10-1. The layers in a Linux system.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 The Shell
• Command line interface
– Faster
– More powerful
– Easily extensible
• First word entered will be a program name
– Commands take arguments
– Wild card characters used
– Filters, pipes used
• Shell scripts
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Linux Utility Programs (1)
1. File and directory manipulation commands.
2. Filters.
3. Program development tools, such as editors
and compilers.
4. Text processing.
5. System administration.
6. Miscellaneous.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Linux Utility
Programs (2)

Figure 10-2. A few of the

common Linux utility
programs required by
POSIX.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Kernel Structure

Figure 10-3. Structure of the Linux kernel

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Processes: Fundamental Concepts (1)

Figure 10-4. Process creation in Linux.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Processes: Fundamental Concepts (2)

Figure 10-5. Some of the signals required by POSIX.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Process Management
System Calls in Linux (1)

Figure 10-6. Some system calls relating to processes. The return

code s is −1 if an error has occurred, pid is a process ID, and
residual is the remaining time in the previous alarm. The
parameters are what the names suggest.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Process Management
System Calls in Linux (2)

Figure 10-7. A highly simplified shell.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Implementation of Processes and
Threads in Linux (1)
Process descriptors
1. Scheduling parameters
2. Memory image
3. Signals
4. Machine registers
5. System call state
6. File descriptor table
7. Accounting
8. Kernel stack
9. Miscellaneous
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Implementation of Processes and
Threads in Linux (2)

Figure 10-8. The steps in executing the

command ls typed to the shell.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Threads in Linux

Figure 10-9. Bits in the sharing flags bitmap.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Scheduling in Linux (1)

Three classes of threads for scheduling

purposes:
1. Real-time FIFO.
2. Real-time round robin.
3. Timesharing.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Scheduling in
Linux (2)

Figure 10-10. Illustration of

Linux run queue data
structures for (a) the Linux
O(1) scheduler

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Scheduling in Linux (3)

Figure 10-10. Illustration of Linux run queue data structures

for (b) the Completely Fair Scheduler
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Booting Linux

Figure 10-11. The sequence of processes used

to boot some Linux systems.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Memory Management
Fundamental Concepts (1)

Figure 10-12. (a) Process A’s virtual address space.

(b) Physical memory. (c) Process B’s virtual address space.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Memory Management
Fundamental Concepts (2)

Figure 10-13. Two processes can share a mapped file.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Memory Management
System Calls in Linux

Figure 10-14. Some system calls relating to memory

management. The return code s is −1 if an error has
occurred; a and addr are memory addresses, len is a length,
prot controls protection, flags are miscellaneous bits, fd is a
file descriptor, and offset is a file offset.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Physical Memory Management (1)

Linux Memory Zones:

1. ZONE_DMA and ZONE_DMA32
2. ZONE_NORMAL
3. ZONE_HIGHMEM

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Physical Memory Management (2)

Figure 10-15. Linux main memory representation.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Physical Memory Management (3)

Figure 10-16. Linux uses four-level page tables.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Memory Allocation Mechanisms

Figure 10-17. Operation of the buddy algorithm

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
The Page Replacement Algorithm

Figure 10-18. Page states considered in the

page frame replacement algorithm.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
I/O in Linux – Networking (1)

Figure 10-19. The uses of sockets for networking

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 I/O in Linux – Networking (2)

Common socket types:

1. Reliable connection-oriented byte stream.
2. Reliable connection-oriented packet stream.
3. Unreliable packet transmission.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Input/Output System Calls in Linux

Figure 10-20. The main POSIX calls

for managing the terminal.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Implementation of I/O in Linux (1)

Figure 10-21. Some of the file operations supported for

typical character devices.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Implementation of I/O in Linux (2)

Figure 10-22. The Linux I/O system showing

one file system in detail.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Linux File System:
Fundamental Concepts (1)

Figure 10-23. Some important directories

found in most Linux systems.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Linux File System:
Fundamental Concepts (2)

Figure 10-24. (a) Before linking. (b) After linking.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Linux File System:
Fundamental Concepts (3)

Figure 10-25. (a) Separate file systems. (b) After mounting.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Linux File System:
Fundamental Concepts (4)

Figure 10-26. (a) A file with one lock.

(b) Addition of a second lock. (c) A third lock.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 File System Calls in Linux (1)

Figure 10-27. Some system calls relating to files. The return code s
is −1 if an error has occurred; fd is a file descriptor, and position is
a file offset. The parameters should be self explanatory.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 File System Calls in Linux (2)

Figure 10-28. The fields returned by the stat system call.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 File System Calls in Linux (3)

Figure 10-29. Some system calls relating to directories. The

return code s is −1 if an error has occurred; dir identifies a
directory stream, and dirent is a directory entry. The
parameters should be self explanatory.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 The Linux Virtual File System

Figure 10-30. File system abstractions supported by the VFS.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
The Linux Ext2 File System (1)

Figure 10-31. Disk layout of the Linux ext2 file system.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 The Linux Ext2 File System (2)

Figure 10-32. (a) A Linux directory with three files. (b) The
same directory after the file voluminous has been removed.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
The Linux Ext2 File System (3)

10-33. Some fields in the i-node structure in Linux

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 The Linux Ext2
File System (4)

Figure 10-34. The

relation between the
file descriptor table,
the open file
description table, and
the i-node table.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 NFS Architecture

Figure 10-35. Examples of remote mounted file systems.

Directories are shown as squares and files are shown as circles.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 NFS Implementation

Figure 10-36. The NFS layer structure

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Linux Security
Fundamental Concepts

Figure 10-37. Some example file protection modes.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Security System Calls in Linux

Figure 10-38. Some system calls relating to security. The return

code s is −1 if an error has occurred; uid and gid are the UID and
GID, respectively. The parameters should be self explanatory.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Android – Design Goals
1. Open-source platform for mobile devices
2. Support 3rd party apps with robust, stable API
3. 3rd party apps compete on level playing field
4. Users need not deeply trust 3rd party apps
5. Support mobile user interaction
6. Manage app processes for users
7. Encourage apps to interoperate, collaborate
8. Full general-purpose OS
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Android Architecture (1)

Figure 10-39. Android process hierarchy.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Android Architecture (2)

Figure 10-40. Publishing and interacting with system services.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Wake Locks
Contrast idle CPU, true sleep
1. Idle state may use more power than true
sleep
2. Idle CPU can wake up at any moment if work
becomes available
3. Idle CUP does not tell you that you can turn
off other hardware not needed in true sleep

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Dalvik

Figure 10-41. Creating a new Dalvik process from zygote.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Binder IPC

Figure 10-42. Binder

IPC architecture.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Binder Kernel Module (1)

Figure 10-43. Basic Binder IPC transaction

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Binder Kernel Module (2)

Figure 10-44. Binder cross-process object mapping.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Binder Kernel Module (3)

Figure 10-45. Transferring Binder objects between processes.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Binder User-Space API (1)
User-space object-oriented library
1. IBinder is an abstract interface for a Binder
object
2. Binder is a concrete Binder object
3. Parcel is a container for reading and writing
data that is in a Binder transaction.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Binder User-Space API (2)
Three classes now make it fairly easy to write
IPC code:
• Subclass from Binder.
1. Implement onTransact to decode and
execute incoming calls.
2. Implement corresponding code to create a
Parcel that can be passed to that object’s
transact method.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Binder User-Space API (3)

Figure 10-46. Binder user-space API.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Binder Interfaces and AIDL (1)

Figure 10-47. Simple interface described in AIDL.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Binder Interfaces and AIDL (2)

Figure 10-48. Binder interface inheritance hierarchy.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
Binder Interfaces and AIDL (3)

Figure 10-49. Full path of an AIDL-based Binder IPC.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Android Applications (1)

Figure 10-50. Basic service manager AIDL interface.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Android Applications (2)
Contents of an apk
1. A manifest describing what the application is,
what it does, and how to run it
2. Resources needed by the application
3. The code itself
4. Signing information, securely identifying the
author

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Android Applications (3)

Figure 10-51. Basic structure of AndroidManifest.xml.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Android Applications (4)

Figure 10-51. Basic structure of AndroidManifest.xml.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Activities (1)

Figure 10-52. Starting an email application’s main activity.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Activities (2)

Figure 10-53. Starting the camera application after email.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Activities (3)

Figure 10-54. Removing the email process to

reclaim RAM for the camera.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Activities (4)

Figure 10-55. Sharing a

camera picture
through the email
application.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Activities (5)

Figure 10-56. Returning to the email application.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Services (1)
A service has two distinct identities:
1. It can be a self-contained long-running
background operation.
2. It can serve as a connection point for other
applications or the system to perform rich
interaction with the application

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Services (2)

Figure 10-57. Starting an application service.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Services (3)

Figure 10-58. Interface for controlling a sync service’s sync

interval.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Services (4)

Figure 10-59. Binding to an application service.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Receivers

Figure 10-60. Sending a broadcast to application receivers.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Content Providers

Figure 10-61. Interacting with a content provider.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Application Sandboxes
Security (1)

Figure 10-62. Common UID assignments in Android

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Security (2)

Figure 10-63. Requesting and using a permission.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Security (3)

Figure 10-64. Accessing data without a permission.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Security (4)

Figure 10-65. Sharing a

picture using a content
provider.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Security (5)

Figure 10-66. Adding a

picture attachment
using a content provider.
Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Starting Processes

Figure 10-67. Steps in launching a new application process.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Process Lifecycle

Figure 10-68. Process importance categories.

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Process Dependencies (1)

Figure 10-69. Typical state of process importance

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 Process Dependencies (2)

Figure 10-70. Process state after email stops using camera

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.
 End

Chapter 10

Tanenbaum & Bo, Modern Operating Systems:4th ed., (c) 2013 Prentice-Hall, Inc. All rights reserved.