From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V5 0/2] shadow: upgrade from 4.1.4.3 to 4.2.1
Date: Mon, 21 Jul 2014 19:16:30 +0100 [thread overview]
Message-ID: <1405966590.22985.103.camel@ted> (raw)
In-Reply-To: <53CCF28B.1050804@mlbassoc.com>
On Mon, 2014-07-21 at 04:59 -0600, Gary Thomas wrote:
> On 2014-07-21 02:27, Richard Purdie wrote:
> > On Thu, 2014-07-17 at 15:53 +0800, Chen Qi wrote:
> >> The following changes since commit 846bc50fde11bbb36c8eb5b2e3ae6bb644c037f3:
> >>
> >> ltp: use "foreign" automake strictness (2014-07-16 10:27:16 +0100)
> >>
> >> are available in the git repository at:
> >>
> >> git://git.openembedded.org/openembedded-core-contrib ChenQi/shadow-4.2.1
> >> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=ChenQi/shadow-4.2.1
> >>
> >> Chen Qi (2):
> >> shadow: upgrade from 4.1.4.3 to 4.2.1
> >> oeqa: fix return status in pam.py to match shadow-4.2.1
> >
> > I think but am not 100% sure this has introduced another regression:
> >
> > https://autobuilder.yoctoproject.org/main/builders/nightly-oecore/builds/177
> >
> > The issue is that X doesn't start in oe-core built images. It does work
> > correctly in poky. The issue is that the /etc/init.d/xserver-nodm script
> > returns:
> >
> > root@qemuarm:/etc# /etc/init.d/xserver-nodm start
> > Starting Xserver
> > su: applet not found
> >
> > or to be more specific:
> >
> > root@qemuarm:/etc# su -l -c '/etc/X11/Xserver&' xuser
> > su: applet not found
> >
> >
> > The poky images appear to work since we install bash. If you remove bash
> > from packagegroup-core-device-devel.bb, the poky images will show the
> > same error.
> >
> > I think this is something to do with the none-suid busybox binary not
> > containing su support, but why su is being called there, I don't know.
> > su is being provided by shadow in the image. If I make su provided by
> > busybox the problem also goes away.
>
> The problem (reported last week on the Yocto list) is su.shadow
> changed how it behaves. The old version would end up passing
> the script off by
> 6761 execve("/bin/sh", ["/bin/sh", "-c", "/etc/X11/Xserver"], [/* 7 vars */]) = 0
> whereas the new version does
> 961 execve("/bin/sh", ["-su", "-c", "/etc/X11/Xserver"], [/* 7 vars */]) = 0
Hmm, busybox is interpreting that "-su" as an argument to call su, which
busybox.nosuid doesn't have within it as an applet, hence the error
message.
> I still haven't figured out why su.shadow now behaves this way.
That does indeed look like what we need to figure out...
Cheers,
Richard
prev parent reply other threads:[~2014-07-21 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 7:53 [PATCH V5 0/2] shadow: upgrade from 4.1.4.3 to 4.2.1 Chen Qi
2014-07-17 7:53 ` [PATCH V5 1/2] " Chen Qi
2014-07-17 7:53 ` [PATCH V5 2/2] oeqa: fix return status in pam.py to match shadow-4.2.1 Chen Qi
2014-07-21 8:27 ` [PATCH V5 0/2] shadow: upgrade from 4.1.4.3 to 4.2.1 Richard Purdie
2014-07-21 10:59 ` Gary Thomas
2014-07-21 18:16 ` Richard Purdie [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=1405966590.22985.103.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.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