From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: fakechroot
Date: Mon, 16 Sep 2019 10:38:44 +0200 [thread overview]
Message-ID: <45b92ae7-08a1-3312-27ae-296b48f3517b@siemens.com> (raw)
In-Reply-To: <20190913121107.GN6062@yssyq.m.ilbers.de>
On 9/13/19 2:11 PM, Baurzhan Ismagulov wrote:
> On Fri, Sep 13, 2019 at 12:57:45PM +0200, Quirin Gylstorff wrote:
>> 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.
>
> Thanks, the persistent view was my actual question. I think we should be
> looking at pseudo, since the tools without persistency aren't going to work for
> our use case. Or do you see a possibility for fakechroot fakeroot?
>
If using fakeroot and fakechroot, debootstrap knows it is running in a
fakeroot and adapts itself to this environment. From the previous test
with pseudo it does not do that for pseudo[1].
I did not test of pseudo runs with --variant=fakeroot.
[1]
https://groups.google.com/forum/#!msg/isar-users/WV0N4X2ZZMo/4EQI3c1wBQAJ
> With kind regards,
> Baurzhan.
>
Kind regards
Quirin
next prev parent reply other threads:[~2019-09-16 8:39 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 ` fakechroot Quirin Gylstorff
2019-09-13 12:11 ` fakechroot Baurzhan Ismagulov
2019-09-16 8:38 ` Quirin Gylstorff [this message]
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=45b92ae7-08a1-3312-27ae-296b48f3517b@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