11-18-2008
Naming conventions for shared libraries in Linux
Hello,
I'm wondering what is the naming conventions for *.so shared libraries in linux. For example, a library in /lib, say libcrypt-2.7.so has a symbolic link called libcrypt.so.1 pointing to it, yet libncursesw.so.5.6 has a symbolic link called libncursesw.so.5 pointing to it. What is the relationship between the numbers in the symbolic links and the actual targets?
10 More Discussions You Might Find Interesting
1. Programming
Hello everybody,
I am having major problems at the moment with shared libraries and I have to little knowledge of them to solve them. So please, please help me :)
Ok this is the problem:
I have a library A, which uses B and C, and C uses again D.
If I try to run A as plugin in apache,... (0 Replies)
Discussion started by: Micky
0 Replies
2. Programming
I am compiling code which produces .a and .la libraries. How can I produce .so libraries? I know that gcc -shared does but how? (2 Replies)
Discussion started by: thalex
2 Replies
3. Linux
How do i make a library shared
say i have a library a.so which i have just compiled.
I want to make it shared how do i make it
Next Queation is what is the difference between a.so.0 a.so.1 a.so.2 & a.so :rolleyes: (1 Reply)
Discussion started by: wojtyla
1 Replies
4. Programming
anybody knows how to view loaded shared libraries by running processes in linux enviornment? any command or tool ?
thanks a lot (3 Replies)
Discussion started by: princelinux
3 Replies
5. UNIX Desktop Questions & Answers
Hi All,
I need to know standard naming convention for Unix libraries (including all flavours of unix)..As I have gone through some sites and found out
The UNIX convention for naming of libraries is
lib<name>.so.<major>.<minor>.<revision>
so is it statndard . also does it change... (0 Replies)
Discussion started by: rkshukla14
0 Replies
6. UNIX for Advanced & Expert Users
can someone explain whether my understanding is correct
lets suppose we have a program that uses library x.
if x is static then the code of x will be part of our program, so if we're going to have 5 executables of our program, then each executable will have x as part of it.
Also, x does not... (2 Replies)
Discussion started by: JamesByars
2 Replies
7. Solaris
These are findings by me with my little experience with Solaris 10. Please correct me if wrong..
In x86 systems with ide hard disk:
c= controller
d=disk
s=slice
1.Here controller c0 means the primary ide controller ide0.
controller c1 means the secondary ide controller ide1.
... (5 Replies)
Discussion started by: saagar
5 Replies
8. Solaris
Hi all,
Is there anyway i can control the naming of the disk device ?
I have added an iscsi disk on server1 using iscsiadm , devfsadm and it is now showing as
/dev/dsk/c2t0d0 in node1
However, i am worried that the same disk will appear as
/dev/dsk/cXtXd0 in node2
This iscsi disk(lun)... (0 Replies)
Discussion started by: javanoob
0 Replies
9. Programming
This is the first time that I created a dynamic library in linux and although the program works, I do not get the correct information about the library when executing ldd.
I explain the details:
1) Source code:
bye_fn.c:
#include <stdio.h>
#include "hello.h"
void bye (const char*... (9 Replies)
Discussion started by: jose_spain
9 Replies
10. Cybersecurity
Hey guys, not sure should I post it here or in 'What is on Your Mind?'
I'm discussing usage of DSL (domain specific language) in security tools with my colleagues. We haven't been able to reach an agreement over naming conventions.
There are many tools using DSL: splunk, sumologic,... (2 Replies)
Discussion started by: Tobby P
2 Replies
LEARN ABOUT XFREE86
git-symbolic-ref
GIT-SYMBOLIC-REF(1) Git Manual GIT-SYMBOLIC-REF(1)
NAME
git-symbolic-ref - Read, modify and delete symbolic refs
SYNOPSIS
git symbolic-ref [-m <reason>] <name> <ref>
git symbolic-ref [-q] [--short] <name>
git symbolic-ref --delete [-q] <name>
DESCRIPTION
Given one argument, reads which branch head the given symbolic ref refers to and outputs its path, relative to the .git/ directory.
Typically you would give HEAD as the <name> argument to see which branch your working tree is on.
Given two arguments, creates or updates a symbolic ref <name> to point at the given branch <ref>.
Given --delete and an additional argument, deletes the given symbolic ref.
A symbolic ref is a regular file that stores a string that begins with ref: refs/. For example, your .git/HEAD is a regular file whose
contents is ref: refs/heads/master.
OPTIONS
-d, --delete
Delete the symbolic ref <name>.
-q, --quiet
Do not issue an error message if the <name> is not a symbolic ref but a detached HEAD; instead exit with non-zero status silently.
--short
When showing the value of <name> as a symbolic ref, try to shorten the value, e.g. from refs/heads/master to master.
-m
Update the reflog for <name> with <reason>. This is valid only when creating or updating a symbolic ref.
NOTES
In the past, .git/HEAD was a symbolic link pointing at refs/heads/master. When we wanted to switch to another branch, we did ln -sf
refs/heads/newbranch .git/HEAD, and when we wanted to find out which branch we are on, we did readlink .git/HEAD. But symbolic links are
not entirely portable, so they are now deprecated and symbolic refs (as described above) are used by default.
git symbolic-ref will exit with status 0 if the contents of the symbolic ref were printed correctly, with status 1 if the requested name is
not a symbolic ref, or 128 if another error occurs.
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-SYMBOLIC-REF(1)