[Frans Pop] > In exactly which scenario would it be executed more than twice?
I expect it to run the triggers several times, once for each block of packages passed from apt to dpkg, but have not verified that this is the case. I had a look in the installation log for Debian Edu based on Squeeze, and here it is called four times: r...@tjener:~# grep -C1 update-init /var/log/installer/syslog Mar 14 06:03:00 in-target: Setter opp initramfs-tools (0.93.4) ... Mar 14 06:03:00 in-target: update-initramfs: deferring update (trigger activated) Mar 14 06:03:00 in-target: Behandler utløsere for initramfs-tools ... -- Mar 14 06:03:12 in-target: Running depmod. Mar 14 06:03:12 in-target: Running update-initramfs. Mar 14 06:03:12 in-target: update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-686 Mar 14 06:03:22 in-target: Examining /etc/kernel/postinst.d. -- Mar 14 07:11:44 in-target: update-alternatives: using /usr/lib/usplash/debian-edu-usplash.so to provide /usr/lib/usplash/usplash-artwork.so (usplash-artwork.so) in auto mode. Mar 14 07:11:44 in-target: update-initramfs: deferring update (trigger activated) Mar 14 07:11:44 in-target: Setter opp debian-edu-doc-en (1.3~20100223~5.0.4+edu0) ... -- Mar 14 07:13:51 in-target: Setter opp usplash (0.5.19-3) ... Mar 14 07:13:52 in-target: update-initramfs: deferring update (trigger activated) Mar 14 07:13:52 in-target: Setter opp util-linux-locales (2.16.2-0) ... -- Mar 14 07:15:18 in-target: Behandler utløsere for initramfs-tools ... Mar 14 07:15:18 in-target: update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-686 Mar 14 07:15:28 debian-edu-fsautoresize: overfull /usr, resizing to 6596198 -- Mar 14 07:46:15 in-target: KILLALL="false" Mar 14 07:46:15 in-target: update-initramfs: deferring update (trigger activated) Mar 14 07:46:16 in-target: Setting up libklibc (1.5.15-1) ... -- Mar 14 07:46:16 in-target: Setting up initramfs-tools (0.93.4) ... Mar 14 07:46:16 in-target: update-initramfs: deferring update (trigger activated) Mar 14 07:46:16 in-target: Setting up syslinux-common (2:3.85+dfsg-1) ... -- Mar 14 07:46:34 in-target: Setting up dmsetup (2:1.02.39-1) ... Mar 14 07:46:34 in-target: update-initramfs: deferring update (trigger activated) Mar 14 07:46:34 in-target: Setting up cryptsetup (2:1.1.0~rc2-1) ... Mar 14 07:46:34 in-target: update-initramfs: deferring update (trigger activated) Mar 14 07:46:34 in-target: Setting up libavahi-common-data (0.6.25-3) ... -- Mar 14 07:47:36 debian-edu-fsautoresize: overfull /var, resizing to 3216998 Mar 14 07:47:37 in-target: Running update-initramfs. Mar 14 07:47:37 in-target: update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-486 Mar 14 07:47:46 in-target: cryptsetup: WARNING: could not determine root device from /etc/fstab -- Mar 14 07:48:03 in-target: update-alternatives: using /usr/lib/usplash/debian-edu-usplash.so to provide /usr/lib/usplash/usplash-artwork.so (usplash-artwork.so) in auto mode. Mar 14 07:48:03 in-target: update-initramfs: deferring update (trigger activated) Mar 14 07:48:03 in-target: Setting up firmware-linux-free (2.6.32-5) ... -- Mar 14 07:48:08 in-target: Setting up usplash (0.5.19-3) ... Mar 14 07:48:08 in-target: update-initramfs: deferring update (trigger activated) Mar 14 07:48:09 in-target: Setting up tasksel-data (2.81) ... -- Mar 14 07:48:09 in-target: Processing triggers for initramfs-tools ... Mar 14 07:48:09 in-target: update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-486 Mar 14 07:48:18 in-target: cryptsetup: WARNING: could not determine root device from /etc/fstab r...@tjener:~# grep -C1 update-init /var/log/installer/syslog|grep Gener Mar 14 06:03:12 in-target: update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-686 Mar 14 07:15:18 in-target: update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-686 Mar 14 07:47:37 in-target: update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-486 Mar 14 07:48:09 in-target: update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-486 r...@tjener:~# It is possible some of these are from setting up the LTSP chroot environment. > I don't much like the patch either. Why doesn't it just use > in-target to run update-initramfs? I did wonder about that too. I expected in-target to handle /proc/ and friends, but do not know why Ubuntu choose to do this outside in-target and did not test if they are needed or not. Decided to pass on the patch untouched for review. :) Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org