From: Henning Schild <henning.schild@siemens.com>
To: <chombourger@gmail.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/2] buildchroot: Enter buildchroot with right user:group directly
Date: Thu, 22 Nov 2018 13:03:44 +0100 [thread overview]
Message-ID: <20181122130344.3d1c1146@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <ef651f7e-0cbc-420a-b291-100fe6dc5691@googlegroups.com>
Am Thu, 22 Nov 2018 02:13:25 -0800
schrieb <chombourger@gmail.com>:
> cool - I will indeed rework the upcoming dpkg-source class to use
> this. Thanks a bunch for the hint!
Hehe, and i even forgot the CC, that i wanted to add. Make sure to
source /isar/common.sh as well. That guy should probably evolve to be
the one entry point into buildchroot, no matter what you do there.
Henning
> On Thursday, November 22, 2018 at 10:38:21 AM UTC+1, Henning Schild
> wrote:
> >
> > From: Henning Schild <hen...@hennsch.de <javascript:>>
> >
> > Instead of using "su" use "chroot --userspec". That should also be
> > the pattern for other chroot users that do not need root. i.e.
> > kernel build and upcoming "apt-get source" fetcher.
> > This way we can skip all the chowning we had/have to do otherwise.
> >
> > Signed-off-by: Henning Schild <henning...@siemens.com
> > <javascript:>>
>
next prev parent reply other threads:[~2018-11-22 12:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 9:38 Henning Schild
2018-11-22 9:38 ` [PATCH 2/2] buildchroot: Assert that we are one of the two valid users Henning Schild
2018-11-23 10:24 ` Maxim Yu. Osipov
2018-11-22 10:13 ` [PATCH 1/2] buildchroot: Enter buildchroot with right user:group directly chombourger
2018-11-22 12:03 ` Henning Schild [this message]
2018-11-22 13:58 ` Henning Schild
2018-11-23 10:24 ` Maxim Yu. Osipov
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=20181122130344.3d1c1146@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=chombourger@gmail.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