Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: RFC: Move PSEUDO_LOCALSTATEDIR for filesystems outside the filesystem
Date: Fri, 17 Aug 2012 15:00:46 -0500	[thread overview]
Message-ID: <502EA2EE.8040506@windriver.com> (raw)
In-Reply-To: <20120814204116.6ba1ff3d@e6410-2>

On 8/14/12 8:41 PM, Peter Seebach wrote:
> 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.

The NFS export scripts and such expect the pseudo DB to be available to them. 
The filesystem can be anywhere the user wants, so somehow we have to know where 
it was extracted, and the only answer we came up with at the time was to put the 
pseudo database into the filesystem directory.  It doesn't cause any harm to the 
target that is being booted, and it ensures that the NFS server setup scripts 
know where the both the root and pseudo DBs are located.

--Mark

> -s
>




      reply	other threads:[~2012-08-17 20:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15  1:41 RFC: Move PSEUDO_LOCALSTATEDIR for filesystems outside the filesystem Peter Seebach
2012-08-17 20:00 ` Mark Hatle [this message]

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=502EA2EE.8040506@windriver.com \
    --to=mark.hatle@windriver.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