red hat system almost talking

red hat system almost talking

[Jude DaShiell]

When I boot now, I hear lilo, then I hear boot, then I hear loading linux,
then I hear the at sign, and all the rest is silence.  If I hit ackspace I
don't hear the beep so this thing is still coming up in gnome mode.  I
managed to log in using gnome and get such changes I have managed using
exec >/dev/ttyS0 2>&1 on a line by itself.
I got Bill's speakup.kmap.gz file stored and loaded into
/etc/sysconfig/keyboard too.  How do I disable gnome permanently so it
doesn't break the log in anymore?


Jude <jdashiel@shellworld.net>

Re: red hat system almost talking

[Mike Gorse]

You should be able to get back to a virtual console by hitting
ctrl-alt-f1.  You may be able to disable Gnome by telling init to start
using a different runlevel.  You should have a line in /etc/inittab like
id:2:initdefault
where the 2 indicates to start with runlevel 2.  The runlevel is often
used to determine which initialization scripts should be run, and x may
not be started with a lower runlevel.  I am not sure how RedHat works,
though, so someone can correct me...

--Michael Gorse / ICQ:22583968 / http://mgorse.home.dhs.org

On Sat, 8 Sep 2001, Jude DaShiell wrote:

> When I boot now, I hear lilo, then I hear boot, then I hear loading linux,
> then I hear the at sign, and all the rest is silence.  If I hit ackspace I
> don't hear the beep so this thing is still coming up in gnome mode.  I
> managed to log in using gnome and get such changes I have managed using
> exec >/dev/ttyS0 2>&1 on a line by itself.
> I got Bill's speakup.kmap.gz file stored and loaded into
> /etc/sysconfig/keyboard too.  How do I disable gnome permanently so it
> doesn't break the log in anymore?
>
>
> Jude <jdashiel@shellworld.net>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>

Re: red hat system almost talking: question related to comments

[Cheryl Homiak]

Your description brings up a question I have.  A few times I have booted
and ended up at something for the login tha said "Pam unix" and something
about opening a session.  At this point I can't read the screen or seem to
do anything with my keyboard and my keyboard doesn't echo, but I get
announcements occasionally about chron stipping for mail or something like
that.  One time when this happened I know it was because i accidentally
had X booting up at start, but this has happened once or twice without me
having any idea how I got there.  What is a "pam unix session" and how
does one end up there without planning it?

Cheryl

Re: red hat system almost talking: question related to comments

[Jude DaShiell]

Don't know what a pam unix session is, haven't experienced one of those
yet.  Another change I did to /etc/inittab was to remove line 57 since it
appeared to be starting up x.  I suppose I could replace that last line
with something to start up bash.  Only thing is that seems to be coming up
already so I don't know.


Jude <jdashiel@shellworld.net>

Re: red hat system almost talking: question related to comments

[Janina Sajka]

This situation you describe isn't exactly making sense to me. But, I would 
offer the following suggestions:

There should be no guessing game about whether you boot with appropriate 
settings or not. Take care of that:

1.)	Get rid of the default /boot/message file. Of course, if you make 
the remaining changes below, it won't matter, but do it anyway. Replace it 
with some simple text like "Welcome to Cheryl's Linux Computer" it doesn't 
matter -- just get rid of the graphic that Redhat puts up by default. PS: 
It's smart to get some ^7 chars in there to ring your bell, as it were;

2.)	Edit lilo.conf to start linux with your speech synth talking if 
you haven't done this already;

3.)	Edit /etc/inittab to make runlevel 3 your default runlevel. Look 
for a line that says:

id:5:initdefault:

and change it to read:

id:3:initdefault:

As for what pam is, it stands for pluggable authentication modules. You 
can usually answer such questions for yourself, though, by using the man 
pages -- man, as in manual. So, you could type:

man pam

Now, a couple of other key basics:

Let me suggest the following man command:

man bash

Also, let me point you to /usr/doc where there's all kind of 
documentation. Pay particular attention to the HOWTO directory there. 
That's your gold mine. Inside there, there are a couple of HOWTOs 
particularly for beginners. Again, I recommend the bash HOWTO, and 
probably the HOWTO for Windows and DOS users.

