From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users <isar-users@googlegroups.com>
Subject: PRoot: Drop sudo around buildchroot
Date: Tue, 24 Oct 2017 22:34:11 +0300 [thread overview]
Message-ID: <8e0fb678-085a-1403-3ee9-f3afef3c080a@ilbers.de> (raw)
Hello all,
I've successfully dropped 'sudo' around buildchroot operations:
- Create buildchroot
- Build dpkg-base package (hello)
- Build dpkg-raw package (example-raw)
The patch is quite small, proot works out-of-the box. I've tested the
following configurations:
- multiconfig:qemuarm-wheezy:isar-image-base
- multiconfig:qemuarm-jessie:isar-image-base
- multiconfig:qemuarm-stretch:isar-image-base
- multiconfig:qemui386-jessie:isar-image-base
- multiconfig:qemui386-stretch:isar-image-base
- multiconfig:qemuamd64-jessie:isar-image-base
- multiconfig:qemuamd64-stretch:isar-image-base
So proot is really good tool :-)
If you'd like to reproduce the test, please try my branch: asmirnov/devel
NOTE: do not forget to install proot: apt-get install proot
Build command:
$ bitbake multiconfig:qemuarm-wheezy:isar-image-base
multiconfig:qemuarm-jessie:isar-image-base
multiconfig:qemuarm-stretch:isar-image-base
multiconfig:qemui386-jessie:isar-image-base
multiconfig:qemui386-stretch:isar-image-base
multiconfig:qemuamd64-jessie:isar-image-base
multiconfig:qemuamd64-stretch:isar-image-base
--
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
next reply other threads:[~2017-10-24 19:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 19:34 Alexander Smirnov [this message]
2017-10-24 20:22 ` Jan Kiszka
2017-10-25 9:48 ` Alexander Smirnov
2017-10-25 14:58 ` Benedikt Niedermayr
2017-10-25 15:29 ` Alexander Smirnov
2017-10-26 8:57 ` Ben Brenson
2017-11-02 17:19 ` Henning Schild
2017-11-02 17:22 ` Henning Schild
2017-11-03 9:00 ` Alexander Smirnov
2017-11-03 9:05 ` Jan Kiszka
2017-11-02 17:33 ` Jan Kiszka
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=8e0fb678-085a-1403-3ee9-f3afef3c080a@ilbers.de \
--to=asmirnov@ilbers.de \
--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