* Michael C. Alonzo ([EMAIL PROTECTED]) wrote: <SNIP> > I had the same problem about a month ago. what i did was to delete > 2.2.19 and use 2.4.7 (only one kernel).
Suddenly, this question makes sense. I just got a bunch of these since I moved to 2.4.10 on this Woody box. When you say delete the 2.2.x kernel, are you talking about the /boot contents? This is what /boot looks like: -rw-r--r-- 1 root root 145842 Jun 21 09:45 System.map-2.2.18 -rw-r--r-- 1 root root 378576 Oct 1 13:51 System.map-2.4.10 -rw-r--r-- 1 root root 4368 Sep 20 15:44 boot-compat.b -rw-r--r-- 1 root root 6128 Sep 20 15:44 boot-menu.b -rw-r--r-- 1 root root 4368 Sep 20 15:44 boot-text.b -rw-r--r-- 1 root root 512 Jun 15 09:53 boot.0300 lrwxrwxrwx 1 root root 17 Oct 1 11:20 boot.b -> /boot/boot-menu.b -rw-r--r-- 1 root root 624 Sep 20 15:44 chain.b drwxr-xr-x 2 root root 12288 Jun 15 08:30 lost+found -rw------- 1 root root 14848 Oct 1 14:10 map -rw-r--r-- 1 root root 67620 Jun 20 16:31 memtest86.bin -rw-r--r-- 1 root root 652 Sep 20 15:44 os2_d.b -rw-r--r-- 1 root root 411139 Oct 1 14:07 vmlinuz-2.2.18 -rw-r--r-- 1 root root 618851 Oct 1 14:10 vmlinuz-2.4.10 If I understand you correctly, you're suggesting that the vmlinuz-2.2.18 kernel be deleted. (?) TIA, Mike Pfleger There's seventy brilliant people on earth. Where are they hiding? "Yashar" -Cabaret Voltaire (off of "2x45")