From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/7] shadow: add a -native recipe with customized utilities
Date: Wed, 01 Jun 2011 14:42:25 +0100 [thread overview]
Message-ID: <1306935745.2529.91.camel@phil-desktop> (raw)
In-Reply-To: <4DE631D3.9070703@ge.com>
On Wed, 2011-06-01 at 13:34 +0100, Martyn Welch wrote:
> On 01/06/11 10:47, Phil Blundell wrote:
> > On Tue, 2011-05-31 at 12:53 -0700, Scott Garman wrote:
> >> This adds a -native recipe for the shadow utilities.
> >>
> >> The custom --root option allows the the following utilities to be
> >> run within a chroot when invoked under pseudo:
> >
> > Rather than patching the code for all these utilities, can't you just
> > wrap them in a call to chroot(8)? That is, make useradd.bbclass do:
> >
> > eval $PSEUDO chroot ${STAGING_DIR_TARGET} useradd ...
> >
> > rather than the existing
> >
> > eval $PSEUDO useradd --root ${STAGING_DIR_TARGET} ...
> >
> > ?
> >
>
> You'd need root privileges to use chroot wouldn't you? I'm assuming you
> wouldn't with the existing.
Doesn't $PSEUDO sort that out? The --root option that Scott has patched
into all the utilities seems to just end up calling chroot(2) anyway so
you would need root privileges at that point. That said, I'm not
entirely au fait with pseudo so I might well be misunderstanding how it
works.
p.
next prev parent reply other threads:[~2011-06-01 13:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 19:53 [PATCH 0/7] User/group creation at preinstall Scott Garman
2011-05-31 18:45 ` [poky] " Koen Kooi
2011-05-31 19:06 ` Saul Wold
2011-05-31 19:51 ` Scott Garman
2011-05-31 19:57 ` Otavio Salvador
2011-05-31 21:16 ` Mark Hatle
2011-05-31 21:27 ` Scott Garman
2011-05-31 21:51 ` Richard Purdie
2011-05-31 21:25 ` Richard Purdie
2011-05-31 19:53 ` [PATCH 1/7] shadow: recipe and patch cleanup Scott Garman
2011-05-31 19:53 ` [PATCH 2/7] shadow: add a -native recipe with customized utilities Scott Garman
2011-06-01 9:47 ` Phil Blundell
2011-06-01 12:34 ` Martyn Welch
2011-06-01 13:42 ` Phil Blundell [this message]
2011-06-01 17:43 ` Scott Garman
2011-06-01 21:05 ` Mark Hatle
2011-06-02 11:19 ` Phil Blundell
2011-09-01 14:46 ` Phil Blundell
2011-09-01 16:41 ` Phil Blundell
2011-09-01 16:54 ` Mark Hatle
2011-09-01 16:58 ` Phil Blundell
2011-09-01 17:25 ` Mark Hatle
2011-09-01 19:44 ` Phil Blundell
2011-09-01 21:59 ` Richard Purdie
2011-09-02 0:02 ` Mark Hatle
2011-09-02 7:15 ` Phil Blundell
2011-09-02 9:50 ` Phil Blundell
2011-09-02 14:03 ` Richard Purdie
2011-09-02 18:43 ` Phil Blundell
2011-09-02 19:17 ` Mark Hatle
2011-05-31 19:53 ` [PATCH 3/7] base-passwd: add -cross recipe with default login.defs Scott Garman
2011-05-31 19:53 ` [PATCH 4/7] useradd.bbclass: new class for managing user/group permissions Scott Garman
2011-05-31 19:53 ` [PATCH 5/7] useradd-example: example recipe for using inherit useradd Scott Garman
2011-05-31 19:53 ` [PATCH 6/7] bitbake.conf: set PSEUDO_PASSWD within FAKEROOTENV Scott Garman
2011-05-31 19:53 ` [PATCH 7/7] package_rpm.bbclass: make RPM use on-disk permissions Scott Garman
-- strict thread matches above, loose matches on Subject: below --
2011-06-02 23:50 [PATCH 0/7] User/group creation at preinstall v2 Scott Garman
2011-06-02 23:50 ` [PATCH 2/7] shadow: add a -native recipe with customized utilities Scott Garman
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=1306935745.2529.91.camel@phil-desktop \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
/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