Control: tag -1 moreinfo On Thu, 2023-04-20 at 16:09 -0400, Joey Hess wrote: > Source: linux > Version: 6.1.20-2 > Severity: normal > > I was upgrading a slow arm board and noticed this: > > Setting up linux-image-6.1.0-7-armmp-lpae (6.1.20-2) ... > I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.18.0-4-armmp-lpae > I: /initrd.img.old is now a symlink to boot/initrd.img-5.18.0-4-armmp-lpae > I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-7-armmp-lpae > I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-7-armmp-lpae > /etc/kernel/postinst.d/initramfs-tools: > update-initramfs: Generating /boot/initrd.img-6.1.0-7-armmp-lpae > > It probably took 5 minutes to generate the initrd, and until then > /initrd.img was a dangling symlink. A power failure in this wide window would > not be fun.
This behaviour is intentional. The expectation is that these symlinks are used by programs that update the boot loader configuration later on, and those will be run only after the initramfs has been generated. What do you think will go wrong here? Ben. -- Ben Hutchings Theory and practice are closer in theory than in practice - John Levine
signature.asc
Description: This is a digitally signed message part
