All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: normal user for Intel BSPs?
Date: Wed, 25 Jan 2012 14:42:41 -0800	[thread overview]
Message-ID: <4F208561.8010804@intel.com> (raw)
In-Reply-To: <4F207F9B.2060809@linux.intel.com>

On 01/25/2012 02:18 PM, Darren Hart wrote:
> On 01/25/2012 09:36 AM, jfabernathy wrote:
>> I've noticed that the meta-intel BSP come up with the default
>> terminal, serial console user, etc. as root.  What would it take to
>> make my own BSP that was exactly the same, but the default was a not
>> admin user, but you could su or sudo to root?
>
> I'm adding Scott G. who I believe has been working on the useradd
> scripts and such (to sanity check the following). I believe you should
> be able to setup new users by extending an image recipe with a new task
> to make the necessary useradd/mod etc calls on the rootfs prior to
> packaging it up.
>
> Scott, can you offer more detail on how that is done?

Hi Jim, Darren:

The useradd mechanism is for supporting custom users and groups in 
recipes. It sounds like what Jim may find more expedient would be to 
define a recipe which includes a first-boot script which creates the 
additional users/groups and then sets up custom ownership on the 
terminal, serial console user, etc. Otherwise you'd have to do this in 
several recipes.

Using the first-boot script approach is documented here:

http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#usingpoky-extend-addpkg-postinstalls

Whereas using the useradd bitbake class is documented in an example 
recipe in meta-skeleton/recipes-skeleton/useradd/useradd-example.bb. 
There is also a slide deck you may find useful here:

http://wiki.yoctoproject.org/wiki/images/e/e6/Custom_Users_Groups_in_Yocto1.1.pdf

I'll also mention that I'm still shaking out bugs in the useradd 
mechanism. We have some race conditions that are complicating matters 
when building from sstate. So if you're using one of our stable 
releases, the first-boot script approach is probably your safest bet.

Scott

-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center


  reply	other threads:[~2012-01-25 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 17:36 normal user for Intel BSPs? jfabernathy
2012-01-25 22:18 ` Darren Hart
2012-01-25 22:42   ` Scott Garman [this message]
2012-01-25 22:54     ` James Abernathy

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=4F208561.8010804@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=dvhart@linux.intel.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.