From: Anton Kachalov <gmouse@google.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Headsup: Alternative to the filesystem overlay
Date: Mon, 21 Sep 2020 11:49:00 +0200 [thread overview]
Message-ID: <CADVsX8-wnxytDGqY_RLAxq3cEzAMoK_bJRnuVa5=-YtPth6guA@mail.gmail.com> (raw)
Message-ID: <20200921094900.kv4ggnNnwkxHU71qUSawcR6XGrrmHBWxC_Tbk9jgFE4@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 365 bytes --]
There was a topic year ago:
https://lists.ozlabs.org/pipermail/openbmc/2019-August/017611.html
Is anyone currently working in this direction? Any thoughts on possible
approaches?
We're going to revisit this and discuss possible solutions.
One point to mention is: introduce an image feature flag that would enable
rootfs overlay, i.e. for development purposes.
[-- Attachment #2: Type: text/html, Size: 572 bytes --]
next reply other threads:[~2020-09-21 9:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 9:49 Anton Kachalov [this message]
2020-09-21 9:49 ` Headsup: Alternative to the filesystem overlay Anton Kachalov
2020-09-21 9:52 Anton Kachalov
2020-09-21 14:33 ` Alexander A. Filippov
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
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-wnxytDGqY_RLAxq3cEzAMoK_bJRnuVa5=-YtPth6guA@mail.gmail.com' \
--to=gmouse@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).