this post was submitted on 12 Nov 2023
674 points (94.6% liked)

linuxmemes

20686 readers
1420 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
poopsmith@lemmy.world
zephyr@lemmy.world
674
Screw init wars, real OGs discriminate based on DE (lemmy.ml)
submitted 10 months ago by frippa@lemmy.ml to c/linuxmemes@lemmy.world
123 comments fedilink hide all child comments
 

I use plasma, BTW

you are viewing a single comment's thread
view the rest of the comments
[–] vettnerk@lemmy.ml 19 points 10 months ago* (last edited 10 months ago) (1 children)

Oversimplified: It's the service that handles starting and stopping of other services, including starting them in the right order after boot. Many people hate it because of astrology and supersticion. Allegedly it's "bloated". But still it has become the standard on many (most?) distros, effectively replacing init.

I like init. It's simple. I like systemd as well. It's convenient. Beyond that i don't have very strong feelings on the matter.

Also, see important answer by topinambour-rex.

[–] drugo@sh.itjust.works 11 points 10 months ago* (last edited 10 months ago) (1 children)

I think the arguments against the "bloat" are not towards systemd as an init system, but rather are because systemd does so many things other than being an init system. I also don't mind systemd, but I absolutely hate systemd-resolved. I do not want my init system to proxy DNS queries by setting my resolv.conf to 127.0.0.53. Just write systemd- and press tab, that's "the bloat". I'm not saying that the systemd devs should not develop any new tools, but why put them all inside one software package? systemd-homed is cool, but useless for 99% of users. Same with enrolling FIDO2 tokens in a LUKS2 volume with systemd-cryptenroll. Far from useless or "bad", but still bloat for an init system.

[–] vettnerk@lemmy.ml 7 points 10 months ago* (last edited 10 months ago)

Now that you mention it, I find systemd messing with my DNS settings incredibly annoying as well, so I can't help but agree on that point. At this production system at work, when troubleshooting, I often need to alter DNS between local, local (in chroot), some other server in the same cluster, and a public one. This is done across several service restarts and the occasional reboot. Not being able to trust that resolv.conf remains as I left it is frustrating.

On the newest version of our production image, systemd-resolvd is disabled.