ls: error while loading shared libraries: libacl.so.1:
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
You might have some trouble finding repositories for RHEL 4.
I'm not sure yum was installed by default on RHEL 4 either (but it might depend on which release). I find that it was not available for 4.0, but was ported to 4.9 so it depends on how uptodate the release is as to whether a historical repository will have it.
I found this discussion on installing yum on a 4.0 saying it wasn't available until it was backported to 4.7/4.8/4.9, but still recommended using "uptodate".
Hi. żDo you erase link libacl.so.1? Sometimes libacl.so or libacl.so.0 (or so.1) is a link to the file libacl.so.1.x.x. When you update the system, may be erased the link and cant put a new one. Or the link continue and the system erase old library and dont change the link.
Another problem may be a diferent 'ls' which need so.1.x.x but the system have so.0.x.x or s.2.x.x
Take a look at the /lib and /usr/lib directories. Sometimes special libraries files were on special directories under /lib/i486 /lib/i686 or /lib/i486-linux-gnu , etc.