On Wed, Oct 24, 2001 at 01:18:52AM +0000, Martin WHEELER wrote: > On Tue, 23 Oct 2001, Ethan Benson wrote: > > > kernels are never upgraded automatically by apt, you have to do it > > yourself: > > That's not quite true -- should you recompile your own kernel, and for > whatever reason, NOT give that new kernel a debian-style name which > conforms *exactly* to the debian naming conventions, you will be > pestered for evermore with attempts by apt to 'upgrade' to the latest > (plain vanilla) version. well yes, the reason kernel images are not automatically upgraded from r2 -> r3 is because its a different package r2: kernel-image-2.2.18 Version: 2.2.18-1 r3: kernel-image-2.2.19 Version: 2.2.19-1 different package so why would apt upgrade it. (and yes i know its actually a pre-something in r2, thats beside the point). if you create your own kernel-image-2.2.19 package and your version number is not greater then the debian one then yes apt will try to upgrade it like any other package, and this in fact occurs sometimes in unstable dists since the kernel version is the same, but a few debian revisions will be done (-2 -3 -4 etc), this very rarly to never effects the stable release since by the time a new stable is released a much newer kernel is available and used. its also possible the 2.2.19 images will get a backported security patch which would cause an automatic apt upgrade for anyone with the 2.2.19 image already installed. as for your custom kernel problem the solution is trivial: make-kpkg --revision=5:2.2.19-1 or --revision=5:2.2.19-`hostname`.1 is something i use. the 5: is an epoch which will make your version number always newwer then any debian version (unless a debian kernel somehow gets an epoch larger then 5, a very unlikly scenerio). one last point, if you never actually install a kernel-image package after you install a new system from boot-floppies apt will never upgrade you kernel, since boot-floppies don't install any kernel-image they simply untar the modules into /lib/modules and cp the vmlinux files to /boot and symlink it to / dpkg never knows about it. -- Ethan Benson http://www.alaska.net/~erbenson/
Attachment:
pgpAHz2VkPjCj.pgp
Description: PGP signature