From: Dave Mielke <Dave@mielke.cc>
To: Linux Kernel Mailing List
<linux-kernel%40vger.kernel.org@beta.private.mielke.cc>
Cc: Samuel Thibault <Samuel.Thibault@ens-lyon.org>
Subject: The regrettable demise of the TIOCSTI ioctl.
Date: Sat, 1 Apr 2023 02:25:22 -0400 [thread overview]
Message-ID: <ZCfOUSZ87LaBVjq7@beta.private.mielke.cc> (raw)
It seems that, starting in the 6.2 kernel (I think), there's a move underway to get rid of the TIOCSTI ioctl. The fact that the kernel configuration information says "provides no meaningful real-world utility any more" shows that the kernel developers seem to be unaware of an important subset of their users who absolutely depend on TIOCSTI.
By removing TIOCSTI, you have broken several users' *ability* to work at all with their current hardware!
The users I'm referring to are those who rely on their ability to work productively with braille devices. They use BRLTTY (see brltty.app). Most braille devices, these days, have braille keyboards. BRLTTY interprets what its users type on those braille keyboards, and uses TIOCSTI to inject those characters. Since I'm unaware of any adequate replacement for TIOCSTI, I'm asking (begging?) that this ioctl please be NOT removed.
Even disablign it isn't good because a blind user who relies on his/her braille keyboard won't be able to fix the problem by logging in and issuing the needed sysctl command (try imagining how you'd do that without your keyboard). We could distribute a brltty.conf sysctl.d file, but that isn't a great idea either given that, in
the end, it'd end up being run on all systems since BRLTTY is generally distributed.
Please understand that it simply isn't true at all that TIOCSTI has no practical use these days. It most certainly does!
Thanks for at least hearing me out.
--
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke | 2213 Fox Crescent | WebHome: http://Mielke.cc/
EMail: Dave@Mielke.cc | Ottawa, Ontario | Twitter: @Dave_Mielke
Phone: +1 613 726 0014 | Canada K2A 1H7 |
reply other threads:[~2023-04-01 7:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZCfOUSZ87LaBVjq7@beta.private.mielke.cc \
--to=dave@mielke.cc \
--cc=Samuel.Thibault@ens-lyon.org \
--cc=linux-kernel%40vger.kernel.org@beta.private.mielke.cc \
/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®