Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/9] builder: Add password for user
Date: Wed, 14 Nov 2012 08:05:31 -0800	[thread overview]
Message-ID: <50A3C14B.7080707@linux.intel.com> (raw)
In-Reply-To: <50A3A633.2040801@windriver.com>

On 11/14/2012 06:09 AM, Mark Hatle wrote:
> On 11/13/12 11:32 PM, 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 |    5 +++--
>>   1 files changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta/recipes-graphics/builder/builder_0.1.bb
>> b/meta/recipes-graphics/builder/builder_0.1.bb
>> index 5c12c14..7ac531c 100644
>> --- a/meta/recipes-graphics/builder/builder_0.1.bb
>> +++ b/meta/recipes-graphics/builder/builder_0.1.bb
>> @@ -1,7 +1,7 @@
>>   SUMMARY = "New user to do specific job"
>>   DESCRIPTION = "This recipe create a new user named ${PN}, who is
>> used for specific jobs like building. The task can be auto started via
>> mini X"
>>   SECTION = "x11"
>> -PR = "r4"
>> +PR = "r5"
>>   LICENSE = "MIT"
>>   LIC_FILES_CHKSUM =
>> "file://builder_hob_start.sh;endline=5;md5=84796c3c41785d86100fdabcbdade00e"
>>
>>
>> @@ -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 .gLibiNXn0P12"
>
> This should work, but can you add a comment that indicates the
> plain-text for the password?
>
Ahh, that would take all the fun out!

v2 coming with Otavio's suggestion also!

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
>
>



  reply	other threads:[~2012-11-14 16:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14  5:32 [PATCH 0/9] Fixes and Updates Saul Wold
2012-11-14  5:32 ` [PATCH 1/9] packagegroup-self-hosted: add sftp server Saul Wold
2012-11-14  5:32 ` [PATCH 2/9] builder: Add password for user Saul Wold
2012-11-14 11:21   ` Otavio Salvador
2012-11-14 14:09   ` Mark Hatle
2012-11-14 16:05     ` Saul Wold [this message]
2012-11-14  5:32 ` [PATCH 3/9] less: Update to 451 Saul Wold
2012-11-14 11:26   ` Otavio Salvador
2012-11-14 11:33     ` Paul Eggleton
2012-11-14 11:36       ` Otavio Salvador
2012-11-14 14:54         ` Richard Purdie
2012-11-14  5:32 ` [PATCH 4/9] psmisc: Update to 22.20 Saul Wold
2012-11-14  5:32 ` [PATCH 5/9] kconfig-frontends: Update to 3.6 Saul Wold
2012-11-14  5:32 ` [PATCH 6/9] sysstat: Update to 10.1.2 Saul Wold
2012-11-14 11:24   ` Otavio Salvador
2012-11-14  5:32 ` [PATCH 7/9] mx: Update to 1.4.7 Saul Wold
2012-11-14  5:32 ` [PATCH 8/9] sqlite3: Update to 3.7.14.1 Saul Wold
2012-11-14  8:30   ` Martin Jansa
2012-11-14  5:32 ` [PATCH 9/9] pulse: fix Bashism in string test Saul Wold

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=50A3C14B.7080707@linux.intel.com \
    --to=sgw@linux.intel.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