public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Tom Moore <tom@tomstroubleshooting.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Slackware upgrade woes
Date: Tue, 5 Apr 2005 12:54:52 -0400	[thread overview]
Message-ID: <20050405165452.GA10029@zeus> (raw)
In-Reply-To: <x7mzsd2pj5.fsf@speech.braille.uwo.ca>

A couple of weeks ago I reported this on the reflector and Gene and a few others tried to help me out.
Semed to lock up my machine when I went to paste some text from one console to another.

Tom

On Tue, Apr 05, 2005 at 11:48:14AM -0400, Kirk Reiser wrote:
> Ouch on the lock-up on mark/cut/paste.  Has anybody else patched
> 2.4.29 and found the same results or better yet that it actually
> works?  I have to say that the 2.4.x support days are very limited
> because 2.6.x has made a significant divergence and so maintaining
> both 2.4 and 2.6 would be a lot more overhead.  Any volunteers to pick
> up the 2.4.x maintenance?
> 
>   Kirk
> 
> -- 
> 
> Kirk Reiser				The Computer Braille Facility
> e-mail: kirk@braille.uwo.ca		University of Western Ontario
> phone: (519) 661-3061
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


  reply	other threads:[~ UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Chuck Hallenbeck
 ` Kirk Reiser
   ` Tom Moore [this message]
   ` Re[2]: " Farhan
     ` Kenny Hitt
   ` Luke Yelavich
     ` Kirk Reiser
       ` David Csercsics
 ` Chuck Hallenbeck
   ` Sean McMahon
   ` jim grimsby
     ` Gregory Nowak
 ` Gregory Nowak
 ` Adam Myrow
   ` Chuck Hallenbeck
     ` Kirk Reiser
       ` Chuck Hallenbeck
       ` nick G
 ` Ralph W. Reid

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=20050405165452.GA10029@zeus \
    --to=tom@tomstroubleshooting.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).