cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org,
	Henning Schild <henning.schild@siemens.com>
Cc: Wang Jing <wangjing@siemens.com>,
	Gylstorff Quirin <quirin.gylstorff@siemens.com>
Subject: Re: [cip-dev] [isar-cip-core][PATCH 0/6] improve root home moving for layers
Date: Mon, 2 Jan 2023 11:42:29 +0100	[thread overview]
Message-ID: <bee9645b-15e1-0f93-d0b5-df8974711459@siemens.com> (raw)
In-Reply-To: <8a8848a0-a801-78bf-e4db-162c19aa3f31@siemens.com>

On 21.12.22 14:01, Gylstorff Quirin wrote:
> 
> 
> On 11/29/22 13:24, Henning Schild via lists.cip-project.org wrote:
>> The original idea was to make the rootfs home dir move and symlink
>> reusable in another layer, while also playing back some findings from
>> that other layer.
>>
>> That is p1...p4
>>
>> p5 and p6 are drive by findings, feel free to pick in any order i do not
>> care about them too much
>>
>> Henning Schild (6):
>>    customizations: make postinst idempotent
>>    customizations: make postinst script report all potential errors
>>    customizations: comment why we can not actually change home easily
>>    change-root-homedir: split root home move into own package
>>    kas: set clear text root password
>>    CONTRIBUTING: fix note on patch prefixes
>>
>>   CONTRIBUTING.md                               |  2 +-
>>   kas-cip.yml                                   |  4 ++--
>>   .../change-root-homedir.bb                    |  5 +++++
>>   .../change-root-homedir/files/postinst        | 21 +++++++++++++++++++
>>   recipes-core/customizations/common.inc        |  5 +++--
>>   recipes-core/customizations/files/postinst    | 10 ++++-----
>>   6 files changed, 37 insertions(+), 10 deletions(-)
>>   create mode 100644
>> recipes-core/change-root-homedir/change-root-homedir.bb
>>   create mode 100644 recipes-core/change-root-homedir/files/postinst
>>
>>
>>
> 
> Looks good to me. Tested with qemu-amd64.
> 
> Acked-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> 

Didn't hit the list and also patchwork. Please check for the reason and
resubmit.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux



  reply	other threads:[~2023-01-02 10:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221129122451.32155-1-henning.schild@siemens.com>
2022-12-21 13:01 ` [cip-dev] [isar-cip-core][PATCH 0/6] improve root home moving for layers Gylstorff Quirin
2023-01-02 10:42   ` Jan Kiszka [this message]
     [not found]     ` <20230102180405.6cc06e3d@md1za8fc.ad001.siemens.net>
2023-01-02 17:23       ` Jan Kiszka

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=bee9645b-15e1-0f93-d0b5-df8974711459@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=henning.schild@siemens.com \
    --cc=quirin.gylstorff@siemens.com \
    --cc=wangjing@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;
as well as URLs for NNTP newsgroup(s).