Kconfig.binfmt 7.2 KB

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