------- Comment From niklas.schne...@ibm.com 2020-06-26 09:45 EDT------- (In reply to comment #17) > Eoan and later d-i, new installer, curtin do not install > /etc/kernel-img.conf. > Upgraded systems keep having it (ie. installed with bionic or xenial, and > upgraded). > > Can you please let me know if _removing_ /etc/kernel-img.conf breaks $ sudo > make install, and if adding /etc/kernel-img.conf back fixes $ sudo make > install? > > Cause the expectation is that `/etc/kernel-img.conf` should not be there, > yet everything should still work correctly. > > I think somewhere something is reading "link_in_boot=yes" and was not > updated with the new implicit default to always assume that on recent ubuntu.
For me the installkernel script (including in the current case "sudo make install" from a mainline Linux tree) doesn't update the /boot/initrd.img symlink. Interestingly a package upgrade for linux-generic does overwrite this symlink. Not with the /etc/kernel-img.conf[0] and not without it either. As before the /boot/vmlinuz link is always updated. [0] # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = yes do_initrd = yes link_in_boot = yes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
