Package: kernel-image-2.6.8-2-686 Version: 2.6.8-16sarge1 dispair:~> sudo dpkg --install /var/cache/apt/archives/kernel-image-2.6.8-2-686_2.6.8-16sarge1_i386.deb (Reading database ... 94347 files and directories currently installed.) Preparing to replace kernel-image-2.6.8-2-686 2.6.8-16 (using .../kernel-image-2.6.8-2-686_2.6.8-16sarge1_i386.deb) ... The directory /lib/modules/2.6.8-2-686 still exists. Continuing as directed. Unpacking replacement kernel-image-2.6.8-2-686 ... dpkg: error processing /var/cache/apt/archives/kernel-image-2.6.8-2-686_2.6.8-16sarge1_i386.deb (--install): unable to make backup link of `./boot/config-2.6.8-2-686' before installing new version: Operation not permitted dpkg-deb: subprocess paste killed by signal (Broken pipe) Searching for GRUB installation directory ... found: /boot/grub . Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst . Searching for splash image... none found, skipping... Found kernel: /vmlinuz-2.6.13 Found kernel: /vmlinuz-2.6.8-2-686 Found kernel: /vmlinuz-2.6.8-1-386 Updating /boot/grub/menu.lst ... done
Errors were encountered while processing: /var/cache/apt/archives/kernel-image-2.6.8-2-686_2.6.8-16sarge1_i386.deb dispair:~> The problem is due to the fact that my /boot directory is actually a vfat partition: dispair:~> grep boot /proc/mounts /dev/hda1 /boot vfat rw,nodiratime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1 0 0 dispair:~> and vfat does not support symlinks or hard links. Hence failing to make a backup link for the existing kernel image should not be a fatal error for installing the package. At least, not a fatal error that can't be overridden somehow, as --force-all still fails... Cheers, Dave. -- Dave Chinner [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]