From: Saul Wold <sgw@linux.intel.com>
To: Qi.Chen@windriver.com
Cc: qingtao.cao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] switch to using busybox instead of tinylogin
Date: Tue, 28 May 2013 16:02:28 +0900 [thread overview]
Message-ID: <51A45684.6020803@linux.intel.com> (raw)
In-Reply-To: <cover.1369719531.git.Qi.Chen@windriver.com>
On 05/28/2013 02:39 PM, Qi.Chen@windriver.com wrote:
> From: Chen Qi <Qi.Chen@windriver.com>
>
> The following changes since commit 21089515bd18ba18e86ec8f72ff8141b9fb1dea8:
>
> ref-manual: Added xmlto and dblatex packages for docs (2013-05-22 17:23:41 +0100)
>
> are available in the git repository at:
>
> git://git.pokylinux.org/poky-contrib ChenQi/tinylogin-busybox
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/tinylogin-busybox
>
> Chen Qi (2):
> packagegroup-core-boot: use busybox as the default login manager
> busybox: enable login/password commands by default
>
As Otavio suggested, these need to be re-ordered.
Does this all work correctly without the need to use "setuid" of the
busybox binary, it seems we currently are doing setuid for the busybox
binary since we include SUID app, but what would happen to tinylogin if
we remove that?
Sau!
> meta/recipes-core/busybox/busybox-1.20.2/defconfig | 26 ++++++++++----------
> .../packagegroups/packagegroup-core-boot.bb | 2 +-
> 2 files changed, 14 insertions(+), 14 deletions(-)
>
prev parent reply other threads:[~2013-05-28 7:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 5:39 [PATCH 0/2] switch to using busybox instead of tinylogin Qi.Chen
2013-05-28 5:39 ` [PATCH 1/2] packagegroup-core-boot: use busybox as the default login manager Qi.Chen
2013-05-28 5:39 ` [PATCH 2/2] busybox: enable login/password commands by default Qi.Chen
2013-05-28 6:17 ` Otavio Salvador
2013-05-28 6:25 ` [PATCH 0/2] switch to using busybox instead of tinylogin Jonathan Liu
2013-05-28 6:32 ` ChenQi
2013-05-28 7:02 ` Saul Wold [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=51A45684.6020803@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=Qi.Chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=qingtao.cao@windriver.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