From 71ff3fc6328b9630f185887ccf18a7b06a44dce7 Mon Sep 17 00:00:00 2001
From: Tien-Ren Chen <trchen@chromium.org>
Date: Thu, 8 Jul 2010 15:27:59 +0800
Subject: [PATCH] fix disappearing vmlinuz_hd.vblock problem

Review URL: http://codereview.chromium.org/2905001
---
 build_image | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/build_image b/build_image
index 23dcf5b477..9b94d99c56 100755
--- a/build_image
+++ b/build_image
@@ -318,16 +318,7 @@ make_image_bootable() {
   # create_base_image(). However, it could break the build if it is a clean
   # build because vmlinuz_hd.vblock hasn't been created by build_kernel_image.sh
   if [[ "${ARCH}" = "x86" ]]; then
-    STATEFUL_LOOP_DEV=$(sudo losetup -f)
-    if [ -z "${STATEFUL_LOOP_DEV}" ] ; then
-      echo "No free loop device. Free up a loop device or reboot. exiting. "
-      exit 1
-    fi
-    sudo losetup "${STATEFUL_LOOP_DEV}" "${STATEFUL_FS_IMG}"
-    sudo mount "${STATEFUL_LOOP_DEV}" "${STATEFUL_FS_DIR}"
     sudo cp "${OUTPUT_DIR}/vmlinuz_hd.vblock" "${STATEFUL_FS_DIR}"
-    sudo umount -d "${STATEFUL_FS_DIR}"
-    STATEFUL_LOOP_DEV=
   fi
 
   # START_KERN_A is set by the first call to install the gpt.