So, you have migrated your arch linux to systemd and your beloved rc.local is not executed anymore? Time to jump into the systemd by writing your own unit. You have two options. One would be to write a unit that simple executes the rc.local. The second option would be to split up your rc.local into logical parts and write one unit per logical part (like "setup [w]lan, mount filesystems, start service xyz").
I want to provide you a way to implement the second solution. I can tell you, after you have written your first systemd unit, the concept of systemd won't be that big alien in you mind. I still have a tear drop in my eyes when i think back to my "only two files to configure my system"-systemV times, but thats nothing for this blog entry .
So lets go and write a systemd unit to start up your wlan interface by using wpa_supplicant and dhcpd.
We have to split this task into two steps. First we create the systemd service which determines when and how our real script should be handled. The second step includes writing of the script that contains the "real work".
First step - writing the systemd service
Description="something usefull in here"
the service file is a wrapper. the real action is done in the on the following line (should be set with +x)
two example targets below
we only want to execute a script by the service - fire and forget - one shot only
the following two lines define what should happen when the service is started or stopped
Second step - write the bashscript
case "$1" in
wpasupplicant -B -D wext -i wlan0 -c /etc/wpasupplicant.conf
dhcpcd -b wlan0
dhcpd wlan0 --exit
Now, we only have to enable this service.
sudo systemctl enable wlanwpasupplicant.service
And thats it, try a reboot and enjoy your first systemd service
Example on github.com
Writing custom service files