Back to home page

LXR

 
 

    


0001 config BINFMT_ELF
0002         bool "Kernel support for ELF binaries"
0003         depends on MMU && (BROKEN || !FRV)
0004         select ELFCORE
0005         default y
0006         ---help---
0007           ELF (Executable and Linkable Format) is a format for libraries and
0008           executables used across different architectures and operating
0009           systems. Saying Y here will enable your kernel to run ELF binaries
0010           and enlarge it by about 13 KB. ELF support under Linux has now all
0011           but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
0012           because it is portable (this does *not* mean that you will be able
0013           to run executables from different architectures or operating systems
0014           however) and makes building run-time libraries very easy. Many new
0015           executables are distributed solely in ELF format. You definitely
0016           want to say Y here.
0017 
0018           Information about ELF is contained in the ELF HOWTO available from
0019           <http://www.tldp.org/docs.html#howto>.
0020 
0021           If you find that after upgrading from Linux kernel 1.2 and saying Y
0022           here, you still can't run any ELF binaries (they just crash), then
0023           you'll have to install the newest ELF runtime libraries, including
0024           ld.so (check the file <file:Documentation/Changes> for location and
0025           latest version).
0026 
0027 config COMPAT_BINFMT_ELF
0028         bool
0029         depends on COMPAT && BINFMT_ELF
0030         select ELFCORE
0031 
0032 config ARCH_BINFMT_ELF_STATE
0033         bool
0034 
0035 config BINFMT_ELF_FDPIC
0036         bool "Kernel support for FDPIC ELF binaries"
0037         default y
0038         depends on (FRV || BLACKFIN || (SUPERH32 && !MMU) || C6X)
0039         select ELFCORE
0040         help
0041           ELF FDPIC binaries are based on ELF, but allow the individual load
0042           segments of a binary to be located in memory independently of each
0043           other. This makes this format ideal for use in environments where no
0044           MMU is available as it still permits text segments to be shared,
0045           even if data segments are not.
0046 
0047           It is also possible to run FDPIC ELF binaries on MMU linux also.
0048 
0049 config ELFCORE
0050         bool
0051         help
0052           This option enables kernel/elfcore.o.
0053 
0054 config CORE_DUMP_DEFAULT_ELF_HEADERS
0055         bool "Write ELF core dumps with partial segments"
0056         default y
0057         depends on BINFMT_ELF && ELF_CORE
0058         help
0059           ELF core dump files describe each memory mapping of the crashed
0060           process, and can contain or omit the memory contents of each one.
0061           The contents of an unmodified text mapping are omitted by default.
0062 
0063           For an unmodified text mapping of an ELF object, including just
0064           the first page of the file in a core dump makes it possible to
0065           identify the build ID bits in the file, without paying the i/o
0066           cost and disk space to dump all the text.  However, versions of
0067           GDB before 6.7 are confused by ELF core dump files in this format.
0068 
0069           The core dump behavior can be controlled per process using
0070           the /proc/PID/coredump_filter pseudo-file; this setting is
0071           inherited.  See Documentation/filesystems/proc.txt for details.
0072 
0073           This config option changes the default setting of coredump_filter
0074           seen at boot time.  If unsure, say Y.
0075 
0076 config BINFMT_SCRIPT
0077         tristate "Kernel support for scripts starting with #!"
0078         default y
0079         help
0080           Say Y here if you want to execute interpreted scripts starting with
0081           #! followed by the path to an interpreter.
0082 
0083           You can build this support as a module; however, until that module
0084           gets loaded, you cannot run scripts.  Thus, if you want to load this
0085           module from an initramfs, the portion of the initramfs before loading
0086           this module must consist of compiled binaries only.
0087 
0088           Most systems will not boot if you say M or N here.  If unsure, say Y.
0089 
0090 config BINFMT_FLAT
0091         bool "Kernel support for flat binaries"
0092         depends on !MMU || ARM || M68K
0093         depends on !FRV || BROKEN
0094         help
0095           Support uClinux FLAT format binaries.
0096 
0097 config BINFMT_ZFLAT
0098         bool "Enable ZFLAT support"
0099         depends on BINFMT_FLAT
0100         select ZLIB_INFLATE
0101         help
0102           Support FLAT format compressed binaries
0103 
0104 config BINFMT_SHARED_FLAT
0105         bool "Enable shared FLAT support"
0106         depends on BINFMT_FLAT
0107         help
0108           Support FLAT shared libraries
0109 
0110 config HAVE_AOUT
0111        def_bool n
0112 
0113 config BINFMT_AOUT
0114         tristate "Kernel support for a.out and ECOFF binaries"
0115         depends on HAVE_AOUT
0116         ---help---
0117           A.out (Assembler.OUTput) is a set of formats for libraries and
0118           executables used in the earliest versions of UNIX.  Linux used
0119           the a.out formats QMAGIC and ZMAGIC until they were replaced
0120           with the ELF format.
0121 
0122           The conversion to ELF started in 1995.  This option is primarily
0123           provided for historical interest and for the benefit of those
0124           who need to run binaries from that era.
0125 
0126           Most people should answer N here.  If you think you may have
0127           occasional use for this format, enable module support above
0128           and answer M here to compile this support as a module called
0129           binfmt_aout.
0130 
0131           If any crucial components of your system (such as /sbin/init
0132           or /lib/ld.so) are still in a.out format, you will have to
0133           say Y here.
0134 
0135 config OSF4_COMPAT
0136         bool "OSF/1 v4 readv/writev compatibility"
0137         depends on ALPHA && BINFMT_AOUT
0138         help
0139           Say Y if you are using OSF/1 binaries (like Netscape and Acrobat)
0140           with v4 shared libraries freely available from Compaq. If you're
0141           going to use shared libraries from Tru64 version 5.0 or later, say N.
0142 
0143 config BINFMT_EM86
0144         tristate "Kernel support for Linux/Intel ELF binaries"
0145         depends on ALPHA
0146         ---help---
0147           Say Y here if you want to be able to execute Linux/Intel ELF
0148           binaries just like native Alpha binaries on your Alpha machine. For
0149           this to work, you need to have the emulator /usr/bin/em86 in place.
0150 
0151           You can get the same functionality by saying N here and saying Y to
0152           "Kernel support for MISC binaries".
0153 
0154           You may answer M to compile the emulation support as a module and
0155           later load the module when you want to use a Linux/Intel binary. The
0156           module will be called binfmt_em86. If unsure, say Y.
0157 
0158 config BINFMT_MISC
0159         tristate "Kernel support for MISC binaries"
0160         ---help---
0161           If you say Y here, it will be possible to plug wrapper-driven binary
0162           formats into the kernel. You will like this especially when you use
0163           programs that need an interpreter to run like Java, Python, .NET or
0164           Emacs-Lisp. It's also useful if you often run DOS executables under
0165           the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
0166           <http://www.tldp.org/docs.html#howto>). Once you have
0167           registered such a binary class with the kernel, you can start one of
0168           those programs simply by typing in its name at a shell prompt; Linux
0169           will automatically feed it to the correct interpreter.
0170 
0171           You can do other nice things, too. Read the file
0172           <file:Documentation/binfmt_misc.txt> to learn how to use this
0173           feature, <file:Documentation/admin-guide/java.rst> for information about how
0174           to include Java support. and <file:Documentation/admin-guide/mono.rst> for
0175           information about how to include Mono-based .NET support.
0176 
0177           To use binfmt_misc, you will need to mount it:
0178                 mount binfmt_misc -t binfmt_misc /proc/sys/fs/binfmt_misc
0179 
0180           You may say M here for module support and later load the module when
0181           you have use for it; the module is called binfmt_misc. If you
0182           don't know what to answer at this point, say Y.
0183 
0184 config COREDUMP
0185         bool "Enable core dump support" if EXPERT
0186         default y
0187         help
0188           This option enables support for performing core dumps. You almost
0189           certainly want to say Y here. Not necessary on systems that never
0190           need debugging or only ever run flawless code.