Dummy question.
On one of my Kali Linux installations there isn't enough space on /boot. So, installing a new kernel image fails.
Usually this is caused by having too many old kernels installed. But I my case I only have the running kernel installed. But the initrds have a size of ~200MB. As the initrds on a different Kali system are only around 125 MB I wonder if something goes wrong creating the initrds? Any ideas what I should check?
@realn2s another option, not sure it's in Kali, to create the initrd tailored to your computer. But yes, initrd sizes are a bit crazy right now.
@realn2s I consider keeping boot (not /boot/efi) on a separate partition a thing from an ancient past when bootloaders where unable to access the kernel image in the root filesystem because of limitations of the DOS era. Is default Kali still doing this on recent Installations? #Debian on which Kali is AFAIK based does not do this anymore.
@realn2s Have you checked whether they are compressed?
@mkj
All of them are cpio archives (the small ones as well)
Both Kali system are VirtualBox VMs
@realn2s Okay, so no obvious difference there, then. Hmm.
@mkj
They are actual different Kernels
The large is initrd.img-6.18.5+kali-amd64 the small images are initrd.img-6.12.25-amd64
I can recall that I explicitly choose one of the versions
It turns out the large ones are Roling 2025.4 the small ones are 2025.2
I'll update the system to check if I see the same behaviour
