lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080120093744.eklhad@comcast.net>
Date:	Wed, 20 Feb 2008 09:37:44 -0500
From:	Karl Dahlke <eklhad@...cast.net>
To:	linux-kernel@...r.kernel.org
CC:	sam@...nborg.org, jengelh@...putergmbh.de, randy.dunlap@...cle.com,
	Valdis.Kletnieks@...edu
Subject: adapter, what's in a name

First, my mail client, edbrowse.sourceforge.net,
doesn't have a reply all function.
Never needed it.
Guess I better implement it.   :-)
Should probably take me a couple days of spare time,
if I can find a couple days of spare time;
and I'm sure other users will want it.
Meantime, I pulled the emails out of the headers and pasted them in.
Hope that reasonably works.

As was pointed out, it is difficult to place an accessibility adapter
under one particular subsystem.
Mine takes over the screen, to be a screen reader,
and it captures tty output, because it is more than just a screen reader,
it buffers output, exactly as generated, for my review.
And it uses the serial port to send text to my external synthesizer,
but sometimes it uses an on-board synth, and all this would be useless
if it didn't intercept keystrokes to read lines,
words, letters, and so on.
And I want to enhance it to do the same thing for usb keyboards.
It touches many subsystems, and doesn't belong in any one of them over the others.
It actually changes the computer, in a fundamental way.
That's why I suggested a new directory drivers/accessibility.

Here is another reason.
When you run make config, these accessibility adapters belong together logically.
CONFIG_ACCESSIBILITY
help:
Say Y here if you need to adapt this computer for a disabled user.
Saying Y will not increase the size of your kernel,
it will only offer various modules that you can use to
magnify the screen, modify the keyboard, send text to a speech synthesizer,
and so on.
If you don't anticipate any disabled users, it is ok to say N.

Most people will say N,
or perhaps M, building everything as modules in case they are needed some day.
I don't know, it just makes sense to me I guess.
If we can go along with this,
I can write a patch for drivers/Makefile and drivers/Kconfig
that would put this in place.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