All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander A. Filippov" <a.filippov@yadro.com>
To: Adriana Kobylak <anoo@linux.ibm.com>
Cc: openbmc <openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org>,
	openbmc@lists.ozlabs.org, Anton Kachalov <rnouse@google.com>,
	"Alexander A. Filippov" <a.filippov@yadro.com>
Subject: Re: Headsup: Alternative to the filesystem overlay
Date: Tue, 22 Sep 2020 11:06:27 +0300	[thread overview]
Message-ID: <20200922080627.GA16274@bbwork.lan> (raw)
In-Reply-To: <3f491d1ca08a5480af9d4555121da090@linux.vnet.ibm.com>

On Mon, Sep 21, 2020 at 02:42:49PM -0500, Adriana Kobylak wrote:
> On 2020-09-21 09:33, Alexander A. Filippov wrote:
> > I solved the problem with a difference of the user groups set during
> > firmware
> > upgrade by installing a systemd service which starts on the first BMC
> > boot after
> > upgrade and merges groups from RWFS and new ROFS.
> > 
> > This recipe is stored in our internal repo only, but I can share it if
> > it is
> > interesting to someone.
> 
> I'd be interested, if you would share it. Thanks!
> 

Here is it.
  https://gerrit.openbmc-project.xyz/c/openbmc/meta-yadro/+/36650

But it looks I was wrong. In fact, the script just adds missing groups from a 
predefined list instead of the merging files from RWFS and new ROFS.

--
Regards,
Alexander

  reply	other threads:[~2020-09-22  8:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21  9:52 Headsup: Alternative to the filesystem overlay Anton Kachalov
2020-09-21 14:33 ` Alexander A. Filippov
2020-09-21 19:42   ` Adriana Kobylak
2020-09-21 19:42     ` Adriana Kobylak
2020-09-22  8:06     ` Alexander A. Filippov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-09-21  9:49 Anton Kachalov

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=20200922080627.GA16274@bbwork.lan \
    --to=a.filippov@yadro.com \
    --cc=anoo@linux.ibm.com \
    --cc=openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=rnouse@google.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 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.