From: Saul Wold <sgw@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] builder: Add password for user
Date: Thu, 01 Nov 2012 08:38:50 -0700 [thread overview]
Message-ID: <5092978A.5000607@linux.intel.com> (raw)
In-Reply-To: <509295B0.3000707@windriver.com>
On 11/01/2012 08:30 AM, Mark Hatle wrote:
> On 11/1/12 2:32 AM, Saul Wold wrote:
>> This is needed to allow openssh to work correctly for the Eclipse
>> plugin to have access to the build appliance to view/modify recipes
>> and lauch builds
>>
>> Signed-off-by: Saul Wold <sgw@linux.intel.com>
>> ---
>> meta/recipes-graphics/builder/builder_0.1.bb | 3 ++-
>> 1 files changed, 2 insertions(+), 1 deletions(-)
>>
>> diff --git a/meta/recipes-graphics/builder/builder_0.1.bb
>> b/meta/recipes-graphics/builder/builder_0.1.bb
>> index 5c12c14..d46e960 100644
>> --- a/meta/recipes-graphics/builder/builder_0.1.bb
>> +++ b/meta/recipes-graphics/builder/builder_0.1.bb
>> @@ -18,7 +18,8 @@ inherit useradd
>> USERADD_PACKAGES = "${PN}"
>> USERADD_PARAM_${PN} = "--system --create-home \
>> --groups video,tty,audio \
>> - --user-group ${PN}"
>> + --user-group ${PN} \
>> + --password ${PN}"
>
> The above won't work. The password passed to --password, must be in
> encrypted in crypt(3) format.
>
Ah, thanks, turns out I also missed the PR Bump!
v2 coming
Sau!
> --Mark
>
>>
>> do_install () {
>> install -d -m 755 ${D}${sysconfdir}/mini_x/session.d
>>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
prev parent reply other threads:[~2012-11-01 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 7:32 [PATCH] builder: Add password for user Saul Wold
2012-11-01 15:30 ` Mark Hatle
2012-11-01 15:38 ` 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=5092978A.5000607@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=mark.hatle@windriver.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