-----Original Message----- From: Stephen Powell <zlinux...@wowway.com> To: debian-user@lists.debian.org Subject: Re: Trunk version of linux-image ISSUE Date: Sat, 17 Apr 2010 12:49:27 -0400 (EDT)
On Sat, 17 Apr 2010 09:37:30 -0400 (EDT), JW Foster wrote: > Examining /etc/kernel/postrm.d . > run-parts: executing /etc/kernel/postrm.d/extlinux > 2.6.32-trunk-686 /boot/vmlinuz-2.6.32-trunk-686 > run-parts: /etc/kernel/postrm.d/extlinux exited with return code 1 Normally, when a script in /etc/kernel/*/<scriptname> fails, and the script name matches a package name (extlinux in this case), the script was installed by that package. Since you're using grub as your bootloader, and since extlinux was designed for use with the syslinux boot loader, I'm not sure why you have it installed in the first place. That could be your problem. -- .''`. Stephen Powell : :' : `. `'` `- -- John Foster ---------------------------------------- Thanks to all who responded. This situation was resolved by applying the intell, gleaned from the thoughts provided by Stephen & others from all of you. Here is what I did. 1. used mc to locate every vestige of the trunk version, and physically deleted all of them. Recall I was able to get the other version to boot up, albeit without it being properly configured correctly. 2. used synaptic to purge syslinux & extlinux & mkrboot. Both extlinux & syslinux were added by mkrboot when I installed it to make some bootable media. 3. reinstalled the upgraded regular linux-image. 4. celebrated the fact that given time this list has solved every issue I've ever had with linux. An opinion: the trunk version is NOT properly packaed with approriate warnings & should be removed from the distro, or at least sent to experimental. John -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1271857349.5563.9.ca...@brutus
