mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jocelyn Falempe <jfalempe@redhat.com>
To: Nicolas Pitre <nico@fluxnic.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
	Calixte Pernot <calixte.pernot@grenoble-inp.org>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] vt: Add enable module parameter
Date: Mon, 26 Jan 2026 23:59:41 +0100	[thread overview]
Message-ID: <5707632d-3fd8-4a5e-9273-dd7d48d5b438@redhat.com> (raw)
In-Reply-To: <28snspp2-3912-rs5o-04s0-1648504sq90r@syhkavp.arg>

On 26/01/2026 18:24, Nicolas Pitre wrote:
> On Mon, 26 Jan 2026, Greg Kroah-Hartman wrote:
> 
>> On Mon, Jan 26, 2026 at 02:05:36PM +0100, Jocelyn Falempe wrote:
>>> I think that one of the reason, is that if you switch off VT, of course some
>>> users will complain, as it has a lot of implications.
>>
>> Again, that's a distro's policy decision to make, don't force the kernel
>> to support a wishy-washy distro's decision :)
> 
> As a daily VT user for my primary Linux interface due to accessibility
> needs, I'm baffled by the idea of distributions removing this support.
> 
> Of course this has lots of implications. For many users with
> disabilities, VT is not optional - it's the only _fully_ usable
> interface.
> 
> Consider this my official objection. Just don't do that.

That patch is clearly for people like you, that will need more time to 
adapt their tools and workflow to a VT-less system.
It's also less practical to develop alternative, if you need to rebuild 
your kernel to disable VT.
Regarding accessibility, I don't see any technical reason why a VT-less 
system would be less efficient that what is currently available with VT.

-- 

Jocelyn

> 
> 
> Nicolas
> 


  reply	other threads:[~2026-01-26 22:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26  9:21 Jocelyn Falempe
2026-01-26  9:33 ` Greg Kroah-Hartman
2026-01-26  9:43   ` Jocelyn Falempe
2026-01-26 10:20     ` Greg Kroah-Hartman
2026-01-26 10:30       ` Greg Kroah-Hartman
2026-01-26 10:49         ` Jocelyn Falempe
2026-01-26 10:57           ` Greg Kroah-Hartman
2026-01-26 10:48       ` Jocelyn Falempe
2026-01-26 10:59         ` Greg Kroah-Hartman
2026-01-26 12:26           ` Jocelyn Falempe
2026-01-26 12:46             ` Greg Kroah-Hartman
2026-01-26 13:05               ` Jocelyn Falempe
2026-01-26 14:36                 ` Greg Kroah-Hartman
2026-01-26 17:24                   ` Nicolas Pitre
2026-01-26 22:59                     ` Jocelyn Falempe [this message]
2026-01-26 23:00                   ` Jocelyn Falempe

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=5707632d-3fd8-4a5e-9273-dd7d48d5b438@redhat.com \
    --to=jfalempe@redhat.com \
    --cc=calixte.pernot@grenoble-inp.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=nico@fluxnic.net \
    /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

all inboxes | Powered by JetHome®