Have you gotten to mail and web browsing? Most folks start out, and some 
never leave, pine and lynx for these, respectively. In each, be sure to 
configure them to track the cursor. It'll make you a lot happier.

 On 
Sat, 8 Sep 2001, Cheryl Homiak wrote:

> Your description brings up a question I have.  A few times I have booted
> and ended up at something for the login tha said "Pam unix" and something
> about opening a session.  At this point I can't read the screen or seem to
> do anything with my keyboard and my keyboard doesn't echo, but I get
> announcements occasionally about chron stipping for mail or something like
> that.  One time when this happened I know it was because i accidentally
> had X booting up at start, but this has happened once or twice without me
> having any idea how I got there.  What is a "pam unix session" and how
> does one end up there without planning it?
> 
> Cheryl
> 
> 
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
> 

-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org

Will electronic books surpass print books? Read our white paper,
Surpassing Gutenberg, at http://www.afb.org/ebook.asp

Download a free sample Digital Talking Book edition of Martin Luther
King Jr's inspiring "I Have A Dream" speech at
http://www.afb.org/mlkweb.asp

Learn how to make accessible software at
http://www.afb.org/accessapp.asp

Re: red hat system almost talking: question related to comments

[Cheryl Homiak]

Excuse me, but I don't understand the nature of this reply.  First of all,
I'm not using Redhat; I'm using debian.  Secondly, I know perfectly well
what pam is, what bash is, what man pages are, and how to read howtos, and
I do all these things.  I am sure, however, that your pointers would be
helpful to somebody who did not know these things and use these tools.  I
was simply asking a question about an isolated occurrence of ending up at
some kind of "pam unix session".  I know Janina's advice is well-meant,
but while my question may have been an indication of ignorance of a
particular circumstance, it wasn't indicative ot ignorance of tools and
documentation or failure to use them.

Cheryl

Re: red hat system almost talking: question related to comments

[S. Massy]

Sounds to me as though you were somewhere where logs where being
spewed out. Do you have your logs redirected to a tty? In such case
you might just have ended up on that VC.

Also, if you're using Debian unstable, there's been times where the
cron package was misconfigured and it was outputting to STDERR instead
of logging properly, if it happened just once it might have been
because of that.

On Mon, 10 Sep 2001, Cheryl Homiak <chomiak@shellworld.net> wrote:

> Excuse me, but I don't understand the nature of this reply.  First of all,
> I'm not using Redhat; I'm using debian.  Secondly, I know perfectly well
> what pam is, what bash is, what man pages are, and how to read howtos, and
> I do all these things.  I am sure, however, that your pointers would be
> helpful to somebody who did not know these things and use these tools.  I
> was simply asking a question about an isolated occurrence of ending up at
> some kind of "pam unix session".  I know Janina's advice is well-meant,
> but while my question may have been an indication of ignorance of a
> particular circumstance, it wasn't indicative ot ignorance of tools and
> documentation or failure to use them.
> 
> Cheryl
> 
> 
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list

Re: red hat system almost talking

[L. C. Robinson]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 4054 bytes --]

On Sat, 8 Sep 2001, Jude DaShiell wrote:

> then I hear the at sign, and all the rest is silence.  If I hit ackspace I
> don't hear the beep so this thing is still coming up in gnome mode.  I

Gnome isn't really relevant here, it's the X11 (X-windows) system
that underlies it.  X is the graphical mode of linux, and you
want to directly boot into text mode.  That is controlled by
runlevel, in /etc/inittab, or on the boot command line.  The
runlevels are explained in the commentary in /etc/inittab at the
top.  X is runlevel 5.  Text mode with networking (so you can
use the internet), is 3.  So the next time you boot linux, you can
just add a 3, surrounded by white space, after your kernel name.

