openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Kachalov <rnouse@google.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: /etc/migration.d
Date: Wed, 14 Oct 2020 20:47:57 +0200	[thread overview]
Message-ID: <CADVsX8_eYXAtGMgoe9LEKRtaf0ufdn0BJA+Fn8J9xpAKnTDStQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

With moving from root-only environment to unprivileged users' space, we
need to ensure a smooth transition. To achieve that we need a mechanism for
one-shot per-package scripts that would take care of migration. That's not
only about groups & owners, but a general approach. It's similar to
firstboot, but has a different purpose.

I'm going to prototype a robust / naive solution to start a service before
everything else in the system with a condition (non-empty /etc/migration.d)
and iterate through all files. Each script has to run at list with "set -e"
to bail out on failures. If the script succeeded -- it will be removed.

The tricky part is: what if the script fails? Keep it, ignore the failure
and proceed with others and then boot the system? Or proceed other scripts
as well and then enter some "failure state"?

[-- Attachment #2: Type: text/html, Size: 937 bytes --]

             reply	other threads:[~2020-10-14 18:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 18:47 Anton Kachalov [this message]
2020-10-16 16:50 ` /etc/migration.d Ed Tanous
2020-10-16 17:10   ` /etc/migration.d Anton Kachalov
2020-10-16 20:25 ` /etc/migration.d Patrick Williams
2020-10-16 21:01   ` /etc/migration.d Anton Kachalov
2020-10-20 11:22     ` /etc/migration.d Anton Kachalov
2020-10-22 16:19       ` /etc/migration.d Anton Kachalov
2020-10-22 19:51         ` /etc/migration.d Ed Tanous
     [not found]         ` <CAH2-KxA9cX49Kfp4SbRPdY1wRt3u8T7o-hUfkBORZNZ9yUXoSg@mail.gmail.com>
2020-10-22 20:39           ` [gbmc-team] /etc/migration.d Anton Kachalov
2020-10-22 20:45             ` Ed Tanous

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=CADVsX8_eYXAtGMgoe9LEKRtaf0ufdn0BJA+Fn8J9xpAKnTDStQ@mail.gmail.com \
    --to=rnouse@google.com \
    --cc=openbmc@lists.ozlabs.org \
    /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).