linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Busby <jdb2@pobox.com>
To: linux-fsdevel@vger.kernel.org
Subject: How to access "upper" directory of overlayfs programatically
Date: Wed, 12 Sep 2018 12:51:12 -0500	[thread overview]
Message-ID: <5B995210.1030104@pobox.com> (raw)

Hello. I'm new to this list and I don't know if this is the right forum 
for my question, but, I've asked this same question on many forums and 
never received an answer -- please don't flame me.

I have a Debian based Linux live system which is running out of RAM and 
was booted without the "persistent" boot option, so the capser-rw 
filesystem was never created.

I wish to gain access to the "upper" directory of the overlayfs 
filesystem in the casper init scripts initramfs "/cow/upper" filesystem 
so that I may programatically save the filesystem, hopefully without 
having to re-implement cp.

I know how to commit the changes of a Debian based live CD session to a 
storage device, but only if the live session in question was booted with 
the "persistent" option.

I've looked at the overlayfs source code but I still can't figure out 
how to accomplish what I want.

I'm sorry if this is  stupid question -- hopefully it's not.

Thank you,

Jonathan

                 reply	other threads:[~2018-09-12 22:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5B995210.1030104@pobox.com \
    --to=jdb2@pobox.com \
    --cc=linux-fsdevel@vger.kernel.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).