Renamed /lib (following advice in a BB) and now nothing works
 

This is making me crazy (not to mention, look terrible). Following in structions in a BB thread, trying to fix an original problem with system-config-xxxx commands not working, I renamed /lib to /lib~. Now nothing works. Even the mv command to rename the folder back as it should be is broken.

How can I dig myself out of this hole without reinstalling?

-sf

that shouldn't happen, what error do you get when you run 'mv'?

Boot a rescue CD and rename /lib~ back to /lib.

------------------
Steve Stites

boot up a livecd and fix it, next time don't rename any of the top level directories

Renamed /lib (following advice in a BB) and now nothing works
 

Thanks for all the help, guys. I was having a stupid time trying to get the RAID drivers to work on a boot CD, so I gave up. Fortunately there was a recent content backup, so I was forced to rebuild and restore.

Lesson learned!

Indeed, a live CD is the best solution.

BTW, where is this post you speak of, I want to see it. The advice you followed is quite dangerous, you should NEVER rename any top-level directory, EVER. There can be no justification for doing this, basically it is madness to do this, unless you (not specifically 'you') want to break stuff on purpose.