this post was submitted on 11 Jul 2025
205 points (96.4% liked)

Linux

56365 readers
490 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
top 23 comments
sorted by: hot top controversial new old
[–] Everyday0764@lemmy.zip 7 points 1 day ago (1 children)

i would read it, if medium allowed me...

[–] irotsoma@lemmy.blahaj.zone 2 points 22 hours ago (1 children)

That was a lot of really good info. I've been having to deal with some more complex systemd configurations at work which has gotten me interested in the subject. This was a really good intro and will help a lot in my own self-hosted activities as well as work.

[–] sebastiancarlos@lemmy.sdf.org 1 points 21 hours ago

Thanks bro, just doing my best to keep our kind employed and informed. Long live the machine whisperers

[–] theshatterstone54@feddit.uk 44 points 2 days ago (2 children)

If you’re a new or intermediate Linux user or sysadmin, you might have felt an odd fascination with the myth of systemd. I invite you to this deep dive into systemd's nuts and bolts. I'm not gonna beat around the bush: It's a hairy business, it will be hard, but I promise juicy and satisfying rewards if you keep pumping through this guide.

Let’s start by uncovering the “D” of systemd, the secret sauce that doesn't get the love it deserves: D-Bus.

Okay, those innuendos have to be intentional!

[–] corsicanguppy@lemmy.ca 23 points 2 days ago
  1. Take a non-stop Linux box where even the kernel can be patched while it's hot
  2. Glance at d-bus sideways
  3. Now you must reboot.

Thank you Ted, that's the joke.

article has a typo. opinion discarded.

/s

[–] SnotFlickerman@lemmy.blahaj.zone 38 points 2 days ago (2 children)
[–] d00phy@lemmy.world 12 points 2 days ago

This is the beauty of open source. If you wrote an app called “eeznuts” and mad it something everyone needed, eventually a sysadmin somewhere would get to explain that joke to a stiff EVP, and they’d both have a good chuckle about it.

[–] _spiffy@lemmy.ca 6 points 2 days ago

Ha! Gottem.

[–] MonkderVierte@lemmy.zip 5 points 1 day ago* (last edited 1 day ago)

Why it is a guide, it's not a visual guide.

[–] syklemil@discuss.tchncs.de 5 points 1 day ago

I've very barely dipped my toes in dbus before, and the option to have something else is on its face attractive (not a fan of XML and the late 90s/early aughties style of oop), but JSON for a system interface?

I mean, Kubernetes shows that yaml can work, but in this day and age I'd expect several options for serialisation, and for the default to be binary, not strings.

String serialisations are primarily for humans IMO, either as readers or writers. As writers we want something with comments (and preferably no "find the missing }" game), so for that most of us would prefer something like TOML if the data is simple enough, and actually Yaml for complexity at the level of Kubernetes—JSON manages to be even more of a PITA at that level.

But machine-to-machine? Protobuf, cap'n'proto, postcard, even CBOR should all be alternatives to examine

[–] Naich@lemmings.world 19 points 2 days ago (2 children)

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.

[–] edinbruh@feddit.it 9 points 2 days ago

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

[–] corsicanguppy@lemmy.ca 3 points 2 days ago (1 children)

I don't know why but I just found it incomprehensible.

#alwaysHasBeen, but for us graybeards the confusion has been "this is a solution with no problem" and "it's eaten WHAT now?"

[–] atzanteol@sh.itjust.works 11 points 2 days ago

As a proper "gray beard" myself the utility of systemd vs. sys-v init scripts has always been blindingly obvious. 🤷

[–] dan@upvote.au 10 points 2 days ago

Great article! This helped me understand a lot more about D-Bus.

[–] haroldstork@lemmy.ml 6 points 1 day ago

Informative and informal. Love it!

[–] leo85811nardo@lemmy.world 7 points 2 days ago

That title gotta be intentional

[–] TropicalDingdong@lemmy.world 4 points 2 days ago (1 children)

the Millie Vanillie of vibe coding if you will..

[–] corsicanguppy@lemmy.ca 1 points 2 days ago

Systemd is the Kanye West of vibe-coding.

[–] Album@lemmy.ca 2 points 2 days ago

Ayyyyy!

Love systemd thanks for the writeup 👍🏽