From: "brian Moore" <admin@bmoore.yi.org>
To: speakup@braille.uwo.ca
Subject: Re: adding speakup to server distros
Date: Wed, 02 Jan 2002 20:09:50 -0500 [thread overview]
Message-ID: <200201022009500130.00152A9C@mail> (raw)
In-Reply-To: <Pine.LNX.4.43.0201021211220.16682-100000@wb2flw.octothorp.org>
HI Bill. thanks. will give that a shot. what the hell, let's see
what happens. will make a test box and see if I can make it work.
thanks. Brian.
*********** REPLY SEPARATOR ***********
On 1/2/02 at 12:15 PM William F. Acker WB2FLW +1-303-777-8123 wrote:
>Hi,
>
> Everything you need should be in
>ftp://ftp.octothorp.org/pub/redhat-7.0/ RH released the 2.2.19-7.0.8
>kernel as an update, and if that's the kernel you have, then just
replace
>it with the speakup enabled one from my site.
>
>
>
>
> HTH.
> Bill in Denver
>
>
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201012028420370.0065B56A@mail>
` brian Moore
` Geoff Shang
` brian Moore
` William F. Acker WB2FLW +1-303-777-8123
` brian Moore [this message]
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=200201022009500130.00152A9C@mail \
--to=admin@bmoore.yi.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).