Comment Re:Give my my SysVInit (Score 1) 157
Yes you absolutely can do it for some modules. For example, systemd-timesyncd can be removed and ntpd or chrony installed instead if you need more functionality than just simple client time syncing, such as when you need your own time source as well as syncing.
Likewise systemd-resolved is often left out and a caching local DNS server can be used instead, or left out entirely.
And I very well could remove systemd-networkd and systemd-container since I don't use containers, flatpak, or kvm.
Can I remove others? Possibly, but there's not a lot of reason to do so. These modules serve valid purposes and address actual technical shortcomings we had before, such as process cleanup which was often a problem before systemd-pam.
Shrug. It's not a boogeyman. No one's out to get you. It's not a government plot. There are many valid reasons why systemd has become a core Linux component. There are plenty of distros (and operating systems) that eschew systemd if you don't want or need features like containers and KDE or Gnome, etc.
that can run your old classic desktop environments like you always used to.