From: Deedra Waters <dmwaters@gentoo.org>
To: speakup@braille.uwo.ca
Subject: Re: gentoo dropping speakup support (fwd)
Date: Sun, 17 Jun 2007 22:08:23 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0706172204200.6924@monster> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I understand the concerns that both of you as well as others have. I
spent 2 hours this morning arguing on both sides of this argument with
the amd64 lead for gentoo as well as other people. Here's the bottom
line.
The kernel folks have said that "speakup's code sucks" the gentoo kernel
folks have said the same thing in the bug. The bottom line for them is
the code sucks there's less and less reason to support speakup, and now
it's breaking on more and more arches. You 2 at least seem to think that
if you sit back and wait, sooner or later it's going to get fixed. The
reality is that from what i can tell speakup has 1 main coder, kirk. I'm
sure that kirk has other things besides speakup he's working on, While
there may be a fix, it's not going to be a quick fix and the reality is
that the only fix that has been found for this problem is to bring part
of it out into user space, see comment 8 i think it is on the bug. So
the reality is it's being slowly dragged into user space anyway, you
might as well do it right and make it decent code in the process so that
distros can start supporting it again.
On Sun, 17 Jun 2007, Zachary Kline wrote:
> Date: Sun, 17 Jun 2007 19:30:52 -0700
> From: Zachary Kline <Z_kline@hotmail.com>
> Reply-To: Speakup is a screen review system for Linux.
> <speakup@braille.uwo.ca>
> To: Speakup is a screen review system for Linux. <speakup@braille.uwo.ca>
> Subject: Re: gentoo dropping speakup support
>
> Hello,
> I agree. It is simply not going to work if it is forced into user
> space. The fact I have a supported hardware synthesizer means that I'm able
> to read everything as it comes up, debug things that don't, etc. I couldn't
> go back to even software speech, because with software speech you don't get
> that, and the reason is user space. Speech-dispatcher and speechd-up and
> such are userspace programs, and so if the machine doesn't get to a point
> where they can launch we're dead in the water. I for one am going to be
> attending a university in the fall, and don't look forward to having to ask
> a sighted person to tell me what the kernel panic says or how the FSCK is
> coming.
> Please, if possible reconsider this decision. It is extremely unproductive
> in the longterm. Any problems Speakup may have building with 2.6.22 will be
> fixed in due course.
> Thank you,
> Zachary Kline.
>
> ----- Original Message -----
> From: "Travis Siegel" <tsiegel@softcon.com>
> To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
> Sent: Sunday, June 17, 2007 7:20 PM
> Subject: Re: gentoo dropping speakup support
>
>
> >I have to strongly disagree here as relates to bootable messages.
> > Speakup makes linux the *only* os where blind users can see the boot
> > up as it happens. Even dos can't do that, and I have more than once
> > managed to fix a machine with linux because of the speakup capability
> > to speak *all* bootup messages. Dumping them to a logfile, booting
> > with a live cd, then reading the log may work for users who are
> > advanced enough to figure it out, (or are lucky enough to have simple
> > enough configurations this can be done) but by doing so, you're
> > basically saying that those who want to troubleshoot their own boxes
> > w/o sighted assistance are sol.
> > And, if the hd is bad, then your logging isn't going to work anyhow.
> > Not to mention, this isn't a process that can be done w/o sighted
> > assistance.
> > While I'm more of a slackware user than anything else, having speakup
> > work out of the box is something I've enjoyed almost since speakup
> > was released, and I for one would be extremely sorry (not to mention
> > irritated at the lack of access it would mean) to have it removed
> > into user space. There's already programs for user space access
> > (yasr anyone) and while those work for normal usage, they aren't
> > usable for troubleshooting and/or fixing a broken machine. I've been
> > doing my own technical support since 1990 (or thereabouts) and having
> > this capability now removed would be the equivalent of moving to
> > vista before any screen readers were specifically targeted to it.
> > Sure, you could use the system, but you're not going to get anywhere
> > near the full use out of your system you'd otherwise get.
Deedra Waters - Gentoo accessibility and amd64 -
dmwaters@gentoo.org
Gentoo linux: http://www.gentoo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFGdfcnU5AGPOTGNc8RAtU/AJoDWWvMqJmhkLSanU6w4SxbSHLGWACfVV0W
RjtdEqnDQbb0As0tGK+kZ3g=
=r+dK
-----END PGP SIGNATURE-----
next reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Deedra Waters [this message]
-- strict thread matches above, loose matches on Subject: below --
Deedra Waters
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0706172204200.6924@monster \
--to=dmwaters@gentoo.org \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).