Re: [PATCH RESEND 00/62] initrd: remove classic initrd support
Askar Safin <[email protected]>
| Newsgroups | gmane.linux.ports.sparc,gmane.linux.drivers.devicetree,gmane.linux.kernel.initramfs,gmane.linux.acpi.devel,gmane.linux.ports.alpha,gmane.linux.kernel.api,gmane.linux.kernel.cross-arch,gmane.linux.ports.arm.kernel,gmane.linux.block,gmane.linux.documentation,gmane.linux.kernel.efi,gmane.comp.file-systems.ext4,gmane.linux.file-systems,gmane.linux.ports.hexagon,gmane.linux.kernel,gmane.linux.ports.mips,gmane.linux.ports.parisc,gmane.linux.ports.riscv,gmane.linux.ports.sh.devel,gmane.linux.kernel.arc,gmane.linux.uml.devel,gmane.linux.ports.ppc64.devel |
|---|---|
| Message-ID | <CAPnZJGAp-wG+9wDmmisfpxvFbRtXkG-RipAuZe=fi1BWy-3G-Q@mail.gmail.com> |
On Mon, Sep 22, 2025 at 5:29 PM Nicolas Schichan <[email protected]> wrote: > > Then in September 2026 I will fully remove initrd. > > Is there a way to find some kind of middle ground here ? I still plan to fully remove initrd in September 2026. Maintainers will decide whether they will merge my patchset. You may try to convince them. > I can send a patch for that but first I need to sort out my SMTP > issues from the other day. If you still have mail issues, consider applying for @linux.dev email, they are free for Linux devs ( https://linux.dev/ ). Also, I just tried to test whether your use case is still supported in mainline (i. e. uncompressed initrd with root=/dev/ram0). It turned out that on modern kernels you need to enable recently introduced CONFIG_BLK_DEV_WRITE_MOUNTED to make this work. So, make sure to enable this when upgrading kernel. -- Askar Safin