From: "Sina Bahram" <sbahram@nc.rr.com>
To: "'Speakup is a screen review system for Linux.'"
<speakup@braille.uwo.ca>
Subject: RE: gentoo dropping speakup support
Date: Sun, 17 Jun 2007 17:18:38 -0400 [thread overview]
Message-ID: <002501c7b125$1326ba80$ca01a8c0@quark> (raw)
In-Reply-To: <BAY141-DAV12A1A443C7CCD911E43F4D8F1C0@phx.gbl>
In the spirit of open discovery, I will point out that I've never had any
problems with the accessibility of the ssh installation of gentoo.
I have sighted colleagues who never once have to use a monitor hooked up to
the target machine during a gentoo install, and only use ssh to accomplish
this, and I've done the same.
Take care,
Sina
-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Zachary Kline
Sent: Sunday, June 17, 2007 4:37 PM
To: Speakup is a screen review system for Linux.
Subject: Re: gentoo dropping speakup support
Hello,
I would like to formally state that I disapprove of this removal. It is
only thanks to Speakup being included in the default kernel that we are able
to perform unassisted installations of Gentoo at all. This seems as if it
would be a great step backwards.
Might I suggest that we attempt to contact the Speakup mailing list and
developers for information on this issue?
Thank you,
Zachary Kline.
----- Original Message -----
From: "William Hubbs" <williamh@gentoo.org>
To: <speakup@braille.uwo.ca>
Sent: Sunday, June 17, 2007 1:00 PM
Subject: gentoo dropping speakup support
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> All,
>
> because of this bug [1], gentoo linux will be dropping support for speakup
> in its official kernels starting at 2.6.22.
>
> [1] http://bugs.gentoo.org/show_bug.cgi?id=177794
>
> Is there any possibility at all that speakup could be moved into user
> space as the bug suggests? I feel that if we can go into user space this
> will b a better approach.
>
> Thanks,
>
> - --
> William Hubbs
> gentoo accessibility team lead
> williamh@gentoo.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
>
> iD8DBQFGdZLWblQW9DDEZTgRAsCOAJoD/roDmHTKu7ji8qTXZ2eoX47T1ACeIivJ
> j/qhb9Z6KNpfitEvr7Onrug=
> =mpb2
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
William Hubbs
` Zachary Kline
` Sina Bahram [this message]
` Gaijin
` Tom Moore
` Michael Whapples
` Deedra Waters
` Travis Siegel
` Zachary Kline
` C.M. Brannon
` Doug Sutherland
` Deedra Waters
` Travis Siegel
` Gaijin
` Doug Sutherland
` Luke Yelavich
` Jim Grimsby Jr.
` Doug Sutherland
` Gaijin
` Doug Sutherland
` Michael Whapples
` Lorenzo Taylor
` Samuel Thibault
` Travis Siegel
` Gaijin
` John covici
` Luke Yelavich
Keith Hinton
` James Homuth
` Gaijin
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='002501c7b125$1326ba80$ca01a8c0@quark' \
--to=sbahram@nc.rr.com \
--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).