public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Nikhil Nair <nn201@cus.cam.ac.uk>
To: blinux-list@redhat.com, linux-access@ssv1.union.utah.edu
Subject: Debian installation - interested?
Date: Wed, 27 Nov 1996 20:10:34 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.3.95.961127192354.5187A-100000@amasis.trin.cam.ac.uk> (raw)

Hi all,

I was talking with Bruce Perens (Debian Project Leader) a while back - he
had bought himself a DecTalk, and was toying with the idea of
speech-friendly installation.  As a blind Debian developer myself, I'm
interested in accessibility issues, and would like to see Debian become
the first distribution to provide installation disks with accessibility
add-ons, as opposed to these being provided by third-parties.

Having said all that, I'm a soft Braille user, and don't have a DecTalk,
so have no feel for the usefulness of Bruce's idea.  I'm a bit cautious,
because if the installation disk wrote directly to the DecTalk, that would
presumably interfere with any screen-reader (if there was one ...).

So what I'd like to know from you all is: what do you think would be most
useful?  Presumably many people don't have DecTalks, but do many have
second machines to use as serial terminals?  If having a serial terminal
installation procedure would be useful, should there be a choice of which
com port to use?  How should this be selected - would separate rootdisks
be needed, or would a simple choice on the main keyboard (say pressing 1
or 2) be OK?

Cheers,

Nikhil.

--
Nikhil Nair
Trinity College, Cambridge, England
Tel.: +44 1223 368353
Email: nn201@cus.cam.ac.uk
       nnair@debian.org




             reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Nikhil Nair [this message]
 ` Nicolas Pitre
   ` Graham Swallow

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.3.95.961127192354.5187A-100000@amasis.trin.cam.ac.uk \
    --to=nn201@cus.cam.ac.uk \
    --cc=blinux-list@redhat.com \
    --cc=linux-access@ssv1.union.utah.edu \
    /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).