From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Adam Saponara <as@php.net>
Cc: Jiri Slaby <jirislaby@kernel.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] vt: Add boot param for setting default vt console
Date: Thu, 12 Mar 2026 15:29:39 +0100 [thread overview]
Message-ID: <2026031235-catcher-amazingly-cfed@gregkh> (raw)
In-Reply-To: <20260301214804.283484-1-as@php.net>
On Sun, Mar 01, 2026 at 04:48:04PM -0500, Adam Saponara wrote:
> Presently the default console is hard-coded to vt1.
>
> The param allows for setting a different default. The param defaults to 0
> (vt1), preserving the current behavior. It is clamped by the constants
> `(MIN|MAX)_NR_CONSOLES`. If set `>= MIN`, `con_init` will initialize that
> vt as well (a couple extra kilobytes heap for the `vc_data` and
> `vc_screenbuf` structs).
>
> Without this feature, users achieve the same effect with an init
> script[0][1][2][3]. This works but requires an extra `chvt(1)` which can
> race with user interaction and flicker the screen at login.
What user interaction races? I'm loath to change this as I've not seen
any bug reports for this. What changed to cause this issue?
And this is for the "odd" systems that want a graphical login, BUT still
want to default to the console? That's a very odd configuration, and I
think that we should just stick with the fix that we have for those that
want to do this as adding more boot parameters that we need to support
for forever feels like a bad idea.
sorry,
greg k-h
prev parent reply other threads:[~2026-03-12 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 21:48 [PATCH] vt: Add boot param for setting default vt console Adam Saponara
2026-03-12 14:29 ` Greg Kroah-Hartman [this message]
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=2026031235-catcher-amazingly-cfed@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=as@php.net \
--cc=jirislaby@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.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