public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: fakechroot
Date: Fri, 13 Sep 2019 12:57:45 +0200	[thread overview]
Message-ID: <ea373cc9-ad87-b406-cb16-f63db758f3ee@siemens.com> (raw)
In-Reply-To: <20190913093317.GL6062@yssyq.m.ilbers.de>



On 9/13/19 11:33 AM, Baurzhan Ismagulov wrote:
> On Fri, Sep 13, 2019 at 11:08:21AM +0200, Quirin Gylstorff wrote:
>> This was only an initial test but with fakechroot and fakeroot it should be
>> possible to have a non-priviledged debootstrap and chroot process.
>>
>> - Initial Creating with debootstrap did work. e.g.:
>>    fakechroot fakeroot debootstrap buster amd64
>> - what also work was using chroot to enter the create rootfs.
>>    fakechroot chroot amd64
> 
> Thanks for sharing. That could be a welcome change.
> 
> 1. How does fakechroot fakeroot perform privileged operations like chown,
>     mknod, accessing other's files, mounting, etc.?
> 
>     We need that information to be consistent across multiple commands in
>     multiple recipes (bootstrap, customize, install stuff, deploy, etc.).
>     Wrapping one command is probably possible with any tool -- but currently I
>     don't see how they could do what we need.
> 
>     Regarding keeping the information across multiple commands, Yocto's pseudo
>     should allegedly be able to do that (not sure whether it keeps the state in
>     a daemon or a file). Evaluating that was our next step (very low prio ATM)
>     -- maybe that could be interesting for you as well.
> 

fakechroot, fakeroot and pseudo are all using a similar mechanism by 
modifying the LD_PRELOAD_PATH with there own Libraries and abstracting 
the necessary systemcalls. pseudo uses a sqlite Database to get a 
persistent view on the topic.

> 2. fakechroot fakeroot is reported to work with foreign-arch chroots. Have you
>     tried that?

I will test it.
> 
> With kind regards,
> Baurzhan.
> 

  parent reply	other threads:[~2019-09-13 10:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13  8:00 fakechroot Quirin Gylstorff
2019-09-13  8:14 ` fakechroot Baurzhan Ismagulov
     [not found]   ` <8db6f5f1-8a36-768c-1b5d-0a0a3df866fb@siemens.com>
2019-09-13  9:33     ` fakechroot Baurzhan Ismagulov
2019-09-13  9:41       ` fakechroot Jan Kiszka
2019-09-13  9:51         ` fakechroot Baurzhan Ismagulov
2019-09-17  9:14         ` fakechroot Henning Schild
2019-09-17  9:52           ` fakechroot Jan Kiszka
2019-09-13 10:57       ` Quirin Gylstorff [this message]
2019-09-13 12:11         ` fakechroot Baurzhan Ismagulov
2019-09-16  8:38           ` fakechroot Quirin Gylstorff
2019-09-17  9:22             ` fakechroot Henning Schild

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=ea373cc9-ad87-b406-cb16-f63db758f3ee@siemens.com \
    --to=quirin.gylstorff@siemens.com \
    --cc=isar-users@googlegroups.com \
    /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