Comment 14 for bug 1877088

On Fri, 26 Jun 2020 at 15:01, bugproxy <email address hidden> wrote:
>
> ------- Comment From <email address hidden> 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.

.deb package uses very different maintainer scripts / codepath, and is
not the same operation as "sudo make install".

I personally always build my kernels as debs, and install debs, rather
than doing "sudo make install". But I am a distribution developer, and
I care for .debs to work right. Kernel developers, I guess, are
inverse, and care for "upstream" $ sudo make install to work.

>
> Not with the /etc/kernel-img.conf[0] and not without it either.
> As before the /boot/vmlinuz link is always updated.
>

That is slightly concerning, as to how $ sudo make install, ever
worked before..... Or what has changed since.

Normally, $ sudo make install, should lookup if /sbin/installkernel is
available, and call that to "do what it has to do, on a given
distribution", and that script is shipped by the debianutils package
which is required and must be installed always. And it hasn't been
touched in ages.

I wonder which arguments are passed to /sbin/installkernel by $ sudo
make install. And whether the 4th argument is passed, and if it is
empty, /, or /boot. It should be either empty, or /boot.

--
Regards,

Dimitri.