Hot answers tagged symlink
From the ldd command it looks like the binary is looking in /lib/x86_64-linux-gnu and not /usr/lib/x86_64-linux-gnu where you found the symlink. Try running these and see if you still get the same error: sudo ln -s /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 /lib/x86_64-linux-gnu/libcrypto.so.6 sudo ln -s /lib/x86_64-linux-gnu/libssl.so.1.0.0 ...
The OS has permissions on the directories and if they don't permit a user to create anything in /etc it would be a security hole if some other mechanism would have the OS open other files than it thinks it is doing. (If the user has the permissions there is no need to fool the OS, then she can just change the files). That permissions on /etc are normally ...
Unless programs spend almost all their time to accede these files, this shouldn't be a problem. But I suggest that you test (possibly with a larger number of symlink indirections) and see if you can notice a loss of performance. FYI, Debian introduces at least 2 level of symlink indirections for common programs via /etc/alternatives, and I don't think ...
Or, simpler: ls -l | grep -v ^l
The first answer doesn't seem to adress the question, and the second one only applies to Apache. One thing I can think of for linux in general is that it's only possible for an ordinary user to make a hard link to a symbolic link if the user is the owner of the symbolic link. Why one would want to make such a link, I don't know. Another thing is that an ...
While replacing symbolic links to directories we should use -n option. Example: ln -sfn /path/to/directory /target/directory
Only top voted, non community-wiki answers of a minimum length are eligible