busybox: init: changed upgrade to update in notes/messages

This commit is contained in:
sky42 2019-09-18 20:46:55 +02:00
parent 4ba4ba6df2
commit 01931c4940

View File

@ -267,9 +267,9 @@ get_project_arch() {
fi
}
# If the project/arch of current matches the upgrade, then it is considered compatible.
# Otherwise, mount the upgrade SYSTEM partition and, if canupdate.sh is available,
# call the script to determine if the current upgrade file can be applied on to the
# If the project/arch of current matches the update, then it is considered compatible.
# Otherwise, mount the update SYSTEM partition and, if canupdate.sh is available,
# call the script to determine if the current update file can be applied on to the
# current system - 0 means it is compatible, non-zero that it is not compatible.
is_compatible() {
local result=1
@ -642,7 +642,7 @@ check_out_of_space() {
if [ "$(df /storage | awk '/[0-9]%/{print $4}')" -eq "0" ]; then
echo ""
echo "The $1 is corrupt, or there is not enough"
echo "free space on /storage to complete the upgrade!"
echo "free space on /storage to complete the update!"
echo ""
echo "Please free up space on your /storage partition"
echo "by deleting unecessary files, then try again."
@ -710,7 +710,7 @@ check_update() {
mkdir -p $UPDATE_DIR/.tmp &>/dev/null
sync
echo "UPGRADE IN PROGRESS"
echo "UPDATE IN PROGRESS"
echo ""
echo "Please do not reboot or turn off your @DISTRONAME@ device!"
echo ""
@ -863,7 +863,7 @@ check_update() {
mount_part "$UPDATE_DIR/$UPDATE_SYSTEM" "/update" "ro,loop"
# Verify that the new upgrade is compatible with the current system - this should avoid creating
# Verify that the new update is compatible with the current system - this should avoid creating
# non-booting systems after (for example) an RPi tar is incorrectly applied to an RPi2 system.
if [ ! -f "$UPDATE_ROOT/.nocompat" ]; then
if ! check_is_compatible "$UPDATE_FILENAME"; then