What could this folder mean /etc/init.d?

I have to install an app provided by tplink for its outdoor access point. The app is provided in tar.gz file and its manual specifies that the file be untar and the install.sh be executed. However, it seems to look for a certain init.d which I am not so sure has something to do with sysv or not. Anyway, I am only familiar with systemd. I wonder if there is anything that could resolve this.

[Omada_SDN_Controller_v5.9.31_Linux_x64]$ sudo bash ./install.sh 
[sudo] password for cw: 
Omada Controller will be installed in [/opt/tplink/EAPController] (y/n): y
Installation start ...
ln: failed to create symbolic link '/etc/init.d/tpeap': No such file or directory
which: no mongod in (/home/cw/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/var/lib/snapd/snap/bin)
Install Omada Controller failed!
Roll back ...

Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

If you don’t know what you’re doing, you better use premade scripts to install it.

It is available in the AUR.


Read the AUR WIKI page first Arch User Repository - Manjaro then you can install it when you understand it all.

Using provided Linux installation from manufacturer is often/always a bad idea, because they make installers for Ubuntu generally, or other specific OS and do not target/support Arch and its derivatives, hence the use of install scripts made by Arch community is preferred instead.

init.d is another init daemon. It is alternative to systemd. Since systemd is a couple of years old and quite popular, this install script should be pretty archaic.
As a general rule: install things manually as last resort. If you do not understand what a script does, do not install.

In that particular case - omada-controller (5.9.31) is available as AUR package. And i see in the build script is is made for systemd. So it is no brainer - install that.