171
Systemd's Nuts and Bolts - A Visual Guide to Systemd
(medium.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Jul 2025
171 points (96.2% liked)
Linux
56309 readers
886 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
I started reading that because I want to learn more about systemd and ended up wanting to go back to DOS. Presumably it all makes sense, but when I tried to read it my brain stopped working and my eyes slid off the bottom of the screen.
I don't know why but I just found it incomprehensible.
I have yet to read this, but. But the first part is like the internals of systemd, you won't immediately need it.
If you want to make use of systemd, you can skip directly to where it explains unit files. You'll soon see just how much it can do for you
#alwaysHasBeen, but for us graybeards the confusion has been "this is a solution with no problem" and "it's eaten WHAT now?"
As a proper "gray beard" myself the utility of systemd vs. sys-v init scripts has always been blindingly obvious. 🤷