Package: kernel-package Version: 10.054~bpo.1 Severity: important I must be missing something obvious, but linux-image packages generated by the kernel-package version above seem to run the configured postinst_hook script *after* running the bootloader, e.g.:
# dpkg -i /tmp/linux-image-2.6.16.29_local.1_i386.deb (Reading database ... 18569 files and directories currently installed.) Preparing to replace linux-image-2.6.16.29 local.1 (using .../linux-image-2.6.16.29_local.1_i386.deb) ... The directory /lib/modules/2.6.16.29 still exists. Continuing as directed. Done. Unpacking replacement linux-image-2.6.16.29 ... Running postrm hook script /usr/local/sbin/update-lilo. Setting up linux-image-2.6.16.29 (local.1) ... Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. 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. Running postinst hook script /usr/local/sbin/update-lilo. # As you can see, the postinst hook is the last thing the postinst runs. This contradicts what "man kernel-img.conf" says, it's different from what the sarge kernel-package did and it also doesn't make sense IMO since the hook typically sets up the bootloader config file, so it should run before the bootloader. Severity important because this will cause a newly installed kernel not to be bootable. Thanks, Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
