this post was submitted on 09 Jul 2025
253 points (85.0% liked)

Linux

56500 readers
1282 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
[–] ExtremeDullard@lemmy.sdf.org 78 points 1 week ago* (last edited 1 week ago) (14 children)

I totally agree. I used to hate systemd for breaking the traditional Unix philosophy, but the reality is that a tight init and service-tracking integration tool really was required. I work with and appreciate systemd every day now. It certainly didn't make things simplier and easier to debug, but it goes a long way towards making a Linux system predictable and consistent.

Poettering can go fuck himself though - and for PulseAudio too. I suspect half of the hate systemd attracted over the years was really because of this idiot.

[–] OmegaLemmy@discuss.online 21 points 1 week ago

systemd is easy to work with, other init systems introduce kinks, I rather break philosophy than deal with that shit

[–] ijhoo@lemmy.ml 20 points 1 week ago (4 children)

Is it really breaking it? As far as I'm aware, it's more like gnu. It has components and you can select what you use (here meaning distros and packagers).

People mistake this for a monolith because it's all named systemd-thing. Integration, like you said, was and is needed. But what if all those separate utilities and services are actually disconnected and speak some protocol different to pipe? Does it make it less unixy?

And poettering is an absolute good guy here. Pulseaudio wasn't perfect, but did it improve things compared to what was there before? Sure it did. Even now, pulesaudio protocol is used within pipewire and it works just fine.

Perfect is the enemy of good. And while all these tools might not be perfect, they are the best in the Linux world.

[–] ExtremeDullard@lemmy.sdf.org 30 points 1 week ago (4 children)

poettering is an absolute good guy here

Agreed. But he's also an abrasive know-it-all. A modicum of social skills and respect goes a long way towards making others accept your pet projects.

pulesaudio protocol is used within pipewire and it works just fine.

I wasn't talking about the protocol, I was talking about the implementation: PulseAudio is a crashy, unstable POS. I can't count the number of hours this turd made me waste, until PipeWire came along.

[–] ijhoo@lemmy.ml 14 points 1 week ago (2 children)

Pulseaudio was introduced in 2004. How come it took almost 20y for it to be replaced if it was that bad?

Implementation, being what it is, improved the situation compared to alsa and other things before it. Again, while not perfect it made things better for everyone.

It's funny that this is a thing attributed to poettering as bad since things before were way worse... why not throw Sticks and stones at those people?

I really don't get it.

And all of these things are optional. The fact that distro people and companies select them is because they solve real world problems.

[–] p03locke@lemmy.dbzer0.com 17 points 1 week ago

Pulseaudio was introduced in 2004. How come it took almost 20y for it to be replaced if it was that bad?

Did you learn nothing from X11 usage? May I remind you that X11 was invented by Xerox in the fucking 80s?!

Bad software attaches itself to OSs like a cancer.

load more comments (1 replies)
[–] calamityjanitor@lemmy.world 12 points 1 week ago (3 children)

I always assumed that Poettering is an arse to people because of the hate he got for systemd. I imagine it's hard to see the best in people when there's a crowd of haters everywhere you go. Though I have no idea what he was like beforehand.

[–] ijhoo@lemmy.ml 17 points 1 week ago (3 children)

People are idiots.

Poettering got death threats for systemd.

load more comments (3 replies)
load more comments (2 replies)
[–] Laser@feddit.org 9 points 1 week ago

Agreed. But he’s also an abrasive know-it-all. A modicum of social skills and respect goes a long way towards making others accept your pet projects.

This isn't what I get when reading bug reports he interacts in. Yeah, sometimes he asks if something can't be done another way – but he seems also very open to new ideas. I rather think that this opinion of him is very selective, there are cases where he comes off as smug, but I never got the impression this is the majority of cases.

I wasn’t talking about the protocol, I was talking about the implementation: PulseAudio is a crashy, unstable POS. I can’t count the number of hours this turd made me waste, until PipeWire came along.

PipeWire for audio couldn't exist nowadays without PulseAudio though, in fact it was originally created as "PulseAudio for Video"; Pulse exposed a lot of bugs in the lower levels of the Linux audio stack. And I do agree that PipeWire is better than PulseAudio. But it's important to see it in the context of the time it was created in, and Linux audio back then was certainly different. OSS was actually something a significant amount of people used…

load more comments (1 replies)
load more comments (3 replies)
load more comments (12 replies)
[–] webghost0101@sopuli.xyz 46 points 1 week ago (10 children)

