From: Rob Landley <rob@landley.net>
To: David Disseldorp <ddiss@suse.de>, Askar Safin <safinaskar@gmail.com>
Cc: linux-fsdevel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
initramfs@vger.kernel.org, Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>,
patches@lists.linux.dev
Subject: Re: [PATCH 1/2] init: ensure that /dev/console is (nearly) always available in initramfs
Date: Sun, 22 Feb 2026 19:27:50 -0600 [thread overview]
Message-ID: <6d34c95a-a2ea-46a4-b491-45e7cb86049b@landley.net> (raw)
In-Reply-To: <20260220105913.4b62e124.ddiss@suse.de>
On 2/19/26 17:59, David Disseldorp wrote:
>> This problem can be solved by using gen_init_cpio.
It used to work, then they broke it. (See below.)
>> But I think that proper solution is to ensure that /dev/console
>> is always available, no matter what. This is quality-of-implementation
>> feature. This will reduce number of possible failure modes. And
>> this will make easier for developers to get early boot right.
>> (Early boot issues are very hard to debug.)
>
> I'd prefer not to go down this path:
> - I think it's reasonable to expect that users who override the default
> internal initramfs know what they're doing WRT /dev/console creation.
> - initramfs can be made up of concatenated cpio archives, so tools which
> insist on using GNU cpio and run into mknod EPERM issues could append
> the nodes via gen_init_cpio, while continuing to use GNU cpio for
> everything else.
Who said anything about gnu? Busybox has a cpio, toybox has a cpio...
once upon a time it was a posix command, removed from the standard for
the same reason tar was removed, and that was just as widely ignored.
It's an archive format. There are tools that create that archive format
from a directory.
The kernel itself had a fairly generic one one built-in, which you
_could_ use to create cpio archives with /dev/console as a regular
user... until the kernel guys decided to break it. I carried a patch to
fix that for a little while myself:
https://landley.net/bin/mkroot/0.8.10/linux-patches/0011-gen_init_cpio-regression.patch
But I just got tired of fighting lkml.
> Thanks, David
Rob
next prev parent reply other threads:[~2026-02-23 2:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 21:03 [PATCH 0/2] init: ensure that /dev/console and /dev/null are (nearly) always available in initramfs Askar Safin
2026-02-19 21:03 ` [PATCH 1/2] init: ensure that /dev/console is " Askar Safin
2026-02-19 23:59 ` David Disseldorp
2026-02-20 19:11 ` Askar Safin
2026-02-23 1:19 ` David Disseldorp
2026-02-23 21:41 ` Askar Safin
2026-02-23 1:27 ` Rob Landley [this message]
2026-02-23 2:33 ` David Disseldorp
2026-02-23 16:11 ` Rob Landley
2026-02-23 17:34 ` Askar Safin
2026-02-23 19:45 ` Rob Landley
2026-02-23 23:04 ` Askar Safin
2026-02-19 21:03 ` [PATCH 2/2] init: ensure that /dev/null " Askar Safin
2026-02-20 0:26 ` David Disseldorp
2026-02-21 0:16 ` Askar Safin
2026-02-23 1:15 ` Rob Landley
2026-02-23 21:18 ` Askar Safin
2026-02-23 0:17 ` [PATCH 0/2] init: ensure that /dev/console and /dev/null are " Rob Landley
2026-02-23 20:58 ` Askar Safin
2026-02-24 19:02 ` Rob Landley
2026-03-07 3:22 ` Askar Safin
2026-03-10 12:51 ` Rob Landley
2026-03-23 3:47 ` 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=6d34c95a-a2ea-46a4-b491-45e7cb86049b@landley.net \
--to=rob@landley.net \
--cc=brauner@kernel.org \
--cc=ddiss@suse.de \
--cc=initramfs@vger.kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=safinaskar@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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