Salix Forums

Try running lilosetup from the command line to see more messages:

Akuna wrote:Did you check the partition to ensure nothing has been erased (i.e. in /boot)?

Mount sda1 and check if the file /sbin/init is there and executable.

Nothing has been erased as far as I can tell. /sbin/init is there in sda1. lilosetup.py did not produce anything different ...no extended verbiage or anything. Now my friend is saying that they applied all updates before rebooting So, the story changed and the truth came out. Can you provide further guidance? Now I'm thinking something in the updates screwed up the system. How can we track that down?

Boot with live medium, mount sda1 to /mnt/sda1 and run "ldconfig -r /mnt/sda1". Maybe this helps.

EDIT: Or try to reinstall latest glibc packages: "spkg --root=/mnt/sda1 -u --reinstall /mnt/sda1/var/slapt-get/patches/glibc..."

I tried running that command to upgrade/reinstall glibc but it says file does not exist. Is that the correct command? The reason I ask is that when I go into that directory and do ls I see glibc in there. I see glibc-2.13-x86_64-6_slack13.37.txz. running ldconfig now.

ldconfig did not correct the error. Still recieving the same error as originally reported.

mpadilla2 wrote:I tried running that command to upgrade/reinstall glibc but it says file does not exist. Is that the correct command? The reason I ask is that when I go into that directory and do ls I see glibc in there. I see glibc-2.13-x86_64-6_slack13.37.txz. running ldconfig now.

Of course you have to expand that command by the glibc file name you have in that directory

.../patches/packages/glibc...

I tried the command again and this time it starts to act like it's going to reinstall...then I get the following:

What command exactly did you enter?