From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] UID management
Date: Wed, 1 Jun 2016 11:28:02 +0200 [thread overview]
Message-ID: <20160601112802.3b66873f@free-electrons.com> (raw)
In-Reply-To: <35ca1901-4687-d84a-716b-30b52d460890@gmail.com>
Hello,
On Wed, 1 Jun 2016 11:15:02 +0200, Marco Trapanese wrote:
> Hello, I kindly ask a suggestion about the best way to manage UIDs.
> On my host system, where I have the overlay directory, the UID of the user is 1000.
> The home directory of my normal user in the target system is /opt.
>
> The overlay files copied into /opt belong to the dbus user, which has the UID 1000.
> The owner of that home directory should be user defined in the user_table file, with UID 1100:
>
> user 1100 user 1100 =user /opt /bin/sh dialout,wheel,lp,pulse,audio,network,pulse-access
> root:x:0:
> user:x:1100:
> dbus:x:1000:dbus
>
> I'm not sure which is the recommended way to get rid of this.
> I have to (manually?) chown the overlay file and set them to UID 1100?
By default, Buildroot chowns all files of the root filesystem to the
root user (i.e UID 0, GID 0). You can override that:
1/ On a per-package basis using the <pkg>_PERMISSIONS variable.
2/ Globally on your system, by passing a permission table using the
BR2_ROOTFS_DEVICE_TABLE option.
See the Buildroot manual for details.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-06-01 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 9:15 [Buildroot] UID management Marco Trapanese
2016-06-01 9:28 ` Thomas Petazzoni [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=20160601112802.3b66873f@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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