summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Frysinger <vapier@chromium.org>2017-05-07 02:18:50 -0400
committerchrome-bot <chrome-bot@chromium.org>2017-05-13 15:25:43 -0700
commit36e030df800f8df7913a3629ea0ab8636dc789e5 (patch)
tree107a9db250c9619f73fd7e8151029fece90b9680
parent9e7caccd3556f7b29246df69af54a8bfbae2e489 (diff)
downloadvboot-stabilize-9554.B.tar.gz
image_signing: strip_boot_from_image.sh: convert to info/error helpersstabilize-9554.B
This makes the output easier to follow when multiple scripts are being run. BRANCH=None BUG=chromium:714598 TEST=signing images still works Change-Id: I48edde260e1d1db88f65624c7ff46ad2ac1cc2f4 Reviewed-on: https://chromium-review.googlesource.com/498100 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: David Riley <davidriley@chromium.org>
-rwxr-xr-xscripts/image_signing/strip_boot_from_image.sh4
1 files changed, 2 insertions, 2 deletions
diff --git a/scripts/image_signing/strip_boot_from_image.sh b/scripts/image_signing/strip_boot_from_image.sh
index dcbdf05d..5e650af6 100755
--- a/scripts/image_signing/strip_boot_from_image.sh
+++ b/scripts/image_signing/strip_boot_from_image.sh
@@ -30,7 +30,7 @@ fi
zero_free_space() {
local rootfs="$1"
- echo "Zeroing freespace in ${rootfs}"
+ info "Zeroing freespace in ${rootfs}"
# dd is a silly thing and will produce a "No space left on device" message
# that cannot be turned off and is confusing to unsuspecting victims.
( sudo dd if=/dev/zero of="${rootfs}/filler" bs=4096 conv=fdatasync \
@@ -47,7 +47,7 @@ strip_boot() {
mount_image_partition ${image} 3 ${rootfs_dir}
sudo rm -rf "${rootfs_dir}/boot" &&
- echo "/boot directory was removed."
+ info "/boot directory was removed."
# To prevent the files we just removed from the FS from remaining as non-
# zero trash blocks that bloat payload sizes, need to zero them. This was