Using systemd still allows you to have custom scripts run on boot up. Given a shell script you want to have running on boot you'd have linked that script to /et

Using systemd still allows you to have custom scripts run on boot up. Given a shell script you want to have running on boot you'd have linked that script to /etc/rc3.d on sysvinit. With systemd the proper way to activate it is a service file in /etc/systemd/… or /lib/systemd/… . It's different but I wouldn't call it more or less complicated than sysvinit. There are a lot of example/skeleton files floating around, especially archlinux's collection is useful. Of course, systemd allows for much more configuration than simple running of scripts on boot, but you can fine tune later.