Kconfig 6.95 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84

menu "Code maturity level options"

config EXPERIMENTAL
	bool "Prompt for development and/or incomplete code/drivers"
	---help---
	  Some of the various things that Linux supports (such as network
	  drivers, file systems, network protocols, etc.) can be in a state
	  of development where the functionality, stability, or the level of
	  testing is not yet high enough for general use. This is usually
	  known as the "alpha-test" phase among developers. If a feature is
	  currently in alpha-test, then the developers usually discourage
	  uninformed widespread use of this feature by the general public to
	  avoid "Why doesn't this work?" type mail messages. However, active
	  testing and use of these systems is welcomed. Just be aware that it
	  may not meet the normal level of reliability or it may fail to work
	  in some special cases. Detailed bug reports from people familiar
	  with the kernel internals are usually welcomed by the developers
	  (before submitting bug reports, please read the documents
	  <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
	  <file:Documentation/BUG-HUNTING>, and
	  <file:Documentation/oops-tracing.txt> in the kernel source).

	  This option will also make obsoleted drivers available. These are
	  drivers that have been replaced by something else, and/or are
	  scheduled to be removed in a future kernel release.

	  Unless you intend to help test and develop a feature or driver that
	  falls into this category, or you have a situation that requires
	  using these features, you should probably say N here, which will
	  cause the configurator to present you with fewer choices. If
	  you say Y here, you will be offered the choice of using features or
	  drivers that are currently considered to be in the alpha-test phase.

endmenu


menu "General setup"

config SYSVIPC
	bool "System V IPC"
	---help---
	  Inter Process Communication is a suite of library functions and
	  system calls which let processes (running programs) synchronize and
	  exchange information. It is generally considered to be a good thing,
	  and some programs won't run unless you say Y here. In particular, if
	  you want to run the DOS emulator dosemu under Linux (read the
	  DOSEMU-HOWTO, available from
	  <http://www.linuxdoc.org/docs.html#howto>), you'll need to say Y
	  here.

	  You can find documentation about IPC with "info ipc" and also in
	  section 6.4 of the Linux Programmer's Guide, available from
	  <http://www.linuxdoc.org/docs.html#guide>.

config BSD_PROCESS_ACCT
	bool "BSD Process Accounting"
	help
	  If you say Y here, a user level program will be able to instruct the
	  kernel (via a special system call) to write process accounting
	  information to a file: whenever a process exits, information about
	  that process will be appended to the file by the kernel.  The
	  information includes things such as creation time, owning user,
	  command name, memory usage, controlling terminal etc. (the complete
	  list is in the struct acct in <file:include/linux/acct.h>).  It is
	  up to the user level program to do useful things with this
	  information.  This is generally a good idea, so say Y.

config SYSCTL
	bool "Sysctl support"
	---help---
	  The sysctl interface provides a means of dynamically changing
	  certain kernel parameters and variables on the fly without requiring
	  a recompile of the kernel or reboot of the system.  The primary
	  interface consists of a system call, but if you say Y to "/proc
	  file system support", a tree of modifiable sysctl entries will be
	  generated beneath the /proc/sys directory. They are explained in the
	  files in <file:Documentation/sysctl/>.  Note that enabling this
	  option will enlarge the kernel by at least 8 KB.

	  As it is generally a good thing, you should say Y here unless
	  building a kernel for install/rescue disks or your system is very
	  limited in memory.

85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129
choice
	prompt "Kernel log buffer size"
	default LOG_BUF_SHIFT_17 if ARCH_S390
	default LOG_BUF_SHIFT_16 if X86_NUMAQ || IA64
	default LOG_BUF_SHIFT_15 if SMP
	default LOG_BUF_SHIFT_14
	help
	  Select kernel log buffer size from this list (power of 2).
	  Defaults:  17 (=> 128 KB for S/390)
		     16 (=> 64 KB for x86 NUMAQ or IA-64)
	             15 (=> 32 KB for SMP)
	             14 (=> 16 KB for uniprocessor)

config LOG_BUF_SHIFT_17
	bool "128 KB"
	default y if ARCH_S390

config LOG_BUF_SHIFT_16
	bool "64 KB"
	default y if X86_NUMAQ || IA64

config LOG_BUF_SHIFT_15
	bool "32 KB"
	default y if SMP

config LOG_BUF_SHIFT_14
	bool "16 KB"

config LOG_BUF_SHIFT_13
	bool "8 KB"

config LOG_BUF_SHIFT_12
	bool "4 KB"

endchoice

config LOG_BUF_SHIFT
	int
	default 17 if LOG_BUF_SHIFT_17=y
	default 16 if LOG_BUF_SHIFT_16=y
	default 15 if LOG_BUF_SHIFT_15=y
	default 14 if LOG_BUF_SHIFT_14=y
	default 13 if LOG_BUF_SHIFT_13=y
	default 12 if LOG_BUF_SHIFT_12=y

130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147
endmenu


menu "Loadable module support"

config MODULES
	bool "Enable loadable module support"
	help
	  Kernel modules are small pieces of compiled code which can be
	  inserted in or removed from the running kernel, using the programs
	  insmod and rmmod. This is described in the file
	  <file:Documentation/modules.txt>, including the fact that you have
	  to say "make modules" in order to compile the modules that you chose
	  during kernel configuration.  Modules can be device drivers, file
	  systems, binary executable formats, and so on. If you think that you
	  may want to make use of modules with this kernel in the future, then
	  say Y here.  If unsure, say Y.

148 149
config MODULE_UNLOAD
	bool "Module unloading"
150
	depends on MODULES
151 152 153 154 155
	help
	  Without this option you will not be able to unload any
	  modules (note that some modules may not be unloadable
	  anyway), which makes your kernel slightly smaller and
	  simpler.  If unsure, say Y.
156

Rusty Russell's avatar
Rusty Russell committed
157 158
config MODULE_FORCE_UNLOAD
	bool "Forced module unloading"
159
	depends on MODULE_UNLOAD && EXPERIMENTAL
Rusty Russell's avatar
Rusty Russell committed
160 161 162 163 164 165 166
	help
	  This option allows you to force a module to unload, even if the
	  kernel believes it is unsafe: the kernel will remove the module
	  without waiting for anyone to stop using it (using the -f option to
	  rmmod).  This is mainly for kernel developers and desparate users.
	  If unsure, say N.

167 168 169 170 171 172 173 174 175
config OBSOLETE_MODPARM
	bool
	default y
	depends on MODULES
	help
	  You need this option to use module parameters on modules which
	  have not been converted to the new module parameter system yet.
	  If unsure, say Y.

176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191
config KMOD
	bool "Kernel module loader"
	depends on MODULES
	help
	  Normally when you have selected some drivers and/or file systems to
	  be created as loadable modules, you also have the responsibility to
	  load the corresponding modules (using the programs insmod or
	  modprobe) before you can use them. If you say Y here however, the
	  kernel will be able to load modules for itself: when a part of the
	  kernel needs a module, it runs modprobe with the appropriate
	  arguments, thereby loading the module if it is available. (This is a
	  replacement for kerneld.) Say Y here and read about configuring it
	  in <file:Documentation/kmod.txt>.

endmenu