On Sun, Jul 01, 2001 at 02:14:50PM +0200, Joerg Johannes wrote:
> 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... ;)
I am very very sorry for the bad advice:( I was sure I had done this in the
past and the original kernel was automatically moved by dpkg to kernel-old or
something like that after using the revision line.
kent
--
From seeing and seeing the seeing has become so exhausted
First line of "The Panther" - R. M. Rilke
