ld-linux.so.2 dynamic linker

[manfree]

Hi all,

What does it mean with the following command?
Seems it just display the files in /tmp only?
but somebody says that this is related with the dynamic linker
Anybody could help ?
thanks

[Fedora pub]# /usr/lib/ld-linux.so.2 /bin/ls -l /tmp
total 6808
-rw------- 1 sam sam 2785564 Aug 17 21:40 FlashjAvNbc
drwx------ 2 root root 4096 Aug 18 21:14 gconfd-root
drwx------ 3 sam sam 4096 Aug 18 17:54 gconfd-sam
drwx------ 2 sam sam 4096 Aug 17 21:04 keyring-73s7mW
drwx------ 2 sam sam 4096 Aug 18 17:54 keyring-guwnBR
srwxr-xr-x 1 root root 0 Aug 18 02:05 mapping-root
srwxr-xr-x 1 sam sam 0 Aug 18 17:54 mapping-sam
drwx------ 2 root root 4096 Aug 18 21:14 orbit-root
drwx------ 2 sam sam 4096 Aug 19 00:20 orbit-sam
drwx------ 2 sam sam 4096 Aug 17 20:22 plugtmp
drwx------ 2 sam sam 4096 Aug 17 21:51 plugtmp-1
-rw------- 1 sam sam 5336 Aug 17 21:38 plugtmp-1-1
drwx------ 2 sam sam 4096 Aug 18 21:23 plugtmp-2
drwx------ 2 sam sam 4096 Aug 18 17:54 ssh-dMQdEM2276
-rw-r--r-- 1 sam sam 4046481 Aug 17 20:07 tmp.xpi
drwx------ 2 sam sam 4096 Aug 18 17:54 virtual-sam.FdzK87
drwx------ 2 sam sam 4096 Aug 17 21:04 virtual-sam.XaWcQD

[Rubberman]

From the ld-linux.so man page:

LD.SO(8)                   Linux Programmer’s Manual                  LD.SO(8)

NAME
       ld.so, ld-linux.so* - dynamic linker/loader

DESCRIPTION
       The programs ld.so and ld-linux.so* find and load the shared libraries needed
       by a program, prepare the program to run, and then run it.

       Linux binaries require dynamic linking  (linking  at  run  time)  unless  the
       -static option was given to ld during compilation.

       The  program  ld.so  handles  a.out  binaries,  a  format  used long ago; ld-
       linux.so* handles ELF (/lib/ld-linux.so.1 for libc5,  /lib/ld-linux.so.2  for
       glibc2),  which  everybody has been using for years now.  Otherwise both have
       the same behaviour, and use the  same  support  files  and  programs  ldd(1),
       ldconfig(8) and /etc/ld.so.conf.

       The  shared  libraries  needed  by  the  program  are searched for in various
       places:

       o      (ELF only) Using the DT_RPATH dynamic section attribute of the  binary
              if  present  and DT_RUNPATH attribute does not exist.  Use of DT_RPATH
              is deprecated.

       o      Using the environment variable LD_LIBRARY_PATH.  Except  if  the  exe-
              cutable  is  a  set-user-ID/set-group-ID  binary,  in which case it is
              ignored.

       o      (ELF only) Using the  DT_RUNPATH  dynamic  section  attribute  of  the
              binary if present.

       o      From the cache file /etc/ld.so.cache which contains a compiled list of
              candidate libraries previously found in the  augmented  library  path.
              If,  however,  the  binary  was linked with -z nodeflib linker option,
              libraries in the default library paths are skipped.

       o      In the default path /lib, and then /usr/lib.  If the binary was linked
              with -z nodeflib linker option, this step is skipped.

SYNOPSIS
       The  dynamic linker can be run either indirectly through running some dynami-
       cally linked program or library (in which case no command line options to the
       dynamic  linker  can be passed and, in the ELF case, the dynamic linker which
       is stored in the .interp section of the program is executed) or  directly  by
       running:

       /lib/ld-linux.so.*  [OPTIONS] [PROGRAM [ARGUMENTS]]

As you note in the SYNOPSIS, normally this is executed automatically by an executable. In fact, I have never used the dynamic linker directly myself.

So, to answer your question, what you did is the same as "/bin/ls -l /tmp" by itself.