linux/fs/Kconfig.binfmt
<<
>>
Prefs
   1config BINFMT_ELF
   2        bool "Kernel support for ELF binaries"
   3        depends on MMU && (BROKEN || !FRV)
   4        default y
   5        ---help---
   6          ELF (Executable and Linkable Format) is a format for libraries and
   7          executables used across different architectures and operating
   8          systems. Saying Y here will enable your kernel to run ELF binaries
   9          and enlarge it by about 13 KB. ELF support under Linux has now all
  10          but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
  11          because it is portable (this does *not* mean that you will be able
  12          to run executables from different architectures or operating systems
  13          however) and makes building run-time libraries very easy. Many new
  14          executables are distributed solely in ELF format. You definitely
  15          want to say Y here.
  16
  17          Information about ELF is contained in the ELF HOWTO available from
  18          <http://www.tldp.org/docs.html#howto>.
  19
  20          If you find that after upgrading from Linux kernel 1.2 and saying Y
  21          here, you still can't run any ELF binaries (they just crash), then
  22          you'll have to install the newest ELF runtime libraries, including
  23          ld.so (check the file <file:Documentation/Changes> for location and
  24          latest version).
  25
  26config COMPAT_BINFMT_ELF
  27        bool
  28        depends on COMPAT && BINFMT_ELF
  29
  30config BINFMT_ELF_FDPIC
  31        bool "Kernel support for FDPIC ELF binaries"
  32        default y
  33        depends on (FRV || BLACKFIN || (SUPERH32 && !MMU) || C6X)
  34        help
  35          ELF FDPIC binaries are based on ELF, but allow the individual load
  36          segments of a binary to be located in memory independently of each
  37          other. This makes this format ideal for use in environments where no
  38          MMU is available as it still permits text segments to be shared,
  39          even if data segments are not.
  40
  41          It is also possible to run FDPIC ELF binaries on MMU linux also.
  42
  43config CORE_DUMP_DEFAULT_ELF_HEADERS
  44        bool "Write ELF core dumps with partial segments"
  45        default y
  46        depends on BINFMT_ELF && ELF_CORE
  47        help
  48          ELF core dump files describe each memory mapping of the crashed
  49          process, and can contain or omit the memory contents of each one.
  50          The contents of an unmodified text mapping are omitted by default.
  51
  52          For an unmodified text mapping of an ELF object, including just
  53          the first page of the file in a core dump makes it possible to
  54          identify the build ID bits in the file, without paying the i/o
  55          cost and disk space to dump all the text.  However, versions of
  56          GDB before 6.7 are confused by ELF core dump files in this format.
  57
  58          The core dump behavior can be controlled per process using
  59          the /proc/PID/coredump_filter pseudo-file; this setting is
  60          inherited.  See Documentation/filesystems/proc.txt for details.
  61
  62          This config option changes the default setting of coredump_filter
  63          seen at boot time.  If unsure, say Y.
  64
  65config BINFMT_SCRIPT
  66        tristate "Kernel support for scripts starting with #!"
  67        default y
  68        help
  69          Say Y here if you want to execute interpreted scripts starting with
  70          #! followed by the path to an interpreter.
  71
  72          You can build this support as a module; however, until that module
  73          gets loaded, you cannot run scripts.  Thus, if you want to load this
  74          module from an initramfs, the portion of the initramfs before loading
  75          this module must consist of compiled binaries only.
  76
  77          Most systems will not boot if you say M or N here.  If unsure, say Y.
  78
  79config BINFMT_FLAT
  80        bool "Kernel support for flat binaries"
  81        depends on !MMU && (!FRV || BROKEN)
  82        help
  83          Support uClinux FLAT format binaries.
  84
  85config BINFMT_ZFLAT
  86        bool "Enable ZFLAT support"
  87        depends on BINFMT_FLAT
  88        select ZLIB_INFLATE
  89        help
  90          Support FLAT format compressed binaries
  91
  92config BINFMT_SHARED_FLAT
  93        bool "Enable shared FLAT support"
  94        depends on BINFMT_FLAT
  95        help
  96          Support FLAT shared libraries
  97
  98config HAVE_AOUT
  99       def_bool n
 100
 101config BINFMT_AOUT
 102        tristate "Kernel support for a.out and ECOFF binaries"
 103        depends on HAVE_AOUT
 104        ---help---
 105          A.out (Assembler.OUTput) is a set of formats for libraries and
 106          executables used in the earliest versions of UNIX.  Linux used
 107          the a.out formats QMAGIC and ZMAGIC until they were replaced
 108          with the ELF format.
 109
 110          The conversion to ELF started in 1995.  This option is primarily
 111          provided for historical interest and for the benefit of those
 112          who need to run binaries from that era.
 113
 114          Most people should answer N here.  If you think you may have
 115          occasional use for this format, enable module support above
 116          and answer M here to compile this support as a module called
 117          binfmt_aout.
 118
 119          If any crucial components of your system (such as /sbin/init
 120          or /lib/ld.so) are still in a.out format, you will have to
 121          say Y here.
 122
 123config OSF4_COMPAT
 124        bool "OSF/1 v4 readv/writev compatibility"
 125        depends on ALPHA && BINFMT_AOUT
 126        help
 127          Say Y if you are using OSF/1 binaries (like Netscape and Acrobat)
 128          with v4 shared libraries freely available from Compaq. If you're
 129          going to use shared libraries from Tru64 version 5.0 or later, say N.
 130
 131config BINFMT_EM86
 132        tristate "Kernel support for Linux/Intel ELF binaries"
 133        depends on ALPHA
 134        ---help---
 135          Say Y here if you want to be able to execute Linux/Intel ELF
 136          binaries just like native Alpha binaries on your Alpha machine. For
 137          this to work, you need to have the emulator /usr/bin/em86 in place.
 138
 139          You can get the same functionality by saying N here and saying Y to
 140          "Kernel support for MISC binaries".
 141
 142          You may answer M to compile the emulation support as a module and
 143          later load the module when you want to use a Linux/Intel binary. The
 144          module will be called binfmt_em86. If unsure, say Y.
 145
 146config BINFMT_SOM
 147        tristate "Kernel support for SOM binaries"
 148        depends on PARISC && HPUX
 149        help
 150          SOM is a binary executable format inherited from HP/UX.  Say
 151          Y here to be able to load and execute SOM binaries directly.
 152
 153config BINFMT_MISC
 154        tristate "Kernel support for MISC binaries"
 155        ---help---
 156          If you say Y here, it will be possible to plug wrapper-driven binary
 157          formats into the kernel. You will like this especially when you use
 158          programs that need an interpreter to run like Java, Python, .NET or
 159          Emacs-Lisp. It's also useful if you often run DOS executables under
 160          the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
 161          <http://www.tldp.org/docs.html#howto>). Once you have
 162          registered such a binary class with the kernel, you can start one of
 163          those programs simply by typing in its name at a shell prompt; Linux
 164          will automatically feed it to the correct interpreter.
 165
 166          You can do other nice things, too. Read the file
 167          <file:Documentation/binfmt_misc.txt> to learn how to use this
 168          feature, <file:Documentation/java.txt> for information about how
 169          to include Java support. and <file:Documentation/mono.txt> for
 170          information about how to include Mono-based .NET support.
 171
 172          To use binfmt_misc, you will need to mount it:
 173                mount binfmt_misc -t binfmt_misc /proc/sys/fs/binfmt_misc
 174
 175          You may say M here for module support and later load the module when
 176          you have use for it; the module is called binfmt_misc. If you
 177          don't know what to answer at this point, say Y.
 178
 179config COREDUMP
 180        bool "Enable core dump support" if EXPERT
 181        default y
 182        help
 183          This option enables support for performing core dumps. You almost
 184          certainly want to say Y here. Not necessary on systems that never
 185          need debugging or only ever run flawless code.
 186