During swaret upgrade the bin package got corrupted and i cant restore it from the cd because i cannot log in either as a user or root


Someone could suggest a solution for my problem because reinstall Slackware for sich a sniky error

Start from Slackware CD. Create mount points for your partitions in /mnt and mount them. Your CD should be mounted at /cdrom already. Then use "installpkg -root /mnt /cdrom/slackware/a/bin-11.0-i486-3.tgz" to restore the original Slack 11.0 bin package.

Hi

I mounted my cdrom under /usr and my root partition under /mnt

i tried the command you suggested as usual i installed the package but still couldnt login
and same error prompts

any other suggestion ?

Perhaps you need to re-install coreutils also.

Regards

Hi Bathony

I did re-install the coreutils but im still getting the same error

what i do after loading the cd 1 is:

mount /dev/hda1 /mnt root partition
mount /dev/hdb /usr cdrom

installpkg -root /mnt /usr/slackware/l/*.tgz


additionally i reinstalled glibc 2.4 the one coming with slackware 11 since the error message points me there.

regards

Then you should downgrade bash in order to be able to login again. Then install first the required libraries (glib and glibc) and then the programs that are compiled against these libraries (binutils, bash, etc)
I think that you need to create a new mountpoint to mount your root partition and not use /usr and/or /mnt that already exist.

As the Slackware install CD tells you, do not directly mount any file systems under any of the existing directories from the boot CD (I.E. /mnt), create new directories under /mnt to mount your devices.

This is what happens when you use unsupported third party automatic dependency resolution tools without understanding their limitations. You have failed to upgrade the glibc-solibs package before upgrading essential system binaries, and since the new binaries that you've installed need the new C library, you have a non-functional system. In the future, be sure to read the CHANGES_AND_HINTS.TXT and UPGRADE.TXT files and do a bit of pre-upgrade research of the forums - you could have saved yourself all this trouble.

In the meantime, there are at least three other recent threads with information on how to recover from this error.

RW