7550 3602ad0575 1.First upload. il y a 5 ans
..
README 3602ad0575 1.First upload. il y a 5 ans
alignment.sh 3602ad0575 1.First upload. il y a 5 ans
avahi-daemon 3602ad0575 1.First upload. il y a 5 ans
banner.sh 3602ad0575 1.First upload. il y a 5 ans
bluetooth 3602ad0575 1.First upload. il y a 5 ans
bootmisc.sh 3602ad0575 1.First upload. il y a 5 ans
checkroot.sh 3602ad0575 1.First upload. il y a 5 ans
dbus-1 3602ad0575 1.First upload. il y a 5 ans
devpts.sh 3602ad0575 1.First upload. il y a 5 ans
dmesg.sh 3602ad0575 1.First upload. il y a 5 ans
functions 3602ad0575 1.First upload. il y a 5 ans
functions.initscripts 3602ad0575 1.First upload. il y a 5 ans
halt 3602ad0575 1.First upload. il y a 5 ans
hostname.sh 3602ad0575 1.First upload. il y a 5 ans
mountall.sh 3602ad0575 1.First upload. il y a 5 ans
mountnfs.sh 3602ad0575 1.First upload. il y a 5 ans
ofono 3602ad0575 1.First upload. il y a 5 ans
populate-volatile.sh 3602ad0575 1.First upload. il y a 5 ans
rc.pvr 3602ad0575 1.First upload. il y a 5 ans
read-only-rootfs-hook.sh 3602ad0575 1.First upload. il y a 5 ans
reboot 3602ad0575 1.First upload. il y a 5 ans
rmnologin.sh 3602ad0575 1.First upload. il y a 5 ans
run-postinsts 3602ad0575 1.First upload. il y a 5 ans
save-rtc.sh 3602ad0575 1.First upload. il y a 5 ans
sendsigs 3602ad0575 1.First upload. il y a 5 ans
single 3602ad0575 1.First upload. il y a 5 ans
sysfs.sh 3602ad0575 1.First upload. il y a 5 ans
systemd-udevd 3602ad0575 1.First upload. il y a 5 ans
umountfs 3602ad0575 1.First upload. il y a 5 ans
umountnfs.sh 3602ad0575 1.First upload. il y a 5 ans
urandom 3602ad0575 1.First upload. il y a 5 ans

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