Re: "/lib/ld-linux.so.2 /usr/bin/emacs" fails: "Memory exhausted"

[Mark Seaborn <mseaborn@onetel.com>]

"Richard M. Stallman" <rms@gnu.org> wrote:

> I don't know anything about what's happening here; I am not sure
> what ld-linux.so.2 does in the first place, or whether that ought
> to work, or what it ought to do.

ld-linux.so.2 is the dynamic linker on GNU/Linux:

  $ /lib/ld-linux.so.2 
  Usage: ld.so [OPTION]... EXECUTABLE-FILE [ARGS-FOR-PROGRAM...]
  You have invoked `ld.so', the helper program for shared library executables.
  This program usually lives in the file `/lib/ld.so', and special directives
  in executable files using ELF shared libraries tell the system's program
  loader to load the helper program from this file.  This helper program loads
  the shared libraries needed by the program executable, prepares the program
  to run, and runs it.  You may invoke this helper program directly from the
  command line to load and run an ELF executable file; this is like executing
  that file itself, but always uses this helper program from the file you
  specified, instead of the helper program file specified in the executable
  file you run.  This is mostly of use for maintainers to test new versions
  of this helper program; chances are you did not intend to run this program.
  
    --list                list all dependencies and how they are resolved
    --verify              verify that given object really is a dynamically linked
                          object we can handle
    --library-path PATH   use given PATH instead of content of the environment
                          variable LD_LIBRARY_PATH
    --inhibit-rpath LIST  ignore RUNPATH and RPATH information in object names
                          in LIST

Plash uses a modified version of the dynamic linker, so it launches
programs by invoking ld-linux.so.2 directly.  It also does this as a
technique for exec()'ing an executable from a chroot() jail without
the executable having to be inside the jail.

Mark