HackerTube 中文?

The Tragedy of systemd

linux.conf.auYouTube ↗

Further reading 1

When one component fails, who can keep working? →One process fails. Must unrelated requests wait? Separate failure propagation from throughput limits, then trace what the operating system and service manager can actually isolate.This video helps answer · Who manages a service after startup?

Caption notes

Service management extends beyond startup: devices appear, services fail and dependencies change. The speaker places systemd in that broader operating-system context.

Original passages · 5
systemd as a project ends up complementing the linux kernel by providing all of this user space system layer
The Tragedy of systemd · ▶ 15:32–15:45
an important distinction to be drawn between system D the implementation and system D as a set of ideas
The Tragedy of systemd · ▶ 20:13–20:32
systemd gets really right is the notion of user level units
The Tragedy of systemd · ▶ 24:31–24:43
providing all of this user space system layer
The Tragedy of systemd · ▶ 15:36–15:51
maintaining services needs to listen to hardware and software changes
The Tragedy of systemd · ▶ 12:43–12:55

Hacker News comments

View original on HN ↗