summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/intltool
diff options
context:
space:
mode:
authorPeter Seebach <peter.seebach@windriver.com>2012-08-27 13:32:30 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-08-29 16:02:10 -0700
commit92e40ec8599d567f3907837c616b83e089c2b544 (patch)
tree4e0173fa06524583fd17ca26aa042ce6a1bc0c9b /meta/recipes-devtools/intltool
parentc0aa58f4611d0a9e3cc41c09770f536b3ed6eb66 (diff)
downloadast2050-yocto-poky-92e40ec8599d567f3907837c616b83e089c2b544.zip
ast2050-yocto-poky-92e40ec8599d567f3907837c616b83e089c2b544.tar.gz
runqemu-export-rootfs and friends: don't put pseudo db in target fs
In a few places, we have scripts which use <rootfs>/var/pseudo for the pseudo state directory controlling a given filesystem. This seems possibly risky because it means that stuff running under qemu or whatnot could wipe out the data being used to handle that rootfs. Move this to: <rootfs>/../$(basename_rootfs).pseudo_state to avoid problems. This also solves at least one case (not directly hit by yocto's tree) wherein you could end up trying to remove a rootfs while pseudo was using a database inside that rootfs, and thus the remove would fail. (From OE-Core rev: aa5d6bd006d3b4eede21d8987451876ed3385ab8) Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/intltool')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud