From: Lennart Poettering <lennart@poettering.net>
To: Eric Curtin <ecurtin@redhat.com>
Cc: systemd-devel@lists.freedesktop.org, initramfs@vger.kernel.org,
Yariv Rachmani <yrachman@redhat.com>,
Stephen Smoogen <ssmoogen@redhat.com>,
Douglas Landgraf <dlandgra@redhat.com>
Subject: Re: [RFC] initoverlayfs - a scalable initial filesystem
Date: Tue, 12 Dec 2023 18:37:54 +0100 [thread overview]
Message-ID: <ZXiacj2XYYRvaZ9A@gardel-login> (raw)
In-Reply-To: <CAOgh=FxHsOpDA7izWEd=eA886op17gdTFJPebxnvEwNOmWEyKQ@mail.gmail.com>
On Mo, 11.12.23 12:48, Eric Curtin (ecurtin@redhat.com) wrote:
> Sort of yes, but preferably using that __initramfs_start /
> initrd_start buffer as is without copying any bytes anywhere else and
> without teaching the bootloaders to do things.
>
> The "memmap=" approach you suggested sounds like what we are thinking,
> but do you think we could do this without teaching bootloaders to do
> new things?
Well, in a standard UEFI world it would suffice to teach the memmap=
logic to the stub that is glued in front of the kernel. For example,
make sd-stub find the erofs initrd in the UKI, then trivially
synthesize a memmap= switch and append it to the kernel command line.
but of course, you don't believe in UEFI or good boot loaders, so you
kinda dug your own grave here...
(The main reason why sd-stub doesn't actually support erofs-initrds,
is that sd-stub also generates initrd cpios on the fly, to pass
credentials and system extension images to the kernel, and you can't
really mix erofs and cpio initrds into one)
Lennart
--
Lennart Poettering, Berlin
next prev parent reply other threads:[~2023-12-12 17:37 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 17:59 [RFC] initoverlayfs - a scalable initial filesystem 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2023-12-18 21:59 Askar Safin
[not found] ` <CAOgh=FyA94-7YqGpsAqVQjadegRusoAvRhD=t-ipzVWN0CiJRQ@mail.gmail.com>
2023-12-18 23:31 ` Askar Safin
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=ZXiacj2XYYRvaZ9A@gardel-login \
--to=lennart@poettering.net \
--cc=dlandgra@redhat.com \
--cc=ecurtin@redhat.com \
--cc=initramfs@vger.kernel.org \
--cc=ssmoogen@redhat.com \
--cc=systemd-devel@lists.freedesktop.org \
--cc=yrachman@redhat.com \
/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