So, CentOS didn’t work for me

Not long ago, I decided to install CentOS on my PC. CentOS isn’t quite made for desktop purposes, but it’s stability still drawed me to install it with Gnome 2 (I really hate Gnome 3).

After setting up the OS and installing the latest driver for my NVIDIA GTX770, it ran absolutely beautiful. But…

I decided that I would give Steam a try on Centos. Actually it’s not officially builded for RHEL, but deb package could be converted into an working RPM. So far so good. The only problem was – and this is where CentOS comes to its limits as Desktop OS – the Steam RPM required glibc > 2.15 and CentOS only comes with 2.12. But why should that stop me? I searched for some RPM’s containing a newer glibc, but I couldn’t find anyone that I would rely on. So, I decided to get the source and compile it myself.

I downloaded glibc 2.19 – currently the latest version – and began my adventure. Actually everything went very well, I got it configured and installed. However, it created a new in /lib64 but it didn’t change the symbolic link /lib64/ to the new version. And this is where I did a fatal mistake.

Instead of re-creating the symbolic link, I (perhaps I was too tired?) moved the existing /lib64/ to /tmp. This doesn’t seem that fatal, does it? Do yourself a big favor and DON’T try to do so.

As sonn it was moved, I couldn’t do anything. And I mean anything. No commands was working, I couldn’t even do ls, ln or anything. I closed the terminal to go online and read about the file and what to do. But Google Chrome wouldn’t open. Now I began to realize how fatal it was. I then tried to open the terminal again. No luck.

Okay, but I could change to another shell by pressing <ALT>+F1 (or something). As supposed, I now got another shell and was asked to authenticate myself. But after entering the username, I was just promted for login again.

I now decided to reboot, which resultet in a kernel crash while booting. Luckely I still got my Windows 8 partition, which I started up. From Windows I was able – via some program – to mount and edit the partition where CentOS was located. Since it was a symbolic link I moved to /tmp, I couldn’t copy/paste it to /lib64 again. And I couldn’t make a new symbolic link.

So I decided to copy the new to – that should work, I thought.

Well, the kernel panic was solved, but now CentOS complained about multiple other errors. That’s it, I don’t wanna use anymore time on it, I’m going for a new install.

But this time I try openSUSE instead. That should give me some more updated packages to play with. :-)

Leave a Reply