public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: kestrell <aeryadne@world.std.com>
To: Blinux <blinux-list@redhat.com>
Subject: Re: FAQ Suggestions/Perceptions from a Novice--worth 2 cents.
Date: Fri, 10 Nov 2000 11:57:43 -0500 (EST)	[thread overview]
Message-ID: <Pine.SGI.3.95.1001110114021.21667C-100000@world.std.com> (raw)
In-Reply-To: <200011100040.QAA06810@sugarbeet.ultimanet.com>


I think Gary offered a great manifesto for the newbie blind linux user. I
also have the greatest respect for the other members of this list, and the
amazing things they do, but also feel, as a true newbie even after a year
of reading not only this list but the newbie list and the redhat list and
a couple of others, along with reading about a couple hundred documents
and websites, that there is a huge gap in the information needed for a
beginner to actually begin.

I use linx also, not because I don't have an alternative--I have a windows
95 machine, which I also taught myself, along with 3.1 and before that
DOS--but because it is far quicker and cleaner than the graphical
browsers, which is also the opinion of many sighted geeks I've met. I have
the resource of knowing many sighted gurus who could help with linux, but
they are not familiar with my screen reader, or using speech technology
for all aps, and getting a linux box up and running has been a year-long
project. I taught myself what I need to know to be functionally literate
in UNIX and HTML, and am learning PERL, but the linux docs have been
particularly dense as far as where a beginner cac crash-course in learning
linux. 

The reason I am writing this email, which I am trying not to let too much
of my own frustration seep into, is that the reason I got interested in
linux is that I felt it would be an incredible freeing OS for the blind
computer user. I still believe that, but I also believe there is a
desperate need to make the learning process more accessible.  Less
esoteric documentation with step-by-step  lists would not be, I think, a
matter of "dumbing down" for ppl who are already using complicated speech
and braille technology, but might prove to convert many computer users who
want to have an alternative to the mainstream hardware and software but
are intimidated by what seems a lot of geekspeak. 

Lastly, I would like to reiterate that I admire all the ppl who have put
so much time and energy into the linux movement, and none of my comments
are meant to detract from them or what has already been done.

k





  parent reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Gary Wynn
 ` Rick Hayner
 ` Luke Davis
 ` Jude DaShiell
   ` Gary Wynn
     ` Andor Demarteau
       ` Jude DaShiell
 ` kestrell [this message]
 ` Yvonne Smith

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.SGI.3.95.1001110114021.21667C-100000@world.std.com \
    --to=aeryadne@world.std.com \
    --cc=blinux-list@redhat.com \
    /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).