runqemu-export-rootfs and friends: don't put pseudo db in target fs
authorPeter Seebach <peter.seebach@windriver.com>
Mon, 27 Aug 2012 18:32:30 +0000 (13:32 -0500)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 29 Aug 2012 23:02:10 +0000 (16:02 -0700)
commitc76522e3bdb7daf83e32412462c5f9b477ccf8b5
tree8e7370dbd3c594f78664d777200bce664dec5e34
parent0b6d7b30ade10a5d9060c9ba92a507ed150518dd
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>
meta/recipes-devtools/installer/adt-installer/scripts/extract_rootfs
scripts/runqemu-export-rootfs
scripts/runqemu-extract-sdk