8053 beefd0184a 2022-08-08 ct_chen пре 2 година
..
README beefd0184a 2022-08-08 ct_chen пре 2 година
alignment.sh beefd0184a 2022-08-08 ct_chen пре 2 година
avahi-daemon beefd0184a 2022-08-08 ct_chen пре 2 година
banner.sh beefd0184a 2022-08-08 ct_chen пре 2 година
bluetooth beefd0184a 2022-08-08 ct_chen пре 2 година
bootmisc.sh beefd0184a 2022-08-08 ct_chen пре 2 година
checkroot.sh beefd0184a 2022-08-08 ct_chen пре 2 година
dbus-1 beefd0184a 2022-08-08 ct_chen пре 2 година
devpts.sh beefd0184a 2022-08-08 ct_chen пре 2 година
dmesg.sh beefd0184a 2022-08-08 ct_chen пре 2 година
functions beefd0184a 2022-08-08 ct_chen пре 2 година
functions.initscripts beefd0184a 2022-08-08 ct_chen пре 2 година
halt beefd0184a 2022-08-08 ct_chen пре 2 година
hostname.sh beefd0184a 2022-08-08 ct_chen пре 2 година
mountall.sh beefd0184a 2022-08-08 ct_chen пре 2 година
mountnfs.sh beefd0184a 2022-08-08 ct_chen пре 2 година
ofono beefd0184a 2022-08-08 ct_chen пре 2 година
populate-volatile.sh beefd0184a 2022-08-08 ct_chen пре 2 година
rc.pvr beefd0184a 2022-08-08 ct_chen пре 2 година
read-only-rootfs-hook.sh beefd0184a 2022-08-08 ct_chen пре 2 година
reboot beefd0184a 2022-08-08 ct_chen пре 2 година
rmnologin.sh beefd0184a 2022-08-08 ct_chen пре 2 година
run-postinsts beefd0184a 2022-08-08 ct_chen пре 2 година
save-rtc.sh beefd0184a 2022-08-08 ct_chen пре 2 година
sendsigs beefd0184a 2022-08-08 ct_chen пре 2 година
single beefd0184a 2022-08-08 ct_chen пре 2 година
sysfs.sh beefd0184a 2022-08-08 ct_chen пре 2 година
systemd-udevd beefd0184a 2022-08-08 ct_chen пре 2 година
umountfs beefd0184a 2022-08-08 ct_chen пре 2 година
umountnfs.sh beefd0184a 2022-08-08 ct_chen пре 2 година
urandom beefd0184a 2022-08-08 ct_chen пре 2 година

README

You are looking for the traditional init scripts in /etc/init.d,
and they are gone?

Here's an explanation on what's going on:

You are running a systemd-based OS where traditional init scripts have
been replaced by native systemd services files. Service files provide
very similar functionality to init scripts. To make use of service
files simply invoke "systemctl", which will output a list of all
currently running services (and other units). Use "systemctl
list-unit-files" to get a listing of all known unit files, including
stopped, disabled and masked ones. Use "systemctl start
foobar.service" and "systemctl stop foobar.service" to start or stop a
service, respectively. For further details, please refer to
systemctl(1).

Note that traditional init scripts continue to function on a systemd
system. An init script /etc/init.d/foobar is implicitly mapped
into a service unit foobar.service during system initialization.

Thank you!

Further reading:
man:systemctl(1)
man:systemd(1)
http://0pointer.de/blog/projects/systemd-for-admins-3.html
http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities