public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Tuttle <linux-kernel@ttuttle.net>
To: linux-kernel@vger.kernel.org
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	mrkiko.rs@gmail.com, dave@mielke.cc, sebastien.hinderer@loria.fr
Subject: Re: SAK and screen readers
Date: Tue, 05 Dec 2006 19:26:37 -0500	[thread overview]
Message-ID: <20061206002637.GA6237@lion> (raw)
In-Reply-To: <20061205235006.GA8273@bouh.residence.ens-lyon.fr>

[-- Attachment #1: Type: text/plain, Size: 840 bytes --]

On December 05 at 18:50 EST, Samuel Thibault hastily scribbled:
> The problem comes when using SAK: brltty gets killed because it owns an
> fd on /dev/tty0.  This is a problem since the blind user then just can't
> use her computer any more...
> <snip>
> Could there be a solution for brltty yet not being killed by SAK? (like
> letting brltty just nicely close his fd for the current VT, and then
> re-open it later)

How about this?

brltty launches a child process that opens the VT and pipes data back
and forth to the parent process via pipes or fifos.

When the SAK is pressed, the child process will die, and the parent
process will simply relaunch it.

It seems like any solution that involves the kernel not killing brltty
will compromise the (admittedly rudimentary) security that the SAK
offers.

Hope this helps,

Thomas Tuttle

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-12-06  0:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-05 23:50 SAK and screen readers Samuel Thibault
2006-12-06  0:26 ` Thomas Tuttle [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=20061206002637.GA6237@lion \
    --to=linux-kernel@ttuttle.net \
    --cc=dave@mielke.cc \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrkiko.rs@gmail.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=sebastien.hinderer@loria.fr \
    /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