slackware issue on upgrade of kernel.....

i had blacklisted the kernel yesterday but i just wanted the new kernel and did a full system upgrade....and i got this error when slackpkg ran lilo...havent restarted my system yet as i know i would hit kernel panic mode....
why is the file missing?
and which is the package i should get it from?

kindly note i havent installed any files beginning with k during slackpkg install-new step.....since i suspect its for KDE and so i dont want it...correct me if am wrong....

Your Current system is not up to date. You are missing the upgrade to glibc-2.22 provided since Fri Aug 21 21:17:48 UTC 2015.

See the Changelog.

If you run Current you should check the ChangeLog frequently and make sure all updates are done successfully.

Not all packages that have names beginning with "k" are KDE-related. In particular, you'd certainly want to install/upgrade the kmod package, and probably kbd as well.

Is this really related to the OP's question? Or maybe wrong thread?

@Didier: what if all updates aint succesful? like this time round?

having to re-run the whole procedure would work?

kindly note i have blacklisted slackbuilds, alien bobs files and compat32 files....


if i run the whole procedure again would it help?

I was referring to this:
I probably should have started my first sentence with the word "additionally" though, because as you say, it isn't related to the glibc error.

Sorry, but having answered in several similar threads of yours my advice is: wait until you be more acquainted with Slackware to use -current. Especially as going multilib needs even more care to keep your system up to date. And not doing so you will spend more time repairing what's broken (if possible) than actually using your system.

@didier: yes same thoughts racing through my head too...stick on to stable for now before i jump to current...current requires lots of homework and maybe i need to wait a little more...going to 14.1 for now....

As said before, there's a few files to check before going -current. The docs.slackware.com related pages are a good start and I believe the way to do things right. There's something related to your problem at the very beginning...

The 'k' package series is kernel source. You would want the corresponding source for your kernel IF you intend to compile external kernel modules (e.g. VirtualBox, Nvidia, AMD Catalyst) The 'KDE' package series will have a lot of packages that start with k but there are others like kmod (from the 'a' package series) that you do need.

I can't see it being practical to blacklist things by the first letter of package filenames, rather, it would be better to just not have any of the KDE series installed if you don't want those packages getting installed/upgraded. You still might need the qt library though but that is in package series l.

One rule of thumb... if you are going to try your luck upgrade things piecemeal from Slackware-current, at least upgrade glibc first.

glibc-solibs from package series a
glibc-zoneinfo from a
glibc from l
glibc-i18n from l

If you have installed glibc-debug or glibc-profile you should upgrade those too. (or removepkg them first... they aren't normally needed)

You can put packages in a directory, drop down to runlevel 1 and cd into the directory and:

upgradepkg --reinstall --install-new *.txz

(--reinstall --install-new switches aren't necessary in an upgradepkg command if you're sure the packages are all installed, and do not have identical version names)

Reboot normally, as soon as that completes. (ctrl-alt-del is fine if your shell has crashed or anything)

Glibc is serious stuff and can leave you dead in the water if you do not upgrade it correctly. Generally, upgrading to NEWER glibc packages is safe. (Right now it should be, anyway)

I get that you (the original poster) have decided to just stick with stable but it's still best to know what's going on.

Do you have Alien Bob's multilib packages installed? You probably need to simply update the multilib GLIBC package - but you should update all of the multilib packages.

Your error from lilo looks just like the one that I received when I tried updating the kernel without first updating the multilib/compat32 files.

-Lirey

thanks everyone...but i went back to 14.1...and now running stable....

@TheRealGrogan: that was informative...thanks...i missed some libraries frankly cos i assumed k is for kde only...i see my mistakes now...

@lirey: i had alienbob multilib packages installed...but i had blacklisted them during my update this time round...maybe it was all to just update glibc...but maybe when i go current again,,,,for now sticking on to stable 14.1 till i get a better hang of it...

since am in stable 14.1 now, a system upgrade should be fairly easy right? no checks required i assume?

This is the "tried-and-true" method for upgrading Slackware: UPGRADE.TXT. You can use slackpkg for this as well, but it's usually safer to upgrade according to that file. If you run multilib, you need to skip the gcc/glibc packages, and install/upgrade them from Alien BOB's multilib instead. CHANGES_AND_HINTS.TXT shows what packages have been added or removed since the last release. Added packages are automatically installed if upgrading via UPGRADE.TXT, but obsolete packages need to be removed manually.

Sorry, I hadn't considered multilib (It's not the problem in itself... it's clearly the wrong glibc symbols for the 64 bit libdevmapper) but it is different glibc packages you are supposed to have because the dynamic linker is different on the multilib distro. That could be the reason you didn't get the glibc 2.22 packages in your slackpkg upgrade. (and that was probably a good thing)

I haven't used slackpkg or alienbob's multilib so I'm a bit out of the loop. Fortunately others picked up on that clue.

maybe i had to rephrase better but thanks lems...

correct me if am wrong: instead of using slackpkg to update or upgrade, regardless of slackware upgrading to new release(version change) or system updates(for patches) i need to follow the text files you gave right?