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:
pgpJc2n2IsABz.pgp
Description: PGP signature
- References:
- SAK and screen readers
- From: Samuel Thibault <[email protected]>
- SAK and screen readers
- Prev by Date: [PATCH][Trivial] scsi: Fix 'unused variable' warning in scsi.c
- Next by Date: [PATCH] let WARN_ON() output the condition
- Previous by thread: SAK and screen readers
- Next by thread: [PATCH][Trivial] scsi: Fix 'unused variable' warning in scsi.c
- Index(es):
 |