aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/gdb
diff options
context:
space:
mode:
authorPeter Seebach <peter.seebach@windriver.com>2016-05-18 16:30:47 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-05-20 10:20:22 +0100
commit0f1054e7db74bb4a196e00773915d7997b55bdf2 (patch)
tree7108d96cd2afa1661d5217b590c9e1c6fa186b01 /meta/recipes-devtools/gdb
parent7e96806d1282865761fcc047abcb72970279d82d (diff)
downloadopenembedded-core-0f1054e7db74bb4a196e00773915d7997b55bdf2.tar.gz
acl.inc, run-ptest: improve ptest functionality on limited rootfs
ACL's ptest has a handful of failure modes which can be triggered by a restrictive or small system. First, the ptest requires that daemon be in the bin group, which run-ptest attempts to do using gpasswd, but gpasswd is part of shadow, and oe-core removes shadow when it doesn't think shadow will be needed. Even if, say, a package has RDEPENDS on it. Whoops. So we manually sed the group file. This will probably work. Second, the filesystem used for the test has to support ACLs, so we create a dummy ext3 filesystem and use that. Third, the root/permissions test relies on the assumption that "mkdir d" produces a directory which non-root users can access, but in a secure product which defaults to umask 077, this doesn't work. (That fix has been separately reported to upstream acl through their bug report form.) (This may prevent the test from running without mkfs.ext3, but it allows the test to run on targets where root doesn't have ACL support. Tradeoffs, tradeoffs everywhere.) Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/recipes-devtools/gdb')
0 files changed, 0 insertions, 0 deletions