From: Ben Brenson <benbrenson89@googlemail.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: Claudius Heine <claudius.heine.ext@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: PRoot experiments
Date: Fri, 20 Oct 2017 10:18:13 +0200 [thread overview]
Message-ID: <CAF5832UWRVZ8_RifDG4VM9z3KBtneB1OU+dw59twk75MwKxO8w@mail.gmail.com> (raw)
In-Reply-To: <cf1bcf2d-a580-1164-dad4-6b6c13187cdf@ilbers.de>
[-- Attachment #1: Type: text/plain, Size: 1755 bytes --]
Yes, but chroot itself is not working, which is called from multistrap when
creating a rootfs with same architecture as the host system.
I also didn't specify a setupscript and my multistrap.conf looks as follows:
[General]
noauth=false
unpack=true
bootstrap=debian-stretch
aptsources=debian-stretch
[debian-stretch]
source=http://deb.debian.org/debian
suite=stretch
components=main contrib non-free
packages=
May it be possible to provide a self contained version of multistrap? Or
would that be a No-Go?
Regards,
Benedikt
2017-10-19 13:40 GMT+02:00 Alexander Smirnov <asmirnov@ilbers.de>:
> On 10/19/2017 02:36 PM, Benedikt Niedermayr wrote:
>
>> I found the problem.
>>
>> When running multistrap with the host architecture (amd64), then
>> multistrap will automatically run chroot to configure the
>> extracted *.deb packages.
>> This is not the case when running multistrap with a foreign architecture
>> (armhf).
>>
>> Keeping in mind, that also amd64 based rootfs builds should be possible,
>> some problems still persist.
>>
>>
> It's not the problem, PRoot successfully works with QEMU like chroot:
>
> asmirnov@zbook:~/Work/isar/isar/build/tmp/work/debian-jessie-armhf/buildchroot$
> PROOT_NO_SECCOMP=1 proot -q qemu-arm -0 -r rootfs /bin/bash
> proot warning: can't chdir("/home/asmirnov/Work/isa
> r/isar/build/tmp/work/debian-jessie-armhf/buildchroot/./.") in the guest
> rootfs: No such file or directory
> proot info: default working directory is now "/"
> root@zbook:/#
>
>
> Regards,
>> Benedikt
>>
>
> --
> With best regards,
> Alexander Smirnov
>
> ilbers GmbH
> Baierbrunner Str. 28c
> D-81379 Munich
> +49 (89) 122 67 24-0
> http://ilbers.de/
> Commercial register Munich, HRB 214197
> General manager: Baurzhan Ismagulov
>
[-- Attachment #2: Type: text/html, Size: 2857 bytes --]
next prev parent reply other threads:[~2017-10-20 8:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 12:29 Alexander Smirnov
2017-10-19 8:59 ` Henning Schild
2017-10-19 10:10 ` Ben Brenson
[not found] ` <b0082bee-94d7-48c6-8582-93efc4171b59@googlegroups.com>
2017-10-19 10:14 ` Alexander Smirnov
2017-10-19 10:39 ` Claudius Heine
2017-10-19 10:44 ` Benedikt Niedermayr
2017-10-19 11:08 ` Claudius Heine
2017-10-19 11:15 ` Benedikt Niedermayr
2017-10-19 11:37 ` Alexander Smirnov
2017-10-19 11:36 ` Benedikt Niedermayr
2017-10-19 11:40 ` Alexander Smirnov
2017-10-19 13:37 ` Ben Brenson
2017-10-20 8:18 ` Ben Brenson [this message]
2017-10-20 8:52 ` Claudius Heine
2017-10-20 9:21 ` Ben Brenson
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=CAF5832UWRVZ8_RifDG4VM9z3KBtneB1OU+dw59twk75MwKxO8w@mail.gmail.com \
--to=benbrenson89@googlemail.com \
--cc=asmirnov@ilbers.de \
--cc=claudius.heine.ext@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