From: Steven Smith <sos22@cam.ac.uk>
To: Paul Kraus <pkraus@pelsupply.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Kernel
Date: Wed, 23 Oct 2002 15:20:28 +0100 [thread overview]
Message-ID: <20021023142028.GA420@cam.ac.uk> (raw)
In-Reply-To: <002d01c27a90$4d1d7290$64fea8c0@pkrausxp>
[-- Attachment #1: Type: text/plain, Size: 1704 bytes --]
> On the Linux kernel archive they list 2.4.19 as the current stable
> kernel. When I click on this it downloads patch-2.4.19.
> If I go through the directory on the ftp site they have both
> linux-2.4.19 (source for the kernel) and the patch-2.4.19. If you get
> the linux kernel .19 do you also need the patch?
No. You only need the patch if you have the source to version .18 and
want the source to version .19.
> If so do you apply the patch to the source or to the compile kernel
> and how do you apply it?
The patch would be applied to the source of the previous kernel
version. In general, patches are much, much smaller than full source
distributions, so are easier to download, and more friendly on the
various archive sites.
Different people will give you different recipes for applying patches,
but the one I usually use goes like this:
1) Uncompress the patch.
2) cd to the directory where you have the source to the previous version.
3) ``patch -p1 < path_to_patch''
It's quite rare to find that a patch applies cleanly on the first
attempt; go ``find -name '*.rej' | less'' from the source directory to
find any complaints. These usually indicate that your source pool
didn't quite match the version used to produce the patch (e.g. if
you've specified an EXTRAVERSION in the top level Makefile), and
should be reasonably easy to fix. If you find a reject file
``foo/bar.rej'', open up ``foo/bar.rej'' and ``foo/bar'' in a text
editor, and apply the changes listed in ``foo/bar.rej'' to
``foo/bar''. (This is a lot easier than it sounds).
As always, you should try and use one of the mirrors if at all
possible, rather than the main kernel archive.
Steven Smith,
sos22@cam.ac.uk.
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-10-23 14:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 12:32 Kernel Paul Kraus
2002-10-23 14:20 ` Steven Smith [this message]
2002-10-23 19:38 ` Kernel Jos Lemmerling
-- strict thread matches above, loose matches on Subject: below --
2023-09-07 12:07 kernel Artemis Ramirez
2011-09-16 12:43 Kernel Jestin Joy
2011-09-16 17:17 ` Kernel DiP
2005-08-12 11:58 kernel Srinivas K
2005-08-12 12:11 ` kernel Erik Mouw
2005-08-25 4:45 ` kernel Shwetha V
2005-08-25 7:40 ` kernel vamsi krishna
2005-08-25 9:38 ` kernel Jesper Juhl
2005-09-16 8:06 ` kernel Chikkali
2006-03-31 10:34 ` kernel vinayak
2003-10-23 13:34 Kernel Háber János
2003-10-23 16:48 ` Kernel Takashi Iwai
2003-02-22 7:15 kernel paul raj
2003-02-22 8:15 ` kernel Jurriaan
2002-08-28 21:18 kernel N1UAN Bob
2002-05-15 14:39 kernel Melissa Vandenbrink
2002-04-29 15:21 kernel Halil Demirezen
2001-10-18 15:09 kernel tushar korde
2001-10-18 16:12 ` kernel Mark Frazer
2001-05-31 11:31 kernel robert seczkowski
2001-05-31 11:45 ` kernel Alan Cox
2001-05-31 11:52 ` kernel Keith Owens
2000-11-07 3:55 kernel Joe Harrington
2000-11-07 4:09 ` kernel David Riley
2000-01-31 13:38 Kernel Jori
1998-03-06 18:25 xntp ralf
1998-03-06 22:49 ` kernel Ulf Carlsson
1998-03-06 23:56 ` kernel ralf
1998-03-07 21:37 ` kernel Ulf Carlsson
1998-03-07 22:20 ` kernel Oliver Frommel
1998-03-08 9:58 ` kernel Ulf Carlsson
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=20021023142028.GA420@cam.ac.uk \
--to=sos22@cam.ac.uk \
--cc=linux-newbie@vger.kernel.org \
--cc=pkraus@pelsupply.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.