Testing again, but without initramfs-tools installed, and with kernel-img.conf set to do_initrd = yes and link_in_boot = no
End result is this:
# ls -l /vmlinu* /initrd.img* /boot/initrd.img* ls: cannot access '/boot/initrd.img*': No such file or directory lrwxrwxrwx 1 root root 53 May 28 10:30 /initrd.img -> boot/initrd.img-5.13.0-051300rc3daily20210526-generic lrwxrwxrwx 1 root root 50 May 28 10:30 /vmlinuz -> boot/vmlinuz-5.13.0-051300rc3daily20210526-generic lrwxrwxrwx 1 root root 33 May 28 10:30 /vmlinuz.old -> boot/vmlinuz-5.11.0-16-lowlatency
initrd.img symlink from / is a dangling one. /vmlinuz* are correctly updated. initrd.img.old is not existant.
This confirms that the revised postin.d snippet is working correctly and it doesn't matter if it is ordered before or after generating initrd.
Testing again, but without initramfs-tools installed, and with kernel-img.conf set to do_initrd = yes and link_in_boot = no
End result is this:
# ls -l /vmlinu* /initrd.img* /boot/initrd.img* initrd. img*': No such file or directory img-5.13. 0-051300rc3dail y20210526- generic 5.13.0- 051300rc3daily2 0210526- generic 5.11.0- 16-lowlatency
ls: cannot access '/boot/
lrwxrwxrwx 1 root root 53 May 28 10:30 /initrd.img -> boot/initrd.
lrwxrwxrwx 1 root root 50 May 28 10:30 /vmlinuz -> boot/vmlinuz-
lrwxrwxrwx 1 root root 33 May 28 10:30 /vmlinuz.old -> boot/vmlinuz-
initrd.img symlink from / is a dangling one.
/vmlinuz* are correctly updated.
initrd.img.old is not existant.
This confirms that the revised postin.d snippet is working correctly and it doesn't matter if it is ordered before or after generating initrd.