Unrelated but how do people feel about the ai images when used for something like this.

The font is very telling for being DallE

[–] NightFantom@slrpnk.net 33 points 1 week ago (2 children)

I think it strongly detracts from the post. I basically skipped right to the comments without clicking the link because I'm assuming it's AI slop, and I'm hoping the comments are interesting.

load more comments (2 replies)
[–] jol@discuss.tchncs.de 15 points 1 week ago (1 children)

I strong hate these imagines with a piss tint. I can't stand them. And the text has these tiny AI-flavoured imperfections too.

load more comments (1 replies)
[–] HiddenLayer555@lemmy.ml 8 points 1 week ago* (last edited 1 week ago) (7 children)

People would be less mad if you straight up used a stock image with a watermark so I don't understand why people go out of their way to use AI when they know people will comment on it and it will detract from the point of the article.

Also, using AI in the thumbnail makes people automatically assume you're using AI in the text as well. And if you're not doing that, why would you lessen the perceived value of your writing by making it seem like you are?

It just seems pointless and actively harms your actual goals because people will get hung up on the fact that you used AI and ignore your actual valid points. Especially when you're writing about open source projects when most people interested in open source are vehemently anti-AI, it really just shows you don't know your target audience.

load more comments (7 replies)
[–] isVeryLoud@lemmy.ca 7 points 1 week ago

The piss stain colour palette confirms it.

load more comments (6 replies)
[–] Kabutor@lemmy.dbzer0.com 37 points 1 week ago (3 children)

It's refreshing to read to someone that actually says "I was so wrong"

I was wrong also with systemd, I hated it mainly because I already knew init.d, where files are, where configs where etc. Some years later hate is gone, I'm not a power user, but I just now know how to handle my things with systemd and all is good.

load more comments (3 replies)
[–] Allero@lemmy.today 29 points 1 week ago (12 children)

I'd say the main bad part of systemd is how it's used and now expected everywhere.

If you search for some Linux guides or install something complicated or whatnot, they always expect you to have systemd. Otherwise, you're on your own figuring how things work on your system.

This shouldn't really happen. Otherwise, yes, it's great, it integrates neatly, and is least pain to use.

[–] Strit@lemmy.linuxuserspace.show 27 points 1 week ago

In my opnion, systemd is like core-utils at this point.

It's so integrated into most things and the default so many places, that most guides assume you have it.

[–] whaleross@lemmy.world 18 points 1 week ago (1 children)

There is no authority delegating responsibilities of writing tutorials for Linux. It is the responsibility of nobody and everybody. If you can't find one for your problem, write it yourself when you have figured it out.

[–] Allero@lemmy.today 7 points 1 week ago* (last edited 1 week ago) (1 children)

Sure, but I can't single-handedly create an entire knowledge base on doing everything with X, so it's a real and big limitation.

