From: Jonathan Busby <jdb2@pobox.com>
To: linux-unionfs@vger.kernel.org
Subject: Fwd: Re: How to access "upper" directory of overlayfs programatically
Date: Thu, 13 Sep 2018 13:54:45 -0500 [thread overview]
Message-ID: <5B9AB275.7010408@pobox.com> (raw)
In-Reply-To: <5B9AA5EC.8050600@pobox.com>
Oops... forgot that I was replying to you personally :)
-------- Forwarded Message --------
Subject: Re: How to access "upper" directory of overlayfs programatically
Date: Thu, 13 Sep 2018 13:01:16 -0500
From: Jonathan Busby <jdb2@pobox.com>
To: Amir Goldstein <amir73il@gmail.com>
On 09/13/2018 12:33 PM, Jonathan Busby wrote:
>
>
> On 09/12/2018 02:48 PM, Amir Goldstein wrote:
>> [changing over to overlayfs list]
>
> Thanks for this! :D I had been searching for an overlayfs mailing list
> but it seems I overlooked unionfs.
>
>>
>> On Wed, Sep 12, 2018 at 8:52 PM Jonathan Busby <jdb2@pobox.com> wrote:
>>>
>>> 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.
>>>
>>
>> I don't think the programmable API you think of exists, but maybe
>> you can get access to upper dir as admin user.
>>
>> Please share the init scripts responsible for the mounts at live CD boot
>> and the content of /proc/self/mountinfo
>
> The contents of /proc/self/mountinfo are can be found here :
>
> https://pastebin.com/raw/9uQdJ66w
>
> The init scripts responsible for the live CD mounts can be found here :
>
> https://www.dropbox.com/s/j4zqsn8avxrv6zf/initrd-scripts.tar.gz?dl=0
>
> Thanks,
>
> Jonathan
>
>>
>> Thanks,
>> Amir.
>>
I forgot to mention that the init scripts that handle mounting the
overlayfs chroot are located in the /scripts/casper directory, and the
main script is just called "casper".
Regards,
Jonathan
next parent reply other threads:[~2018-09-14 0:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5B9AA5EC.8050600@pobox.com>
2018-09-13 18:54 ` Jonathan Busby [this message]
2018-09-13 19:18 ` Re: How to access "upper" directory of overlayfs programatically Amir Goldstein
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=5B9AB275.7010408@pobox.com \
--to=jdb2@pobox.com \
--cc=linux-unionfs@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 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.