Re: make-kpkg --append-to-version

[ktb <ktb@nixnotes.org>]

On Sat, Jun 30, 2001 at 04:45:33PM +0200, Joost Kooij wrote:
> On Sat, Jun 30, 2001 at 08:22:02AM -0500, ktb wrote:
> > >From zless /usr/doc/kernel-package/README.gz -
> > make-kpkg --revision=custom.1.0 kernel_image
> 
> Nope, this does not make any differences to the filenames that are
> installed by the package, which is what the original poster was after.
> The --revision option sets debian control info only.

Joerg Johannes wrote:
>>> I am trying to build a kernel for athlon on my pentium machine. It must
>>> be 2.4.3 (as I am using at the moment) because I have xfs running on /,
>>> /home, and /var. I want to install both kernels for being able to switch
>>> all my hardware back to the pentium machine if something doesn't work. I
>>> tried to compile the athlon kernel with "--append-to-version athlon" and
>>> I get the eroor message
<snip>
>>> Running without --append-to-version gives me a kernel-image.deb which is 
>>> named exactly as the installed kernel. This is not good, because
>>> installing it may overwrite the existing kernel and stealing me the  
>>> ability to fix anything in case of misconfiguration.
>>> Any idea how to produce a kernel with a different name?

Joerg is running kernel version 2.4.3.  He is compiling another kernel
version 2.4.3 "make-kpkg --revision=custom.1.0 kernel_image" is exactly
what he needs in order to create a 2.4.3 kernel with a revised name.
Otherwise he is right, his original kernel will be overwritten.
kent

-- 
 From seeing and seeing the seeing has become so exhausted
     First line of "The Panther" - R. M. Rilke