this post was submitted on 12 Nov 2023
674 points (94.6% liked)
linuxmemes
21197 readers
193 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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 writesystemd-
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 withsystemd-cryptenroll
. Far from useless or "bad", but still bloat for an init system.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.