From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Alejandro Hernandez Samaniego <alhe@linux.microsoft.com>,
Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] initramfs-framework: Add overlayroot module
Date: Thu, 27 Jan 2022 19:31:55 +0100 [thread overview]
Message-ID: <7e42c014-6ccc-7323-ddea-ec8181711b7d@gmail.com> (raw)
In-Reply-To: <3954c194-7d7f-9dd2-a1f2-54b088396009@linux.microsoft.com>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
On 26.01.2022 19:09, Alejandro Hernandez Samaniego wrote:
> Oops! completely forgot!, I'll add it.
>
> This is loosely based on the overlay-etc.bbclass the difference is that
> the class only works for overlaying /etc and it doesnt require an
> initramfs, but, while its possible to tinker it in such a way that it
> overlays /, its not possible to access the original (RO) / after booting the
> system, this is the reason why this has to be done from initramfs and why
> this doesnt patch the overlay-etc.bbclass instead.
>
> I believe Ubuntu has this feature, coming from the cloud-initramfs
> package, functionally it should be similar although no code was borrowed
> from there.
>
> I'll add a note about the overlay-etc class though.
I missed this part when I answered to your first email this morning. I
generally against expanding the scope of overlayfs (i.e. using it for
the whole / ), because it creates a bigger migration effort when you
need to update the files on a persistent partition. I see the only
difference in your code is that you provide access to original lower
layer fs. Why would you want to do that?
Thanks,
Vyacheslav
[-- Attachment #2: Type: text/html, Size: 1574 bytes --]
next prev parent reply other threads:[~2022-01-27 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 7:22 [PATCH] initramfs-framework: Add overlayroot module Alejandro Enedino Hernandez Samaniego
2022-01-26 14:11 ` [OE-core] " Bruce Ashfield
2022-01-26 18:09 ` Alejandro Hernandez
2022-01-27 18:31 ` Vyacheslav Yurkov [this message]
2022-01-27 7:30 ` Vyacheslav Yurkov
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=7e42c014-6ccc-7323-ddea-ec8181711b7d@gmail.com \
--to=uvv.mail@gmail.com \
--cc=alhe@linux.microsoft.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.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 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.