All of lore.kernel.org
 help / color / mirror / Atom feed
From: Terry Duncan <terry.s.duncan@linux.intel.com>
To: "Alexander A. Filippov" <a.filippov@yadro.com>, openbmc@lists.ozlabs.org
Subject: Re: Alternative to the filesystem overlay
Date: Tue, 20 Aug 2019 17:56:32 -0700	[thread overview]
Message-ID: <791b2ada-c35d-c394-b7f0-fd3f92abeed2@linux.intel.com> (raw)
In-Reply-To: <20190816090955.GA15986@bbwork.lan>

On 8/16/19 2:09 AM, Alexander A. Filippov wrote:

> Most of these issues can be solved by the simple shell scripts. We could modify
> the initramfs/init scenario to exec these scripts at the moment when ROFS and
> RWFS have mounted but are not combined to OVERLAY yet.
> 
> Of course, this method doesn't prevent an occurrence of any new issues of this
> type but brings an easy way to solve them.
> 
> --
> Regards,
> Alexander
> 

Possibly the overlay FS is not expecting and does not support the ROFS 
to change as it does when a new build adds a file to an existing 
directory. When this occurs an overlayed file in the same directory 
could cause corruption in the directory. Are you suggesting scripts that 
detect a change to the underlying FS and attempt to patch the overlay?

Thanks,
Terry

  parent reply	other threads:[~2019-08-21  0:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 17:38 Alternative to the filesystem overlay Adriana Kobylak
2019-08-15 18:43 ` Andrew Geissler
2019-08-16  9:09 ` Alexander A. Filippov
2019-08-20 18:00   ` William Kennington
2019-08-21  7:28     ` Alexander A. Filippov
2019-08-21  0:56   ` Terry Duncan [this message]
2019-08-21  7:09     ` 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=791b2ada-c35d-c394-b7f0-fd3f92abeed2@linux.intel.com \
    --to=terry.s.duncan@linux.intel.com \
    --cc=a.filippov@yadro.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 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.