On Sun, Mar 18, 2012 at 03:15:02PM +0200, Alan McKinnon wrote > Here's what I want: > > When the machine starts, I want services X, Y and Z to run. The > software figures out what order they must start in and how the deps > work. Clean, neat, easy.
systemd is like Captain Picard of STTNG (Start Trek The Next Generation) always saying "make it so". *HOW DO YOU "MAKE IT SO"? That intelligence has to be somewhere. So what alternative do you propose? A bash or ash script is more guaranteed to run than a binary. Shoving all that "intelligence" into the service itself, means that the service has to start up in order to determine whether it's safe for the service to start up. What's wrong with this picture? And if systemd is so great, here's my supersystemd #!/bin/bash ... ... /etc/init.d/net.lo start /etc/init.d/net.eth0 start /etc/init.d/net.sshd start etc, etc, etc -- Walter Dnes <waltd...@waltdnes.org>
