![](https://seccdn.libravatar.org/avatar/b12cfb65ca4faebc3e3aac17838e8f8d.jpg?s=120&d=mm&r=g)
On Wednesday 23 May 2007 09:24, Denis Silakov wrote:
Randall R Schulz wrote:
What kind of bug do you suspect? Is anything malfunctioning?
Almost all Linux executables have at least one dynamically linked library, the one that allows system calls to be made. Most are fully dynamically linked.
Well, I see. Surely, there is no malfunctioning here.
The thing is that we are collecting information about different distributions for the Linux Standard Base -
https://www.linux-foundation.org/dbadmin/browse/distr.php
and in the LSB there are 'Libraries' (system-wide shared libraries) and there are 'Commands' (for example, different utilities). All distribution data is collected automatically, but I don't see at the moment how to distinguish LSB commands from LSB libraries. The idea was to use `file` output, but very often it reports 'shared object' for files which we'd like to add as commands...
Well, in nearly (entirely?) all cases, a file that's really meant to be used as the target of dynamic linking as a shared library will be named with the suffix ".so" followed optionally by some version suffixes of the form (as an extended regular expression, enclosing quotation marks excluded) "(\.[0-9]+)+". I believe kernel module share the same file format, but are named with a .ko suffix. I should state that my information on these topics might be a bit dated, so you might want to verify it, but it's at least approximately accurate.
-- Regards, Denis.
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org