public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Tim Burgess" <tim@blazie.co.uk>
To: <speakup@braille.uwo.ca>
Subject: RE: Problem getting the patch file to work
Date: Wed, 17 May 2000 12:41:22 +0100	[thread overview]
Message-ID: <000101bfbffa$e317f2f0$ffc0c0c0@feenix> (raw)
In-Reply-To: <x73dnim899.fsf@speech.braille.uwo.ca>

Hi,

I had this problem when trying to patch Red Hat 6.1.  It turned out that Red
Hat hadn't provided the full source in their .rpm files.  I downloaded a
2.2.14 kernel source and uncompressed it into my /src/usr directory then
re-ran the patch and all was well.  The complete URL is:

ftp://ftp.kernel.org/pub/linux/kernel/v2.2/linux-2.2.14.tar.gz

I got this info from some helpful folks on the blinux list and I hope this
helps you too!

Tim Burgess

-----Original Message-----
From: speakup-admin@braille.uwo.ca
[mailto:speakup-admin@braille.uwo.ca]On Behalf Of Kirk Reiser
Sent: Tuesday, May 16, 2000 11:38 PM
To: speakup@braille.uwo.ca
Subject: Re: Problem getting the patch file to work


Well, I can only give you a few suggestions because I don't know your
exact arrangement.  Is your linux source directory named linux?
Linux-2.2.13 or whatever won't cut it.  Are you sitting in the
/usr/src directory when you run the patch command?  If you are in the
linux directory it won't work because it expects to patch to the
directory linux.  What version of patch are you using? my patch is
version 2.5.  Okay, let's start from there.

  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: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 David Robinson
 ` Kirk Reiser
   ` Tim Burgess [this message]
     ` William F. Acker WB2FLW +1-303-777-8123
 ` Geoff Shang

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='000101bfbffa$e317f2f0$ffc0c0c0@feenix' \
    --to=tim@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).