Originally posted by pkese
View Post
systemd actually sypports rc.d scripts fine. In fact, you can start your services from those scripts. If you wanted to start apache from rc.d you could do systemctl disable apache to stop it from being started from the unit file and then put in an rc.d script to start it.
This is why the anti-systemd rhetoric is nonsense. it does not take away the old way of doing things, it just adds new features in addition to the older features. So apparently what anti-systemd people object to is the introduction of new features that they think other people should not be allowed to do.
systemd is all open source, so by definition, it can be "taken apart" meaning you can read the source code and do with it what you please.
systemd, due to its ability to use dbus, is also decentralized and allows a loosely coupled way of doing things. This actually allows you to write your own daemon that can respond to system events on the bus. This means it can be made MORE loosely coupled than the shell scripts. This is true especially if you write your daemons which interact with the dbus protocol.
Comment