Salix Forums

All the commands in '/bin' are no longer available. System is now useless.
Guess there is something wrong with the new "libc-2.13-i486-6_slack13.37" slackware-13.37 provides. Or am I wrong?

Thank you for any hint on how to solve the problem.

I am not sure if it is the same problem, if it is then it is a big problem for the Salix OS distro. Maybe reinstalling the glibc package from a live CD would solve your problem [Salix-main] 13.37 i486: upgrade failed. Please wait for a Salix OS staff member for a solution!

George Vlahavas wrote:Start the system from another partition or the installation CD/live CD, mount the / partition somewhere and reinstall the glibc package:

Code: Select all

spkg --root=/mountpoint -u --reinstall /mountpoint/var/slapt-get/patches/packages/glibc-2.13-i486-6_slack13.37.txz

Edit: @SalixOS Perhaps you should confine critical packages such as glibc under the SalixOS repository while at the same time, blacklist glibc of other repositories, in order to avoid such cases.

zAchAry wrote:Maybe reinstalling the glibc package from a live CD would solve your problem

Luckily I am working with a LiveCD. So backgrading to glibc-2.13-i486-5_slack13.37 solves the problem for the time being.

Please wait for a Salix OS staff member for a solution.

Yes ...

Anyway thank you for kind reaction.

ikke wrote:All the commands in '/bin' are no longer available. System is now useless.
Guess there is something wrong with the new "libc-2.13-i486-6_slack13.37" slackware-13.37 provides. Or am I wrong?

A 13.37 LXDE fresh install is already with 2.13-i486-6-slack13.37 and a subsequent update/upgrade applies patches to that, the package name and version remains the same. I assume this is what I have been using the whole time now testing and have not had any problems.

Not an answer, but just what I see from my side, since I've been doing nothing but testing it seems lately.

sojurn wrote:A 13.37 LXDE fresh install is already with 2.13-i486-6-slack13.37 and a subsequent update/upgrade applies patches to that, the package name and version remains the same.

Thank you for this info. This looks very very strange to me...

Is there any difference between 'glibc' on the normal iso and the one on the LiveCD. Or between 'glibc' on Xfce and the one on LXDE. Will try to find out which version of 'glibc' is on the original Salix Live Xfce 13.37 iso which I am using most of the time. Guess it is 2.13-i486-4-slack13.37 but am not sure.

Updating was a nice experience up to now... Have made a special module to keep the updated packages.

Have to add that "Upgrading 'glibc' makes system useless'" happens on a LiveCD system (Salix Live Xfce 13.37) installed on a usb-stick. Updating via the graphical tool or via 'slapt-get' gives the same catastrophic result. Even 'shutdown' is no longer possible ...

Have also Salix Xfce 13.37 installed the normal way on a hard disk but am afraid to update now.

ikke wrote:...Is there any difference between 'glibc' on the normal iso and the one on the LiveCD. Or between 'glibc' on Xfce and the one on LXDE. Will try to find out which version of 'glibc' is on the original Salix Live Xfce 13.37 iso which I am using most of the time. Guess it is 2.13-i486-4-slack13.37 but am not sure.

Have to add that "Upgrading 'glibc' makes system useless'" happens on a LiveCD system (Salix Live Xfce 13.37) installed on a usb-stick. Updating via the graphical tool or via 'slapt-get' gives the same catastrophic result. Even 'shutdown' is no longer possible ...

Have also Salix Xfce 13.37 installed the normal way on a hard disk but am afraid to update now.

You could always just image it first, then nothing can go wrong.

I don't know enough to answer (and lxde only has an install CD, no live CD), although it sounds like the usb installation somehow. It got me wondering myself about the iso's from the download page, if they ever change for example (?). I would have grabbed the copy I just used for testing shortly after it came out (roughly a year ago), and the xfce live CD is newer, not older, than that.

ikke wrote:All the commands in '/bin' are no longer available. System is now useless.

If this happens: Don't log out, run ldconfig.

thenktor wrote:

ikke wrote:All the commands in '/bin' are no longer available. System is now useless.

If this happens: Don't log out, run ldconfig.

There should be a component that will identify such problems and will correct them automatically. It is unfortunate that because of situations like this (the glibc issue is the only one that I know) users may leave Salix OS.

thenktor wrote:

ikke wrote:All the commands in '/bin' are no longer available. System is now useless.

If this happens: Don't log out, run ldconfig.

Did as you told me to do.

Then made a module of all the updates : 'updates.salt'. When booting got a lot of error messages concerning missing groups. Couldn't reach X because the "gdm" group was also missing.
When trying

startx

as root I got even a very kind message from Salix "Go away!". Wondering who put it there and why? Because I am so stupid?? Should I stop using Salix?

Thank you for any hint.

zAchAry wrote:

thenktor wrote:

ikke wrote:All the commands in '/bin' are no longer available. System is now useless.

If this happens: Don't log out, run ldconfig.

There should be a component that will identify such problems and will correct them automatically. It is unfortunate that because of situations like this (the glibc issue is the only one that I know) users may leave Salix OS.

Kindly read my previous message. Salix told me to go away. Am wondering ...