Then make a safety copy of /etc/inittab (the system won't boot if
it gets scrambled, unless you boot with the "emergency" or "-b"
boot parameter into a very limited, stupid system state, where a
sighted user could make repairs (speech probably wouldn't work,
except for experts):

cp /etc/inittab /etc/inittab.save

You should find that the first non-comment line says:

id:5:initdefault:

You just change the 5 to 3:

id:3:initdefault:

After that, runlevel 3, which RedHat (and most everyone else)
configures as textmode, will be the default init state, as the
initdefault keyword suggests, and the system will have be told
specifically to boot into another level if you want anything else.

You can also change system runlevels using the telinit program,
without rebooting.

Even when graphical X is active, textmode is always active on
another virtual console, at the same time, which, as others have
pointed out, can be reached with a key combination (Ctrl-Alt-F1).
X is probably running on virtual console 7 (Alt-F7, from text
mode, the Ctrl is not needed except in X).  RedHat has text
mode login prompts running on the first 6 virtual terminals,
(Alt-F1 through Alt-F6) so X takes the next available one.

Note that even if speech is installed, it won't work if you go
directly to init 5 (graphical mode), until you shift to a text
virtual screen, as discussed.

For the silence, you could add something like the following to
one of the system startup files, probably at the end of
/etc/rc.d/rc.local

play /usr/share/sounds/startup2.wav

# In case sound isn't working, simply add:
echo -e "\a"  # \a is the bell character
sleep 1  # pause 1 second
echo -e "\a"
sleep 1
echo -e "\a"
# repeat as desired

# You could also try (for the first serial port, if you have a
# synth connected there):
echo "System is booted, and speech is active." > /dev/ttyS0

I have included the above in a working script attached, as
/etc/rc.d/boot.notice.audio
Complete installation, configuration, and other
instructions are included in the script commentary.

There is also stuff in the script to automatically switch you to
text mode if your system comes up in the GUI.

I wonder if you couldn't use the RedHat kickstart upgrade scheme
to script the automated installation of speech packages, and
their proper configuration.  I know I could do it, except I don't
know any of the specifics for particular speech hardware, and
can't test it.  I wrote in my contribution to the blinux-FAQ that
kickstart wasn't for beginners, but after reading how difficult
interactive installation really can be for listers here, I have
revised my view.  Maybe kickstart would be an easier way, for
many, if not most users.  If things didn't go right, one could
just tweak the script a bit, and try again, and it should be very
fast, with no output to slow it down.  Has anyone tried this?
See the chapter in the RH reference guide on kickstart for
details, and the HOWTO, plus the sample kickstart config file in
the doc dir on the CD for examples.

LCR

-- 
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid

People buy MicroShaft for compatibility, but get incompatibility and
instability instead.  This is award winning "innovation".  Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html

[-- Attachment #2: /etc/rc.d/boot.notice.audio --]
[-- Type: TEXT/PLAIN, Size: 2672 bytes --]

#! /bin/sh
# /etc/rc.d/boot.notice.audio
# Give audio notice of completed bootup

# INSTALL instructions:
# Read all the commentary in this file before using, and configure as necessary.
# Install this script as: 
# /etc/rc.d/boot.notice.audio
# and set the permissions on this script by doing:
# chmod 755 /etc/rc.d/boot.notice.audio

# Run it from /etc/rc.d/rc.local or equivalent file for your distribution,
# by adding this to the end:
# /etc/rc.d/boot.notice.audio

# This script will self install (for RedHat systems) if you run it as:
# sh this_file install
# You have to be "root" to do this.
# This will run it from rc.local

# Alternatively, if you want to have it run directly from your inittab, do:
# sh this_file install inittab
# That would probably work for any distribution.

# Installation command block: 
if [ "$1" = install ]; then 
   set -x
   grep boot.notice.audio /etc/rc.d/rc.local /etc/inittab && exit 1
   cp $0 /etc/rc.d/boot.notice.audio
   chmod 755 /etc/rc.d/boot.notice.audio
   if [ "$2" != inittab ]; then 
      echo "/etc/rc.d/boot.notice.audio" >> /etc/rc.d/rc.local 
   else
      cp /etc/inittab /etc/inittab.save # for safety
      echo "au:2345c:once:/etc/rc.d/boot.notice.audio" >> /etc/inittab 
      echo "Test this installation by running:"
      echo "telinit c"
   fi
   echo "Installation complete"
   exit
fi

# Licensed under the GPL (GNU public license: that means it's free, with No
# warrantee whatsoever).
# Send suggestions for improvements to lcr@onewest.net
# Tell me if you want one for shutdown, too. (just try putting this at
# end of the halt script, eg, /etc/rc.d/init.d/halt, for starters)


# Begin useful script:

set `/sbin/runlevel`
if [ X$2 = X5 ] ; then
   # echo "We are in runlevel $2, so X is active." 
   # Change to virtual text terminal one after a suitable pause to allow X to get
   # through shifting you to that (X) console:
   (
      # Wait done in a backgound subshell to allow us to continue.
      # sleep 7 + 20 seconds, as necessary:
      sleep 7
      sleep 20
      # Change to the first virtual terminal:
      chvt 1 
   ) &
fi

# In case sound isn't working:
echo -e "\a\c"  # \a is the bell character
sleep 1  # pause 1 second
echo -e "\a\c"
sleep 1
echo -e "\a\c"
# repeat as desired

play /usr/share/sounds/startup2.wav

# You could also try (for the first serial port, if you have a
# synth connected there):
# Let me know if this works (I can't test it).
# echo "System is booted, and speech is active." > /dev/ttyS0
# 2nd port:
# echo "System is booted, and speech is active." > /dev/ttyS1

Re: red hat system almost talking

[Jude DaShiell]

Interesting, run level was originally at 3 and couldn't get speech for
login prompt and beyond.  Had to use exec >/dev/ttyS0 2>&1 to get enough
speech to edit files.


Jude <jdashiel@shellworld.net>

Re: red hat system almost talking

[L. C. Robinson]

On Sun, 9 Sep 2001, Jude DaShiell wrote:

> Interesting, run level was originally at 3 and couldn't get speech for
> login prompt and beyond.  Had to use exec >/dev/ttyS0 2>&1 to get enough
> speech to edit files.

Runlevel 3 is still right.  Your redirection of IO  to the serial
port is a kludgy workaround for not having configured a getty
(login prompt and serial terminal support) for your serial port.
Normal installs never do this for you, because it's impossible
for the distribution vendor to predict what you will have or need
on your serial ports, except for a mouse, which is normally where
you have your synth.

It seems like there was some stuff in the FAQ about how to set up
a serial terminal (which is essentially what your synth is acting
as in this situation).  This can be tricky, because there are
hundreds of different serial terminals out there.  Here are some
old sample lines from my inittab (no longer used):

# t2:345:respawn:/sbin/getty -r1 ttyS1 DT9600 vt320-k311
# t2:345:respawn:/sbin/getty -r1 ttyS1 DT19200 vt100
# t3:2345:respawn:/sbin/getty -r1 ttyS0 ttyS_9600 wyse50
# t4:345:respawn:/sbin/getty -r1 ttyS4 wyse85_384 vt200

# A matching custom line from /etc/gettydefs:
wyse85_384# B38400 CS8 CLOCAL CRTSCTS # B38400 SANE -ISTRIP CLOCAL CRTSCTS #\7@L\nLogin: #wyse85_384

The next to last (or possibly last) entry in each getty line in
inittab is really a reference to a tag on a configuration line in
the /etc/gettydefs file.  Note the custom login prompt, which
includes a '\7', for the bell character (which may not be audible
-- had to use mgetty for that, but things improve).

Stock sample lines from default gettydefs (running at 9600 and 19200 baud):

# 9600 baud Dumb Terminal entry
DT9600# B9600 CS8 CLOCAL # B9600 SANE -ISTRIP CLOCAL #@S login: #DT9600

# 19200 fixed baud Dumb Terminal entry
DT19200# B19200 CS8 CLOCAL # B19200 SANE -ISTRIP CLOCAL #@S login: #DT19200

If the stock DT19200 line was suitable for you, you could
simply add a line to your inittab, after the stock mingetty
lines, like this (or use the more pessimistic 9600 baud
entry):

t0:345:respawn:/sbin/getty -r1 ttyS0 DT19200

If I recall correctly, I added the "-r1" to eliminate the
possibility of automatic terminal to getty chatter (nasty to
diagnose), but you then have to hit return once before you get a
login prompt.

You will also need to set the terminal type for your particular
hardware, so as to eliminate funny terminal escape sequences in your
output, in your .bashrc:

TERM=vt100
export TERM

for a vt100 terminal (change as necessary -- search /etc/termcap
for a terminal entry label appropriate to your synth).  You will
see that I also used an extra (last) field in my custom getty
lines for such a label (sets it even earlier, but might get
changed in /etc/profile).

Someone with the same synth could probably tell you more
specifically what to put in your config lines.

LCR

-- 
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid

Re: red hat system almost talking

[Jude DaShiell]

Okay, this may work.  I found out I was using the red hat distribution
kernel since it had porky near the top of it for a descriptor string for
where it was compiled.  I got some help from Bill over the phone and
downloaded his version of vmlinuz-2.2.16-22 and tried updating the kernel.
This download was done with ncftpget and unfortunately turned out to be
corrupted.  Maybe we can get brick numbers for all files and do downloads
in future and compare brick numbers.  This doesn't guarrantee a perfect
file download, but does make it more likely.  I tried a coupld other
things and managed to trash /boot.  So it's reinstall time again but this
time should be easier.

Jude <jdashiel@shellworld.net>

Re: red hat system almost talking

[Janina Sajka]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 474 bytes --]

On Sun, 9 Sep 2001, L. C. Robinson wrote:

> unless you boot with the "emergency" or "-b"
> boot parameter into a very limited, stupid system state, where a
> sighted user could make repairs (speech probably wouldn't work,
> except for experts):
> 
I've never used -b, but -s or 1, certainly talks quite nicely as long as 
one passes the correct speakup params as well.

Since speakup is in the kernel, it loads any time the kernel loads. It's 
actually inside the kernel.


[-- Attachment #2: /etc/rc.d/boot.notice.audio --]
[-- Type: TEXT/PLAIN, Size: 2672 bytes --]

#! /bin/sh
# /etc/rc.d/boot.notice.audio
# Give audio notice of completed bootup

# INSTALL instructions:
# Read all the commentary in this file before using, and configure as necessary.
# Install this script as: 
# /etc/rc.d/boot.notice.audio
# and set the permissions on this script by doing:
# chmod 755 /etc/rc.d/boot.notice.audio

# Run it from /etc/rc.d/rc.local or equivalent file for your distribution,
# by adding this to the end:
# /etc/rc.d/boot.notice.audio

# This script will self install (for RedHat systems) if you run it as:
# sh this_file install
# You have to be "root" to do this.
# This will run it from rc.local

# Alternatively, if you want to have it run directly from your inittab, do:
# sh this_file install inittab
# That would probably work for any distribution.

# Installation command block: 
if [ "$1" = install ]; then 
   set -x
   grep boot.notice.audio /etc/rc.d/rc.local /etc/inittab && exit 1
   cp $0 /etc/rc.d/boot.notice.audio
   chmod 755 /etc/rc.d/boot.notice.audio
   if [ "$2" != inittab ]; then 
      echo "/etc/rc.d/boot.notice.audio" >> /etc/rc.d/rc.local 
   else
      cp /etc/inittab /etc/inittab.save # for safety
      echo "au:2345c:once:/etc/rc.d/boot.notice.audio" >> /etc/inittab 
      echo "Test this installation by running:"
      echo "telinit c"
   fi
   echo "Installation complete"
   exit
fi

# Licensed under the GPL (GNU public license: that means it's free, with No
# warrantee whatsoever).
# Send suggestions for improvements to lcr@onewest.net
# Tell me if you want one for shutdown, too. (just try putting this at
# end of the halt script, eg, /etc/rc.d/init.d/halt, for starters)


# Begin useful script:

set `/sbin/runlevel`
if [ X$2 = X5 ] ; then
   # echo "We are in runlevel $2, so X is active." 
   # Change to virtual text terminal one after a suitable pause to allow X to get
   # through shifting you to that (X) console:
   (
      # Wait done in a backgound subshell to allow us to continue.
      # sleep 7 + 20 seconds, as necessary:
      sleep 7
      sleep 20
      # Change to the first virtual terminal:
      chvt 1 
   ) &
fi

# In case sound isn't working:
echo -e "\a\c"  # \a is the bell character
sleep 1  # pause 1 second
echo -e "\a\c"
sleep 1
echo -e "\a\c"
# repeat as desired

play /usr/share/sounds/startup2.wav

# You could also try (for the first serial port, if you have a
# synth connected there):
# Let me know if this works (I can't test it).
# echo "System is booted, and speech is active." > /dev/ttyS0
# 2nd port:
# echo "System is booted, and speech is active." > /dev/ttyS1

Re: red hat system almost talking

[Janina Sajka]

Jude:

It's sounding to me as though you do not have the kernel with speakup 
already compiled in--for whatever reason.

I presume you're hearing the lilo prompt by virtue of the serial command 
string in lilo.conf. But hearing the 'at' sign during the boot process is 
a pretty strong indicator of the kudzu new hardware detector trying to 
figure out what that thing attached at that port is. This would not happen 
if speakup were being launched.

So, it's one of two things:

1.)	For whatever reason, you're not passing the correct speakup 
synthesizer command;

2.)	For whatever reason, the kernel you installed doesn't have speakup 
in it;

