Re: make-kpkg --append-to-version
Vineet Kumar wrote:
>
> Incorrect. Using --revision-number=custom.1.0 will result in a
> creation of ../kernel-image-2.4.5_custom.1.1_i386.deb . This is a
> different revision of the same debian package kernel-image-2.4.5 . He
> does want as Joost suggests: --append-to-version=athlon , which will
> result in something like
> ../kernel-image-2.4.5athlon_Custom.1.00_i386.deb , which is a debian
> package for kernel-image-2.4.5athlon , and will insert appropriately
> named files in /boot (i.e. vmlinuz-2.4.5athlon ,
> System.map-2.4.5athlon and config-2.4.5athlon ).
>
> I agree with Joost: what is needed is a make-kpkg clean, so that when
> the control files are rebuilt they will be for the package
> kernel-image-2.4.5athlon
>
> Vineet
>
Your're absolutly right! This is what I should have done. I did it the
other way (what kent suggested), and my old kernel was overwritten durin
install. However, it was not that bad, because it worked, in the end (I
was not able to reboot my pentium machine, but now, typing this, atholn
works very well. I'll keep this in mind for future upgrades... ;)
joerg
> * ktb (ktb@nixnotes.org) [010630 10:13]:
> > 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
> >
Reply to: