> You can force it if you want to, but in normal operations, starting sshd without waiting for the network to appear is just flat out wrong. It will not work.

> You can force it if you want to, but in normal operations, starting sshd without waiting for the network to appear is just flat out wrong. It will not work. There is no such thing as flat out wrong. Troubleshooting other peoples servers I need to work around many different situations. A '--ignore-dependencies" is nice, but won't cut it as it depends greatly on the situation at hand. Perhaps sshd also has a dependency not just on networking but also on slapd or something. Perhaps I do not want networking, but I do want slapd to be running. systemd having a better memory than me is, well, true. It doesn't solve my problems for me though. The Windows Registry also has a better memory than me, but I prefer my configs in a textfile I can parse, grep and maintain with any tool I choose. Same with systemd: better memory than me, but I do not really need a better memory than me. My memory is good enough. But meanwhile the world has made up it's mind and in all likelyhood Debian will be using systemd. So I might as well start the learning curve and be done with it.