public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: hello from a new member
Date: Sun, 30 Nov 2008 16:58:01 -0700	[thread overview]
Message-ID: <20081130235801.GA5221@localhost.localdomain> (raw)
In-Reply-To: <49332596.9070501@aim.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Actually, if you're using a 2.6.x or later kernel, you don't even need
to patch the kernel; you can just build speakup as modules. This is
described here:

http://speech.braille.uwo.ca/pipermail/speakup/2008-May/046202.html

Hth.

Greg


On Sun, Nov 30, 2008 at 11:45:26PM +0000, Michael Whapples wrote:
> Hello,
> Not using either of those distros I don't know if they have a way you  
> can create a kernel with speakup and make it a package you install. If  
> they do then you might want to go that route as hopefully you would use  
> basically the same config and so might be able to use the modules from  
> the distro.
>
> An alternative is to look at those distros which include speakup or  
> speakup packages (this is why I stick with slackware, although it  
> doesn't allow installing by software synth). GRML (www.grml.org) is  
> debian based and has a software synth on the CD. You may want to look at  
> it. GRML can be run as a live CD (good for system maintainance or just  
> learning about speakup), or you can install GRML to hard disk, or there  
> is a script to create a debian installation.
>
> If you resort to just generic instructions for compiling a kernel with  
> speakup, there are many docs online about compiling kernels. One I use  
> (mainly because I use slackware) is the slackware details for creating a  
> speakup enabled kernel (although fairly generic)
 
> ftp.slackware.com/pub/slackware/slackware/source/k/README_SPEAKUP_PATCH.TXT 
>  
> <ftp://ftp.slackware.com/pub/slackware/slackware/source/k/README_SPEAKUP_PATCH.TXT>
> . If you aren't using an existing config which specifies using speakup  
> then remember when configuring the kernel (make menuconfig) to enable  
> speakup and the software synth option. Also some distos (I think ubuntu  
> is one of them) use grub instead of lilo, make sure that you update grub  
> so it knows about the new kernel if grub is used instead of updating 
> lilo.
>
> It really is easier to start with a pre-compiled kernel (particularly if  
> you aren't used to kernel configuration).
>
> Michael Whapples


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkkzKIkACgkQ7s9z/XlyUyAMwACfYY90vpEIxGkdRFWImDIlKJom
aB4AoMoB/981idlO05vUYSI8MNVxT1xw
=FUC7
-----END PGP SIGNATURE-----

  parent reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Aruni Sharma
 ` Michael Whapples
   ` Alonzo
   ` Gregory Nowak [this message]
     ` Michael Whapples
       ` Willem van der Walt
         ` Gregory Nowak

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=20081130235801.GA5221@localhost.localdomain \
    --to=greg@romuald.net.eu.org \
    --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).