From: Mike Looijmans <mike.looijmans@topic.nl>
To: openembedded-core@lists.openembedded.org
Subject: Living without shadow
Date: Fri, 16 May 2014 17:04:39 +0200 [thread overview]
Message-ID: <53762907.8060600@topic.nl> (raw)
Any package that wants to add user accounts (e.g. dbus) automatically
installs the "shadow" package into the image. This appears to be done by
adduser.bbclass.
We want to keep it small, and can easily live without the shadow
package. Busybox already provides adduser and similar commands, and also
handles login etc. just fine. So I tried adding a line
RPROVIDES_busybox+="shadow"
to the busybox recipe. I would expect to have an alternative provider
now, and no more forces installation of the big shadow.
The result was much more surprising though. Letting busybox provide
"shadow" resulted in failing to build the rootfs. The "adduser" command
did not work on the host. This was very unexpected - does shadow deliver
something into the sysroot that adduser.bbclass needs?
How can I get rid of the shadow package?
--
Mike Looijmans
next reply other threads:[~2014-05-16 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 15:04 Mike Looijmans [this message]
2014-05-16 17:23 ` Living without shadow Mark Hatle
2014-05-17 6:41 ` Mike Looijmans
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=53762907.8060600@topic.nl \
--to=mike.looijmans@topic.nl \
--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