From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id A6C4B1EF7BC; Wed, 8 Oct 2014 18:06:07 -0400 (EDT) Received: from mta1.math.wisc.edu (mta1.math.wisc.edu [144.92.166.23]) by befuddled.reisers.ca (Postfix) with ESMTP id 6AEB31EF7AF for ; Wed, 8 Oct 2014 18:06:05 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mta1.math.wisc.edu (Postfix) with ESMTP id EF2BD49CE99; Wed, 8 Oct 2014 17:06:04 -0500 (CDT) Received: from mta1.math.wisc.edu ([127.0.0.1]) by localhost (mta1.math.wisc.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZgVkl5sGTHiF; Wed, 8 Oct 2014 17:06:04 -0500 (CDT) Received: from mta1.math.wisc.edu (localhost [127.0.0.1]) by mta1.math.wisc.edu (Postfix) with ESMTP id 7D51049CE91; Wed, 8 Oct 2014 17:06:04 -0500 (CDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mta1.math.wisc.edu X-Spam-Level: X-Spam-Status: No, score=-101.0 required=6.5 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=disabled version=3.3.2 Received: from mailhost.math.wisc.edu (erdos.math.wisc.edu [144.92.166.25]) by mta1.math.wisc.edu (Postfix) with ESMTP; Wed, 8 Oct 2014 17:06:04 -0500 (CDT) Received: from [144.92.166.19] (vv507j.math.wisc.edu [144.92.166.19]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mailhost.math.wisc.edu (Postfix) with ESMTPS id 79F3142021F; Wed, 8 Oct 2014 17:06:04 -0500 (CDT) Message-ID: <5435B544.2090907@math.wisc.edu> Date: Wed, 08 Oct 2014 17:05:56 -0500 From: "John G. Heim" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.8.1 MIME-Version: 1.0 To: Glenn , "Speakup is a screen review system for Linux." Subject: Re: the push to get rid of CONFIG_VT in the kernel and the future of Speakup References: <87zjd64c16.fsf@mushroom.PK5001Z> <543593E4.5040400@gmail.com> <54359B9E.10203@verizon.net> <5435AE9F.1090306@math.wisc.edu> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 X-BeenThere: speakup@linux-speakup.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Oct 2014 22:06:08 -0000 You can switch to a character user interface and use speakup even after starting the graphical user interface. But as I said, I don't consider that a key part of the linux accessibility infrastructure. Again, I understand some people prefer to use the character user interface full time. I could understand if the linux big shots said that was going to have to go away. But doing something that would make it impossible for blind people to have access to the boot messages that sighted people get -- that is unacceptable. Well, like somebody else said, we may have to accept it. But that would be very bad. On 10/08/14 16:50, Glenn wrote: > Isn't SpeakUp used in the terminal after booting to a GUI? > ----- Original Message ----- > From: "John G. Heim" > To: "Speakup is a screen review system for Linux." > > Sent: Wednesday, October 08, 2014 4:37 PM > Subject: Re: the push to get rid of CONFIG_VT in the kernel and the future > of Speakup > > > Yeah, if you're a linux sysadmin, hardware speech is not some luxury you > can do without. It's not a matter of convenience, it's a matter of > possible or not possible. > > I know there are still some people who use speakup as their primary > screen reader. But that user base has to be dwindling. In my opinion, > the only reason that speakup remains a key part of the linux > infrastructure is that it allows blind systems admins to get speech > during boot. I think it would be understandible if they said you blind > people will just have to use the GUI if not for the fact that if you > are a sys admin, you need those boot messages. > > On 10/08/14 15:16, Al Sten-Clanton wrote: >> My knowledge of this business is minimal, but I thought that one >> advantage of the current approach, if you can use a hardware speech >> synthesizer, is that you can get at least some of the boot-up >> messages--not as early as sighted folks get them, but well before >> software speech can kick in. If this is true, wouldn't the proposed >> change be a very builty-in reduction in non-visual access? >> >> Al >> >> On 10/08/2014 03:43 PM, Kyle wrote: >>> It does appear to me that something like this will force more of Speakup >>> into userspace. However, unlike others, I'm not entirely opposed to the >>> idea of Speakup leaving the kernel, and I think it can only be a good >>> thing, especially on newer machines, where dedicated serial ports are >>> all but obsolete, and software in userspace can take better advantage of >>> things like Pulseaudio and libusb, meaning more extensive software and >>> hardware speech support. For example, there would no longer be a need >>> for kernel modules to control speech synthesizers, and there would no >>> longer be a need to have external userspace connectors such as Espeakup, >>> as the entire Speakup screen reader could be moved into userspace, and >>> anything that interfaces with a speech synthesizer could be either >>> internal or could be a library that interfaces with a speech API like >>> speech-dispatcher or others. Even better, if Speakup is moved entirely >>> into userspace, it could give rise to far better access to consoles on >>> *BSD and other Unix operating systems, as the code could be far more >>> portable between operating systems when it doesn't have to be tied into >>> a specific kernel. Just my $0.02 BSD. That's Bahamian dollars lol. >>> ~Kyle >>> http://kyle.tk/ >>> >> _______________________________________________ >> Speakup mailing list >> Speakup@linux-speakup.org >> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > _______________________________________________ > Speakup mailing list > Speakup@linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > > _______________________________________________ > Speakup mailing list > Speakup@linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup >