mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: patching the kernel
Date: Sun, 9 Mar 2003 22:25:22 +0100	[thread overview]
Message-ID: <20030309212521.GQ27794@lug-owl.de> (raw)
In-Reply-To: <200303091711.21652.jbriggs@briggsmedia.com>

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

On Sun, 2003-03-09 17:11:21 -0500, joe briggs <jbriggs@briggsmedia.com>
wrote in message <200303091711.21652.jbriggs@briggsmedia.com>:
> My apologies for this question that is so basic to all of you, but can any of 
> you please point me toward a howto or instructions for exactly how to 'patch 
> a kernel'?  For example, at kernel.org, the latest stable kernel is 2.4.20, 
> and is actually a patch.  I currently use 2.4.19 under Debian and routinely 
> rebuild & install it no problem.  If I download a kernel 'patch', do I apply 
> it to the entire directory, or the compiled kernel, etc.?  Thanks so much.

	tar xzf .../linux-2.4.19.tar.gz
		-or-
	tar xjf .../linux-2.4.19.tar.bz2

and then apply the patch:

	cd linux-2.4.19
	zcat .../patch-2.4.20.gz | patch -p1
		-or-
	bzcat .../patch-2.4.20.bz2 | patch -p1

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-03-09 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09 22:11 joe briggs
2003-03-09 21:19 ` Sam Ravnborg
2003-03-09 21:25 ` Jan-Benedict Glaw [this message]
2003-03-10  4:41 ` scott thomason

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=20030309212521.GQ27794@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®