From: Peter Seebach <peter.seebach@windriver.com>
To: "openembedded-core@"
<lists.openembedded.org.openembedded-core@lists.openembedded.org>
Subject: RFC: Move PSEUDO_LOCALSTATEDIR for filesystems outside the filesystem
Date: Tue, 14 Aug 2012 20:41:16 -0500 [thread overview]
Message-ID: <20120814204116.6ba1ff3d@e6410-2> (raw)
Got a bug related to this that probably only affects our build
environment, but it caused me to note:
When we're using export/dist as a user-mode NFS root (under pseudo),
the PSEUDO_LOCALSTATEDIR is export/dist/var/pseudo.
This seems a bit weird to me -- I don't think pseudo's db should be
part of the filesystem it's maintaining. And I'm wondering whether
there is a historical reason for this that I need to be aware of,
before I propose moving it to something like export/pseudo.
... And if not, I propose we move it to something like export/pseudo.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next reply other threads:[~2012-08-15 1:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 1:41 Peter Seebach [this message]
2012-08-17 20:00 ` RFC: Move PSEUDO_LOCALSTATEDIR for filesystems outside the filesystem Mark Hatle
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=20120814204116.6ba1ff3d@e6410-2 \
--to=peter.seebach@windriver.com \
--cc=lists.openembedded.org.openembedded-core@lists.openembedded.org \
--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 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.