Package: linux-2.6 Version: 2.6.18-1 Hello,
Just now, I installed linux-image-2.6.18-1-amd64. At first try, I got this output: Setting up linux-image-2.6.18-1-amd64 (2.6.18-1) ... Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-1-amd64/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/2.6.18-1-amd64/source Running depmod. Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. yaird error: bad value in /boot/config-2.6.18-1-amd64: CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" (fatal) mkinitrd.yaird failed to create initrd image. Failed to create initrd image. dpkg: error processing linux-image-2.6.18-1-amd64 (--configure): subprocess post-installation script returned error exit status 9 ... Errors were encountered while processing: linux-image-2.6.18-1-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-2.6.18-1-amd64 (2.6.18-1) ... Running depmod. Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. yaird error: bad value in /boot/config-2.6.18-1-amd64: CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" (fatal) mkinitrd.yaird failed to create initrd image. Failed to create initrd image. dpkg: error processing linux-image-2.6.18-1-amd64 (--configure): subprocess post-installation script returned error exit status 9 Errors were encountered while processing: linux-image-2.6.18-1-amd64 I then updated yaird: ... Preparing to replace yaird 0.0.12-14 (using .../yaird_0.0.12-18_amd64.deb) ... ... ...and reconfigured: # dpkg-reconfigure linux-image-2.6.18-1-amd64 Running depmod. Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. Not updating initrd symbolic links since we are being updated/reinstalled (2.6.18-1 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.18-1 was configured last, according to dpkg) You already have a LILO configuration in /etc/lilo.conf Running boot loader as requested Testing lilo.conf ... Testing successful. Installing the partition boot sector... Running /sbin/lilo ... Installation successful. # If I understand everything correctly, this means that the kernel image package needs version in the dependency on yaird to be updated. HTH. Much love, -- Miciah Masters <[EMAIL PROTECTED]> / <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]