public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: "Mike A. Harris" <mharris@opensourceadvocate.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.4 add suffix for uname -r
Date: Sun, 06 May 2001 17:45:06 +1000	[thread overview]
Message-ID: <3437.989135106@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sun, 06 May 2001 03:35:34 -0400." <Pine.LNX.4.33.0105060334390.1549-100000@asdf.capslock.lan>

On Sun, 6 May 2001 03:35:34 -0400 (EDT), 
"Mike A. Harris" <mharris@opensourceadvocate.org> wrote:
>On Sun, 6 May 2001, Keith Owens wrote:
>>A frequent requirement is to rename vmlinuz-2.x.y to 2.x.y-old or
>>2.x.y.save to preserve a working kernel.
>
>I don't see how this patch is necessary when we have
>"EXTRAVERSION" available.  Change EXTRAVERSION in your kernel
>builds and it is totally a non issue.  No renaming of anything is
>necessary.

You already have a working kernel which you want to rename to use as a
backup version.  Changing EXTRAVERSION and recompiling builds a new
kernel and adds uncertainty about whether the kernel still works - did
you change anything else before recompiling?  Look at all the install
scripts that rename vmlinuz to vmlinuz-old.


  reply	other threads:[~2001-05-06  7:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-06  7:15 [patch] 2.4 add suffix for uname -r Keith Owens
2001-05-06  7:35 ` Mike A. Harris
2001-05-06  7:45   ` Keith Owens [this message]
2001-05-06  8:12     ` Lars Marowsky-Bree
2001-05-06  8:36       ` Mike Castle
2001-05-06  9:01         ` Lars Marowsky-Bree
2001-05-06 17:08         ` Russell King
2001-05-06  9:16     ` Mike A. Harris
2001-05-07 17:29 ` Pavel Roskin

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=3437.989135106@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mharris@opensourceadvocate.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