From: "Tim Burgess" <tim.burgess@blazie.co.uk>
To: <speakup@braille.uwo.ca>
Subject: RE: kernel compile gone wrong.
Date: Mon, 24 Sep 2001 14:45:53 +0100 [thread overview]
Message-ID: <000501c144ff$3e4cbbd0$f9b4e5d4@tim02> (raw)
In-Reply-To: <Pine.LNX.4.33.0109231413560.21167-100000@wb2flw.octothorp.org>
Hi all,
I got a good kernel compile out of 2.4.6 and SpeakUp 0.10a.tar.gz then blew
it all by getting my lilo.conf entry wrong, I think. I'm now stuck until I
can borrow some eyeballs to see if I can retrieve the situation.
In the meantime, thanks to all of you who have gritted your teeth at my
incompetence so far.
Tim
-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of William F. Acker
WB2FLW +1-303-777-8123
Sent: 23 September 2001 21:18
To: speakup@braille.uwo.ca
Subject: RE: kernel compile gone wrong.
Hi, Tim,
I have a patch for 2.4 kernels made from the 20010917 CVS snapshot of
Speakup. I can make a 2.2 version if you need it. Just say the word and
I'll send it off.
HTH.
Bill in Denver
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
Shaun Oliver
` Frank Carmickle
` Shaun Oliver
` Tim Burgess
` Shaun Oliver
` Steve Holmes
` Tim Burgess
` Janina Sajka
` Tim Burgess
` Janina Sajka
` Gregory Nowak
` Gregory Nowak
` Janina Sajka
` Janina Sajka
` Tim Burgess
` Gregory Nowak
` Tim Burgess
` William F. Acker WB2FLW +1-303-777-8123
` Tim Burgess
` Gregory Nowak
` Tim Burgess [this message]
` Shaun Oliver
` Tim Burgess
` Tim Burgess
` Charles Hallenbeck
` Tim Burgess
` Shaun Oliver
` Gregory Nowak
` Gregory Nowak
` Gregory Nowak
` Tim Burgess
Holmes, Steve
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='000501c144ff$3e4cbbd0$f9b4e5d4@tim02' \
--to=tim.burgess@blazie.co.uk \
--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).