Is the current SystemD rant derived from years ago (while they’ve improved a lot)?
No it’s almost always been derived from people’s behinds.
Should Linux community rant about bigger problems such as Wayland related things not ready for current needs of normies?
Yes.
Systemd is spectacular in many ways. Every modern OS has a process management system that can handle dependencies, schedule, manage restarts via policy and a lot more. Systemd is pretty sophisticated on that front. I’ve been able to get it to manage countless services in many environments with great success and few lines of code.
Speaking as someone who uses OpenRC on all my machines . . . no, systemd is not necessarily slow, and personally I don’t care about the speed of my init system anyway. Thing is, systemd also has nothing that makes it more useful to me than OpenRC, so I have no incentive to change. Plus, I dislike the philosophy behind it, the bloat, and the obnoxious behaviour the project showed when interacting with others in its early days. I’m a splitter, not a lumper, and systemd’s attempts to absorb All The Things strike me as rather . . . Windows-like.
So, in a technical sense I have no reason to believe that systemd is inferior to OpenRC + sysv, and it may be superior for some use cases which are not mine. I don’t spend a lot of time ranting about it, and I see no point in trying to convince people not to use it if it fits their needs. But I still won’t use it if I have another option.
I agree. SystemD is a great service daemon (or, sigh, unit daemon in the stupid parlance). I like unit file syntax and I like the ergonomics of systemctl. It’s solid and I appreciate the feeling of consistency that systemd lends to the otherwise chaotic landscape of Linux distrobutions.
It’s for this reason that I’m willing to forgive SystemD overstepping the boundaries of services somewhat. System init/mounting? Sure, that’s a blurry line after all. Logging? Okay – it does make sense to provide a single reliable solution if the alternative is dealing with dozens of different implementations. Network resolution & session management? Fine, I’ll begrudgingly accept that it’s convenient to be able to treat logins/networking as psuedo-services for the sake of dependencies.
If that’s as far as the scope crept, SystemD and I would be cool, but the so-called “component” list just keeps on going. SystemD has no business being a boot manager, nor a credential manager, nor a user manager, nor a container manager, nor an NTP client. I understand why they can’t deprecate most of this junk, but why can’t they just at least make this cruft optional to install?
Systemd (PID1) is not your boot manager, network deamon, resolver, user manager or ntp service.
Those are entirely independent deamons that happen to be developed under the systemd project umbrella but can be exchanged for equivalent components.
Tkey are gully optional.
In many cases, the systemd project’s one is one of the best choices though, especially when used with other systemd-developed components.
In some cases, there is no other viable choice because the systemd-* is just better and nobody wants to deal with something worse.
I’ve read this can depend a lot on the bluetooth card. Personally after replacing my cheapo dongle from like 2012 that probably just didn’t do a recent enough BT version I didn’t have any issues connecting to them.
What card do you have? Might be useful for anyone else who has the same issue.
Nope. None of this affects Fedora. Fedora is upstream from RHEL, meaning code from Fedora is contributed towards Redhat Enterprise Linux, and not the other way around
Got no issues with AirPods Pro and arch. Installed blueman and it’s dependencies and it connected just fine. Managed to configure pipewire to automatically switch between a2dp sink and hsp depending on the current usage.
I haven’t had any problem on Garuda with my AirPods. I saw another guy say he had no problems with manjaro and arch. I didn’t know people were having problems on other distros or setups.
The problem of systemd is that it hasn’t been just a replacement of init as they initially claimed, and now deny they ever did. Things like Mono, Gnome and systemd are bad for the ecosystem long term.
An init done by constructive people wouldn’t be a problem at all.
The problem of systemd is that it hasn’t been just a replacement of init as they initially claimed
Apart from the PID 1 part of systemd, almost all tools are optional.
Although I have a positive opinion about the systemd project, I used netctl instead of systemd-networkd for a long time without any problems. And even today I don’t use systemd-resolved because I use a combination of unbound and Pi-Hole in my private LAN. And so on.
So you can’t say that the systemd project has replaced various solutions in such a way that you don’t have a choice anymore.
Honestly, that looks like a fairly short list and half of the tools interact closely with useful functionality that didn’t even exist at all before systemd came around.
They’re a pretty big contributor to Linux, so even if you don’t see their work you’re probably using it anyway. lwn.net/Articles/915435/
added value that cannot be fulfilled by independent experts or FOSS community
Wrong question IMO. It’s more relevant to ask “without Red Hat, would independent experts or the FOSS community have added the same value?”. Sure, it’s possible that Red Hat has some highly skilled developers that possess unique skills required for their contributions, but in general contributing to FOSS projects is more about willingness to spend large amounts of time and resources on something that doesn’t give you money in return.
Lots of large companies “could” have spent thousands of hours contributing to Linux, but unless they actually do it then it is irrelevant.
I decided to go with Da Vinci Resolve for video editing and I might migrate to something to replace Lightroom in future, can’t now, because I have all my Lightroom catalogues at work.
I mostly use photoshop to remove objects from photos, place in images rendered with blender and retouch them to look like they were part of the photo, I think Darktabke doesn’t have tools similar to healing brush and patch tools in photoshop. Although photoshop is working perfectly so far, it would be nice to find a native application that is up to the task. I haven’t really tried hard to look for linux alternative that can do that.
EDIT:
Wait, I just looked into it and there are such tools! Thank you for suggestion! I might try it!
I do not think systemd is bad, I (and personal preference here) much prefer it over the older style of init systems.
Quite frankly, one of the things that has always irked me about a portion of the Linux community is that as far as I know, a strength and selling point of Linux has always been the freedom of choice. And yet, people start wars over your choices. For example, I know at least on r/Linux if you were to make a post saying that you liked Snaps over Flatpaks you’d get torn to shreds over it. Wouldn’t matter what reasons you had either.
It is always something. Whether its about Arch vs other distros, Snaps vs Flatpak vs AppImage vs Traditional packaging, X11 vs Wayland, systemd vs Sys V/init.d, pulseaudio vs pipewire, etc.
I never understood why it mattered so much what someone ran on their own computer. Assuming they’re the only one using it, what is the big deal if they choose to run OpenRC, X11, Snaps, and Alsa?
And I get a bad feeling the next one is going to be immutable distros vs non-immutable distros, but I guess we’ll see.
It’s a massive question, and I think quite a lot of the argument comes from the fact that it depends what direction you’re answering it from.
As a user, do I like being able to just systemctl enable --now whatever.service , and have a nice overview of ‘how’s my computer’ in systemctl status ? Yes, that’s a big step up from symlinking run levels and other nonsense, much easier.
As an administrator, do I like having services, mounts and timers all managed in one way? Yes, that is very nice - can do more with less, and have to spend less time hunting for where things are configured. Do I think that the configuration files for these are a fucking mess of ‘just keep adding new features in’ and the override system is lunacy? Also yes.
As a developer trying to do post-mortem debugging, who just wants all the logs in front of him for some server that’s gone wrong somehow, which I often have to request via an insane daisy-chain of emails and ‘Salesforce nonsense that our tech support use’ from our often fairly non-technical end users, on some server that I’ve no other access to? No, I do not find having logs spread between /var/log and journalctl (and various CloudFormation logs in a web console) makes my life easier. I would be pleased if that got sorted out.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.