From: Peter Seebach <peter.seebach@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>, yocto@yoctoproject.org
Subject: Re: pseudo interaction issue
Date: Mon, 26 Mar 2012 11:44:05 -0500 [thread overview]
Message-ID: <20120326114405.59b3eacc@wrlaptop> (raw)
In-Reply-To: <1332610903.28414.24.camel@ted>
On Sat, 24 Mar 2012 17:41:43 +0000
Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> One or the other of the above on their own doesn't do this. Funky.
That's very strange. I wouldn't have expected LOCALSTATEDIR to have
any effect either way; it might change how pseudo runs, but it shouldn't
affect whether it's being enabled.
If we are starting with pseudo loaded, I'm pretty sure it's unsafe to
unset PSEUDO_PREFIX ever. After a fork(), pseudo will still be in
memory, and if PSEUDO_PREFIX is unset, Bad Things Happen.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2012-03-26 16:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 17:35 pseudo interaction issue Paul Eggleton
2012-02-17 18:50 ` Mark Hatle
2012-03-14 9:02 ` Xu, Dongxiao
2012-03-22 1:49 ` Xu, Dongxiao
2012-03-22 16:18 ` Peter Seebach
2012-03-23 1:01 ` Xu, Dongxiao
2012-03-23 2:29 ` Peter Seebach
2012-03-23 3:21 ` Xu, Dongxiao
2012-03-23 7:16 ` Peter Seebach
2012-03-23 12:20 ` Paul Eggleton
2012-03-23 20:06 ` Peter Seebach
2012-03-23 22:45 ` Peter Seebach
2012-03-24 17:15 ` Richard Purdie
2012-03-24 17:41 ` Richard Purdie
2012-03-26 16:44 ` Peter Seebach [this message]
2012-03-26 16:47 ` Richard Purdie
2012-03-26 17:18 ` Peter Seebach
2012-03-26 21:45 ` Richard Purdie
2012-03-27 3:47 ` Peter Seebach
2012-03-27 14:26 ` Peter Seebach
2012-03-26 7:43 ` Peter Seebach
2012-03-26 9:23 ` Richard Purdie
2012-03-26 20:36 ` Peter Seebach
2012-03-26 20:41 ` Peter Seebach
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=20120326114405.59b3eacc@wrlaptop \
--to=peter.seebach@windriver.com \
--cc=paul.eggleton@linux.intel.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.