Debian/Squueze - Linux 2.6.32-5-686 #1 SMP Sat Jul 24 02:27:10 UTC 2010 i686 GNU/Linux
last week the upgrading to sub '27' of captioned linux-image stopped
on a line saying 'Running yes' while running update-initramfs. To
continue, I had to find the relating process and kill it, thus receiving
an error and no upgrading of the image.
I tried a few times until, almost by chance, looking at the 'ps' output I
saw this line:
thus becoming aware there really was a '/usr/bin/yes' program (in coreutils
pkg). So I decided to try again after hijacking 'yes' (moving it to
# apt-get upgrade
Setting up linux-image-2.6.32-5-686 (2.6.32-27) ...
update-initramfs: Generating /boot/initrd.img-2.6.32-5-686
) points to /boot/initrd.img-2.6.32-5-686
(/boot/initrd.img-2.6.32-5-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-686.postinst line 347.
) points to /boot/vmlinuz-2.6.32-5-686
(/boot/vmlinuz-2.6.32-5-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-686.postinst line 347.
User postinst hook script [yes] failed to execute: No such file or directory
dpkg: error processing linux-image-2.6.32-5-686 (--configure):
subprocess installed post-installation script returned error exit status 255
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
Despite the error, the image is correctly created and the bootloader
updated. However, looking into the 'postinst' file, I was unable to find a call to
'yes' so I do not quite understand what and why is happening. On the
other hand, I see no reason why such a program, whose aim is to 'output
a string repeatedly until killed' should intervene in the upgrading
Thanks for any help.
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo. ?//
Fa' qualche cosa di cui non sei capace!" (diceva Henry Miller) ] (°|°)
Ricevo solo messaggi Content-Type: plain/text (no html o multipart). )=(
!!! --> e-mail a mio nome via OE (M$) sono false e infette <-- !!!
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com