Gecko [ www.prositehelp.com ]

Name	Size	Permission	Date
050_prepare_checks.sh	1.24 KB	-rw-r--r--	2026-04-01 09:39
060_compare_files.sh	3.48 KB	-rw-r--r--	2026-04-01 09:39
110_bind_mount_proc_sys_dev_run.sh	6.2 KB	-rw-r--r--	2026-04-01 09:39
520_confirm_finalize.sh	3.25 KB	-rw-r--r--	2026-04-01 09:39
880_check_for_mount_by_id.sh	8.22 KB	-rw-r--r--	2026-04-01 09:39
890_finish_checks.sh	1.49 KB	-rw-r--r--	2026-04-01 09:39
900_remount_sync.sh	1.24 KB	-rw-r--r--	2026-04-01 09:39

Rename

# Copy md5sum files to COVE_INSTALL_DIR if they exist
if is_true "$COVE_VERIFY_BINARIES" ; then
    local rear_dir="$VAR_DIR/layout/config"
    local cove_dir="$COVE_INSTALL_DIR/rear/var/lib/rear/layout/config"
    for md5sum_file in files.md5sum cove-files.md5sum ; do
        if test -f "$rear_dir/$md5sum_file" ; then
            mkdir -p "$cove_dir"
            cp "$rear_dir/$md5sum_file" "$cove_dir/$md5sum_file"
        fi
    done
fi

# Skip when there are no checksums:
test -s $VAR_DIR/layout/config/files.md5sum || return 0

LogPrint "Checking if certain restored files are consistent with the recreated system"
DebugPrint "See $VAR_DIR/layout/config/files.md5sum what files are checked"
local md5sum_stdout
# The exit status of the assignment is the exit status of the command substitution
# which is usually the exit status of 'md5sum' that is forwarded by 'chroot'
# except 'chroot' fails (e.g. with 127 if 'md5sum' cannot be found).
# Because the redirections are done before chroot is run
# (in chroot plain 'md5sum -c --quiet' is run with redirected stdin)
# the 'md5sum' stdin comes from VAR_DIR/layout/config/files.md5sum in the recovery system.
# The 'md5sum' stdout messages like
#   /path/to/this: FAILED
#   /path/to/that: FAILED open or read
# provide sufficient information so we do not output 'md5sum' stderr messages like
#   md5sum: /path/to/that: No such file or directory
#   md5sum: WARNING: 1 line is improperly formatted
#   md5sum: WARNING: 1 listed file could not be read
#   md5sum: WARNING: 1 computed checksum did NOT match
# on the user's terminal but have them only in the log file as usual via stderr:
if ! md5sum_stdout="$( chroot $TARGET_FS_ROOT md5sum -c --quiet < $VAR_DIR/layout/config/files.md5sum )" ; then
    LogPrintError "Restored files in $TARGET_FS_ROOT do not fully match the recreated system"
    LogPrintError "(files in the backup are not same as when the ReaR rescue/recovery system was made)"
    # This 'sed' call must not be done in the above command substitution as a pipe
    # because then the command substitution exit status would be the one of 'sed'.
    # Prefix the reported files in the 'md5sum' stdout lines with '/mnt/local'
    # because this is the right path for the user in the currently running ReaR recovery system
    # for the restored files that do not match the md5sums that were saved at "rear mkrescue" time,
    # cf. https://github.com/rear/rear/pull/2954#issuecomment-1467645338 and subsequent comments.
    # The 'md5sum' stdout lines that report files start with '/' because
    # var/lib/rear/layout/config/files.md5sum contains file names with full path.
    # Prefix all 'md5sum' stdout lines with two spaces indentation
    # for better readability what the 'md5sum' stdout lines are:
    LogPrintError "$( sed -e "s|^/|$TARGET_FS_ROOT/|" -e 's/^/  /' <<< "$md5sum_stdout" )"
    LogPrintError "Manually check if those changed files cause issues in your recreated system"
    return 1
fi

# For COVE backup with binary verification enabled, treat checksum mismatch as fatal error
if is_true "$COVE_VERIFY_BINARIES" ; then
    LogPrint "Checking if COVE files are consistent"
    if ! md5sum_stdout="$( chroot $TARGET_FS_ROOT md5sum -c --quiet < $VAR_DIR/layout/config/cove-files.md5sum )" ; then
        LogPrintError "Restored files in $TARGET_FS_ROOT do not fully match the recreated system"
        LogPrintError "$( sed -e "s|^/|$TARGET_FS_ROOT/|" -e 's/^/  /' <<< "$md5sum_stdout" )"

Error "COVE binary verification failed: checksums do not match"
    fi
fi