this post was submitted on 20 Feb 2026
120 points (75.9% liked)

Technology

81611 readers
4451 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] hoppolito@mander.xyz 22 points 21 hours ago (2 children)

It uses a completely different paradigm of process chaining and management than POSIX and the underlying Unix architecture.

I think that's exactly it for most people. The socket, mount, timer unit files; the path/socket activations; the After=, Wants=, Requires= dependency graph, and the overall architecture as a more unified 'event' manager are what feels really different than most everything else in the Linux world.

That coupled with the ini-style VerboseConfigurationNamesForThatOneThing and the binary journals made me choose a non-systemd distro for personal use - where I can tinker around and it all feels nice and unix-y. On the other hand I am really thankful to have systemd in the server space and for professional work.

[–] cenzorrll@piefed.ca 6 points 17 hours ago (1 children)

I'm not great at any init things, but systemd has made my home server stuff relatively seamless. I have two NASs that I mount, and my server starts up WAY faster than both of them, and I (stupidly) have one mount within the other. So I set requirements that nasB doesn't mount until nasA has, then docker doesn't start until after nasB is mounted. Works way better than going in after 5 minutes and remounting and restarting.

Of course, I did just double my previous storage on A, so I could migrate all of Bs stuff back. But that would require a small amount of effort.

[–] WhyJiffie@sh.itjust.works 1 points 31 minutes ago

what do you use as a prerequisite for the nas A mount? or does it iust keep trying in a loop?

[–] passepartout@feddit.org 9 points 21 hours ago* (last edited 21 hours ago) (1 children)

I've started doing podman quadlets recently, and the ini config style is ugly as hell compared to yaml (even lol) in docker compose. The benefits outweigh that though imho.

[–] cecilkorik@lemmy.ca 5 points 18 hours ago

I agree that quadlets are pretty ugly but I'm not sure that's the ini style's fault. In general I find yaml incredibly frustrating to understand, but toml/ini style is pretty fluent to me. Maybe just a preference, IDK.