I use plasma, BTW
this post was submitted on 12 Nov 2023
668 points (94.5% liked)
linuxmemes
21210 readers
57 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
sudoin 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
I see way more posts that are pro-systemd than anti these days, so I think you might be tilting at windmills a bit.
I would love to think about systemd less, but I've worked with it professionally since a year or so before Debian switched while I was an intern working in embedded. I got to see the flame wars and shaped my opinion of systemd by wrestling with its growing pains. Writing your own service files and working with DBus was ass back then, and while it has gotten better, my patience with it has diminished. In the end the frustration was enough that after I ditched windows, systemd was the next to go.
That would be the end of it, but other programs keep growing annoying systemd dependencies or their projects get swallowed up by the systemd ecosystem entirely. I was so excited at the start to work with the parallel execution and dependency management, but the number of times systemd broke something, swallowed up the output, and then corrupted its own journal and lost the logs really turned me against it.
I don't know, I'm not a power-user so systemd is just a thing in the background, I don't have much opinions over it.
No systemd love or hate for me, as for the meme, I respect both opinions (I'm still learning btw) but don't particularly like proselitjzers. Sharing an opinion and experiences (like you did) is fine and often informative, what I don't like are people (expecially on lower-quality places like 4chan) spamming stuff like "systemd is the devil and killed my child" or "systemd weights more than the Linux kernel" I guess I need to make up my mind, haven't interacted with the OS at a low enough level yet.
I understand what you mean. If you are on the fence and not super interested in init systems, you can pretty easily get by with systemd without thinking about it. Most desktop environments have tools to manage user services in easy GUI's, and you can find guides for anything more advanced you want to accomplish with them usually.
If you want to dive in though, systemd is a great init system to learn. Nowadays learning systemd is a lot less of a moving target, and it's in use virtually everywhere so the knowledge is valuable. It's also fairly well documented at this point, which is great for learning how it works.
My personal advice if you want to go that path is to just open up some service files. There are lots of interesting examples in
/lib/systemd/systemSystemd service files are just plain text, and pretty straightforward to read. Its divided into nice sections, and naming is pretty straightforward (Or the systemd brainworms are really in deep). Look for names you recognize or programs you use. Especially ones you are familiar with on the command line. I don't recommend changing them to start, especially in the system directory, just open a couple and you should quickly start seeing the connections between what they are trying to accomplish and whats in each file. Then if you see anything you don't understand or peaks your curiousity check the documentation. Once you're ready try writing one of your own for something in the usr service directory. No pressure though, its not necessarily essential knowledge