years ago systemd comes to chakra as init replacement for the old, well tested and reliable init process because systemd has some fancy features.
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
so have systemd some “surprises” in his belly… some handy and some useless and some dangerous and all without my permission.
yes dangerous, a view weeks ago i had a unbootable system and other time systemd-fsck deleted booth filsystem checkpoints and i lost all my data.
my thought is: split systemd into his 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:
- init daemon
- a package group for network with systemd-network, systemd-resolv, systemd-rfkill
- a package fo systemd-nspawn
- a package group for journal-remote, journal-upload
- a package for systemd-sysusers
- a package for systemd-cryptsetup
- a package for systemd-quotacheck
- a package for systemd-machined
i think systemd filthy fingers shouldn’t touch my system less it is possible.
what do you think?