The Tragedy of systemd

The Tragedy of systemd

linux.conf.au via YouTube Direct link

Intro

1 of 39

1 of 39

Intro

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

The Tragedy of systemd

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 The Ancestry of systemd
  3. 3 Seventh Edition Unix (1979)
  4. 4 housekeeping functions like... mounting filesystems, and starting daemons.
  5. 5 Living Computers Museum+Labs
  6. 6 Then things changed
  7. 7 System Configuration
  8. 8 Automated Service Management
  9. 9 The Idea of systemd
  10. 10 The Idea of launchd
  11. 11 From launchd to systemd
  12. 12 For a fast and efficient boot-up two things are crucial: ► To start less And to start more in parallel
  13. 13 An init system that is responsible for maintaining services needs to listen to hardware and software changes.
  14. 14 System Management
  15. 15 The Reality of systemd
  16. 16 Adoption
  17. 17 It violates UNIX philosophy!
  18. 18 It's bloated and monolithic!
  19. 19 It's buggy!
  20. 20 It's not portable!
  21. 21 UNIX is dead
  22. 22 cgroups
  23. 23 User-level units
  24. 24 systemd represents change
  25. 25 The Knee-jerk
  26. 26 Abuse Isn't Cool
  27. 27 Contempt Isn't Cool
  28. 28 Why?
  29. 29 The Next Generation
  30. 30 The Promise of systemd
  31. 31 Message Transport
  32. 32 RPC Framework
  33. 33 Service Lifecycle
  34. 34 Automation via API
  35. 35 Containers
  36. 36 The System Layer
  37. 37 Consistent Device Naming
  38. 38 Better Log/Event/Audit Handling
  39. 39 A New Model Of An Application

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.