obmc-flash-bmc: Specify full path for mktemp
Some eMMC systems report the following error when updating u-boot:
Dec 02 18:14:40 openbmc systemd[1]: Starting Write image 3ca0afa1 to BMC storage...
Dec 02 18:14:41 openbmc obmc-flash-bmc[507]: mktemp: (null): Read-only file system
Dec 02 18:14:41 openbmc obmc-flash-bmc[508]: dd: can't open '': No such file or directory
Dec 02 18:14:41 openbmc obmc-flash-bmc[510]: /usr/bin/obmc-flash-bmc: line 462: : No such file or directory
It appears that the TMPDIR variable is not set in that environment,
even though that a manual mktemp command works, so may be tied to
the script running in a bash shell.
In any case, specify the full path for the mktemp directory so that
it creates the file in /tmp/ and doesn't attempt to create it in
the running rootfs directory which is read-only.
Tested: Error was not seeing in the failing system and u-boot was updated.
Change-Id: I407a1e4f0d185d8fbb1e4f939bf8283246299a2d
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
diff --git a/obmc-flash-bmc b/obmc-flash-bmc
index af477b9..4b29bb3 100644
--- a/obmc-flash-bmc
+++ b/obmc-flash-bmc
@@ -456,7 +456,7 @@
# Since the image file can be smaller than the device, copy the device to a
# tmp file and write the image file on top, then compare the sum of each.
# Use cat / redirection since busybox does not have the conv=notrunc option.
- tmpFile="$(mktemp ubootdev.XXXXXX)"
+ tmpFile="$(mktemp /tmp/ubootdev.XXXXXX)"
dd if="${device}" of="${tmpFile}"
devSum="$(sha256sum ${tmpFile})"
cat < "${image}" 1<> "${tmpFile}"