salve,

years ago systemd comes to arch as init replacement for the old, well tested and reliable init process because systemd has some fancy features.

and now?
systemd is growing in his functionality and brought some “features” to our system…silent with the behaviour of an trojan horse.
do you know the story about the trojan horse? no? i will tell you in a short version

after 10 years beach party and permanent disturbing the locals leaf the achain troublemakers the trojan shores.
next day comes the trojan citizens and found on the beach a lot of garbage and a big wooden horse. thy thought the horse where a nice gift to pallas athene and brought it to the city but in the night comes some achain warriors out of the horses belly and opened the ports to troja for the other achaian warriors… a mass of trojans where slaughtered, the surviving ends there lifetime in slavery and the city was burned to the ashes.

so have systemd some “surprises” in his belly… some handy and some useless and some dangerous and some without my permission.
yes dangerous, a view weeks ago i had a unbootable system and other time systemd-fsck deleted booth f2fs filsystem checkpoints and i lost all my data.

my thought is: split systemd into the functionality to make it more KISS like and bring back the control of your systems
you know “divide et impera”

i think it should be splinted in to the:

1) init daemon
2) a package group for network with systemd-network, systemd-resolv, systemd-rfkill
3) a package fo systemd-nspawn
4) a package group for journal-remote, journal-upload
5) a package for systemd-sysusers
6) a package for systemd-cryptsetup
7) a package for systemd-quotacheck
8) a package for systemd-machined
9) <your idea>

i think systemd filthy fingers shouldn’t touch my system less it is possible.
what do you think?

K_eep
I_t
S_mall
S_tupid
…and systemd is every thing else but not small nor simple