aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRafał Miłecki <rafal@milecki.pl>2019-09-05 13:08:13 +0200
committerRafał Miłecki <rafal@milecki.pl>2019-09-08 09:10:30 +0200
commit1c510fe2980cd787602786e82f44602549d607d4 (patch)
tree84b5dd699efb1b0451d292b406100602fe3f65d8
parent7db655991443a98f84e4c39e733232d41d2d6137 (diff)
downloadupstream-1c510fe2980cd787602786e82f44602549d607d4.tar.gz
upstream-1c510fe2980cd787602786e82f44602549d607d4.tar.bz2
upstream-1c510fe2980cd787602786e82f44602549d607d4.zip
base-files: validate firmware for compatibility with backup
This allows platform code to check if firmware image can be used with preserving a backup. It may be used e.g. when installing vendor firmwares that won't restore appended backup archive. Suggested-by: Luis Araneda <luaraneda@gmail.com> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
-rwxr-xr-xpackage/base-files/files/usr/libexec/validate_firmware_image7
1 files changed, 7 insertions, 0 deletions
diff --git a/package/base-files/files/usr/libexec/validate_firmware_image b/package/base-files/files/usr/libexec/validate_firmware_image
index a07796c9dc..f85fb9e4b4 100755
--- a/package/base-files/files/usr/libexec/validate_firmware_image
+++ b/package/base-files/files/usr/libexec/validate_firmware_image
@@ -8,6 +8,7 @@ include /lib/upgrade
VALID=1
FORCEABLE=1
+ALLOW_BACKUP=1
# Mark image as invalid but still possible to install
notify_firmware_invalid() {
@@ -20,6 +21,11 @@ notify_firmware_broken() {
FORCEABLE=0
}
+# Mark image as incompatible with preserving a backup
+notify_firmware_no_backup() {
+ ALLOW_BACKUP=0
+}
+
# Add result of validation test
notify_firmware_test_result() {
local old_ns
@@ -55,5 +61,6 @@ json_init
json_close_object
json_add_boolean valid "$VALID"
json_add_boolean forceable "$FORCEABLE"
+ json_add_boolean allow_backup "$ALLOW_BACKUP"
json_dump -i
json_set_namespace $old_ns