All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: "Dominig ar Foll (Intel Open Source)" <dominig.arfoll@fridu.net>,
	 yocto@yoctoproject.org
Subject: Re: Changing UID GID
Date: Wed, 15 Feb 2017 14:55:51 +0000	[thread overview]
Message-ID: <1487170551.4342.7.camel@linux.intel.com> (raw)
In-Reply-To: <c5a4c802-163e-6e4b-e7c2-fc2f598c11ec@fridu.net>

[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]

On Wed, 2017-02-15 at 15:43 +0100, Dominig ar Foll (Intel Open Source)
wrote:
>     Hello,
> 
>       
> 
>       in AGL project we are facing an issue as when we create new
> images
>       the UID,GID of given packages can (and does) change depending
> of
>       the build.
> 
>       This induces issues when we create partial update file using
> image
>       diffs.
> 
>       
> 
>       Could you let us know if we need to create our own solution, or
> if
>       yocto already has a model to enforce a known UID-GID on
> packages
>       coming from internal or external repo such as Open-Embedded 
>       without patching (or creating a bbappend) for each imported
> package
>       ?

You can use useradd-staticids, which will use a table of known uid/gid
rather than using the next available id.

See the docs:
http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-
classes-useradd

and the commit which introduced the feature:
http://git.yoctoproject.org/clean/cgit.cgi/poky/commit/meta/classes/use
radd-staticids.bbclass?id=4bc6982ea60929226bcd9d206b4879dea2a3157c

Joshua

[-- Attachment #2: Type: text/html, Size: 1655 bytes --]

  reply	other threads:[~2017-02-15 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 14:43 Changing UID GID Dominig ar Foll (Intel Open Source)
2017-02-15 14:55 ` Joshua Lock [this message]
2017-02-15 14:57 ` Patrick Ohly
2017-02-17  9:58   ` Changing UID GID (thaks) Dominig ar Foll (Intel Open Source)

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=1487170551.4342.7.camel@linux.intel.com \
    --to=joshua.g.lock@linux.intel.com \
    --cc=dominig.arfoll@fridu.net \
    --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.