Keith Daniels wrote: > My bias is anti systemd, just so you know.-- scant documentation and there > has never been a security review of its package. > Meanwhile the situation has improved. There are many things improved including documentation. What I can recommend is the "systemd cheat sheet" which can be found in different flavors around. Just few examples. https://wiki.debian.org/systemd/CheatSheet https://gist.github.com/mbodo/8f87c96ce11e91f80fbf6175412a2206 My personal experience is ... after looking into it I used systemd free debian for some time until I was ready to move my system to systemd. It took me few hours ... mainly fixing some custom networking logic (scripts that would execute on certain conditions) and migrating few scripts. Since than I can not complain. I moved all systems from init to systemd - no issue. I can just conclude that the main problem is the unwillingness to grow. Of course I can understand this - why fixing something again after some 10-15y when it was working flawlessly ... but guys this is called evolution - for good or for bad. Using the default system brings the advantage that it is easily maintainable - and working on each and every package to work around systemd is IMO less efficient. As for the Felix's problem I think it is related to default manager. Did you try to remove or fix the service? # ls -al /etc/systemd/system/display-manager.service lrwxrwxrwx 1 root root 31 Jan 6 02:43 /etc/systemd/system/display-manager.service -> /lib/systemd/system/tdm.service # cat /lib/systemd/system/tdm.service [Unit] Description=Trinity Display Manager Documentation=man:tdm-trinity(1) Conflicts=getty@... plymouth-quit.service After=systemd-user-sessions.service getty@... plymouth-quit.service [Service] # temporary safety check until all DMs are converted to correct # display-manager.service symlink handling ExecStartPre=/bin/sh -c '[ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "tdm" ]' ExecStart=/opt/trinity/bin/tdm Restart=always regards