As Dirk and Ghanima stated in their answers, the service may be overwritten by future updates/upgrades of the system. But systemd has a mechanism to avoid this. You can use a drop in file. An update/upgrade will only modify the main service. The drop in file is not effected by it and will also modify the updated main service. You can simply create a drop in ...
As Dirk's answer pointed out the raspberrypi-net-mods.service is responsible for relocating wpa_supplicant.conf. It is located in /etc/systemd/multi-user-target.wants/.
This is the actual code (see here):
ExecStart=/bin/mv /boot/wpa_supplicant.conf /etc/wpa_supplicant/wpa_supplicant.conf
It's a service. In this case it's raspberrypi-net-mods.service.
systemctl status raspberrypi-net-mods.service will give status, including full path of the service file.
systemctl cat raspberrypi-net-mods.service will show path and contents.
Be aware that an update/upgrade could modify the service file in the future.
Rpi can no longer boot after installing wrong LCD driver. How to fix?
A quick and dirty fix is:
Use a new SD card with a freshly downloaded Raspbian image, without any new LCD driver installed.
Then install your correct LCD driver.
You can fiddle with the Raspbian config files to remove wrongly ...
See Headless Raspbian WiFi Setup in How to set up networking/WiFi
Specifically Raspbian checks the contents of the boot directory for a file called wpa_supplicant.conf, and will copy the file into /etc/wpa_supplicant, replacing any existing wpa_supplicant.conf file that may be there. The file in the boot directory is then removed. This can be used to ...
It turns out the problem I had was the bootup option I choose. The correct option would have been to choose "Graphical Installer" (there are two install options, probably either, but I went with the graphical one).
The "Run with Persistance" option was just running the OS from the CD.
I have seen messages like unable to make backup link of "some file.svg" when trying to install software on a fat formated partition. fat does not support links so this message will come up every time something tries to set a link. May it be possible that you try to use a fat partition in any way? I have never used Raspberry Pi Desktop but as written there it ...
For booting to the command line, look here https://www.kiwi-electronics.nl/blog?journal_blog_post_id=5&lang=en
There is a setting under system to change boot to CLI (command line interface)
Once you are at the command line,
should get you to the GUI, see here https://www.raspberrypi.org/forums/viewtopic.php?t=9488
You can also set it to ...
Ok I got it to work, not sure if it's the most elegant of ways but it works...
Created an extra file with the following and called the file from rc.local
cp /media/pi/drive/file.sh /home/pi
sudo chmod +x /home/pi/file.sh
not sure how long to wait but reckoned 30s is ok, it copies the file over, changes to executable ...
Please take note that using /etc/rc.local has limitations due to Compatibility with SysV. We have seen many problems here on this site using it. Following the recommendation of the developers from systemd you should avoid using it.
It may be possible that the USB drive isn't mounted before executing the commands. I suggest to use a systemd unit file. Just ...
/etc/rc.local runs as root so you NEVER need sudo in there.
It also runs with a limited environment and /etc as the current working directory. So you can't use relative file names. Use the full path for everything with no strange punctuation.
mount /dev/sda1 /media/pi
cp /media/pi/drive/file /home/pi/script
chmod 755 /home/pi/script
su pi /...