A few weeks ago I made my slack64-current multilib. As per tutorial I blacklisted glibc and gcc in /etc/slackpkg/blacklist:
# run "lilo" after upgrade). If you think the same, uncomment the lines
# aaa_elflibs can't be updated.
# Now we can
When I did slackpkg update and upgrade-all
I got all the gcc* glibc* kernel* packages available for an upgrade. What am I doing wrong?
If I actually upgrade the kernel that way and then run lilo, will it keep the lilo.conf entry of the old kernel? Will it remove the old kernel from the system?