All of
 help / color / mirror / Atom feed
From: "Vyacheslav Yurkov" <>
To: Andrei Gherzan <>,
	openembedded <>
Subject: Re: [OE-core] [PATCH] overlayfs.bbclass: generate overlayfs mount units
Date: Wed, 9 Jun 2021 21:04:41 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Andrei,
Like you mentioned, it's application specific. The advantage of 
overlayfs here is that you preserve the data that was changed by user 
(in case of persistent storage), which of course would hide the data 
from rootfs, or your just see the defaults from rootfs if the data was 
not changed. With bind mounts you would need to copy default data first 
into your tmpfs/ext4 bind mount if you wanna have defaults.

> I was looking into something like this lately. There are actually two kinds of write access - volatile (tmpfs) and persistent (to disk). So my approach would have been to use bind mounts from a tmpfs/ext4 based on configuration per recipe. Is there any advantage to working with overlayfs in this case? The main idea is to have state that doesn't come from the ro part of the OS because otherwise, updates will be shadowed by the overlayfs. So I fail to see the advantage of using a set of overlayfs mounts instead of bind mounts. At least with bind mounts, it will always shadow the rootfs bits so you can catch early this case.
> Depending on your use case, most of the times, you'd want this "state" setup happening pre init (in initramfs, for example), especially if you want to handle persistent systemd logging or machine id, etc.

      reply	other threads:[~2021-06-09 19:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 14:21 [PATCH] overlayfs.bbclass: generate overlayfs mount units Vyacheslav Yurkov
2021-06-03 14:35 ` [OE-core] " Bruce Ashfield
2021-06-04 17:22   ` Vyacheslav Yurkov
2021-06-04 18:24     ` Bruce Ashfield
2021-06-04 20:20 ` Ayoub Zaki
2021-06-05  6:31   ` Vyacheslav Yurkov
2021-06-05  7:37 ` Adrian Freihofer
2021-06-05  9:28   ` Vyacheslav Yurkov
2021-06-09 13:56 ` Andrei Gherzan
2021-06-09 19:04   ` Vyacheslav Yurkov [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.