Correct order of parameters in call to tune2fs
Under some systems this leads to an error if the oder of parameters does not comply exactly with the way it is specified. Change-Id: Ie1ff871dfffecaf95e7ac467b18543561aaa0ceb
This commit is contained in:
parent
71c68bf18d
commit
616cca72b1
@ -414,7 +414,7 @@ eval_run_d block-device "IMAGE_BLOCK_DEVICE="
|
|||||||
sudo mkfs $MKFS_OPTS -t $FS_TYPE -L ${DIB_ROOT_LABEL} ${IMAGE_BLOCK_DEVICE}
|
sudo mkfs $MKFS_OPTS -t $FS_TYPE -L ${DIB_ROOT_LABEL} ${IMAGE_BLOCK_DEVICE}
|
||||||
# Tuning the rootfs uuid works only for ext filesystems.
|
# Tuning the rootfs uuid works only for ext filesystems.
|
||||||
if echo "$FS_TYPE" | grep -q "^ext"; then
|
if echo "$FS_TYPE" | grep -q "^ext"; then
|
||||||
sudo tune2fs ${IMAGE_BLOCK_DEVICE} -U ${DIB_IMAGE_ROOT_FS_UUID}
|
sudo tune2fs -U ${DIB_IMAGE_ROOT_FS_UUID} ${IMAGE_BLOCK_DEVICE}
|
||||||
fi
|
fi
|
||||||
mkdir $TMP_BUILD_DIR/mnt
|
mkdir $TMP_BUILD_DIR/mnt
|
||||||
sudo mount ${IMAGE_BLOCK_DEVICE} $TMP_BUILD_DIR/mnt
|
sudo mount ${IMAGE_BLOCK_DEVICE} $TMP_BUILD_DIR/mnt
|
||||||
|
Loading…
Reference in New Issue
Block a user