All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andy Pont" <andy.pont@sdcsystems.com>
To: "'Rudolf J Streif'" <rudolf.streif@gmail.com>, <yocto@yoctoproject.org>
Subject: Re: Setting root password
Date: Thu, 24 Sep 2015 17:21:41 +0100	[thread overview]
Message-ID: <009301d0f6e5$197dc180$4c794480$@pont@sdcsystems.com> (raw)
In-Reply-To: <7720054.5AybCaxdE3@rjs-mbpro.streifs.net>

Rudi wrote…

> > Still, I think is a good ideia to understand what is going wrong with
> > EXTRA_USERS_PARAMS, other users may having the same problem.
>
> EXTRA_USERS_PARAMS works for me all the time. The stanza is what I am
using 
> in my image recipes:
> 
> EXTRA_USERS_PARAMS = "\
> groupadd developers; \
> useradd -p `openssl passwd ${DEV_PASSWORD}` developer; \
> useradd -g developers developer; \
> usermod -p `openssl passwd ${ROOT_PASSWORD}` root; \
>"
>
> If this is an accurate copy of what you are using
>
> EXTRA_USERS_PARAMS = "usermod -P <encrypted_password> root;"
>
> then the issue probably is the capital -P. It should be lowercase.

Good spot.  I copied and pasted it from an article I found on the web!
Having changed it to lower case it now works as expected!

Thanks,

Andy.



  reply	other threads:[~2015-09-24 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5603f9ce.e9d1440a.dc3ac.43adSMTPIN_ADDED_BROKEN@mx.google.com>
2015-09-24 13:45 ` Setting root password Daniel.
2015-09-24 13:59   ` Andy Pont
     [not found]   ` <560401bd.46256b0a.11836.2eefSMTPIN_ADDED_BROKEN@mx.google.com>
2015-09-24 14:16     ` Daniel.
2015-09-24 14:20       ` Daniel.
2015-09-24 15:17         ` Rudolf J Streif
2015-09-24 16:21           ` Andy Pont [this message]
2015-09-29  9:04           ` Paul Eggleton
2015-09-24 13:24 Andy Pont
  -- strict thread matches above, loose matches on Subject: below --
2013-10-11 14:35 Jack Mitchell
2013-10-11 15:08 ` Koen Kooi
2013-10-12  2:04 ` ChenQi

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='009301d0f6e5$197dc180$4c794480$@pont@sdcsystems.com' \
    --to=andy.pont@sdcsystems.com \
    --cc=rudolf.streif@gmail.com \
    --cc=yocto@yoctoproject.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 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.