From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id 884261EF83B; Thu, 9 Oct 2014 16:29:56 -0400 (EDT) Received: from opera.rednote.net (opera.rednote.net [IPv6:2600:3c03::f03c:91ff:fe70:e783]) by befuddled.reisers.ca (Postfix) with ESMTPS id 3473F1EF83D for ; Thu, 9 Oct 2014 16:29:50 -0400 (EDT) Received: from opera.rednote.net (localhost [IPv6:::1]) by opera.rednote.net (8.14.8/8.14.7) with ESMTP id s99KTeUd012973 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 9 Oct 2014 20:29:40 GMT Received: (from janina@localhost) by opera.rednote.net (8.14.8/8.14.6/Submit) id s99KTe21012972; Thu, 9 Oct 2014 16:29:40 -0400 X-Authentication-Warning: opera.rednote.net: janina set sender to janina@rednote.net using -f Date: Thu, 9 Oct 2014 16:29:40 -0400 From: Janina Sajka To: Glenn , "Speakup is a screen review system for Linux." Subject: Re: a little sysadmin story Message-ID: <20141009202940.GO1044@opera.rednote.net> References: <86a956i23h.fsf@vibrator.pk5001z> <20141009125200.GI1044@opera.rednote.net> <86ppe1gyed.fsf@vibrator.pk5001z> <543691D1.9050000@tysdomain.com> <543693B5.9060601@tysdomain.com> <5436A145.30001@verizon.net> <478C3EC865774707826A4B0E156AE72B@your2c061f0461> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <478C3EC865774707826A4B0E156AE72B@your2c061f0461> X-Operating-System: Linux opera.rednote.net 3.16.3-200.fc20.x86_64 X-PGP-Key: http://rednote.net/JaninaSajka_gpg_key.html User-Agent: Mutt/1.5.23 (2014-03-12) 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: Thu, 09 Oct 2014 20:29:57 -0000 Glenn, are you talking about the Opticon? Didn't someone start remanufacturing that relatively recently? Glenn writes: > What we need is a piece of hardware that does OCR directly from the video > port. > It seems like that would be a relatively easy device to produce, given what > we have these days. > Glenn > ----- Original Message ----- > From: "Al Sten-Clanton" > To: ; "Speakup is a screen review system for Linux." > > Sent: Thursday, October 09, 2014 9:52 AM > Subject: Re: a little sysadmin story > > > First, I thank Janina for raising certain issues better than I could. > (I also thank others who've made valuable points from different angles.) > > Second, where is the equivalent code for kicking in the monitor when we > boot up? Shouldn't the aim be to treat our access technology in the > same or an equivalent way, to the degree possible? > > Al > > On 10/09/2014 09:55 AM, Littlefield, Tyler wrote: > > I also wanted to point out that most companies and organizations are a > > bit weird about installing anything. The fact that Speakup is in the > > kernel, but the entire idea of installing a special program which > > they're not sure of, be it screen reader or magnification bothers most > > people, so this isn't just an issue of Speakup possibly being better. > > There are reasons and there obviously is a need for speakup to get > > better, perhaps that means coming out of kernel space. But a sad story > > from once upon a time with a moral unrelated is not quite the point. > > On 10/9/2014 9:46 AM, Littlefield, Tyler wrote: > >> This whole story sounds like it needs another couple of bears to make > >> it all interesting. So speakup crashed the kernel. I've had issues, > >> but apart from known bugs I've never seen speakup panic the kernel all > >> the time. Speakup caused a system to crash? Perhaps. People should > >> also backup their work. > >> On 10/9/2014 9:34 AM, Deedra Waters wrote: > >>> Janina, > >>> > >>> speakup was the cause because when bossman came down to hook up a > >>> monitor and look, the panick messages had something to do with speakup. > >>> > >>> As for backing up their work, they were trying to fix their fuck-up to > >>> begin with. The initial problem wasn't with speakup. However when i was > >>> helping them debug it, speakup made the kernel panick and crash. > >>> > >>> Debian i dont think likes people with root access on their box to begin > >>> with, but i think they kind of didn't like speakup in their kernel to > >>> begin with. > >>> > >>> I suspect on the other hand that if speakup was a user-space app, it > >>> wouldn't have mattered to them so much. If a userspace program crashes > >>> it doesn't take down the whole box. When speakup does though, it takes > >>> down the whole box. > >>> > >>> > >> > >> > > > _______________________________________________ > 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 -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@asterisk.rednote.net Email: janina@rednote.net Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Protocols & Formats http://www.w3.org/wai/pf Indie UI http://www.w3.org/WAI/IndieUI/