The solution to the first is to be sure and type, by hand, first the 
correct kernel name, followed by a space, followed by speakup_synth=ltlk 
and then pressing enter at the lilo boot prompt. Again, you may need to do 
a Ctrl-X first, unless you've replaced /boot/message with a simple text 
file;

Of course, the better solution is to have the string in lilo.conf below 
the 'read only' line of the section that names the kernel being loaded. 
The syntax is:

	append="speakup_synth=ltlk"

The solution to the second issue is to get the appropriate kernel rpm 
package and install it. Use ftp to go to speakup.octothorp.org and then cd 
to /pub/roswell/b1/RedHat/RPMS/ -- beware the capital letters in RedHat 
and in RPMS. Get the appropriate kernel image for your system -- probably 
kernel-2.4.7-6.i386.rpm and install it as follows:

	rpm -ivh kernel-2.4.7-6.i386.rpm

You will now have a new vmlinuz. I believe the rpm installer will run lilo 
for you, but just in case, there's no harm in learning to do it by hand. 
So, type lilo and press enter.

As for coming up in GNOME, edit /etc/inittab.

There's a line that reads:
id:5:initdefault:

The 5 tells linux to start the gui interface by default. So, to get the 
text based run level with networking by default, change it to:

id:3:initdefault:

Do not modify the X references at the bottom of the file. It won't hurt, 
if you're not running X, but you'll want to eventually. Of course, you'll 
probably have reinstalled before then! <grin>

 On Sat, 8 Sep 2001, Jude DaShiell wrote:

> When I boot now, I hear lilo, then I hear boot, then I hear loading linux,
> then I hear the at sign, and all the rest is silence.  If I hit ackspace I
> don't hear the beep so this thing is still coming up in gnome mode.  I
> managed to log in using gnome and get such changes I have managed using
> exec >/dev/ttyS0 2>&1 on a line by itself.
> I got Bill's speakup.kmap.gz file stored and loaded into
> /etc/sysconfig/keyboard too.  How do I disable gnome permanently so it
> doesn't break the log in anymore?
> 
> 
> Jude <jdashiel@shellworld.net>
> 
> 
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
> 

-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org

Will electronic books surpass print books? Read our white paper,
Surpassing Gutenberg, at http://www.afb.org/ebook.asp

Download a free sample Digital Talking Book edition of Martin Luther
King Jr's inspiring "I Have A Dream" speech at
http://www.afb.org/mlkweb.asp

Learn how to make accessible software at
http://www.afb.org/accessapp.asp