diskimage-builder/elements/ramdisk/cleanup.d/99-extract-ramdisk-files

#!/bin/bash

set -e
set -x

IMAGE_NAME=${IMAGE_NAME:-'image'}

cp $TMP_MOUNT_PATH/tmp/ramdisk $IMAGE_NAME.initramfs
cp $TMP_MOUNT_PATH/tmp/kernel $IMAGE_NAME.kernel
/bin/bash all the things. Since we are using bash syntax in some of the element fragments, we should make sure we use bash for all of them, so that things don't break on systems where /bin/sh != /bin/bash. Change-Id: If2f043c57aa4e1492b7f9839213ef6123f683612 2013-11-07 04:25:34 +00:00			`#!/bin/bash`
Build ramdisks in an image chroot. Ramdisks are now built inside a chroot which is built by the normal image build process. Doing so improves our independence of the precise state of the build host. This fixes bug 1194055. Change-Id: Ibc254fbb9e7b404b5f38c1b35bcde8a4136e8e28 2013-07-01 16:20:15 +00:00
			`set -e`
			`set -x`

Default name for ramdisks to image. If you build a ramdisk with ramdisk-image-create and forget to specify -o, you end up with a .kernel and .initramfs file as the image outputs. This commit defaults the $IMAGE_NAME value to image so you'd end up with image.kernel and image.initramfs Change-Id: I10f3ac9ad178c32119523e4da930070e3ade4f73 2013-12-04 18:45:29 +00:00			`IMAGE_NAME=${IMAGE_NAME:-'image'}`

Build ramdisks in an image chroot. Ramdisks are now built inside a chroot which is built by the normal image build process. Doing so improves our independence of the precise state of the build host. This fixes bug 1194055. Change-Id: Ibc254fbb9e7b404b5f38c1b35bcde8a4136e8e28 2013-07-01 16:20:15 +00:00			`cp $TMP_MOUNT_PATH/tmp/ramdisk $IMAGE_NAME.initramfs`
			`cp $TMP_MOUNT_PATH/tmp/kernel $IMAGE_NAME.kernel`