Without Systemd
I really sympathize with people who try to avoid systemd but I think it is a futile exercise.<p>Every piece of software these days assume you are running systemd and make your life miserable when you try not rely on systemd, and sometimes, it is even not possible to run without systemd at all.<p>Unfortunately, people don&#x27;t remember how was the systemd adoption and why it was so controversial.<p>systemd was promoted as a init system, but in reality, it is more than that, it is a suite of software; we have journald, firewalld, udevd, logind, networkd, resolved and many more.<p>People forgot how systemd was forced to everybody when Gnome made systemd-logind a hard dependency and logind was extracted to elogind so people could initialize their desktop without using systemd.<p>The same happened with udev, forcing Gentoo to fork it into eudev to avoid systemd dependency.<p>People complaint about portability and compatibility because you cannot interact with systemd-* without systemd; you are coupled.<p>The problem is not systemd as a software, is the attempt to hijack the entire ecosystem, replacing existing services with services dependents of systemd, forcing systemd adoption.<p>And the question I ask to you is: who is behind this?