> On 20010514.2057, Jacob Meuser said ... > > > Another general debian question. How do most people handle it when > > they build/install their own kernel from source, and a new kernel > > comes out and apt wants to install it? Should I remove the kernel > > stuff via dselect/apt, or put it on hold? > > > 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. :( -Rob Random Quote: ------------ I lost a button hole today.
