Package: linux-image-2.6.14-1-686 Version: 2.6.14-1 Severity: important
Usually the install Just Works, but today: % dpkg -i /var/cache/apt/archives/linux-image-2.6.14-1-686_2.6.14-1_i386.deb (Reading database ... 174825 files and directories currently installed.) Preparing to replace linux-image-2.6.14-1-686 2.6.14-1 (using .../linux-image-2.6.14-1-686_2.6.14-1_i386.deb) ... The directory /lib/modules/2.6.14-1-686 still exists. Continuing as directed. Unpacking replacement linux-image-2.6.14-1-686 ... Setting up linux-image-2.6.14-1-686 (2.6.14-1) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: malformed line in /etc/fstab:9 (fatal) Failed to create initrd image. dpkg: error processing linux-image-2.6.14-1-686 (--install): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: linux-image-2.6.14-1-686 % echo $? 1 I notice a mention of "/etc/fstab:9" -- perhaps that means line #9: % nl /etc/fstab | grep "^ *9" 9 /dev/hdc /mnt/cdrw iso9660 noauto,user,ro ...no, my cdrw drive shouldn't influence kernel upgrades. Maybe the '9' means lines without comments: # search for lines without comments that aren't blank, # then number 'em, and print #9 % grep -v "^#\|^ *$" /etc/fstab | nl | grep "^ *9" 9 /dev/hdb1 /mnt/f vfat noauto,rw,owner,user 0 2 ...but a 'vfat' drive shouldn't matter either. Hope this helps... -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages linux-image-2.6.14-1-686 depends on: ii module-init-tools 3.2-pre9-3 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.11-9 Yet Another mkInitRD linux-image-2.6.14-1-686 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]