����JFIF���������
__ __ __ __ _____ _ _ _____ _ _ _ | \/ | \ \ / / | __ \ (_) | | / ____| | | | | | \ / |_ __\ V / | |__) | __ ___ ____ _| |_ ___ | (___ | |__ ___| | | | |\/| | '__|> < | ___/ '__| \ \ / / _` | __/ _ \ \___ \| '_ \ / _ \ | | | | | | |_ / . \ | | | | | |\ V / (_| | || __/ ____) | | | | __/ | | |_| |_|_(_)_/ \_\ |_| |_| |_| \_/ \__,_|\__\___| |_____/|_| |_|\___V 2.1 if you need WebShell for Seo everyday contact me on Telegram Telegram Address : @jackleetFor_More_Tools:
# mkboot-workflow.sh
#
# mkboot workflow for Relax-and-Recover
#
# This file is part of Relax-and-Recover, licensed under the GNU General
# Public License. Refer to the included COPYING for full text of license.
# According to https://github.com/rear/rear/pull/2965
# the mkboot workflow is not for normal usage but for testing and development
# see https://github.com/rear/rear/pull/2965#issue-1651096154
# "mkboot workflow for bare boot image without rescue info
# (for testing stuff not related to backup/restore)"
# and https://github.com/rear/rear/pull/2965#issuecomment-1511613739
# "mkboot allows me to create a generic boot media
# without caring about a backup method or rescue stuff,
# super useful for working on a feature like Python that doesn't depend on anything"
# so we list the mkboot workflow only when "rear help" is called in verbose mode:
test "$VERBOSE" && WORKFLOW_mkboot_DESCRIPTION="create boot media without recovery information (for testing and development)"
WORKFLOWS+=( mkboot )
WORKFLOW_mkboot () {
SourceStage "prep"
SourceStage "rescue"
SourceStage "build"
SourceStage "pack"
SourceStage "output"
}