load more comments (1 replies)
load more comments (10 replies)
[–] thatradomguy@lemmy.world 22 points 1 week ago (6 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.

[–] urandom@lemmy.world 19 points 1 week ago (2 children)

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

load more comments (2 replies)
[–] DarkMetatron@feddit.org 14 points 1 week ago (4 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 😜

load more comments (4 replies)
[–] MangoCats@feddit.it 7 points 1 week ago (2 children)

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 (2 replies)
load more comments (2 replies)
[–] morkyporky@suppo.fi 21 points 1 week ago (7 children)

I hated it and still do because for a period of years every weird, difficult to find issue on a bunch of servers was caused by systemd. It may be fine now, but I switched to Devuan and have had incredible stability. Poettering's response to security issues was also terrible and honestly the dude seems like a real piece of shit.

load more comments (7 replies)
[–] the_wiz@feddit.org 21 points 1 week ago

I still doesn't like it...

[–] sxan@midwest.social 18 points 1 week ago (9 children)

I've been using systemd on most of my systems since it was released; I was an early jumper to upstart as well.

The thing I don't like about systemd is how pervasive in the OS it is. It violates the "do one thing, do it well" Unix philosophy, and when systemd went from an init system to starting to take everything over, I started liking it less.

My issues with systemd is that it isn't an unmitigated success, for me. journald is horrible: it's slow and doesn't seem to catch everything (the latter is extremely rare, but that it happens occasionally makes me nervous). There are several gotchas in running user services, such as getting in-session services working correctly (so that user services can access the user session kernel keyring).

Recently I've been using dinit on a system, and I'm pretty happy with it. I may switch all of my systems over to it; I'm running Arch everywhere, and while migrating Arch to Artix was scary the first time, in the end it went fairly smoothly.

Fundamentally, systemd is a monolithic OS system. It make Linux into more of a Windows or MacOS, where a bunch of different systems are consolidated under a single piece of software. While it violates the Unix philosophy, it has been successful because monolithic systems tend to be easier to use: users really only have to learn two command-line tools, vs a dozen. Is it categorically better, just because the user interface is easier for new Linux users?

load more comments (9 replies)
[–] DonutsRMeh@lemmy.world 16 points 1 week ago

I've never used any other init system since I'm relatively new to Linux (8 years of use). So, systemd is all I know. I don't mind it, but I have this one major issue with it. That "stop job for UID 1000......" Or whatever it says. It's hands down the most annoying thing I have ever experienced in Linux. Making me wait for 3 minutes sometimes is just insane. I know I can go in and make it wait for 5 seconds /etc/systemd/system.conf or whatever, but why? Also, another one usually pops up.

Other than that, I really like how I can make timers. I like how I can make scripts run on boot, logout or login. And I like how I can make an app a background service that can auto start if they ever crashed. Maybe all of this can be done with other init systems? I wouldn't know, but I like these in systemd

[–] socsa@piefed.social 16 points 1 week 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.

load more comments (1 replies)
[–] procapra@lemmy.ml 14 points 1 week ago (5 children)

I use it because I'm frankly too dumb to use something else, but if that wasnt the case, i dont think id be speaking fondly of it.

I'm a ram usage fetishist, I absolutely disagree with the "unused ram is wasted ram" phrase that has caught on with people.

I see some of these distros running a graphical environment with only 90mb ram usage and i cream myself. All of them run something other than systemd, usually avoid GNU stuff, and...require you basically to be a developer to use them.

I already run a half broken, hacked together system due to my stubborness, I can't imagine how fucked I'd be if I tried one of these cool kid minimalist distros.

load more comments (5 replies)
[–] idriss@lemmy.ml 13 points 1 week ago

I totally agree.

I hate to admit I didn't want anything to do with systemd because it took me forever to get somewhat familiar with some other mainstream init systems.

Then, I didn't care for a while until I developed software that had to keep running using some sort of init system. The obvious choice was whatever the default I had (systemd) and I fell in love with the convenience of systemd (templates, timers, ..). I started shipping sample systemd with the things I provide & yes, you are on your own if you use something else.

[–] paequ2@lemmy.today 13 points 1 week ago (6 children)

I'm in Guix Linux land right now and I miss journald. I'm supposed to wade through all the log files in /var/log myself??

[–] mactan@lemmy.ml 18 points 1 week ago (1 children)

I still have no idea how to find the right record to read but at least I can run a journalctl --follow till my crash happens

load more comments (1 replies)
load more comments (5 replies)
[–] projectmoon@forum.agnos.is 13 points 1 week ago (1 children)

I'm over here still using OpenRC. Mostly because I want to. Some servers I run have systemd on them. systemd is generally nice. OpenRC has finally gained the ability to run user services, which is also very nice.

[–] sxan@midwest.social 9 points 1 week ago

dinit also has the ability to run user services, FWIW.

[–] juipeltje@lemmy.world 12 points 1 week ago

I decided to finally lean into using systemd more while i've been using NixOS, since the OS already relies heavily on it anyway. Created targets for my window managers, starting all my programs with services instead of autostart scripts, etc. And it worked fine for the most part, except for some reason, in qtile the systray widget refuses to load the nm-applet when it's started through systemd. Waybar does not have this problem. I can't help notice that systemd is not just a little slower, which isn't the biggest deal in the world, but it also tends to hang more often when shutting down, which is a bit annoying and reminds me of windows lol. Before NixOS i used Void, and while i never really cared too much about what init system i'm running, i can't help but really appreciate runit for being so simple and fast. I'm thinking of moving back to Void but using the Nix package manager on top. I recently found a solution to the nix driver problem when using it on other distros, so now i should be able to combine the best of both worlds.

[–] gnuhaut@lemmy.ml 12 points 1 week ago (4 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.

load more comments (4 replies)
[–] dino@discuss.tchncs.de 10 points 1 week ago

Void Linux doesn't use systemd.

[–] LeFantome@programming.dev 8 points 1 week ago

Though I see Systemd as an improvement, I still do not like it.

The Chimera Linux FAQ captures my thoughts quite well:

https://chimera-linux.org/docs/faq#what-is-the-projects-take-on-systemd

load more comments
view more: next ›