quick summary
- Monolithic design: Systemd is a large, complex piece of software that combines many system management functions, rather than having separate, specialized tools as in the traditional Unix philosophy.
- Proprietary configuration format: Systemd uses its own configuration file format (.service, .socket, etc.) rather than traditional plaintext configuration files.
- Tight integration: Systemd is deeply integrated with the kernel and other core system components, rather than maintaining a more modular, loosely-coupled architecture.
- Complexity: The systemd codebase is very large and feature-rich, which some see as unnecessary complexity compared to simpler init systems like SysV init or BSD init.
- Departure from Unix principles: Systemd is seen by some as moving away from the Unix philosophy of "do one thing and do it well" in favor of a more centralized, opinionated system management approach.
few comparison
- Launching script just after boot sequence
in SysVinit you can run scripts during the boot process ( right after the system finishes booting up ) simply by putting your shell command into /etc/rc.local
To achieve the same result in systemd is rather complex see
- https://unix.stackexchange.com/a/544826
- https://www.linuxbabe.com/linux-server/how-to-enable-etcrc-local-with-systemd
- https://www.cyberciti.biz/faq/how-to-enable-rc-local-shell-script-on-systemd-while-booting-linux-system/
- to be continued...