On Tue, Jul 31, 2007 at 01:15:19AM +0300, Sasho Angelov wrote: > When I try to purge old linux image: > > sudo dpkg --purge --force-all linux-image-2.6.14-2-k7 Why --force-all ? > (Reading database ... 259033 files and directories currently installed.) > Removing linux-image-2.6.14-2-k7 ... > Purging configuration files for linux-image-2.6.14-2-k7 ... > Searching for GRUB installation directory ... found: /boot/grub > Searching for default file ... found: /boot/grub/default > Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst > Searching for splash image ... none found, skipping ... > Found kernel: /boot/vmlinuz-2.6.22-1-k7 > Updating /boot/grub/menu.lst ... done > > And stop here. Only I can do is to press Ctrl+C > then result is: > dpkg: error processing linux-image-2.6.14-2-k7 (--purge): > subprocess post-removal script killed by signal (Interrupt) > Errors were encountered while processing: > linux-image-2.6.14-2-k7 > > > /var/lib/dpkg/info/linux- image-2.6.14-2-k7.list is empty file > > What to do??? Which debconf frontend do you use? I've had that happen to me when I "accidentally" used the GNOME front-end. Not a problem, unless you're on a virtual console and DISPLAY is set - then it shows the GUI on the X display that I'm not looking at.... Took me a while to figure out... -- Karl E. Jorgensen karl@jorgensen.org.uk http://www.jorgensen.org.uk/ karl@jorgensen.com http://karl.jorgensen.com ==== Today's fortune: old inkjet cartridges emanate barium-based fumes
Attachment:
signature.asc
Description: Digital signature