public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Janina Sajka <janina@afb.net>
To: <blinux-list@redhat.com>
Subject: Re: red hat system almost talking
Date: Mon, 10 Sep 2001 02:15:37 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0109100211170.1274-200000@toccata.grg.afb.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0109082327240.1105-200000@rupin.localnet>

[-- 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


  parent reply	other threads:[~ UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Jude DaShiell
 ` Mike Gorse
 ` red hat system almost talking: question related to comments Cheryl Homiak
   ` Jude DaShiell
   ` Janina Sajka
     ` Cheryl Homiak
       ` S. Massy
 ` red hat system almost talking L. C. Robinson
   ` Jude DaShiell
     ` L. C. Robinson
       ` Jude DaShiell
   ` Janina Sajka [this message]
 ` Janina Sajka

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.4.33.0109100211170.1274-200000@toccata.grg.afb.net \
    --to=janina@afb.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).