From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] base-passwd: disable problematic login.defs options
Date: Sun, 19 Jun 2011 21:13:07 -0500 [thread overview]
Message-ID: <4DFEACB3.7090405@windriver.com> (raw)
In-Reply-To: <4DFB98A2.9040303@intel.com>
On 6/17/11 1:10 PM, Scott Garman wrote:
> On 06/17/2011 10:22 AM, Otavio Salvador wrote:
>> On Fri, Jun 17, 2011 at 17:19, Scott Garman<scott.a.garman@intel.com> wrote:
>>> Sorry, I forgot to mention that shadow-utils-native is what is used to
>>> modify the passwd/group files in the target sysroot. It seems that having a
>>> -native recipe install files into a target sysroot would be worse than
>>> including an optional file with base-passwd that may or may not be used in
>>> target systems.
>>
>> Why not make an shadow-target package with this?
>
> To just install a login.defs file? I'm open to it if a few more people
> think this is a better idea.
The file is needed in order for the utilities that add, remove and modify
users/groups to function properly. The full version from shadow utils is used
so we are sure we can dead with both shadow-less and shadowed filesystem images.
(It's also more full featured then busybox, yet busybox is still compatible
with it.)
As for the separate package, that should be fine.. but remember this is a very
small file, so is it worth "another" package? (If so, then base-files likely
should depend on it for build-time, but not run-time.)
--Mark
> Scott
>
next prev parent reply other threads:[~2011-06-20 2:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 18:49 [PATCH 0/1] Fix for runtime errors due to login.defs Scott Garman
2011-06-16 18:50 ` [PATCH 1/1] base-passwd: disable problematic login.defs options Scott Garman
2011-06-16 23:54 ` Khem Raj
2011-06-17 16:34 ` Scott Garman
2011-06-17 16:43 ` Khem Raj
2011-06-17 17:19 ` Scott Garman
2011-06-17 17:22 ` Otavio Salvador
2011-06-17 18:10 ` Scott Garman
2011-06-20 2:13 ` Mark Hatle [this message]
2011-06-20 2:41 ` Khem Raj
2011-06-20 3:33 ` Scott Garman
2011-06-17 10:11 ` Koen Kooi
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=4DFEACB3.7090405@windriver.com \
--to=mark.hatle@windriver.com \
--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