Sign in to confirm you’re not a bot
This helps protect our community. Learn more
These chapters are auto-generated

Introduction

0:00

Summary

6:02

Systemd is not monolithic

7:00

Universal

7:50

Highlevel objects

8:35

Respectability

10:03

Limits

11:40

Maintenance

12:18

Minimize Test Matrix

15:55

ReadOnly System Images

19:35

Empty EDC

20:42

Stateless

22:23

Beasties

23:47

Innovation

26:11

Resource Management

29:52

Problem Solving

32:55

We never want to be exclusive

33:46

Fluff divine

35:19

StartStop

35:49

Dynad

36:22

cron

38:00

hub

38:32

audit

39:24

journal

40:49

watchdogs

42:39

PID

44:25

Draw the line

45:37

Who is using this

48:24

You can still run it

49:39

Future of the project

51:16

Integration of utilities

53:44

Disadvantages

58:14
Lennart Poettering - systemd as the Core OS
51Likes
12,223Views
2012Dec 1
systemd has grown from a mere init system into a basic set of components to build a Linux OS from. It is now used at the core of Fedora, OpenSUSE, Mageia, Tizen and will soon make its appearance in the various big enterprise Linuxes as well. It is also available in all important community distributions. In this talk I'd like to explain where we are coming from, what we currently offer and where we want to go with systemd. I will give an overview of the various components, and our general approach to OS design. We will give a special focus on our quest to cover all three major bases of Linux: embedded/mobile, desktop and server and what we are doing to make systemd attractive to ehm.

Follow along using the transcript.

Hasgeek TV

37.2K subscribers