When does systemd stop? Linux without it is increasingly looking unlikely in the future. Are we not worried about it being a single point of failure and attack vector?
This isn't a moan about the unix philosophy btw, but a genuine curiosity about how we split responsibilities in todays linux environment.
SystemD will consume the entirety of Linux, bit by bit.
In 2032, SystemD announces they're going to be introducing a new way to manage software on Linux
In 2035, SystemD will announce they're making a display system to replace the ageing Wayland
In 2038, the SystemD team announces they're making their own desktop environment
In 2039 SystemD's codebase has grown to sixteen times its size in the 2020s. SystemD's announces they're going to release replacements for most other packages and ship their own vanilla distro.
In 2045 SystemD's distro has become the standard Linux distribution. Most other distros have quietly faded away.
In 2047, SystemD announces they're going to incorporate most of GNU into SystemD. Outrage ensues from the Free Software Foundation, which vehemently opposes this move.
In 2048, Richard Stallman dies of a heart attack after attempting to clone SystemD's git repo. SystemD engages in a hostile takeover and all resistance within the FSF crumbles
In 2050, SystemD buys the struggling RedHat from IBM for $61 million.
In 2053, most world governments have been pressured into using SystemD.
In 2054, Linus Torvalds, fearing for his life, begins negotiations to merge kernel development into SystemD
In 2056, the final message on the Linux kernel development mailing list is sent.
In 2058, Torvalds dies under suspicious circumstances after his brand-new laptop battery explodes.
In 2060, SystemD agents assassinate the CEO of Microsoft.
In 2063, after immense pressure from SystemD-controlled human rights organisations, Arch developers discontinue development.
In 2064, the remaining living Debian developers release the next stable version of their clandestine and highly illegal distro.
Yes, because it's easier to take care of octogenarians than people who might actually put up a fight to having their laptop batteries replaced with a pipe bomb.
One way to notice a person has "systemd derangement syndrome" is by looking at how they write systemd: if they write it SystemD they are already in late stages of SDS and it isn't curable anymore.
By this logic the Linux kernel is also a single point of failure and attack vector.
sudo isn't going away, so does doas.
run0 is just another alternative to use or not.
There are still distribution out there without systemd and if there ever won't be any systemd-free distributions left and systemd would become a critical part of the Linux ecosystem, then it would get the same treatment as the Linux kernel with many professional maintainers.
plus, it isn't like this isn't exactly like adding another "door" to the "systemd building". It's a modular component of systemd, so more akin to replacing the sudo building with a new, but still separate, systemd sudo building
@Olap
I agree. As someone who uses systemd on daily basis (I use Arch, BTW 😄) I really like it, but I am a bit worried about it being a single point of attack. Maybe just push doas as default instead? I never used doas but I watched few videos about it, so I guess it's fine and probably better than sudo (less bloated).
Just my few cents.
I don't see how something would be inherently easier to attack if it is called systemd-foo instead of just foo. Attack surface and vectors do not depend on which project develops a particular tool.
They seem to. Debian explicitly supports multiple init systems, sysvinit being the primary alternative, so packages have to handle systemd-init not being there.