SWAMPy

✎ CARVE FLESH

EDITING: 480_initialize_write_protect_settings.sh

# USB output typically resides on a writable disk device
# which should be protected against overwriting by "rear recover"
# cf. https://github.com/rear/rear/issues/1271
# This code registers the USB output device as write protected.

# The values of the 'lsblk' output columns in WRITE_PROTECTED_ID_TYPES
# of the ReaR recovery system disk (parent of USB_DEVICE) are automatically added
# to the WRITE_PROTECTED_IDS array during "rear mkrescue/mkbackup".
# The default WRITE_PROTECTED_ID_TYPES are UUID PTUUID PARTUUID WWN.
local ids
ids="$( write_protection_ids "$USB_DEVICE" )"
# ids is a string of IDs separated by newline characters so quoting for 'test' is required
# but no quoting to add them to the array to get each ID as a separated array element:
if test "$ids" ; then
    WRITE_PROTECTED_IDS+=( $ids )
    DebugPrint "USB disk IDs of '$USB_DEVICE' added to WRITE_PROTECTED_IDS"
else
    LogPrintError "Cannot write protect USB disk of '$USB_DEVICE' via ID (no ID found)"
fi

# The file system label of the ReaR data partition (i.e. USB_DEVICE) on the ReaR recovery system disk
# is automatically added to WRITE_PROTECTED_FS_LABEL_PATTERNS during "rear mkrescue/mkbackup".
# Empty lines in the lsblk output get automatically ignored (i.e. no empty array elements get added)
# and we do not alert the user via LogPrintError because file system labels are optional:
if WRITE_PROTECTED_FS_LABEL_PATTERNS+=( $( lsblk -ino LABEL "$USB_DEVICE" ) ) ; then
    DebugPrint "File system label of '$USB_DEVICE' added to WRITE_PROTECTED_FS_LABEL_PATTERNS"
else
    DebugPrint "Cannot write protect USB disk of '$USB_DEVICE' via file system label (none found)"
fi

CANCEL

Name	Type	Size	Modified	Actions
↩ ..	DIR	—	—
📄 040_set_NETFS_requirements.sh	SH	398 B	2023-02-16 11:22	EDIT
📄 060_set_usb_device.sh	SH	1.4 KB	2023-02-16 11:22	EDIT
📄 380_copy_usb_fs_module.sh	SH	5.1 KB	2023-02-16 11:22	EDIT
📄 480_initialize_write_protect_settings.sh	SH	1.6 KB	2023-02-16 11:22	EDIT