__ __ __ __ _____ _ _ _____ _ _ _
| \/ | \ \ / / | __ \ (_) | | / ____| | | | |
| \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | |
| |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | |
| | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | |
|_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1
if you need WebShell for Seo everyday contact me on Telegram
Telegram Address : @jackleet
For_More_Tools:
# build/default/995_md5sums_rootfs.sh
#
# Create md5sums for all regular files in ROOTFS_DIR
# and store the result in ROOTFS_DIR as md5sums.txt
# so that in the recovery system one can test via
# pushd / ; md5sum --quiet --check md5sums.txt ; popd
# if the regular files in the recovery system are intact.
# That test must happen first of all during recovery system startup
# before files may get changed by recovery system startup scripts
# see skel/default/etc/scripts/system-setup for details.
# The reason behind is that there could be errors during loading/unpacking
# of the initrd/initramfs which are reported (if one knows how to look for them)
# but at least some errors do not abort the boot process so that
# it could happen that files in the recovery system are corrupt
# but the user may not notice the actual error and get any kind
# of inexplicable errors later when using the recovery system,
# see https://github.com/rear/rear/issues/1859
# and https://github.com/rear/rear/issues/1724
# Skip that if the user had specified to exclude md5sums for all files:
test "all" = "$EXCLUDE_MD5SUM_VERIFICATION" && return || Log "Creating md5sums for regular files in $ROOTFS_DIR"
local md5sums_file="md5sums.txt"
# Careful in case of 'return' after 'pushd' (must call the matching 'popd' before 'return'):
pushd $ROOTFS_DIR 1>&2
cat /dev/null >$md5sums_file
# Do not provide a md5sums.txt in the recovery system if it was not successfully created here.
# Exclude the md5sums.txt file itself and all .gitignore files here in any case.
# Exclude all files with a trailing '~' in their name because those are also excluded
# when the recovery system initrd is made by pack/GNU/Linux/900_create_initramfs.sh
# (there via find . ! -name "*~"), see https://github.com/rear/rear/issues/2127
# Exclude all regular files in /dev/ (device nodes get already excluded by 'find -type f')
# because sometimes it could happen that there are regular files in /dev/ in ROOTFS_DIR
# which won't get copied into the recovery system so that those regular files in /dev/
# are missing when etc/scripts/system-setup tries to verify their md5sums, for example
# see https://github.com/rear/rear/issues/1883#issuecomment-409875733
# and https://github.com/rear/rear/issues/1891#issue-347952166
# that both read (excerpts):
# md5sum: ./dev/.SRC-Semaphore: No such file or directory
# ./dev/.SRC-Semaphore: FAILED open or read
# where /dev/.SRC-Semaphore seems to be related to IBM Reliable Scalable Cluster Technology (RSCT)
# see http://www-01.ibm.com/support/docview.wss?uid=isg1IV35736
# Excluding particular files from being verified during recovery system startup
# happens via EXCLUDE_MD5SUM_VERIFICATION in skel/default/etc/scripts/system-setup
# Be safe against blanks or special characters in file names
# by using appropriate options for all commands in the pipe,
# cf. https://github.com/rear/rear/issues/1372
# In particular newer kernel firmware files have blanks in file names like
# firmware/brcm/brcmfmac43430a0-sdio.ONDA-V80 PLUS.txt
# firmware/brcm/brcmfmac43455-sdio.MINIX-NEO Z83-4.txt
# cf. https://github.com/rear/rear/issues/2407
find . -xdev -type f -print0 | grep -E -z -v '/md5sums\.txt|/\.gitignore|~$|/dev/' | xargs -0 md5sum -b >>$md5sums_file || cat /dev/null >$md5sums_file
popd 1>&2