public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: philwh@gate.net
To: blinux-list@redhat.com
Subject: Re: talking terminals
Date: Tue, 22 Aug 2000 21:11:31 -0400	[thread overview]
Message-ID: <20000822211131.B340@lpwh.pwh.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0008220754340.513-100000@gondor.notarealdomain.org>; from cbrannon1979@earthlink.net on Tue, Aug 22, 2000 at 07:56:03AM -0700

I must say you are completely incorrect. I have installed linux
using a serial terminal dozens of times since 1994 when I started
with linux.
I have installed both slackware and redhat using a serial
terminal, the most recent last
friday afternoon when I installed
redhat 6.2 on my computer at work without any sighted help whatsoever.
just for anyone who wishes to know how,
at the boot prompt after booting the installation floppy from redhat,
type the following command to install using a 
serial terminal, or more acurately a serial console:
text console=ttyS0,9600n8
or in my case since i was impatient,
text console=ttyS0,115200n8

it worked without a problem.

phil

On Tue, Aug 22, 2000 at 07:56:03AM -0700, cbrannon1979@earthlink.net wrote:
> I was reading all the discussion about talking terminals yesterday.  The
> way I see it, they have a very big disadvantage to a screenreader for a
> blind person with a hardware synthesizer.  You need sighted help to install
> Linux with a talking terminal.  And IMNSHO, a sighted person reading a screen
> for me is a very poor substitute for speech output, especially if you're
> like me, and don't
> know anyone in your area who uses Linux.  I installed Zipspeak with absolutely
> zero sighted assistance.  And as far as I can tell, kernels built with
> Speakup can do this for full distributions, as well.  This would make
> Linux the only operating system that can be installed by someone who is blind
> without sighted help.  Maybe I could install DOS on my own, if I'd done it
> enough, but I wouldn't have the computer actually talking to me while I was
> installing.  And, with Speakup you get speech from bootup to power
> down.  Only thing that
> won't talk to you now is the BIOS, and there's supposedly a board you can get
> that'll send the BIOS messages out the serial port.    Compare this setup to
> Win-95, where speech isn't necessarily constant, even if you're booted and the 
> screenreader's active.  (JFW crashes so easy its sick.)
> But getting back to the topic of talking terminals. Anyone remember the
> old Apple II computer from the seventies?  That's what I started out
> on; and I seem to remember that the synthesizer for those was only about
> $150, or so.  Question is, if a blind person doesn't have a hardware
> synth, would it be possible to use an Apple II as a terminal under
> Linux?  You can still find them, once in a while, and like I said, the
> synth was cheap, even new.  I seem to remember them having a serial port,
> so I'd think they could be usable as talking terminals, for someone with
> limited funds who doesn't have, and can't afford a hardware synthesizer.
> Later.
> 
> 
> 
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list




  reply	other threads:[~ UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 cbrannon1979
 ` philwh [this message]
   ` Brent Harding
     ` philwh
       ` Brent Harding
         ` philwh
     [not found] <Pine.LNX.4.21.0008220754340.513-100000@gondor.notarealdoma in.org>
 ` Brent Harding
 ` Count Zero
   ` tyler
   ` Brent Harding
     ` A. R. Vener
       ` Brent Harding
     ` Count Zero

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=20000822211131.B340@lpwh.pwh.com \
    --to=philwh@gate.net \
    --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).