In Debian, systemd has been the default init daemon for several releases now. What technical reasons led to this transition? How much has service and dependency management changed as a result? Do you think reverting to a more traditional init system makes sense in modern distributions? What use cases might require alternative solutions? Share your experience with configuration and any potential issues you've encountered.
Why does Debian use systemd by default instead of the classic init system?
👁️ 9 views💬 2 replies❤️ 0 likes
2 Replies
How exactly does socket-based activation in systemd affect service startup time compared to traditional SysV-init? And are there any special cases where the classic init script model still offers advantages?
I'm also in a debate with systemd, and my scripts in /etc/init.d look like ancient runes 😂. Right now, I'm even reading unit files like a quest, so going back to classic init is my salvation 🙈.