Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Seebach <peter.seebach@windriver.com>
To: Alex Franco <alejandro.franco@linux.intel.com>
Cc: clarson@kergoth.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Fix recursive mode -st on BUILDDIR setup
Date: Wed, 2 Sep 2015 16:47:25 -0500	[thread overview]
Message-ID: <20150902164725.5a011ab8@seebs-worktop> (raw)
In-Reply-To: <1441211805-17543-1-git-send-email-alejandro.franco@linux.intel.com>

On Wed, 2 Sep 2015 11:36:45 -0500
Alex Franco <alejandro.franco@linux.intel.com> wrote:

> -chmod -R -st "$BUILDDIR" 
> +chmod -st "$BUILDDIR"

I was about to say! I just did an update to a version with this, and as it
happens, my build dir also contains about four full copies of tmp-glibc and
sstate-cache corresponding to different versions of pseudo I was comparing
between...

I'd say maybe both $BUILDDIR and $BUILDDIR/conf. Although it might not be a
horrible idea to think about cleaning out sticky bits, because it occurs to
me: pseudo is not stripping the set* bits when writing to the filesystem.
Which means that a build directory can end up containing files owned by the
build user, and setuid, which is maybe a Bad Thing.

... It may be that pseudo should strip those bits from the filesystem.

-s
-- 
Listen, get this.  Nobody with a good compiler needs to be justified.


  parent reply	other threads:[~2015-09-02 21:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 16:36 [PATCH] Fix recursive mode -st on BUILDDIR setup Alex Franco
2015-09-02 17:51 ` Richard Purdie
2015-09-02 18:25   ` Martin Jansa
2015-09-02 21:27     ` Alex Franco
2015-09-03  0:57       ` Martin Jansa
2015-09-03 20:01         ` Alex Franco
2015-09-03 21:43           ` Martin Jansa
2015-09-03 21:54             ` Alex Franco
2015-09-02 21:47 ` Peter Seebach [this message]
2015-09-02 22:28   ` Alex Franco

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150902164725.5a011ab8@seebs-worktop \
    --to=peter.seebach@windriver.com \
    --cc=alejandro.franco@linux.intel.com \
    --cc=clarson@kergoth.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox