public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>,
	isar-users@googlegroups.com, Claudius Heine <ch@denx.de>
Subject: Re: putting users into groups (created by packages)
Date: Thu, 22 Jul 2021 20:27:08 +0200	[thread overview]
Message-ID: <2ed2675d-f7f3-486a-665b-884611f55822@siemens.com> (raw)
In-Reply-To: <20210722183337.5ac359d2@md1za8fc.ad001.siemens.net>

On 22.07.21 18:33, Henning Schild wrote:
> Hi,
> 
> i just had a need to install docker and join a user into that group.
> But even though the package would create the group ... i found myself
> having to create the group anyways. Because we run
> "ROOTFS_CONFIGURE_COMMAND" before installing packages.
> 
> So i need 
> 
> +IMAGE_PREINSTALL += "docker.io ca-certificates apparmor"
> +
> +USER_admin[groups] += "docker"
> 
> and
> 
> +GROUPS += "docker"
> +GROUPS_docker[flags] = "system"
> 
> Would it not be nice to move "image_configure_accounts" into
> ROOTFS_POSTPROCESS_COMMAND? So these last two lines would not be
> needed. Especiall the last one is nasty ... because i have to mimic the
> flags of a postinst.
> 

When does debian preseed apply account settings, before or after
installing packages? I would be surprised if they did that upfront but I
also didn't check.

Jan

PS: As we are discussing wishlists: Would be nice to also accept
clear-text passwords (just like preseed does) to allow picking them up
from upcoming "kas menu". Yes, security implications are understood.

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

  reply	other threads:[~2021-07-22 18:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22 16:33 Henning Schild
2021-07-22 18:27 ` Jan Kiszka [this message]
2021-07-23  6:41   ` Henning Schild
2021-07-23  9:27     ` Claudius Heine

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=2ed2675d-f7f3-486a-665b-884611f55822@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=ch@denx.de \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    /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