[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <198e7535627.e16dd6a239997.462747272790524454@zohomail.com>
Date: Tue, 26 Aug 2025 21:00:55 +0400
From: Askar Safin <safinaskar@...omail.com>
To: "Byron Stanoszek" <gandalf@...ds.org>
Cc: "Christoph Hellwig" <hch@....de>, "gregkh" <gregkh@...uxfoundation.org>,
"julian.stecklina" <julian.stecklina@...erus-technology.de>,
"linux-fsdevel" <linux-fsdevel@...r.kernel.org>,
"linux-kernel" <linux-kernel@...r.kernel.org>,
"rafael" <rafael@...nel.org>,
"torvalds" <torvalds@...ux-foundation.org>,
"viro" <viro@...iv.linux.org.uk>,
"Gao Xiang" <hsiangkao@...ux.alibaba.com>,
"Thomas Weißschuh" <thomas.weissschuh@...utronix.de>
Subject: Re: [PATCH] initrd: support erofs as initrd
---- On Tue, 26 Aug 2025 18:21:50 +0400 Byron Stanoszek <gandalf@...ds.org> wrote ---
> Well, this makes me a little sad. I run several hundred embedded systems out in
> the world, and I use a combination of initrd and initramfs for booting. These
> systems operate entirely in ramdisk form.
Put your squashfs to initramfs. Then do everything as you did before.
I. e. in your /sbin/init copy that squashfs to ramdisk (or, better, loop-mount it), etc.
If I understand you correctly, this will work after removing of initrd.
I will not remove ramdisks. I will remove initramdisks, i. e.
special mounting logic in kernel, which automatically loads and mounts
ramdisk at boot.
--
Askar Safin
https://types.pl/@safinaskar
Powered by blists - more mailing lists