From: Askar Safin <safinaskar@gmail.com>
To: ecurtin@redhat.com
Cc: initramfs@vger.kernel.org, systemd-devel@lists.freedesktop.org
Subject: Re: [RFC] initoverlayfs - a scalable initial filesystem
Date: Tue, 19 Dec 2023 00:59:11 +0300 [thread overview]
Message-ID: <CAPnZJGCPd7Z4PYkNf8ES1t0ZBE=p2Lny6HKzhqNmyfq5UGw0+g@mail.gmail.com> (raw)
Hi. Unfortunately, this is not clear enough from
https://github.com/containers/initoverlayfs how exactly the
second-stage early filesystem is mounted. So, please, add that
information to README. Let me describe how I understand this.
First, init program from (small) first-stage early filesystem mounts
boot/ESP partition, where second-stage early filesystem image (i. e.
erofs) is located. Then that init program mounts that erofs image.
Without copying the whole erofs image into memory. In other words, if
some part of erofs image is not accessed, then not only it is not
uncompressed, it even is not loaded from disk to memory at all. Is my
understanding correct?
--
Askar Safin
next reply other threads:[~2023-12-18 21:59 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 21:59 Askar Safin [this message]
[not found] ` <CAOgh=FyA94-7YqGpsAqVQjadegRusoAvRhD=t-ipzVWN0CiJRQ@mail.gmail.com>
2023-12-18 23:31 ` [RFC] initoverlayfs - a scalable initial filesystem Askar Safin
-- strict thread matches above, loose matches on Subject: below --
2023-12-08 17:59 Eric Curtin
2023-12-09 12:46 ` Luca Boccassi
2023-12-09 14:42 ` Eric Curtin
2023-12-09 14:56 ` Andrei Borzenkov
2023-12-09 15:07 ` Eric Curtin
2023-12-09 15:22 ` Daan De Meyer
2023-12-09 15:46 ` Eric Curtin
2023-12-09 17:19 ` Luca Boccassi
2023-12-09 17:24 ` Eric Curtin
2023-12-09 17:46 ` Luca Boccassi
2023-12-09 17:57 ` Eric Curtin
2023-12-09 18:11 ` Luca Boccassi
2023-12-09 18:26 ` Eric Curtin
2023-12-11 9:57 ` Lennart Poettering
2023-12-11 10:07 ` Lennart Poettering
2023-12-11 11:20 ` Eric Curtin
2023-12-11 11:28 ` Eric Curtin
2023-12-11 11:42 ` Eric Curtin
2023-12-11 11:58 ` Lennart Poettering
2023-12-11 11:51 ` Lennart Poettering
2023-12-11 12:48 ` Eric Curtin
2023-12-11 12:52 ` Eric Curtin
2023-12-12 17:37 ` Lennart Poettering
2023-12-12 17:40 ` Lennart Poettering
2023-12-12 19:05 ` Demi Marie Obenour
2023-12-11 16:28 ` Demi Marie Obenour
2023-12-11 17:03 ` Eric Curtin
2023-12-11 17:46 ` Demi Marie Obenour
2023-12-12 18:00 ` Lennart Poettering
2023-12-12 20:34 ` Nils Kattenbeck
2023-12-12 20:48 ` Eric Curtin
2023-12-12 21:02 ` Lennart Poettering
2023-12-12 22:01 ` Nils Kattenbeck
2023-12-13 9:03 ` Lennart Poettering
2023-12-14 1:17 ` Nils Kattenbeck
2023-12-16 14:34 ` Lennart Poettering
2023-12-11 17:33 ` Neal Gompa
2023-12-11 20:15 ` Luca Boccassi
2023-12-11 20:43 ` Demi Marie Obenour
2023-12-11 20:58 ` Luca Boccassi
2023-12-11 21:20 ` Demi Marie Obenour
2023-12-11 21:45 ` Luca Boccassi
2023-12-12 3:47 ` Paul Menzel
2023-12-12 3:56 ` Paul Menzel
2023-12-12 15:26 ` Paul Menzel
2023-12-11 21:24 ` Eric Curtin
2023-12-12 17:50 ` Lennart Poettering
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='CAPnZJGCPd7Z4PYkNf8ES1t0ZBE=p2Lny6HKzhqNmyfq5UGw0+g@mail.gmail.com' \
--to=safinaskar@gmail.com \
--cc=ecurtin@redhat.com \
--cc=initramfs@vger.kernel.org \
--cc=systemd-devel@lists.freedesktop.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 read-only IMAP folder(s) and NNTP newsgroup(s).