A section of code that can be updated by one several simultaneous tasks

A section of code where variables are read that can be accessed by several simultaneous tasks

A section of code where variables are updated that can be accessed by several simultaneous tasks

A section of code without variables that can be accessed by several simultaneous tasks

A section of code that cannot be read by one several simultaneous tasks

A section of code that can be read by one several simultaneous tasks

3

1

2

4

10

0

8

50 ou plus

ACL

CC

DAC

MAC

RBAC

CAG

lshw

There is no such command in Linux

show interrupts

cat /sys/interrupts

dmidecode

cat /proc/interrupts

ls -i

interrupts

traps

scheduler

bus drivers

arrays

filesystems drivers

mixed C and assembly code

GPU drivers

network drivers

exceptions

inter-process communications

It enables to recover filesystems consistency before they are used

To speed the process, the filesystem journal can be executed

When the journal fails, which is quite uncommon, filesystem check can nonetheless recover consistency

It is always needed for readonly filesystems

It is needed at system boot for all filesystems

It takes a quite long amount of time to execute for large filesystems

It is done at system boot for some filesystems when they have been left in an inconsistent state beforehand

1 second

1 millisecond

1 femtosecond

1 nanosecond

1 picosecond

1 minute

1 microsecond

it depends on the hardware clock

Each kernel process has a separate memory space from other kernel processes

All processes share the same memory space

All kernel processes have the same priority

All users share the same memory space

All user-space processes have the same priority

A failure of one process in user-space might cause the whole system to fail

All users have root access on the system

All services are implemented in user-space

A failure of one process in kernelspace might cause the whole system to fail

All services are implemented in the kernel

add a journal to the filesystem

set ownership for one user to read and write to the filesystem

check the filesystem consistency

unmount the filesystem

mount the filesystem

ps

sysctl

kill

chsh

gdb

nice