4 ms·

I could not care less about systemd because sysvinit is working fine here. I hate that you are forced in most distros to choose systemd without any alternative.

• cnvogel 13y ago
  Using systemd still allows you to have custom scripts run on boot up. Given a shell script you want to have running on boot you'd have linked that script to /etc/rc3.d on sysvinit. With systemd the proper way to activate it is a service file in /etc/systemd/… or /lib/systemd/… . It's different but I wouldn't call it more or less complicated than sysvinit. There are a lot of example/skeleton files floating around, especially archlinux's collection is useful. Of course, systemd allows for much more configuration than simple running of scripts on boot, but you can fine tune later.
• oblio 13y ago
  I think they're written dozens of times that systemd can run sysvinit scripts. In your experience is that feature not good enough?
• Jasper_ 13y ago
  As the article mentions, systemd has a full sysv init script compatibility mode, with some (trivial) incompatibilities: http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities/ http://www.freedesktop.org/wiki/Software/systemd/Incompatibi...
• 0x006A 13y ago
  i could not care less about sysvinit because systemd is working fine here.