* giovedì 24 ottobre 2002, alle 09:43, Mark T. Valites scrive: > A while back I make-kpkg installed a new 2.4.19 custom kernel. > > This past week, I went to dist-upgrade the system again, except I am > getting caught when apt-get sees the custom kernel deb. It says if I > don't want to overwrite part of it, to exit. When I do, it exits & > appears to go on, but doesn't update any of the debs after the kernel. > How can I get around this?
almost in two ways: 1. because you have your custom kernel, you may "hold" the package via dpkg/dselect, so it will not ibe upgraded. 2. when you make your custom kernel, you may "personalize" it, with proper --revison and --append-to-version tags. this method not prevent kernel-image upgrade, but simply "your" kernel still yours, without touch the "common mainstream". this is what i do usually. In fact, my modules: [EMAIL PROTECTED]:~$ ll /lib/modules/ total 12 drwxr-xr-x 10 root root 4096 Apr 25 17:58 2.2.20 drwxr-xr-x 4 root root 4096 Oct 16 16:44 2.4.18 drwxr-xr-x 4 root root 4096 Oct 18 09:00 2.4.18-preempt-patch and my kernel-image: [EMAIL PROTECTED]:~$ uname -a Linux sparc 2.4.18-preempt-patch #1 Fri Oct 18 03:15:59 CEST 2002 sparc unknown hope useful. -- Maurizio - Tannoiser - Lemmo Founder Member of ERLUG http://erlug.linux.it ------------------------------------------------------------------------------- Wesley: "Swords... one long, one short?" Buffy: "Mmm. Both pointy." --Buffy the Vampire Slayer: Bad Girls