Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] wic: add pseudo to the populate-extfs step
Date: Fri, 18 Oct 2013 10:10:57 -0500	[thread overview]
Message-ID: <52614F81.9010303@windriver.com> (raw)
In-Reply-To: <1382108670.29912.553.camel@ted>

On 10/18/13 10:04 AM, Richard Purdie wrote:
> On Wed, 2013-10-16 at 15:25 -0500, Tom Zanussi wrote:
>> Without this, files in the generated filesystem pick up the wrong
>> ownership.
>>
>> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
>> ---
>>   scripts/lib/mic/kickstart/custom_commands/partition.py | 9 ++++++++-
>>   1 file changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/scripts/lib/mic/kickstart/custom_commands/partition.py b/scripts/lib/mic/kickstart/custom_commands/partition.py
>> index 302cace..0eb0671 100644
>> --- a/scripts/lib/mic/kickstart/custom_commands/partition.py
>> +++ b/scripts/lib/mic/kickstart/custom_commands/partition.py
>> @@ -216,7 +216,14 @@ class Wic_PartData(Mic_PartData):
>>           """
>>           Prepare content for an ext2/3/4 rootfs partition.
>>           """
>> -        populate_script = "%s/usr/bin/populate-extfs.sh" % native_sysroot
>> +        populate_script = "export PSEUDO_PREFIX=%s/usr;" % native_sysroot
>> +        populate_script += "export PSEUDO_LOCALSTATEDIR=%s/../pseudo;" % rootfs_dir
>> +        populate_script += "export PSEUDO_PASSWD=%s;" % rootfs_dir

Location of the passwd file, if we are in a chroot, it will use the chroot'd 
version, otherwise you need to tell pseudo where it is.

>> +        populate_script += "export PSEUDO_NOSYMLINKEXP=1;"

This controls how the symlinks are populated from the point of view of 
non-pseudo environment.  If you intend to manipulate the results (and make them 
useful) -outside- of the pseudo environment, you need this.  If you do all of 
your operations from within pseudo, the defaults are correct.  Otherwise you can 
get links such as "/bin/sh -> /bin/bash" and it points to the host's bash, not 
the chroot's /bin/bash.

>> +        populate_script += "export PSEUDO_DISABLED=0;"

This shouldn't have to be set, unless the disabled has been previously set in 
the environment.

>> +        populate_script += "%s/usr/bin/pseudo %s/usr/bin/populate-extfs.sh" % \
>> +            (native_sysroot, native_sysroot)
>> +
>>           image_extra_space = 10240
>>
>>           image_rootfs = rootfs_dir
>
> I've merged this but I would like to figure out why pseudo can't manage
> more sane defaults rather than needing all of those variables...
>
> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



  reply	other threads:[~2013-10-18 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16 20:25 [PATCH 0/1] wic populate-ext fix Tom Zanussi
2013-10-16 20:25 ` [PATCH 1/1] wic: add pseudo to the populate-extfs step Tom Zanussi
2013-10-16 21:13   ` Darren Hart
2013-10-18 15:04   ` Richard Purdie
2013-10-18 15:10     ` Mark Hatle [this message]
2013-10-18 20:03     ` 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=52614F81.9010303@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