From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/7] base-passwd: populate the target sysroot with passwd/group/login.defs
Date: Thu, 09 Jun 2011 14:23:34 -0700 [thread overview]
Message-ID: <4DF139D6.3070508@intel.com> (raw)
In-Reply-To: <5D76A268-DA2B-4F5A-BDE0-79211C403B0F@dominion.thruhere.net>
On 06/09/2011 01:50 PM, Koen Kooi wrote:
>
> Op 3 jun 2011, om 01:50 heeft Scott Garman het volgende geschreven:
>
>> The passwd, group, and login.defs files in the target sysroot will
>> be used when recipes create custom user and group permissions in
>> their packages.
>>
>> Signed-off-by: Scott Garman<scott.a.garman@intel.com>
>> ---
>> .../base-passwd/base-passwd-3.5.22/login.defs | 386 ++++++++++++++++++++
>
> I'm now getting tons and tons of the following when using shadow:
>
> [ 900.349395] grpconv[682]: unknown configuration item `FAILLOG_ENAB'
> [ 900.357391] grpconv[682]: unknown configuration item `LASTLOG_ENAB'
> [ 900.364196] grpconv[682]: unknown configuration item `OBSCURE_CHECKS_ENAB'
> [ 900.371734] grpconv[682]: unknown configuration item `PORTTIME_CHECKS_ENAB'
> [ 900.381042] grpconv[682]: unknown configuration item `QUOTAS_ENAB'
> [ 900.387878] grpconv[682]: unknown configuration item `MOTD_FILE'
> [ 900.394256] grpconv[682]: unknown configuration item `FTMP_FILE'
> [ 900.400634] grpconv[682]: unknown configuration item `NOLOGINS_FILE'
> [ 900.407348] grpconv[682]: unknown configuration item `ENV_HZ'
> [ 900.413452] grpconv[682]: unknown configuration item `PASS_MIN_LEN'
> [ 900.420104] grpconv[682]: unknown configuration item `SU_WHEEL_ONLY'
> [ 900.426849] grpconv[682]: unknown configuration item `CRACKLIB_DICTPATH'
> [ 900.433929] grpconv[682]: unknown configuration item `PASS_CHANGE_TRIES'
> [ 900.441040] grpconv[682]: unknown configuration item `PASS_ALWAYS_WARN'
> [ 900.448028] grpconv[682]: unknown configuration item `CHFN_AUTH'
> [ 900.454376] grpconv[682]: unknown configuration item `ENVIRON_FILE'
>
>
> which seems to be related to the login.defs change.
What context is this happening in? Runtime, or during a buildstep?
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-06-09 21:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 23:50 [PATCH 0/7] User/group creation at preinstall v2 Scott Garman
2011-06-02 23:50 ` [PATCH 1/7] shadow: recipe and patch cleanup Scott Garman
2011-06-02 23:50 ` [PATCH 2/7] shadow: add a -native recipe with customized utilities Scott Garman
2011-06-02 23:50 ` [PATCH 3/7] base-passwd: populate the target sysroot with passwd/group/login.defs Scott Garman
2011-06-09 20:50 ` Koen Kooi
2011-06-09 21:23 ` Scott Garman [this message]
2011-06-09 21:25 ` Koen Kooi
2011-06-09 21:29 ` Scott Garman
2011-06-10 22:22 ` shadow errors related to login.defs Scott Garman
2011-06-10 22:38 ` Koen Kooi
2011-06-02 23:50 ` [PATCH 4/7] useradd.bbclass: new class for managing user/group permissions Scott Garman
2011-06-28 13:04 ` Richard Purdie
2011-06-28 14:42 ` Mark Hatle
2011-06-29 14:22 ` Richard Purdie
2011-06-29 1:20 ` Scott Garman
2011-06-02 23:50 ` [PATCH 5/7] useradd-example: example recipe for using inherit useradd Scott Garman
2011-06-02 23:50 ` [PATCH 6/7] bitbake.conf: set PSEUDO_PASSWD within FAKEROOTENV Scott Garman
2011-06-02 23:50 ` [PATCH 7/7] package_rpm.bbclass: make RPM use on-disk permissions 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=4DF139D6.3070508@intel.com \
--to=scott.a.garman@intel.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