Do you like systemd?
Do you like systemd?
Do you like systemd?
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.com
goes to tun0
and 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.
Systemd is the greatest innovation that Linux has ever seen bar none.
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
bwwwwt
Happy cake day
pipewire feels close
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.
Sigh
sudo Rule 34:
If there's a user base, there's buttplug.io support...
--force
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.
Linux wouldn't work without furries
We're all shipping the penguin and the wildebeest.
:3
Must your climax be fueled by our frustrations? Vibrators are cheap, you know.
It’s just not the same
I still don't get what you guys have against Windows. Bill Gates has done so much good for the world.
(My body is ready.)
I don't mind all the ads, they're always for things I was just thinking I needed to buy anyway.
Wow there, easy, you’re gonna end up on ER.
At the very least take a smal phone.
Razzzzz
Please tell me your phone has a flared base?
I don't get the systemd hate. The most common complaint I see is that it's too bloated, but Arch uses it, so what gives? Is it just that people dislike change? Like Wayland hate (not Wayland frustration)?
So people hate on systemd because they interpret it as an init system thats gone too far and has thus violated the unix principle. in reality systemd is an entire suite of tools based around a very feature rich and robust service management suite that also includes an init system. there is something to be said about the Linux ecosystem's reliance on systemd, but there are no comparable tools. this is why Arch uses systemd. if you dont want to use systemd, you can use distros like Arco Linux; however currently Gnome no longer works on Arco
Part of the problem with it is that it is very difficult not to use it, for instance if your code uses dbus, that makes systemd a dependency and almost all of the tools are like this. Want to use alternate software with systemd init? A-OK! want to use systemd tools without systemd init? Too bad! This inter-dependence is what I think makes it break the unix philosophy, its components dont like to be replaced or used outside of the "intended" environment of systemd init, keeping it from being replaced without breakage on lot of systems.
On my install for instance, systemd is roped in by xdg-user-dirs (and hence steam), flatpak, fcitx5, and cups. And that is just a few. So the init system isnt a problem to me, the lack of drop-in replacements for its suite of tools is.
So you're saying systemd is the emacs of init?
From what I heard, people hate systemd because Linus Torvald was approached by the NSA to create a backdoor on Linux, he said it wouldn't be possible to change the kernel because there were too many eyes on it, there was a mysterious hack of kernel.org introduced a mysterious code but it was spotted and removed... well, what was the only other thing common to all Linux? The sysv-init, but it was too small, too tight, too specific for them to create a backdoor there, they needed something big, bloated, doing way more than it should do, like it was just supposed to start the system but it can also do unrelated stuff like handling DNS, and an American company shows up bringing systemd, that solved all the problems the NSA had to create a backdoor on Linux, and all distros jumped into the honeypot :)
Lol strangely believable in these times.
Nice conspiracy theory.
Damn, really make sense. Especially nowadays a lot of distros now defaults to systemd.
and all distros jumped into the honeypot
As a filthy casual this is the most distressing part.
I’ve observed the situation shift in just a few years from
“
WinterSystemd is coming”
To
“
WinterSystemd is here, it’s everywhere, and i hate it”
@grok, is this true?
mind sharing some sources?
I'm more frustrated with GNOME devs sabotaging Wayland.
That is a self-inflicted wound caused by how Wayland was designed, particularly the part where they offloaded so much responsibility onto the different compositors.
I'm more frustrated with GNOME devs...
Say no more!
Generally I see a few:
Mainly the last point is the only one I personally find potentially aggravating, but since I never really am in a broken system without journalctl I'm not too bothered by it. I have saved myself some effort thanks to systemd including stuff that the daemons used to provide for themselves.
People wanting the highly deterministic, but slower behavior of the rc scripts.
This is literally it for me. I got to work on an alpine system and it was like a breath of fresh air - I could edit the service script files directly. So easy, so little abstraction
@JackbyDev @nutbutter
People dislike unwanted change. Imagine, you are using some distro for years, and after some update everything changes and you cannot configure system usual way. Many software is changing behaviour You need read tons of docs to change something or worse, while your system hang at boot.
My first try using systemd ended in kernel hang after too much systemd's dmesg flooding (that was slow arm board, so it's unlikely someone might help me with debugging it)
But yes, many people just hate systemd because it was forced change, not even because it's too complex
I'd argue that the systemd trend actually is the one that's change-adverse.
I remember that before systemd there was a lot of innovation when it comes to init systems… the flexibility of the script-based inits made it so most distros had their own spin. And there was more diversity in components that now are part of systemd. I’d argue that ever since systemd became the de-facto standard, innovation in those areas has become niche. Distros are becoming more homogeneous and less open to changes in that sense. Some components are becoming more and more interdependent and it's becoming harder to ship, for example, Gnome, without systemd.
may i ask you to kindly provide the source of this image?
frenky_hw, here's the specific image: twitter (hopefully it is, twitter doesn't work for me rn)
twitter doesn’t work for me rn)
https://nitter.space/moschino_bunny/status/1457773412957376530
tysm❤️
I just like being able to use things I learn across Ubuntu, Debian, Arch and RHEL.
Also prefixing a command with systemd-cat
and having the logs go to the journal is pretty nice. Then I don't have to worry about rotating them.
Listen, we've all done it.
We all have bash or fish or zsh aliases to do it in command.
We all love the feeling of a pulsing phone in our asses.
But we don't talk about it.
But we don’t talk about it.
The first rule of FUDposting club.
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
My biggest complaint with systemd....
Service xxx stop/start/restart is so much easier than
Systemctl stop/start/restart xxx
It fucking annoys me
It seems like every Linux distro I've used both of those will work fine.
I neaver bothered me too much, can you not alias stop to sudo sytemctl stop xxx
Like that you can write “stop wpa_supplicant” instead od “Sudo systemctl stop wpa_supplicant. “
i use mint btw
I dislike systemd less than I dislike sysvinit, so it has that going for it.
Username checks out
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.
Systemd is great! The best thing about it is how efficient and minimal it is!
I love ubuntu snaps.
(sets phone on vibrate)
Well, that's one way to "use" systemd, I guess.
This must be why my post saying Linux made me gay got so many up votes.
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.
Used systemd for years; realistically my first init.
Switched to Gentoo.
Switched to OpenRC.
Lost logs at work on a server.
Some small inconveniences show up on systemd.
Yea, systemd is not that great.
There are people saying they don't want to care about an init system, but it's the same attitude as of those who don't care about what car they drive. Yes, it gets the job done, but that's not good enough for me.
I want the job done properly.
Well, now I do.
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 don't know what systemd is but this is pretty much how I picture all linux users.
And then the phone exploded.
Have one extra buzz from me as well. Screw RedHat and everything it does.
SystemD is that like ntoskrnl.exe?
delete it for free space! (and freedom!)
...
...i'm not asking. do it.
Bzzzzz
I don't really mind it. I picked it when I installed CachyOS.
OwO
All down votes are from all the systemd haters!
I've only ever used systemd, and I'm not really aware of what else is out there, since I think systemd has been the default on all the distros I've tried. Anyone have some good resources on other alternatives and how to start playing around with them?
Most non-systemd users are either contrarians or people who don't want to switch their workflow from some other system that they already know perfectly.
I will always welcome alternative systems on principle alone, but at this point there is not much need for linux "consumers" to consider anything else (unless their distro doesn't ship with systemd of course).
Have a look a this:
For my basic needs it always felt more confusing then necessary. Don't have a hate boner for it, but i prefer not to use it at this point. I'm using Void and i really like how simple runit is.
When looking for an alternative to replace Arch ARM on my Raspberry Pi I tried Void but gave up after discovering it does not use systemd.
I'm still waiting for them to get DNS and user services working. Then it'll finally be usable.
it's fine
they're fine
we're fine
it's fine
yesss
I don't mind the config.
I don't mind most of the features.
I dislike them trying to use timers to get rid of cron
I like it's logging for linux on the desktop if I lose some logs becuas of space that's what i'd do anyway
I don't like it's logging for servers, those logs are necessary and need to be preserved.
journalctl -f is pretty cool
journalctl -fu is pretty cool
This not a kill tony joke?
No, kill Tony just sticks his thumb up his butt for Joe Rogan. Nothing to do with Linux.
omg scary systemd, with Artix I go