public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <ch@denx.de>
To: Gylstorff Quirin <quirin.gylstorff@siemens.com>,
	"Kiszka, Jan (CT RDA IOT SES-DE)" <jan.kiszka@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: Expired root user
Date: Thu, 5 May 2022 18:18:23 +0200	[thread overview]
Message-ID: <f4bcbf05-12ed-6c94-57d8-3808482068f6@denx.de> (raw)
In-Reply-To: <6b5d5d99-a53e-9370-c893-252ffbf0b25a@siemens.com>

Hi Quirin,

On 2022-05-05 17:27, Gylstorff Quirin wrote:
[...]
> 
> Possible solutions are:
> - moving the account creation / modification to the rootfs postprocessing
> - using the systemd first boot service[3] for changing the root password
> 
> Claudius was there are reason why the accounts are created/modified 
> before installing the rootfs? You add the functionality with
> 163f50 meta/classes: add image-account-extension class

TBH, I don't remember, so I would have to guess. It might be that some 
packages that where build by isar and installed later might rely on 
those users and groups existence, but why they can not create their own 
stuff in a pre/postinst or via sysusers.d [1], I currently don't 
remember. Maybe because certain GIDs and UIDs need to fixed to specific 
users/groups over any builds, and adding them dynamically in packages 
might change them depending on the order they are installed.

I guess just moving it to the postprocess step, build some projects and 
see if anything breaks is probably necessary at this point, if you don't 
see any reason for it.

Sorry that I am not that helpful.

kind regards,
Claudius,

[1] https://manpages.debian.org/buster/systemd/sysusers.d.5.en.html

      reply	other threads:[~2022-05-05 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 15:27 Gylstorff Quirin
2022-05-05 16:18 ` Claudius Heine [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=f4bcbf05-12ed-6c94-57d8-3808482068f6@denx.de \
    --to=ch@denx.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=quirin.gylstorff@siemens.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