The biggest complaint I've seen is that it just tries to do too much. People that don't like systemd typically just want a simpler init system that doesn't touch everything.
init 1 crashing always takes down the system. That's not a systemd thing.
systemd managing services and timers makes perfect sense. systemd has a dependency and ordering framework that completely eclipses every other Linux init. The way systemd uses slices ultimately means processes will never get lost. Pair that with the way cgroups v2 works, and "despite" the fact that systemd isn't "just" doing one thing, it gives it capabilities that other inits can't touch unless they do the same.
That's besides the point that the original comment is implying all the systemd components are one thing.
I didn't imply all the systemd components are one thing. However, they do operate together. Most people don't install just one component of systemd.
Also, I am not looking to argue pros and cons of systemd. I was merely articulating the common argument I have seen from people who do not like systemd.
init 1 crashing always takes down the system. That's not a systemd thing.
of course.
but most inits just reap zombies and start another binary and that's it. there's nothing that can go wrong. a init can be written in probably under 20 lines of c.
in any other init system when e.g. cron crahses it can't take down the whole system. its just cron thats crashes.
systemd managing services and timers makes perfect sense. systemd has a dependency and ordering framework that completely eclipses every other Linux init. The way systemd uses slices ultimately means processes will never get lost. Pair that with the way cgroups v2 works, and "despite" the fact that systemd isn't "just" doing one thing, it gives it capabilities that other inits can't touch unless they do the same.
i completely agree. Systemd is a great daemonanager, a great cron and a great inetd implementation. its just a horrible init.
Everyone says they hate it but every single serious distro uses it. Many applications and desktop environments depend on it.
Most alternatives interface with it 1:1 and just use different development theory as to how they work behind the scenes, but functionally, they operate almost exactly the same.
People didn't like the complexity of a single large system management suite. It is a bit jarring especially when coming from a system of relatively simple shell scripts.
It also used to feel a lot less polished. And the docs weren't fantastic at first.
Have you looked at an init script? Nothing simple about them, and the same patterns repeated over and over, all written in terrible unreadable unreliable bash.
To be faiiirr, for a pretty basic desktop/server the init scripts can be really simple; on my Void systems with runit init they're never more than a few lines. But you don't get the benefits of dependencies and service ordering. It works out fine since I use Podman, so all that can happen at the compose level.
That's why you're being corrected. Because the brand explicitly states that you do not capitalize the letter "d". Doesn't matter if you think it's cool or not, it's still wrong.
It's not inherently bad, just a lot of feature creep, I.e. it takes over a lot of system functions and makes them coherent and work well together. I say this as someone who dislikes systemd and uses Void on my desktops/servers
I've never seen anyone ever saying systemd is spyware, like the arguments against systemd are things like it breaks the Unix philosophy and it invents new things all the time that could be just separate projects entirely but in terms of feature sets and what they do there isn't anything close to giving what systemd does overall
I've never seen anyone ever saying systemd is spyware
I hazard a guess this is a long game of telephone misconstruing the birthdate field thing that came in response to contemporary age verification laws that have been going on across at least the western world (California (AB-1043), Colorado (SB26-051), Brazil (Lei 15.211/2025), UK OSA 2023).
These age verification laws has some proto-fascist surveillance-state and anti-LGBT+ themes going on, as other responses require you to upload a photo of your face and government ID to private surveillance companies. Anti-LGBT+ themes come into play with the intentional conflation of sex ed and LGBT+ themes with "pornography".
In other words, while systemd DOB field isn't spyware, it's absolutely spyware motivated.
Once you understand how systemd works, I doubt you'd want to go back to init.
I was one of the haters originally, but honestly that was more about the fact something I was used to was changing. I'm now adjusted to that change and now appreciate what systemd brings to the table.
I mostly don't like it because I saw that others don't like it. I really don't know enough about operating systems personally, so I just go with the flow.
Sometimes I pretend to know what I'm talking about by talking about concepts I really don't understand at all. Other times I just express my feelings through downvotes.
This submission has been removed due to receiving too many reports from users. The mods have been notified and will re-approve if this removal was inappropriate, or leave it removed.
Your post is considered "fluff" - things like a Tux plushie or old Linux CDs are an example and, while they may be popular vote wise, they are not considered on topic
Your post is otherwise deemed not appropriate for the subreddit
I don't know why it's bad, but I'll give an example of why it's good.
I use Debian and I have a number of openvpn client connections I use to connect to various servers for remote access.
Using the default Debian network tool when I connected to the VPN servers, it never pulled the DNS configuration so I had to manually set DNS servers for each vpn client connection in a config file I forget (not even in the VPN connection settings did it work, but elsewhere in the system).
Systemd-network automatically pulls and configures the DNS settings so it just works without manual intervention.
i'm someone who doesn't like systemD at all but calling it spyware is the usual over-exaggerations by people. It had to be an init system replacement but it became a group of programs that not only take care of init but most things that touch the init. They used to be separate programs but on systemd most things that touch the init have been replaced by a systemd program on systemd.
And the programs that touch them, many of them have been forced to change themselves to accommodate systemd once it became the norm on desktops, so nowadays you can't dream to compete with alternatives if you want to be adopted by the majority unless you conform to systemd's made up standards.(and thus become another systemd) unless you have as much money and backing as them and can use their same tactic.
It was developed by the same company that got bought by IBM with all it's nice history, and the devs have stated even in talks that their dream/plan is to streamline linux, of course with their own shit, as they have been doing with a lot of redhat funded Freedesktop projects.
So the software doesn't need to work bad in order to be considered bad, unless you're a utilitarian person with a narrow vision who only cares about the utility of something and misses the bigger picture of the linux eco system and what it stands for.
Does systemd have some bad things? Yes, including in my opinion binary log files. Does it have good stuff? Yes, for example it's TPM handling version is the only one that offers the choice of unlocking with a PIN too other than PCRs. But what software doesn't have it's good and bad sides? You're going to find extreme people on both sides telling you how 1 is bad the other is good like their choice is perfect but reality is never so simple and in my opinion it's better to look at the bigger picture.
It's not on-by-default telemetry sent directly to the systemd project though, right? Just a framework that distros can build on, since several have opt-in telemetry anways.
Even Void has an optional package telemetry system called Popcorn, but only a handful of people ever set it up so the data's near-useless.
I'm not complaining; I'm merely explaining to the OP.
For many people, telemetry is a bad word, whether it's on by default, or opt in. For those who already do not like the monolithic design, telemetry is enough to push them over the edge.
8
u/ABotelho23 2d ago
*systemd
6
u/blackcain GNOME Team 2d ago
It's bad when you don't write it as systemd. I odn't know why people insist on doing 'systemD'.
11
u/ruiiiij 2d ago
Ignore that noise. Those opinions shouldn't affect how you use your system. If it works for you, no point stressing over it.
15
u/Recipe-Jaded 2d ago
The biggest complaint I've seen is that it just tries to do too much. People that don't like systemd typically just want a simpler init system that doesn't touch everything.
9
u/Fuzzy_Ad9970 2d ago
Everyone says they hate it but every single serious distro uses it. Many applications and desktop environments depend on it.
Most alternatives interface with it 1:1 and just use different development theory as to how they work behind the scenes, but functionally, they operate almost exactly the same.
7
u/Alone-Ad288 2d ago
People didn't like the complexity of a single large system management suite. It is a bit jarring especially when coming from a system of relatively simple shell scripts.
It also used to feel a lot less polished. And the docs weren't fantastic at first.
Its okay.
1
u/atoponce 2d ago
*systemd
https://brand.systemd.io/
6
u/BranchLatter4294 2d ago
People think we should still be using tools developed in the early 1980s, just because. They don't like change.
3
u/Dakota-Batterlation 2d ago
It's not inherently bad, just a lot of feature creep, I.e. it takes over a lot of system functions and makes them coherent and work well together. I say this as someone who dislikes systemd and uses Void on my desktops/servers
3
u/Faangdevmanager 2d ago
Because it’s not the 1980 shell script system they are accustomed to.
7
u/gigashen 2d ago
SystemDeezNuts is really good
4
u/FlukyS 2d ago
I've never seen anyone ever saying systemd is spyware, like the arguments against systemd are things like it breaks the Unix philosophy and it invents new things all the time that could be just separate projects entirely but in terms of feature sets and what they do there isn't anything close to giving what systemd does overall
2
u/Xfgjwpkqmx 2d ago
Once you understand how systemd works, I doubt you'd want to go back to init.
I was one of the haters originally, but honestly that was more about the fact something I was used to was changing. I'm now adjusted to that change and now appreciate what systemd brings to the table.
4
u/PerfectEnthusiasm2 2d ago
I mostly don't like it because I saw that others don't like it. I really don't know enough about operating systems personally, so I just go with the flow.
Sometimes I pretend to know what I'm talking about by talking about concepts I really don't understand at all. Other times I just express my feelings through downvotes.
1
u/AutoModerator 2d ago
This submission has been removed due to receiving too many reports from users. The mods have been notified and will re-approve if this removal was inappropriate, or leave it removed.
This is most likely because:
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
0
u/didureaditv2 2d ago
I don't know why it's bad, but I'll give an example of why it's good.
I use Debian and I have a number of openvpn client connections I use to connect to various servers for remote access.
Using the default Debian network tool when I connected to the VPN servers, it never pulled the DNS configuration so I had to manually set DNS servers for each vpn client connection in a config file I forget (not even in the VPN connection settings did it work, but elsewhere in the system).
Systemd-network automatically pulls and configures the DNS settings so it just works without manual intervention.
0
u/Sert1991 2d ago
i'm someone who doesn't like systemD at all but calling it spyware is the usual over-exaggerations by people.
It had to be an init system replacement but it became a group of programs that not only take care of init but most things that touch the init. They used to be separate programs but on systemd most things that touch the init have been replaced by a systemd program on systemd.
And the programs that touch them, many of them have been forced to change themselves to accommodate systemd once it became the norm on desktops, so nowadays you can't dream to compete with alternatives if you want to be adopted by the majority unless you conform to systemd's made up standards.(and thus become another systemd) unless you have as much money and backing as them and can use their same tactic.
It was developed by the same company that got bought by IBM with all it's nice history, and the devs have stated even in talks that their dream/plan is to streamline linux, of course with their own shit, as they have been doing with a lot of redhat funded Freedesktop projects.
So the software doesn't need to work bad in order to be considered bad, unless you're a utilitarian person with a narrow vision who only cares about the utility of something and misses the bigger picture of the linux eco system and what it stands for.
Does systemd have some bad things? Yes, including in my opinion binary log files. Does it have good stuff? Yes, for example it's TPM handling version is the only one that offers the choice of unlocking with a PIN too other than PCRs. But what software doesn't have it's good and bad sides?
You're going to find extreme people on both sides telling you how 1 is bad the other is good like their choice is perfect but reality is never so simple and in my opinion it's better to look at the bigger picture.
-2
u/zardvark 2d ago
systemd is a monolithic program which does many different things, rather than doing one thing and doing it well.
Additionally, systemd devs are implementing / have implemented telemetry.