All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: why rootfs directory in temp is empty
Date: Wed, 23 Dec 2009 09:57:34 +0100	[thread overview]
Message-ID: <hgsm1u$2dd$1@ger.gmane.org> (raw)
In-Reply-To: <ac9c93b10912221425g4fee3ca0kdc0257be7eb677bc@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 22-12-09 23:25, Frans Meulenbroeks wrote:
> 2009/12/22 Denys Dmytriyenko <denis@denix.org>:
>> On Tue, Dec 22, 2009 at 09:05:31AM -0600, Mike Westerhof wrote:
>>> Guo Hongruan wrote:
>>>> Hi guys,
>>>>   Today, I build an base-image using OE. And I want to check the content
>>>> of rootfs, but I found the directory rootfs in building directory is
>>>> empty. I remember there was the ontent of the target root filesystem.
>>>> Why have to remove them? Does it means the rootfs directory is unuseful?
>>>>
>>>> Thanks a lot!
>>>>
>>>
>>> Add IMAGE_KEEPROOTFS = "1" to your local.conf file.
>>> I'm not sure why the change was made to clean it out every build, though.
>>
>> To prevent people from using it as an NFS share and having problems.
> 
> Ehm, can you please clarify why this would cause a problem?

The nfs server doesn't run inside the do_rootfs fakeroot sessions and
hence all the permission will be screwed up. If you can teach OE to
respawn the nfs server inside the fakeroot session, you might get away
with it :)

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLMdt+MkyGM64RGpERAjY1AJwPkbebEMCnt2oSjDTXxJLDMJibgQCeKiIR
y343rN9hGQCkMzn8Kx6csBQ=
=zSNI
-----END PGP SIGNATURE-----




      parent reply	other threads:[~2009-12-23  8:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22  8:54 why rootfs directory in temp is empty Guo Hongruan
2009-12-22 15:05 ` Mike Westerhof
2009-12-22 19:51   ` Denys Dmytriyenko
2009-12-22 22:25     ` Frans Meulenbroeks
2009-12-22 22:40       ` John Faith
2009-12-22 22:46       ` Philip Balister
2009-12-23  1:07         ` Khem Raj
2009-12-23  1:16           ` Guo Hongruan
2009-12-23  8:57       ` Koen Kooi [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='hgsm1u$2dd$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@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.