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

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