Incomplete man page, or???

[oshunluvr]

I was exploring something that involved trying to use the vmlinuz and iniitd.img links with GRUB instead of the kernel images themselves. Looking at this file (KDEneon):

cat /etc/kernel-img.conf
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no

shows those two options.

In Kali:

cat /etc/kernel-img.conf
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = yes

so two more options.

The issue is NONE of these options are documented in the man page. I looked at several sources and they are all the same: kernel-img.conf(5)

Is it just not updated any longer or what?

[oshunluvr]

Ahhh... it appears Debian systems now use /usr/bin/linux-update-symlinks to create the symlinks and it reads /etc/kernel-img.conf and uses those options. linux-update-symlinks

Still, not all the answers there but more relevant:

image_dest
Specifies the directory in which to maintain symlinks
link_in_boot
If set to a true value, specifies that the directory is /boot
no_symlinks
If set to a false value, disables maintenance of symlinks

[oshunluvr]

A 15 year old post revealed this:

The current content of /etc/kernel-img.conf:
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = /sbin/update-grub
postrm_hook = /sbin/update-grub

It appears most of this relates back to the conversion from LILO to GRUB