From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7142] New: ecryptfs needs getent to run
Date: Sun, 1 Jun 2014 17:16:27 +0000 (UTC) [thread overview]
Message-ID: <bug-7142-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7142
Summary: ecryptfs needs getent to run
Product: buildroot
Version: 2014.05
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: xxiao8 at fosiao.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
glibc/eglibc has getent built automatically, it should be copied to target root
filesystem for package ecryptfs to run.
uclibc has a getent under extra/scripts which emulates getenv in glibc/eglibc.
there might be other packages need getent, which is small in size, I would
suggest always put that to target rootfs?
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-06-01 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 17:16 bugzilla at busybox.net [this message]
2014-06-01 17:32 ` [Buildroot] [Bug 7142] ecryptfs needs getent to run bugzilla at busybox.net
2014-08-16 14:43 ` bugzilla at busybox.net
2014-09-02 8:40 ` bugzilla at busybox.net
2014-10-20 21:08 ` bugzilla at busybox.net
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=bug-7142-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.