* Joey Hess <jo...@debian.org> [2009-05-04 15:44]: > * Current linux-kernel postinst runs initramfs-tools -c, which > does not involve triggers, and also does not run flash-kernel. > So it generates an initramfs that never gets used, but the old > one in flash should keep working.
This doesn't seem great to me. It means when you install a kernel version (e.g. 2.6.29 -> 2.6.30) that the new version is not written to flash. maks, why does -c not run run_bootloader? Example: # dpkg -i linux-image-2.6.30-rc8-kirkwood_2.6.30~rc8-1~experimental.1_arm Selecting previously deselected package linux-image-2.6.30-rc8-kirkwood. (Reading database ... 18471 files and directories currently installed.) Unpacking linux-image-2.6.30-rc8-kirkwood (from linux-image-2.6.30-rc8-kirkwood_2.6.30~rc8-1~experimental.1_armel.deb) ... Setting up linux-image-2.6.30-rc8-kirkwood (2.6.30~rc8-1~experimental.1) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.30-rc8-kirkwood W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. debian:~# -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
