this post was submitted on 07 Jan 2025
94 points (99.0% liked)
Linux
48904 readers
1290 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ah. So MM's still in the sidelines and IBM still pulling strings, so little chance of ditching fucking systemd in Fedora, and thus RedHat. That's the one good thing I can see from a regime change: improvement of the codebase by, for example, pruning pet projects when the pets leave for Microsoft.
Not sure why the downvotes on this? Systemd is bloated and known to present security risks. Don't see why looking at alternatives wouldn't be seen as positive growth.
I didn't downvote myself, but did consider it.
For one, it felt a bit out of place; Fedora isn't defined by systemd, nor Red Hat or IBM. One clear example would be how Fedora has chosen to stick with Btrfs; contrary to Red Hat's demands. Don't get me wrong, I don't deny any partnership or whatsoever. But it's not like Fedora's community has no agency.
Secondly, corsicanguppy's comment seems to imply that Fedora only sticks to systemd out of some obligation towards IBM/RedHat or something. As if the overwhelming majority of distros don't default to systemd.
Thirdly, Poettering works for M$ now. Sure. But systemd remains a Linux project. And quite a good one at that. Even if the likes of dinit and s6 are starting to offer some healthy competition, it's undeniable that systemd continues to have the advantage in terms of received man-hours (in development) and adoption. I hope that Fedora eventually gives others the chance to shine. But outright ditching systemd without a perfect replacement is just foolish.
The bloat argument has absolutely no weight as long it's not properly defined. One's bloat is the other's sane default and vice versa. Please, if you're engaging in good faith, come up with a definition by which the likes of dinit and/or s6 are not bloated while systemd is. Please be complete and rigorous in your assessment.
If you're referring to what's addressed in Madaidan's article, you should not forget that Whonix -the very distro Madaidan used to be a security researcher at- employed systemd to enhance security. And while one might say a lot about Poettering, one simply can't deny that they've got a sound understanding of good security standards and how to implement them. It's therefore unsurprising that both Kicksecure and secureblue (i.e. Linux' finest when it comes to hardened distros) heavily rely on systemd for their bidding.
At least we can agree on this 😉.
Ah, I get what you mean now by inflammatory statements (after a thorough reread) and why there may have been downvotes from that. Though interestingly, I didn't feel my comment was very inflammatory and it got downvoted too. 😅
I was looking at it more from just a standpoint of systemd itself, and honestly, just looking at it from the standpoint that fedora and rhel can tend to be industry leaders for change. Honestly, if RHEL and Ubuntu together made some sort of meaningful change from a system perspective, I think we would see that move downstream.
As far as my use of the term bloated, I'm looking at it strictly from a standpoint for the amount of code that goes into the system. The more code you have, the more entries for security risks. I'm not saying that there's anything that's particularly better out there right now, but I think we should always be looking for alternatives regardless of what your views are for the people that created the code. KISS philosophy, basically. That and being open to change to avoid stagnation.