Date: Wed, 6 Dec 2006 00:50:07 +0100
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: linux-kernel@vger.kernel.org
Cc: mrkiko.rs@gmail.com, dave@mielke.cc, sebastien.hinderer@loria.fr
Subject: SAK and screen readers
Message-ID: <20061205235006.GA8273@bouh.residence.ens-lyon.fr>
Mail-Followup-To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	linux-kernel@vger.kernel.org, mrkiko.rs@gmail.com, dave@mielke.cc,
	sebastien.hinderer@loria.fr
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.12-2006-07-14
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1233
Lines: 39

Hi,

BrlTTY is a screen reader: it is a deamon run as root on machines used
by blind users for getting the content of the screen via braille or
speech.

BrlTTY, like other screen readers (susebl, yasr, ...) needs to open
/dev/tty0 for performing various actions, namely:

- VT_ACTIVATE
- GIO_UNISCRNMAP
- GIO_UNIMAP
- KDFONTOP
- VT_GETHIFONTMASK
- VT_GETSTATE
- KDGETMODE
- TIOCSTI
- KDGKBMETA
- KDGKBMODE

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...

Some of the actions above are not directly related to the current VT, so
these could use a generic VT handle ; but at least KD* and TIOCSTI need
to be directed to the current VT, so brltty really needs to have an fd
on the current VT tty.

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)

Samuel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/