From: Jacob Schmude <jschmude@adelphia.net>
To: Hynek Hanke <hanke@volny.cz>
Cc: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: regarding speech-dispatcher, dectalk and the init script
Date: Sun, 2 May 2004 07:26:19 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0405020723110.11598@beavis.screwball> (raw)
In-Reply-To: <20040502112049.GB1256@volny.cz>
Hi
My script looks like this:
--script starts here--
#!/bin/sh
# rc.local - local startup script
#
# Get speech up and running:
/usr/local/bin/speech-dispatcher
sleep 1
modprobe speakup_sftsyn
/usr/local/bin/speechd_up
# Copy the speech settings:
cp /etc/speakup/sftsyn/* /proc/speakup
--script ends--
As can be seen, the script is extremely simple.
On Sun, 2 May 2004, Hynek Hanke wrote:
> On Sun, May 02, 2004 at 07:02:40AM -0400, Jacob Schmude wrote:
> > Speech-dispatcher executes as root in my rc.local script, and root most
> > certainly has permission to access the say command. I get no output when
> > running run_test either, nor when I try to use speechd-el with
> > dtk-generic. Curiously, speechd-el can still use flite as its output even
> > though dectalk won't work when started from the initscript.
>
> Flite and Festival should work. They do for me. It seems there is some
> problem with the generic output module.
>
> Please could you sent me privately your init.d script you use to run
> Speech Dispatcher so that I can test it with epos-generic?
>
> Thank you,
> Hynek
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
Hynek Hanke
` Jacob Schmude
` Hynek Hanke
` Jacob Schmude
` Hynek Hanke
` Jacob Schmude [this message]
` Cheryl Homiak
` nick G
` dking
` Gregory Nowak
` Hynek Hanke
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.58.0405020723110.11598@beavis.screwball \
--to=jschmude@adelphia.net \
--cc=hanke@volny.cz \
--cc=speakup@braille.uwo.ca \
/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).