After downloading iso i did new installation of 14.2 from usb .
Then i did slackpkg update and upgrade-all .

One of the packages to be upgraded must have some error like :
line 499 and 501 or 511 error and some library missing .

There is not enough time to see what package caused the error as upgrade is running to fast .
As a result /bin/bash is declared as missing and system becomes unreachable and not booting .
But /bin/bash exists with details 1164640 bytes Aug 30 21:29 .

After a second installation of 14.2 i tried for a third time update and upgrade-all so i got the same error .
So for another time i cannot boot and i am sending this from usb booted Porteus .

By searching /var/log/packages/ it seems that the last package to be upgraded was glib-solibs-2.23-x86_64-4_slack14.2 .
I don't know if is that that causes the error .

I tried to recreate error from Porteus bash to /mnt/sdb2 (14.2 root):
find . -type f -name slackpkg > ./usr/sbin/slackpkg (so it exists)
chroot /mnt/sdb2 /usr/sbin/slackpkg upgrade-all >
chroot: failed to run command ‘/usr/sbin/slackpkg’: No such file or directory

How can i reverse the error without new installation as chroot not working ?
Am i the only with this error ?

thanks in advance for any help

I'm pretty sure that the missing library is glibc-solibs, not glib-solibs. glib, like most Slackware libraries comes in a complete package, i.e. runtime library plus headers. The only libraries as far as I know that come in solibs (runtime only) packages are glibc and openssl.

Unfortunately glibc is the package that everything else uses, including bash. The only way I can think of to fix this would be to boot from a rescue disc, download glibc-solibs from a mirror and try to install it by running upgradepkg from the Slackware root partition. This is a script, not a program, so it should run if you use your rescue image's bash rather than trying to chroot. I'm not sure though how you would ensure that it gets installed to your hard drive's root partition without chrooting. Hopefully someone else can tell you that.

Thanks for your help .
I will try to do full metal restore .
I am afraid that this glib-solibs package has some error because this happend twice and that can happen to someone else .

@costasdk, your typing habit still seems to be "glib-solibs", not "glibc-solibs".

It's "glibc" you're looking for. Yes, typing that little "c" can make a big difference.

@costasdk

On your first Slackware 14.2 update, follow what I presented in these two posts ( I'm too lazy to rewrite the hints only for you ):

https://www.linuxquestions.org/quest...ml#post6081349

https://www.linuxquestions.org/quest...ml#post6081373

Did you telinit 1 before upgrade?

I'd have a look to UPGRADE.TXT before anything. Even if it's for upgrading from another version, it shows the safe way. I used to do that whenever a sensible package had to be upgraded.