From: Ned Ludd <solar@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] emerge --root : users not created
Date: Tue, 23 Feb 2010 08:58:33 -0800 [thread overview]
Message-ID: <1266944313.5788.73.camel@localhost> (raw)
In-Reply-To: <4B8297AA.9020502@verizon.net>
On Mon, 2010-02-22 at 09:41 -0500, P. Levine wrote:
> Attached is the final version of the chroot patch. I'll submit it in
> the next few days.
>
> It seems absurd to add support for chroot() in useradd and groupadd
> without userdel and groupdel, so the patch includes support for them.
> Also, to create a smaller footprint, I've combined all applicable
> functions into one file. The downside is more complex macro expansions
> (comments included, though), but it allows for a more integrated
> interface (generated function xfgetXXbyYY calls generated functions
> xfsetXXent, xfgetXXent, and xfendXXent), and less alteration of shadow's
> own code.
> PAM isn't a concern because chroot() only strictly works in a process
> with an su uid. And a function to parse the chroot flag before any
> others (leaving argv and argc in a pristine state) is included.
>
> -- Peter Levine
This seems a major improvement over the previous from quickly glancing
over the code. In no time at all I'm sure you will be ready to re hit
upstream.
Q:
If the end user is using Linux-Pam on his/her host system and they run
this. It will ignore loading extra pam modules when entering the chroot?
Or do they flat out need to disable pam on the host so they can take
advantage of this for the chroot?
next prev parent reply other threads:[~2010-02-23 17:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 14:41 [gentoo-embedded] emerge --root : users not created P. Levine
2010-02-22 15:19 ` Peter Stuge
2010-02-22 18:44 ` P. Levine
2010-02-23 16:58 ` Ned Ludd [this message]
2010-02-24 2:01 ` P. Levine
2010-03-06 0:52 ` P. Levine
2010-03-08 11:05 ` Ed W
-- strict thread matches above, loose matches on Subject: below --
2010-02-16 16:14 P. Levine
2010-02-16 15:56 P. Levine
2010-02-16 15:42 P. Levine
2010-02-16 15:20 P. Levine
2010-02-16 15:04 P. Levine
2009-12-14 16:17 Shinkan
2009-12-14 17:14 ` Ed W
2009-12-14 17:47 ` Sven Rebhan
2009-12-14 18:06 ` Peter Stuge
2009-12-15 7:31 ` Sven Rebhan
2009-12-15 8:53 ` Daniel Glaser
2009-12-15 10:33 ` Peter Stuge
2009-12-15 13:31 ` Ahmed Ammar
2009-12-15 14:00 ` Shinkan
2009-12-15 17:37 ` Peter Stuge
2009-12-15 22:24 ` Ahmed Ammar
2009-12-21 21:25 ` Ahmed Ammar
2009-12-21 21:29 ` Ned Ludd
2009-12-22 11:38 ` Peter Stuge
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=1266944313.5788.73.camel@localhost \
--to=solar@gentoo.org \
--cc=gentoo-embedded@lists.gentoo.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