-
Committer:
Bernhard Rosenkraenzer
-
Date:
2011-07-23 22:22:58 UTC
-
Revision ID:
bernhard.rosenkranzer@linaro.org-20110723222234-7w2nxh06mlb2bjyk
Fix linaro-android-media-create after recent mount/umount changes
Without this, this traceback occurs:
mkfs.vfat 3.0.11 (24 Dec 2010)
mount: /dev/mmcblk0p1 already mounted or /tmp/tmp18MYEP/boot-disc busy
mount: according to mtab, /dev/mmcblk0p1 is already mounted on /tmp/tmp18MYEP/boot-disc
Traceback (most recent call last):
File "./linaro-android-media-create", line 144, in <module>
board_config.populate_boot_script(boot_partition, BOOT_DISK, args.consoles)
File "/usr/src/repos/linaro/linaro-image-tools/linaro_image_tools/media_create/android_boards.py", line 82, in populate_boot_script
as_root=True).wait()
File "/usr/src/repos/linaro/linaro-image-tools/linaro_image_tools/cmd_runner.py", line 100, in wait
raise SubcommandNonZeroReturnValue(self._my_args, returncode)
linaro_image_tools.cmd_runner.SubcommandNonZeroReturnValue: Sub process "['mount', '/dev/mmcblk0p1', '/tmp/tmp18MYEP/boot-disc']" returned a non-zero value: 32
The problem is that linaro-android-media-create assumes
populate_partition(... BOOT_DISK ...)
unmounts the boot filesystem after running (no longer true).
Furthermore, board_config.populate_boot_script used to umount
the boot filesystem, causing the umount in the atexit handler to fail.