Have you considered that just “reaping old process IDs” wasn’t enough responsibility for an init daemon on a secure, robust system? That maybe it should be protecting other parts of the system and tracking the liveness of a desired service?
What is the benefit of specifically doing that in init?
If I see an argument like this then I can only assume the interlocutor doesn’t do software engineering.
Its more likely that the user simply has simple needs like running stuff at startup which any init system can do and doesn’t see as much benefits as poster.
Also who loves systemd-resolved?
Being able to assign a nameserver per interface with a domain wildcard is a fucking godsend. I use it every day with a hook script because my job uses some private domains but I don’t want to send my entire DNS history through the VPN. Now
~job.comgoes totun0and that’s the end of it.systemd-resolved is not perfect but with libnss’s overly rigid nature the only alternative for my use-case would be to recreate similar functionality to resolved with dnsmasq – which is just objectively worse especially when you want to use DHCP sometimes but not always. Why reinvent the wheel? resolved does its job and does it well. I had some issues with it a few years ago but have been using it for the past couple years without complaint.
What is the benefit of specifically doing that in init?
What’s the alternative?
Also who loves systemd-resolved?
I don’t think I will ever love anything DNS-related, but it’s still the best solution I’ve used for name resolution on a system with many interfaces.
I fully agree. I am a user with a bit of technical background, but not a lot of detailled knowledge about the inner workings of an operating system (i know boolean logic and basic programming structures - in Pascal lol - from the 90’s, what a transistor does and stuff, how to build my own PCs and handle filesystems and troubleshooting).
With init scripts, i hit a wall pretty fast.
With Systemd i know how to start, stop and configure services, and the suite built around it uses the same conventions everywhere, making the everyday life with Linux for someone like me so much easier and more transparent than ever before.
The other day I wrote I like snaps and shot more rope than Spiderman.
Flatpak is amazing especially with storage being so cheap these days.
I just had an issue with the vscodium flatpak, been using it for two months with no issue in an online course, got to learning GUIs, import module, doesn’t exist. I couldn’t figure out why it wasn’t there, installed three different python versions of it three different ways, still nothing. Couldn’t even get vscodium to point to a different interpreter that I knew was there (yet it doesn’t say it’s not there, just that some things won’t work). Still nothing. Three hours later, after trying everything I could think of, I realized that it was because I installed the flatpak version when it clicked that it worked in Geany and I didn’t have python 3.13 in my repos, yet that was the only one I could see in vscodium.
That sounds like user error.
From a broad enough perspective, everything is user error
Except when the error is in the chip architecture.
No that was me
I don’t know what systemd is but this is pretty much how I picture all linux users.
Systemd is the greatest innovation that Linux has ever seen bar none.
pipewire feels close
Since I started actually doing system administration and actually interacting directly with SystemD all of the hate for it I’d soaked up from enthusiast forums melted away. I’ve never used any of the other init systems so maybe I’m missing out, but I do appreciate SystemD for what it does
Systemd has simplified my life on a few occasions, and it seems to be reliable from what I can tell. At the end of the day if I can get the OS to do what I want in a relatively simple matter, that’s all I care about.
In all seriousness, I’ve yet to encounter a situation where Systemd made any meaningful negative difference in my Linux experience.
I’ve never had problems with any init system, Systemd or otherwise.
I love ubuntu snaps.
(sets phone on vibrate)
Rule 34:
If there’s a user base, there’s buttplug.io support…
Error: That number is already picked for a different rule. Please select a different number.
If you used the right amount of lube you wouldn’t have to force!
Maybe consider rule 33. ‘Lurk more its never enough’
That’s taken too.
Lurk more its never enough is rule 33.
https://rules.nebula-system.com/rule-33
Which you didn’t follow.
Let’s hope the user base is flared.
“I know my playerbase.” -Hakita, the dev of Ultrakill
Okay, so, this place IS filled with furries. Cool.
Every online space is filled with furries, especially the most furry-hostile spaces!
That’s disgusting, I prefer furry-hostile tabs!
I love it when the hostility adapts to my system
Is putting phone in ass a furry thing?
The depicted character has a snout and cat ears
maybe she was just born that way
Why cat ears now, I can’t say
Maybe she was just born that waaaaayyyyy
And an anus!
and my axe
Thought it was more a prison thing.
We’re all shipping the penguin and the wildebeest.
:3
Linux wouldn’t work without furries
omg scary systemd, with Artix I go
And then the phone exploded.
Please mark as nsfw
There’s already systemd in the title
@SkaveRat @possiblylinux127 systemd should be in CW (but do not know if lemmy supports CW)
Good boy.
Systemd is fine.
Journald is fine.
But someone pass me a mace I can beat systemd-resolved and systemd-logind to death with
EDIT: Oh come on
You’ll love resolved when you have to deal with split DNS ;)
Oh trust me I have. resolvconf and openresolve are awful too but for different reasons
Bzzzzz
I don’t know if I like how you’re characterizing furries. Not all of us do this, and I don’t do it… often.
