ArChatter

I just updated an ArchBang VM I have and I ran into, once again, the:

News: The /lib directory becomes a symlink

debacle. Yes, it’s been awhile since I tried updating. My main machine actually updated without a problem (at least until the hard drive died). The “easy way” failed. The “hard way” failed. Finally I just did the verboten -f and broke everything.

But I’m glad to report that not only did the process mentioned below work, it completely cleaned up my VM and now we’re on the straight and narrow, vis-a-vis /usr/lib:

/lib exists in filesystem when installing testing/glibc 2.16.0-2 (Page 1) / [testing] Repo Forum / Arch Linux Forums.