systemd is good, but it is not completely ready yet. Take systemd's user instances: from what I understand, it should be possible to run a user's services/sockets even when he doesn't log in when he is enabled via "loginctl enable-linger $username". But there are currently scripts provided to do that (user-session-units) because lingering doesn't seem to work. When you try to start a systemd user instance on a headless machine, you get errors because the display variable is not set, might be a dbus issue, but user-session-units has a service file that works around that. So, from my impressions, it is not feature-complete yet. Not a biggie though as it already handles much more than any init system I ever saw and makes administration really easy IMHO. TBH, I dunno why you would want to go back to a classic syslog with all the comfort journalctl provides. Or managing your startup dependencies yourself.