-
Notifications
You must be signed in to change notification settings - Fork 236
Description
When there is a backup available (and no internet connection is available), rpi-update should have an option to easily restore this backup. For example the option --restore-backup could trigger this.
When a backup is being made, the local tree of files for /boot/ and for /lib/modules/ (before the backup is being made) should be stored somewhere. Probably in /boot.bak/.files and /lib/modules.bak/.files . Before a backup is being restored, the local paths stored in these files should exist under /boot.bak/ and under /lib/modules.bak/.
This would ensure that restoring a backup will place back at least the files that were there. Restoring additional files should not be a problem, but restoring when files are missing should not be possible and an error should be reported on which files are missing.
After restoring a backup, the new backup should be the version from which the backup was triggered. When a backup has been restored, the .files files from that backup should be deleted.
Implementing this feature would allow not so technical savvy users to perform a restore of a backup easily and safely, especially when no internet connection is available. One of the reasons no internet connection is available, is upgrading to a firmware version that breaks internet functionality.
Additionally, rpi-update --help should explain all features:
- no arguments
- firmware revision argument in terms of a git hash
--restore-backupargument--helpargument--versionargument