public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Thomas D. Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Major problem with Speakup.
Date: Thu, 16 Aug 2001 17:20:19 -0400	[thread overview]
Message-ID: <001601c12699$412cee80$3590fea9@starbase> (raw)

[-- Attachment #1: Type: text/plain, Size: 563 bytes --]

Hello, list. I have recently updated to Redhat 7.1. Also I have the 2.4.3.12 source code, and want to build a custom kernel.
Problem is that Speakup won't patch the kernel. It is driving me crazy. Somebody please give me as simple a fix for this problem as possible, or please release an updated Speakup that actually works with the 2.4.3 kernels and above.
Thanks, and please get back to me ASAP. I need to get this working not only for myself, but a fellow student who mmay need to take some Unix related classes, and I want to build him a kernel as well.


[-- Attachment #2: Type: text/html, Size: 1021 bytes --]

             reply	other threads:[~ UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Thomas D. Ward [this message]
 ` Buddy Brannan
   ` Thomas D. Ward
     ` Gregory Nowak
     ` Kirk Wood
       ` Steve Holmes
         ` Thomas D. Ward
     ` Janina Sajka
     ` Janina Sajka
       ` Thomas D. Ward
         ` Gregory Nowak
           ` using Linux was " Kenny Hitt
         ` Janina Sajka
       ` Gregory Nowak
         ` Scott Howell
           ` Gregory Nowak
             ` Kirk Wood
               ` Gregory Nowak
               ` Brian Borowski
 ` Tommy Moore
   ` Amanda Lee
     ` Thomas D. Ward
       ` Amanda Lee
 ` Gene Collins
 ` William F. Acker WB2FLW +1-303-777-8123
   ` Thomas D. Ward
     ` William F. Acker WB2FLW +1-303-777-8123
       ` Thomas D. Ward
         ` 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='001601c12699$412cee80$3590fea9@starbase' \
    --to=tward@bright.net \
    --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).