Re: Naming Custom Kernels

2001-02-26 Thread Ethan Benson
On Mon, Feb 26, 2001 at 01:27:01PM +0100, Jürgen A. Erhard wrote: > > Whoever edits the top-level Makefile before last compilation decides > what EXTRAVERSION is. > > Yes, patches often do set EXTRAVERSION, but that's of no consequences; > I can't think of a reason a patched kernel should check

Re: Naming Custom Kernels

2001-02-26 Thread Jürgen A. Erhard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > "Martin" == Martin =?iso-8859-1?Q?W=FCrtele?= writes: Martin> On Sat, Feb 24, 2001 at 03:31:49PM -0500, David Raeker-Jordan wrote: Martin> (...) >> What is EXTRAVERSION for and what problems might I cause? Is EXTRAVERSION >> on

Re: Naming Custom Kernels

2001-02-24 Thread Martin Würtele
On Sat, Feb 24, 2001 at 03:31:49PM -0500, David Raeker-Jordan wrote: (...) > What is EXTRAVERSION for and what problems might I cause? Is EXTRAVERSION > only to be used by the official maintainer, or can it safely be edited by > mere mortals? AFAIK EXTRAVERSION is used for patched kernels, e.g.

Naming Custom Kernels

2001-02-24 Thread David Raeker-Jordan
I have read the kernel-package Readme and it says (I think) to name custom kernels like this: make-kpkg --revision=custom.1.0 kernel_image I can do that, but then when I install the kernel and run "uname -a" I get a name like 2.2.18. How can I identify the kernel as a custom kernel version once i