jpokornyiii
commented
2 years ago I chose to go with renaming the file in /boot to avoid the mv but we could do others like: 1) trying to find a strategic place to put "sudo systemctrl disable raspberrypi-net-mods" or 2) removing raspberrypi-net-mods from stage4/02-net-tweaks/00-packages.
I'd like to hear what people think first.
Avoid the mv from /boot on the initial load (when ro hasn't been mounted yet) via /etc/systemd/multi-user-target.wants/raspberrypi-net-mods.service. This looks for /boot/wpa_supplicant.conf and mv's it to /etc/wpa_supplicant/wpa_supplicant.conf. This overwrites all changes made for symlink.