You are not logged in.
Pages: 1
Do we still hate systemd in 2023? Maybe they have fixed all those things for all those years, didn't they?
Offline
Waste of time asking that here!!!
We are here because we want nothing to do with systemd - Debian's biggest mistake was to try & force it onto its users, that's why Devuan exists.
Offline
Do we still hate systemd in 2023? Maybe they have fixed all those things for all those years, didn't they?
If systemd still runs as process id 1, im calling that init "not fixed".
Offline
This malware, called "systemd" added new feature:
A new "soft-reboot" mechanism has been added to the service manager. A "soft reboot" is similar to a regular reboot, except that it affects userspace only: the service manager shuts down any running services and other units, then optionally switches into a new root file system (mounted to /run/nextroot/).
Offline
Lenart now works at microsoft.
Make up your mind on that.
Last edited by czeekaj (2023-08-31 07:41:52)
Offline
Systemd still does NOT adhere to core *nix principles:
Build a tool for a single task, make it perform that task to perfection. It does NOT do other tasks as that compromises the original task execution.
Online
If it was bad eleven years ago then it's still bad today. Probably even worse.
Offline
Systemd still does NOT adhere to core *nix principles:
Build a tool for a single task, make it perform that task to perfection. It does NOT do other tasks as that compromises the original task execution.
Yea, as promised systemd is fully modular and anyone can choose what functionality they want ... oh wait ...
Offline
...imho, it's just M$ hobbling the competition.
pic from 1993, new guitar day.
Offline
Yes it's bad and it has even gotten worse over the years. Gobbling up more and more features. A big blob.
Offline
My understanding of the situation is this:
(1) For the end-user, it doesn't make much of a difference. When you choose to use a Linux distro specifically because it doesn't use systemd, you're taking sides in an ideological battle more than you're making a decision on practical grounds.
(2) At the time when systemd was created, Sysvinit and Upstart were the only init systems around. They had certain unsustainable problems for developers that systemd fixed, and that's why all of the major Linux distros switched to it between 2011 and 2014.
(2) Sysvinit, Upstart, and systemd are no longer the only init systems to choose from, so the case for using systemd is much weaker than it was in 2011-2014.
(4) The real issue is not whether systemd is "good" or "bad". The real issue is whether monopolization of the linux ecosystem by any one init system is good or bad. Spoiler alert: it's very, very bad. Systemd occupies that slot now, but in an alternate timeline where systemd never existed, we'd probably all be whining and bitching about Upstart instead.
Offline
Fair enough; though that storyline that "systemd fixed something unsustainable for developers" is and was just plain marketing speech, and it's far off any reality. But the proponents sure filled the web with that thought so it's voiced failry commonly.
Offline
Fair enough; though that storyline that "systemd fixed something unsustainable for developers" is and was just plain marketing speech, and it's far off any reality.
So what's the real reason why Fedora, RHEL, and Ubuntu moved from Upstart to systemd?
Offline
The person responsible for systemd now works for Microsoft after he wormed systemd into Linux. The Debian vote was a sham:
Combatting revisionist history https://forums.debian.net/viewtopic.php?t=120652
Embrace : Extend : Extinguish in action
Offline
Let us also not overlook the fact that systemd and pretty much everything else coming out of redhat/freedesktop et-al these days is under weak-copyleft or non-copyleft licences (e.g. LGPL or MIT).
If you want to speculate on plausible, non-technical motivation for systemd aggressively absorbing so much functionality previously provided by independent projects, look no further than circumventing the inconvenient (for redhat and their corporate overlords) restrictions in the GPL (especially GPL3) regarding linking non-free code against GPL code and its distribution as part of commercial products.
IOW, is it really "Embrace, Extend, Extinguish", or more "Embrace, Corrupt, Sell"? I expect only time will tell.
Last edited by steve_v (2023-10-24 04:07:26)
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.
Offline
Pages: 1