Gecko [ www.prositehelp.com ]

Linux ih01.iridiumhosting.com 5.14.0-611.55.1.el9_7.x86_64 #1 SMP PREEMPT_DYNAMIC Tue May 19 15:19:29 EDT 2026 x86_64
LiteSpeed
Server IP : 67.227.241.211 & Your IP : 216.73.216.44
Domains : Cant Read [ /etc/named.conf ]
User : dustinhy

Name	Size	Permission	Date
005_remove_workflow_conf.sh	479 B	-rw-r--r--	2026-04-01 09:39
020_translate_url.sh	1.71 KB	-rw-r--r--	2026-04-01 09:39
030_translate_tape.sh	932 B	-rw-r--r--	2026-04-01 09:39
035_valid_backup_methods.sh	988 B	-rw-r--r--	2026-04-01 09:39
036_valid_output_methods.sh	643 B	-rw-r--r--	2026-04-01 09:39
040_check_backup_and_output_scheme.sh	4.17 KB	-rw-r--r--	2026-04-01 09:39
050_check_keep_old_output_copy_var.sh	304 B	-rw-r--r--	2026-04-01 09:39
100_init_workflow_conf.sh	453 B	-rw-r--r--	2026-04-01 09:39
320_include_uefi_env.sh	4.51 KB	-rw-r--r--	2026-04-01 09:39
321_EFISTUB_check_uefi_env.sh	486 B	-rw-r--r--	2026-04-01 09:39
330_include_uefi_tools.sh	577 B	-rw-r--r--	2026-04-01 09:39
340_include_password_tools.sh	270 B	-rw-r--r--	2026-04-01 09:39
380_include_opal_tools.sh	540 B	-rw-r--r--	2026-04-01 09:39
390_include_python.sh	4.41 KB	-rw-r--r--	2026-04-01 09:39
400_save_directories.sh	9.66 KB	-rw-r--r--	2026-04-01 09:39
490_store_write_protect_settings.sh	469 B	-rw-r--r--	2026-04-01 09:39
989_check_for_restore_esp.sh	596 B	-rw-r--r--	2026-04-01 09:39
990_verify_empty_rootfs.sh	1.54 KB	-rw-r--r--	2026-04-01 09:39

Rename

# Verify at the end of the 'prep' stage
# that the ReaR recovery system area (i.e. ROOTFS_DIR)
# is still empty, see prep/README
#
# Only those workflows that actually make a ReaR recovery system
# by running the stages 'rescue', 'build', 'pack', and 'output'
# (in particular the workflows mkrescue, mkbackup and mkopalpba)
# should modify something in ROOTFS_DIR.
#
# In contrast when other workflows that run the 'prep' stage (e.g. mkbackuponly)
# modify something in ROOTFS_DIR then all those modifications will be lost
# because no ReaR recovery system with those modifications is made.
# So the problem is possible inconsistencies between what gets actually used
# during "rear recover" (i.e. the last actually made ReaR recovery system)
# versus what other workflows that run the 'prep' stage may need to have.
# For example mkbackuponly may need a modified ReaR recovery system
# when backup config variables need updated values in the recovery system
# e.g. an updated value for BACKUP_PROG_EXCLUDE or something similar.

# For now do not error out because currently
# some 'prep' scripts modify things in ROOTFS_DIR,
# see https://github.com/rear/rear/issues/2951

# Only check for regular files in ROOTFS_DIR
# so in particular empty directories like ROOTFS_DIR/TMP_DIR are OK
# cf. https://github.com/rear/rear/commit/9b4efb2469b8cf3585206dbb10700960b480008e#r139765325
test "$( find $ROOTFS_DIR -type f )" || return 0
DebugPrint "Modified ReaR recovery system area after 'prep' stage ($ROOTFS_DIR contains regular files)"
Debug "$( find $ROOTFS_DIR -ls )"
return 1