Yes but --

When the kernel packages are updated in the /patches branch, both the generic and huge kernels are updated. As the update process usually is alphabetical, and the letter h comes after the letter g, the huge kernel package is updated after the generic package.

Both package doinst.sh scripts modify the vmlinuz sym link. Thus the huge kernel modifies the sym link last.

The problem could be resolved by removing and not updating the huge package. That is doable. I like to keep the huge package installed as an emergency boot kernel, but that is not a requirement.

The problem can be resolved by using the full file name in grub.cfg. That avoids using the vmlinuz sym link. This is what I have done for many years. When the kernel packages are updated in the /patches branch I update grub.cfg with a sed command and reboot. Unlike lilo, GRUB does not require any compiling after editing grub.cfg.

I block automatic updates of the kernel in the slackpkg configuration. That way there are no surprises. Actually I use a shell script to install new kernels because when I update kernels I like to keep the old version for some days as an emergency backup.

There has been some discussion in this forum about removing the huge package altogether, but only discussion. My opinion only, but I like the idea of eliminating huge. I don't think any other distro maintains a "huge" kernel.

There is a /boot/vmlinuz-generic that is a symlink to the generic kernel that can be used in a grub menu entry

I delete the symlinks as part of my kernel management script. That way, grub picks up the full kernel description & version and displays in the in the menu. Useful if you have multiple kernel versions installed. Whether this is adverse in any way, is unknown to me (as in other programs searching for /boot/vmlinuz etc.) but has worked well for me over the past year. It gives a nice clean and descriptive grub menu. Probably a better way to do it, is to modify my grub script to ignore the symlinks.