From: ChenQi <Qi.Chen@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] extrausers: add util-linux-sulogin to IMAGE_INSTALL
Date: Mon, 15 Sep 2014 09:47:10 +0800 [thread overview]
Message-ID: <5416451E.9060004@windriver.com> (raw)
In-Reply-To: <CAJTo0LY=XCVYQk6pUKtf2WJ6P1AoGZQ+oZP4XyssNxcEFOPbMg@mail.gmail.com>
On 09/15/2014 06:51 AM, Burton, Ross wrote:
> On 9 September 2014 04:01, Chen Qi <Qi.Chen@windriver.com> wrote:
>> Previously, root with password set cannot login in rescue mode for
>> core-image-minimal. This is because that the busybox's sulogin is
>> not configured with FEATURE_SHADOWPASSWORDS enabled.
>>
>> Add util-linux-sulogin in IMAGE_INSTALL_append properly to fix this problem.
> What's the rationale for installing bits of coreutils, verses enabling
> FEATURE_SHADOWPASSWORDS in busybox?
>
> Ross
>
>
If FEATURE_SHADOWPASSWORDS is enabled in busybox, busybox assumes that
there's /etc/shadow in the system, but it's possible that there isn't.
In such case, the related utilities from busybox cannot work correctly.
That's why I chose to installed util-linux-sulogin conditionally in
extrausers.bbclass instead of enabling FEATRUE_SHADOWPASSWORDS in the
defconfig of busybox.
Best Regards,
Chen Qi
prev parent reply other threads:[~2014-09-15 1:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 3:01 [PATCH 0/2] Fix the problem of being unable to login in rescue mode if password is set Chen Qi
2014-09-09 3:01 ` [PATCH 1/2] util-linux: split out util-linux-sulogin Chen Qi
2014-09-09 3:01 ` [PATCH 2/2] extrausers: add util-linux-sulogin to IMAGE_INSTALL Chen Qi
2014-09-14 22:51 ` Burton, Ross
2014-09-15 1:47 ` ChenQi [this message]
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=5416451E.9060004@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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