From: "John Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: My Views Regarding Kernel Vs. Userspace
Date: Fri, 10 Aug 2007 11:59:27 -0500 [thread overview]
Message-ID: <02b901c7db6f$cfe06170$4ba65c90@vv507j> (raw)
In-Reply-To: <E1IJXOh-00087Y-Im@gene3.ait.iastate.edu>
From: "Gene Collins" <collins@gene3.ait.iastate.edu>
> Hi Ace! No Speakup in user space wouldn't have been able to help you
> solve your problem. In my not so humble opinion, those who are whining
> about speakup not needing to be in user space are just full of it and
> don't have the technical knowledge to express such an opinion. Most of
> them still think from a Windows mind set where they are used to being
> told, "no, we can't give you access to that."
That is not true. If anything, the opposite is closer to the truth. Most of
the people who think speakup could reside entirely in user space are so
knowledgable that they don't need to see boot messages. There are other ways
of figuring things out like examining the logs.
My opinion is that while it may be theoretically possible to get along
without access to boot messages, it's not practical. Blind people already
have enough trouble competing for jobs and not having access to boot
messages would be a significant new hurdle to over come.
Also, to be fair, I don't think anybody on this list argued that blind
people don't really need access to boot messages except in terms of
suggesting alternatives. At least this is what I think the intention was.
And, after all, that is useful information to have.
prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
ace
` Kenny Hitt
` Gene Collins
` John Heim [this message]
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='02b901c7db6f$cfe06170$4ba65c90@vv507j' \
--to=jheim@math.wisc.edu \
--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).