Review options for persisting import settings/configs/files

[m-roberts]

The recovery partition can theoretically access the main partition's config files (e.g. wifi) to ensure that the bootloader can do everything that the main OS could.

Another option might be to actually store these config files in recovery partition and symlink to them from the system. A system like mackup would work well for this. It would mean that, for example, Wi-Fi settings can be remembered between installations, speeding up the re-onboarding process.

The advantage of this is that this will work for any config files we can program for, as long as they are in the recovery partition. This provides an easy interface for anyone to get fully configured.

Note that, because they live on the recovery partition which is available to most other systems due to being FAT32, users can copy their files onto a new SD card and immediately benefit from hot-loading the config.

Users can keep backups of these files as a way of providing a Brewfile-esque re-install process. Some thought would need to be given to how to manage potentially sensitive data that might be needed as part of an installation (e.g. WPA2 Enterprise files). Potentially this could be that the user needs to enter an archive's password in order to extract scripts/config files to use as part of setup?

See https://github.com/RPi-Distro/raspberrypi-sys-mods for similar effects/changes (e.g. copying wifi config from /boot)

Incomplete list:

• wpa_supplicant.conf
• Barrier conf