this post was submitted on 09 Jul 2025
250 points (85.5% liked)

Linux

56269 readers
831 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 9 points 22 hours ago (2 children)

Because people here accuse Poettering of being an asshole: I've read some of his blogposts and seen some talks of his and him doing Q&A: He answered professionally, did his best to answer truthfully, did acknowledge when he didn't know something. No rants, no opining on things he didn't know about, no taking questions in bad faith.

As far as I can tell all the people declaring him some kind of asshole are full of shit.

[–] [email protected] 2 points 11 hours ago (1 children)

He answered professionally

Until you ask him about security and CVEs advisories...

[–] [email protected] 4 points 22 hours ago* (last edited 22 hours ago)

He is not that bad, the issue is that, as all foss devs, he is not interested in solving problems he does not feel like are important.

The problem is, he disapproves when resources are allocated in his project to those problems and one main area he is not a fan of is support for legacy stuff.

It just happens that legacy stuff is the majority of the industry, as production environment of half the globe needs to run legacy software and a lot of it on legacy hardware

[–] [email protected] 15 points 1 day ago (1 children)

I'd just like to interject for a moment. What you're refering to as Linux, is in fact, GNU/systemd/Linux, or as I've recently taken to calling it, GNU plus systemd Linux.

[–] [email protected] 5 points 1 day ago
[–] [email protected] 22 points 1 day ago (5 children)

I don't appreciate the attitude and arrogance of the guy behind systemd because he actually believes what he produces can replace everything that already "just works". He wants to push out systemd-homed because "why not". He wants to replace grub. He wants to replace a myriad of things that just flat out don't need to get replaced. autofs, cron, you name it! That kind of thinking and one-size-fits-all mentality is backwards and does not benefit the community in any way. All it does is stuff everything into one bin and so long as influencers like this guy continue to restrict what works or doesn't work according to their own work, the community and its users will not be able to freely develop FOSS. Gnome is a good example of something that creates too much of a dependency on systemd and so when you're trying to use something like Gentoo, it becomes very difficult to get that done and hacks have to made in order to get it working. FOSS shouldn't work like that. He'll keep stripping away legit projects from major distros until IBM/Red Hat finally decide to seal the deal and lock everyone out for good. Sorry if I can't rejoice in the woah whiplash.

[–] [email protected] 7 points 22 hours ago

Grub is shit

[–] [email protected] 8 points 23 hours ago

He wants to replace grub.

I hope so!

[–] [email protected] 16 points 1 day ago (1 children)

The is the first time I’ve ever heard someone accusing grub of „just working“

[–] [email protected] 2 points 12 hours ago

Grub is working perfectly fine.

If it breaks it is, in my experience as a grub user for over 20 years and as a guy working in server hosting for 15 years, either because of failing HDD/SSD or because of user error. People don't read when the updater tells them that running "grub-install" is needed (or they perform it on the wrong drive/partition) and then blame grub when it fails on the next boot.

The crappy bootloader that comes with systemd very often, in my experience, fails to register that a new Kernel was installed and boots the old one (or fails to boot if the package manager removed the old Kernel).

Oh and GRUB has so many useful features, like booting a ISO image. GRUB is a piece of programmer art!

[–] [email protected] 11 points 1 day ago (1 children)

All it does is stuff everything into one bin

Well, it is not one bin. There is no monolithic systemd bin that does everything. There are a lot of separate bin files for all the different tasks. Well and if you don't want to use timers, then don't and just use cron instead. If you don't want to use journald, then just don't and use rsyslog or whatever you want. Don't need systemd-homed? Well, then don't use it. You want to configure your network with something else then systemd-networkd? Great, do it if you want.

The Poettering Army will not come and force you to enable all the options 😜

[–] [email protected] 6 points 1 day ago

So, I don't like the guy either, but for a little devil's advocacy:

The stuff that already "just works" was developed during a very different era in terms of computing power, tasking of the computers which were running the systems, etc. Nobody (serious, and he is serious) develops something different because "why not?" they, at least from their perspective, feel that they are improving on the status quo, at least for the use cases they are considering.

one-size-fits-all mentality is

being decided by the distro maintainers, not the developers. Sure, developers promote their product, but if a distro thinks that multiple flavors are a better path, they distribute multiple flavors. It's not like the systemd developers are filling billion dollar war chests with profit because they're using strong-arm tactics to coerce distro maintainers to adopt their products.

stuff everything into one bin

When one bin serves the purpose, it's a lot easier to maintain, modernize, security harden, etc. than ten bins.

the community and its users will ~~not~~ always be able to freely develop FOSS.

Fork it and your loyal users will follow.

Gnome is a good example of something that creates too much of a dependency

Agreed, I was never happy with GNOME, and starting about 5 years back I have been migrating my systems, personal and professional, off of it. That's the nature of FOSS, no contracts to negotiate, make the choices that make sense for your use cases and execute them.

FOSS shouldn’t work like that.

FOSS, by its very nature, should be expected to work all the ways. If a particular way can't get enough developer traction, it stagnates but never really dies, not until the ecosystem it is dependent upon can no longer find hardware to run on and users willing to run it.

IBM/Red Hat finally decide to seal the deal and lock everyone out for good.

I am very glad that I walked away from CentOS about 8 years back, its proximity to Red Hat never made me happy. I have been trying to walk away from Canonical (toward Debian) for about 3 years now, but it still has some hooks that keep our professional team happier than Debian. If the unhappy ever outweighs the happy, we'll execute the move.

Sorry if I can’t rejoice

Never asked you to. End of devil's advocacy. I still don't like the guy, but I never really interact with him. I do interact with his products and the alternatives, and in my use cases the products speak for themselves. There's nothing about systemd that makes me dig around for systemd free alternatives - they are out there, but for my use cases I don't care. YMMV.

load more comments
view more: next ›