1You are looking for the traditional init scripts in {{ SYSTEM_SYSVINIT_PATH }},
2and they are gone?
3
4Here's an explanation on what's going on:
5
6You are running a systemd-based OS where traditional init scripts have
7been replaced by native systemd services files. Service files provide
8very similar functionality to init scripts. To make use of service
9files simply invoke "systemctl", which will output a list of all
10currently running services (and other units). Use "systemctl
11list-unit-files" to get a listing of all known unit files, including
12stopped, disabled and masked ones. Use "systemctl start
13foobar.service" and "systemctl stop foobar.service" to start or stop a
14service, respectively. For further details, please refer to
15systemctl(1).
16
17Note that traditional init scripts continue to function on a systemd
18system. An init script {{ SYSTEM_SYSVINIT_PATH }}/foobar is implicitly mapped
19into a service unit foobar.service during system initialization.
20
21Thank you!
22
23Further reading:
24        man:systemctl(1)
25        man:systemd(1)
26        http://0pointer.de/blog/projects/systemd-for-admins-3.html
27        https://www.freedesktop.org/wiki/Software/systemd/Incompatibilities
28