public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: <bardiazakeri@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: World writable speakup files in Linux next
Date: Mon, 13 Dec 2010 19:58:46 +0100	[thread overview]
Message-ID: <717F1D3BA1464FA493B4FE46DD9BA6AE@BardiaDator> (raw)
In-Reply-To: <20101213185949.GB29410@rivensight.dyndns.org>

how!
i want help .
whit it


--------------------------------------------------
From: "Frost" <znvyyvfgf@gmail.com>
Sent: Monday, December 13, 2010 7:59 PM
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: World writable speakup files in Linux next

> On Mon, Dec 13, 2010 at 07:20:01PM +0100, bardiazakeri@gmail.com wrote:
>> how i can install spekaup on ubuntu?
> 
> Dunno.  Instructions should be on the installation CD on how to 
> start Ubuntu with Speakup.  How they handle it from there, or if like 
> Debian Squeeze (which I use) and doesn't yet have any speakup modules 
> packages showing in an apt-cache search yet, is another story.  For 
> Debian, SpeakUP is probably already in the kernel, and only needs to be 
> added to /etc/modules with the name of the module, ie: speakup_ltlk for 
> the LiteTalke hardware synthesizer, or in /etc/rc.local, where you would 
> add:
> 
> modprobe speakup_soft
> espeakup
> speakupconf load
> 
> With the previous /etc/rc.local setup, you would need to apt-get 
> install both the espeakup and speakup-tools packages for use with 
> SpeakUP's software speech synthesizer.  Again, I'm not entirely sure 
> about Ubuntu, but the instructions should be either on the installation 
> CD, or on the Ubuntu website.  If they don't, then that's why I went 
> with Debian.  Hope this helps,
> 
> Michael
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

  reply	other threads:[~ UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101210190047.GA19219@kroah.com>
 ` William Hubbs
   ` Frost
 ` Christopher Brannon
   ` William Hubbs
     ` Samuel Thibault
     [not found]       ` <20101212182940.GB16883@kroah.com>
         ` Kirk Reiser
           ` Samuel Thibault
             ` Kirk Reiser
               ` Samuel Thibault
               ` acollins
                 ` Samuel Thibault
             ` Frost
               ` Samuel Thibault
                 ` Kitty Litter
                   ` Samuel Thibault
                 ` Frost
                   ` bardiazakeri
                     ` Frost
                       ` bardiazakeri [this message]
                         ` Littlefield, Tyler
                           ` bardiazakeri
                             ` Kerry Hoath
                               ` Littlefield, Tyler
                                 ` Arch Linux was: " Øyvind Lode
                           ` bardiazakeri
                           ` speakup and ubuntu, was: " Gregory Nowak
                             ` Littlefield, Tyler
                   ` Samuel Thibault
                   ` Michael Whapples
                     ` Samuel Thibault
                       ` Frost
               ` bardiazakeri

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=717F1D3BA1464FA493B4FE46DD9BA6AE@BardiaDator \
    --to=bardiazakeri@gmail.com \
    --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).