ERROR: cannot create symlinks /boot/vmlinuz and /boot/initrd

English Install/Boot/Login
21

The content in 90-local.conf here is meant only to shrink the size of initrds by omitting content that a multibooting environment makes pointless to waste space including — whatever causes a new kernel and/or initrd to prevent booting can be fixed by booting something else if booting an older kernel/initrd won’t do it.

I just added the causal 01-dist.conf to another TW host (gb970), dup’d to 20260531, installed another kernel, and the (expected) result was initramfs-<ver> only instead of initrd-<ver> plus vmlinuz and initrd symlinks.

The solution is obvious, scrapping the un-owned ancient .conf file, but not why naming of the initrd initramfs instead, the apparent reason for symlink creation failure, could result from its content.

22

Well, that question moves the discussion from system administration into implementation details of dracut/kernel-install. You’re free to investigate further by reading the dracut scripts or filing a bug if understanding the exact code path really matters to you. :wink:

23

It only bothers me because none of the file’s content seems related to the name of the file dracut produces. The immediate cause of $SUBJECT has literally been found, so I guess it will be time to label this solved soon, after giving self and others a little more time to possibly consider 01-dist.conf content.