housekeeping functions like... mounting filesystems, and starting daemons.
5
Living Computers Museum+Labs
6
Then things changed
7
System Configuration
8
Automated Service Management
9
The Idea of systemd
10
The Idea of launchd
11
From launchd to systemd
12
For a fast and efficient boot-up two things are crucial: ► To start less And to start more in parallel
13
An init system that is responsible for maintaining services needs to listen to hardware and software changes.
14
System Management
15
The Reality of systemd
16
Adoption
17
It violates UNIX philosophy!
18
It's bloated and monolithic!
19
It's buggy!
20
It's not portable!
21
UNIX is dead
22
cgroups
23
User-level units
24
systemd represents change
25
The Knee-jerk
26
Abuse Isn't Cool
27
Contempt Isn't Cool
28
Why?
29
The Next Generation
30
The Promise of systemd
31
Message Transport
32
RPC Framework
33
Service Lifecycle
34
Automation via API
35
Containers
36
The System Layer
37
Consistent Device Naming
38
Better Log/Event/Audit Handling
39
A New Model Of An Application
Description:
Explore the controversial systemd bootstrap system in this 47-minute conference talk from linux.conf.au. Delve into the history of bootstrap systems, UNIX, and contemporary operating systems to understand why systemd was deemed necessary and why it provokes strong reactions. Journey through the bootstrap process, init history, and the challenges of change in operating systems. Discover the ancestry of systemd, its evolution from Seventh Edition Unix, and how it addresses modern system configuration and automated service management needs. Examine the adoption of systemd, criticisms against it, and its impact on UNIX philosophy. Learn about cgroups, user-level units, and the promise of systemd's features like message transport, RPC framework, and containerization. Gain insights into the next generation of operating systems and the potential future of system management.