From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: PRoot Isar summary
Date: Fri, 10 Nov 2017 19:59:34 +0100 [thread overview]
Message-ID: <e91c31a6-bb28-2d3b-aafe-d91671636ad0@siemens.com> (raw)
In-Reply-To: <1496e693-490f-16d6-0957-c9281ed7dd3e@ilbers.de>
On 2017-11-09 10:57, Alexander Smirnov wrote:
> Hello everybody,
>
> I've tried to completely switch Isar to PRoot, so here are the problems
> I've faced with:
>
> 1. PRoot doesn't work with UID/GID, all the files in PRoot are owned by
> root. The command 'chown' doesn't have any effect.
>
> 2. Some system commands are failed in PRoot: passwd, chpasswd. I see
> message: System error, no other clues (but for Wheezy these commands work).
>
> 3. mkfs.ext4 doesn't work under proot, lots of files are dropped in
> resulting image.
>
> So, summary:
> ============
>
> 1. PRoot could be an intermediate option for:
> + Buildchroot creation.
> + Packages building.
> - Drawback: works slowly.
Aren't issues 1 and 2 from above affecting these use cases as well?
>
> 2. For image generation the other tool should be considered.
>
What is plan B now? Plan C remains falling back to VM builds, I suppose.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2017-11-10 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 9:57 Alexander Smirnov
2017-11-10 18:59 ` Jan Kiszka [this message]
2017-11-10 19:42 ` Alexander Smirnov
2017-11-11 17:22 ` Benedikt Niedermayr
2017-11-12 8:53 ` Claudius Heine
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=e91c31a6-bb28-2d3b-aafe-d91671636ad0@siemens.com \
--to=jan.kiszka@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