this post was submitted on 01 Apr 2024
319 points (93.2% liked)
linuxmemes
24384 readers
434 users here now
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
sudoin 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.
founded 2 years ago
MODERATORS
I like being able to see my logs without waiting 20 minutes, knowing who started what without playing cat and mouse with random processes and being able to change something without going through multiple levels of merged configurations files from three different sources.
I also enjoy tools that were developed over decades and not rewritten from scratch reintroducing long-solved issues.
Most of them think that theyβre making a point about an argument their side lost almost a decade ago.
load more comments
(1 replies)
To keep the system simple and transparent.
Its just easier for me to dualboot windows. Im too dumb to find how to do it with systemd :p
That is systemd-boot, which is separate. You should use refind anyways
load more comments
(2 replies)
The kernel is already monolithic enough without adding another piece of monolithic software that everything depends on. IMO the Unix philosophy means we should have interchangeable parts.
There's some amount of user error here but when I did use systemd I had a hard time turning off services I didn't want because they were in the wants-to-have entry of other services. It's like a separate config area to maintain with a specific maintenance tool software instead of flat files.
I'm unfortunately using distros with systemd now tho.
Guix uses shepherd so yeah
It's a give and take honestly.
System-d has better logging. Until you have something that needs to really really log. You can argue that if you have something that's that dependent on logging it shouldn't be logging through the console but it's worked fine for decades. Auto pruning of logs isn't necessarily ideal. Getting console logs and assist logs as a pain in the ass.
Same goes for service dependencies we had this sorted it was answered via run levels and naming. It wasn't necessarily the most elegant solution but it was simple and there was very little to go wrong.
The tools to manage the services and logs are needlessly complicated. Service start, service stop, service status, service log, service enable, service disable. And I shouldn't have to reload the Daemon every time I make a change.
This isn't to say that it's all bad. It's flexible, and for most workflows, it's very automated and very light touch. The other pruning on the log file says probably saved a lot of downtime, a whole lot of downtime.
It's really well suited to desktop.
Service creation is somewhat easier.
Dependencies are more flexible than run levels.
To be honest I wouldn't go out of my way to run in a non-system distro but I would feel a little sigh of relief if something I was screwing with was still init.d
What a loser, not only is it an anime thing it refuses to socialize
Because I left Windows precisely to avoid the kind of shittery that systemd is doing.
It's absolutely no coincidence that the people who have developed the stuff that's brought the most degradation to Linux - systemd, PulseAudio, Gnome's "user has no right to themes" attitude - all come from a Microsoft background or explicitly work for Microsoft.
I'd have far less of a problem if systemd was split into more practical, actually independent things that actually worked and distros didn't buy their snake oil so easily. But for the time being, to me, the systemd experience is pretty much like the PulseAudio experience, what with the whole "waiting 120 seconds for a network interface to activate that it's not going to because it's the damn ethernet port and I'm on the road so the cable is not connected, stupid letter-potter dipshit".
I've been using linux for ~2 years now and only know one of these (GUI installer), anyone smarter than me can explain what they are?
load more comments
(3 replies)
More Code in Kernel-space = less secure
Systemd = a lot of Code in Kernel-space
eBPF: psst, wanna run your code directly in kernel?
load more comments
(4 replies)
Guix integrates with shepherd wonderfully because they're both Guile-based
I think service descriptions being functional scheme code makes more sense in a way than systemd's runtime.
Guix mentioned! π