linuxmemes
Hint: :q!
Sister communities:
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 users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- 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.
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, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
Average journalctl
avoider
Ah, thanks for the reminder! As a happy systemd user I sometimes forget how stubbornly resentful some people in the Linux community are that they still try to keep this up as a topic. Then again, maybe this is just a troll?
I still don't know what people use to create services other than systemd
If you're writing bash scripts you're basically replicating a lot of the functionality of systemd but with larger foot guns
If you're writing bash scripts you're basically replicating a lot of the functionality of systemd
You have that backwards
If you're writing Systemd profile profile profiles you're replicating shell scripts but with a lot of spongey unknown "come on, pumpkin" cancer code that you're only sure will do what you think because you don't know what suddenly capriciously changed in enterfuckingprize code and boy is your remote server screwed. Fuck me if I need to actually rely on something starting.
No one said sysV is awesome. It's built to best practice and it does what it does really well, but that's not a lot. But it does it well. Oh, the days Systemd has ruined trying to work half as well as ; well fuck, every alternative.
The days Systemd doesn't ruin, it's the other cancer, network manager and 'consistent' naming. And devices that don't come up. And devices that don't actually assign a fucking static goddamned address. #youHadOneJob
Spot the parts of enterprise Linux that runs like shit and barely does the same thing twice on two identical adjacent boxes, and I'll show you some whiz kid who shat out some cancer and went to go work at Microsoft.
So. Anyway, because the reliable stuff came before Systemd's change-for-lulz setup, you had them in the wrong order unless you have a time machine.
Maybe the arguments against systemd are issues of the past. I see people, hating systemd, bringing the same arguments of it being unstable, or constantly breaking, again and again.
However, I don't remember actually coming across any of those problems, or discussions about them, for the past 5+ years that I have been using Linux both for my computers and servers.
I have used Ubuntu, Debian, Fedora, Arch, Proxmox, NixOS. All of them use systemd.
They only problem I remember facing with systemd, which is actually never mentioned by anti-systemd people, is about its containers system, nspawn, which enables some security features by default. Those break things that tend to work with LXC without much tweaking. Docker, for example, may face issues running inside nspawn.
Systemd is actually way more reliable than other solutions. Forget things like cron and startup scripts. Systemd can monitor and automatically try to restart software.
Systemd hate mostly boils down to hating change
Was gonna ask what's wrong with Systemd but decided to look it up and I now see why, at least from what I was reading.
I mean, if you want an init (e.g. embedded linux), sysd may not be way you want. On desktops, tho, you ultimately end up hacking together more or less the same functionality with sticks'n'shit. And yes, sysd timers are more readable than crontab, sue me.
Edit: the point is, sysd is not (only) an init.
Oh hey a Linux furry. Never seen that on Lemmy before
Xenia is about as old as Tux, and was proposed as a Linux mascot back in the 90's
She's actually been parr of quite a few memes on here, so, now you're in it too :)