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
ln(1) General Commands Manual ln(1)
Name
ln - link to a file
Syntax
ln [ -f ] [ -i ] [ -s ] name1 [name2]
ln [ -f ] [ -i ] [ -s ] name ... directory
Description
A link is a directory entry referring to a file. A file, together with its size and all its protection information may have several links
to it. There are two kinds of links: hard links and symbolic links.
By default makes hard links. A hard link to a file is indistinguishable from the original directory entry. Any changes to a file are
effective independent of the name used to reference the file. Hard links may not span file systems and may not refer to directories.
Given one or two arguments, creates a link to an existing file name1. If name2 is given, the link has that name. The name2 may also be a
directory in which to place the link. Otherwise it is placed in the current directory. If only the directory is specified, the link is
made to the last component of name1.
Given more than two arguments, makes links to all the named files in the named directory. The links made have the same name as the files
being linked to.
Options
-f Forces existing destination pathnames to be removed before linking without prompting for confirmation.
-i Write a prompt to standard output requesting information for each link that would overwrite an existing file. If the response from
standard input is affirmative, and if permissions allow, the link is done. The -i option has this effect even if the standard input is
not a terminal.
-s Creates a symbolic link.
A symbolic link contains the name of the file to which it is linked. The referenced file is used when an operation is performed on
the link. A on a symbolic link returns the linked-to file. An must be done to obtain information about the link. The call may be
used to read the contents of a symbolic link. Symbolic links may span file systems and may refer to directories.
See Also
cp(1), mv(1), rm(1), link(2), readlink(2), stat(2), symlink(2)
ln(1)