[SOLVED] Strange problem: /usr/lib64/ - Not a Directory
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hello there. I've been experimenting with Arch Linux in VirtualBox to test out this pretty useful software. Whilst trying to get 3d acceleration working I checked for the existence of /usr/lib64/VBoxOGL.so and, to my astonishment, lib64 is there, but it's "Not a directory".
Has anyone ever come across something like this? I'm not sure when exactly this happened or whether its always been a file. Ever heard of a directory turning into a file?
Getting it fixed isn't too important since it's practically a fresh install, but I think it's important to find out why this has happened...
I guess that means some manual action or script tried to copy a .so file into /usr/lib64 but /usr/lib64 didn't exist, so it copied that .so to rather than into /usr/lib64
I don't know whether Arch Linux is supposed to have a /usr/lib64. Do you know whether Arch Linux is "multi lib"? Also, your whole question assumes you are using a 64 bit build of Arch Linux. If it were 32 bit, then it isn't multi lib and /usr/lib64 shouldn't exist. Please confirm that you are talking about a 64 bit build of Arch Linux.
Yes, it's a 64 bit arch kernel on a 64-bit VM with a 64-bit Host. I suspect perhaps the Guest Additions may be at fault here, attempting to install into lib64. I'm just installing a fresh Arch64 onto another disk and will have a look at lib64 there...
As for multilib, I haven't installed 32-bit libraries, though I know some people do in Arch. I don't know where these end up though.
Right, on a fresh install, /usr/lib64 does not exist, despite being a 64-bit system. What should I do about this to ensure that installers (e.g. vbox guest additions) are able to put things in the right place? Thanks for your help.
Ok, so I fixed the problem for VBox GA by symlinking /usr/lib64 to /usr/lib as you said debian did and this fixed the problem in this instance. No need to continue that fresh installation, thanks a lot!