On Tue, May 15, 2001 at 03:59:37AM -0700, Rob Hudson wrote: > > I usually install from source without making packages. My system > > doesn't even know I have a kernel: > > jakemsr@nodge:~$ dpkg -l |grep kernel > > ii kernel-package 7.37 Debian Linux kernel package build scripts. > > ii mkrboot 0.91 Make a kernel + rootimage bootable from one > > ii pciutils 2.1.8-2 Linux PCI Utilities (for 2.[123].x kernels) > > Mine is similar... > > ii kernel-image-2 1 Linux kernel binary image for version 2.2.19 > ii kernel-package 7.34 Debian Linux kernel package build scripts. > ii pciutils 2.1.8-2 Linux PCI Utilities (for 2.[123].x kernels) > > Except I did a make-kpkg kernel_image for the linux kernel, and the > did a dpkg -i kernel_image.deb and so it shows up there. But if > debian comes out with kernel-image-2.2.20 later on, it will try to > overwrite mine, right? This happened to me when potato updated it's > kernel and I was still running 2.2.18. I had to Ctrl-c out of the > apt-get upgrade. :( > The Debian policy on kernels is probably explained in the Debian Policy Manual -> apt-get install debian-policy. I admit, I do not know the policy. Perhaps you can build a new kernel, uninstall the kernel deb, then install your new kernel. I don't think I've run into anything other than kernel modules that had dependencies on the kernel package. There is a file somewhere that allows one to set preferences on how to treat updates for packages. You can essentially put a "hold" on any package. Unfortunately, I forgot where this file is :( I got this info from the debian-dpkg mailing list, where it was posted a couple weeks ago. Perhaps a search of the archives would turn up something? <[EMAIL PROTECTED]>
