diff options
Diffstat (limited to 'urunlevel/sysdeps/linux/Config.in')
-rw-r--r-- | urunlevel/sysdeps/linux/Config.in | 296 |
1 files changed, 0 insertions, 296 deletions
diff --git a/urunlevel/sysdeps/linux/Config.in b/urunlevel/sysdeps/linux/Config.in deleted file mode 100644 index 2e364f2..0000000 --- a/urunlevel/sysdeps/linux/Config.in +++ /dev/null | |||
@@ -1,296 +0,0 @@ | |||
1 | # | ||
2 | # For a description of the syntax of this configuration file, | ||
3 | # see scripts/kbuild/config-language.txt. | ||
4 | # | ||
5 | |||
6 | mainmenu "BusyBox Configuration" | ||
7 | |||
8 | config HAVE_DOT_CONFIG | ||
9 | bool | ||
10 | default y | ||
11 | |||
12 | menu "General Configuration" | ||
13 | |||
14 | choice | ||
15 | prompt "Buffer allocation policy" | ||
16 | default CONFIG_FEATURE_BUFFERS_USE_MALLOC | ||
17 | help | ||
18 | There are 3 ways BusyBox can handle buffer allocations: | ||
19 | - Use malloc. This costs code size for the call to xmalloc. | ||
20 | - Put them on stack. For some very small machines with limited stack | ||
21 | space, this can be deadly. For most folks, this works just fine. | ||
22 | - Put them in BSS. This works beautifully for computers with a real | ||
23 | MMU (and OS support), but wastes runtime RAM for uCLinux. This | ||
24 | behavior was the only one available for BusyBox versions 0.48 and | ||
25 | earlier. | ||
26 | |||
27 | config CONFIG_FEATURE_BUFFERS_USE_MALLOC | ||
28 | bool "Allocate with Malloc" | ||
29 | |||
30 | config CONFIG_FEATURE_BUFFERS_GO_ON_STACK | ||
31 | bool "Allocate on the Stack" | ||
32 | |||
33 | config CONFIG_FEATURE_BUFFERS_GO_IN_BSS | ||
34 | bool "Allocate in the .bss section" | ||
35 | |||
36 | endchoice | ||
37 | |||
38 | config CONFIG_FEATURE_VERBOSE_USAGE | ||
39 | bool "Show verbose applet usage messages" | ||
40 | default n | ||
41 | help | ||
42 | All BusyBox applets will show more verbose help messages when | ||
43 | busybox is invoked with --help. This will add a lot of text to the | ||
44 | busybox binary. In the default configuration, this will add about | ||
45 | 13k, but it can add much more depending on your configuration. | ||
46 | |||
47 | config CONFIG_FEATURE_INSTALLER | ||
48 | bool "Support --install [-s] to install applet links at runtime" | ||
49 | default n | ||
50 | help | ||
51 | Enable 'busybox --install [-s]' support. This will allow you to use | ||
52 | busybox at runtime to create hard links or symlinks for all the | ||
53 | applets that are compiled into busybox. This feature requires the | ||
54 | /proc filesystem. | ||
55 | |||
56 | config CONFIG_LOCALE_SUPPORT | ||
57 | bool "Enable locale support (system needs locale for this to work)" | ||
58 | default n | ||
59 | help | ||
60 | Enable this if your system has locale support and you would like | ||
61 | busybox to support locale settings. | ||
62 | |||
63 | config CONFIG_FEATURE_DEVFS | ||
64 | bool "Support for devfs" | ||
65 | default n | ||
66 | help | ||
67 | Enable if you want BusyBox to work with devfs. | ||
68 | |||
69 | config CONFIG_FEATURE_DEVPTS | ||
70 | bool "Use the devpts filesystem for Unix98 PTYs" | ||
71 | default y if CONFIG_FEATURE_DEVFS | ||
72 | help | ||
73 | Enable if you want BusyBox to use Unix98 PTY support. If enabled, | ||
74 | busybox will use /dev/ptmx for the master side of the pseudoterminal | ||
75 | and /dev/pts/<number> for the slave side. Otherwise, BSD style | ||
76 | /dev/ttyp<number> will be used. To use this option, you should have | ||
77 | devpts or devfs mounted. | ||
78 | |||
79 | config CONFIG_FEATURE_CLEAN_UP | ||
80 | bool "Clean up all memory before exiting (usually not needed)" | ||
81 | default n | ||
82 | help | ||
83 | As a size optimization, busybox by default does not cleanup memory | ||
84 | that is dynamically allocated or close files before exiting. This | ||
85 | saves space and is usually not needed since the OS will clean up for | ||
86 | us. Don't enable this unless you have a really good reason to clean | ||
87 | things up manually. | ||
88 | |||
89 | config CONFIG_FEATURE_SUID | ||
90 | bool "Support for SUID/SGID handling" | ||
91 | default n | ||
92 | help | ||
93 | Support SUID and SGID binaries. | ||
94 | |||
95 | config CONFIG_FEATURE_SUID_CONFIG | ||
96 | bool "Runtime SUID/SGID configuration via /etc/busybox.conf" | ||
97 | default y if CONFIG_FEATURE_SUID | ||
98 | depends on CONFIG_FEATURE_SUID | ||
99 | help | ||
100 | Allow the SUID / SGID state of an applet to be determined runtime by | ||
101 | checking /etc/busybox.conf. The format of this file is as follows: | ||
102 | |||
103 | <applet> = [Ssx-][Ssx-][x-] (<username>|<uid>).(<groupname>|<gid>) | ||
104 | |||
105 | An example might help: | ||
106 | |||
107 | [SUID] | ||
108 | su = ssx root.0 # applet su can be run by anyone and runs with euid=0/egid=0 | ||
109 | su = ssx # exactly the same | ||
110 | |||
111 | mount = sx- root.disk # applet mount can be run by root and members of group disk | ||
112 | # and runs with euid=0 | ||
113 | |||
114 | cp = --- # disable applet cp for everyone | ||
115 | |||
116 | Robert 'sandman' Griebl has more information here: | ||
117 | <url: http://www.softforge.de/bb/suid.html >. | ||
118 | |||
119 | config CONFIG_FEATURE_SUID_CONFIG_QUIET | ||
120 | bool "Suppress warning message if /etc/busybox.conf is not readable" | ||
121 | default n | ||
122 | depends on CONFIG_FEATURE_SUID_CONFIG | ||
123 | help | ||
124 | /etc/busybox.conf should be readable by the user needing the SUID, check | ||
125 | this option to avoid users to be notified about missing permissions. | ||
126 | |||
127 | config CONFIG_SELINUX | ||
128 | bool "Support NSA Security Enhanced Linux" | ||
129 | default n | ||
130 | help | ||
131 | Enable support for SE Linux in applets ls, ps, and id. Also provide | ||
132 | the option of compiling in SE Linux applets. | ||
133 | |||
134 | If you do not have a complete SE Linux Full Userland installed, this | ||
135 | stuff will not compile. Go visit | ||
136 | http://www.nsa.gov/selinux/index.html | ||
137 | to download the necessary stuff to allow busybox to compile with this | ||
138 | option enabled. | ||
139 | |||
140 | Most people will leave this set to 'N'. | ||
141 | |||
142 | endmenu | ||
143 | |||
144 | menu 'Build Options' | ||
145 | |||
146 | config CONFIG_STATIC | ||
147 | bool "Build BusyBox as a static binary (no shared libs)" | ||
148 | default n | ||
149 | help | ||
150 | If you want to build a static BusyBox binary, which does not | ||
151 | use or require any shared libraries, then enable this option. | ||
152 | This can cause BusyBox to be considerably larger, so you should | ||
153 | leave this option false unless you have a good reason (i.e. | ||
154 | your target platform does not support shared libraries, or | ||
155 | you are building an initrd which doesn't need anything but | ||
156 | BusyBox, etc). | ||
157 | |||
158 | Most people will leave this set to 'N'. | ||
159 | |||
160 | config CONFIG_LFS | ||
161 | bool "Build with Large File Support (for accessing files > 2 GB)" | ||
162 | default n | ||
163 | select FDISK_SUPPORT_LARGE_DISKS | ||
164 | help | ||
165 | If you want to build BusyBox with large file support, then enable | ||
166 | this option. This will have no effect if your kernel or your C | ||
167 | library lacks large file support for large files. Some of the | ||
168 | programs that can benefit from large file support include dd, gzip, | ||
169 | cp, mount, tar, and many others. If you want to access files larger | ||
170 | than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'. | ||
171 | |||
172 | config USING_CROSS_COMPILER | ||
173 | bool "Do you want to build BusyBox with a Cross Compiler?" | ||
174 | default n | ||
175 | help | ||
176 | Do you want to build BusyBox with a Cross Compiler? If so, | ||
177 | then enable this option. Otherwise leave it set to 'N'. | ||
178 | |||
179 | config CROSS_COMPILER_PREFIX | ||
180 | string "Cross Compiler prefix" | ||
181 | default "/usr/i386-linux-uclibc/bin/i386-uclibc-" | ||
182 | depends on USING_CROSS_COMPILER | ||
183 | help | ||
184 | If you want to build BusyBox with a cross compiler, then you | ||
185 | will need to set this to the cross-compiler prefix. For example, | ||
186 | if my cross-compiler is /usr/i386-linux-uclibc/bin/i386-uclibc-gcc | ||
187 | then I would enter '/usr/i386-linux-uclibc/bin/i386-uclibc-' here, | ||
188 | which will ensure the correct compiler is used. | ||
189 | |||
190 | config EXTRA_CFLAGS_OPTIONS | ||
191 | string "Any extra CFLAGS options for the compiler?" | ||
192 | default "" | ||
193 | help | ||
194 | Do you want to pass any extra CFLAGS options to the compiler as | ||
195 | you build BusyBox? If so, this is the option for you... For example, | ||
196 | if you want to add some simple compiler switches (like -march=i686), | ||
197 | or check for warnings using -Werror, just those options here. | ||
198 | |||
199 | endmenu | ||
200 | |||
201 | menu 'Installation Options' | ||
202 | |||
203 | config CONFIG_INSTALL_NO_USR | ||
204 | bool "Don't use /usr" | ||
205 | default n | ||
206 | help | ||
207 | Disable use of /usr. Don't activate this option if you don't know | ||
208 | that you really want this behaviour. | ||
209 | |||
210 | config PREFIX | ||
211 | string "BusyBox installation prefix" | ||
212 | default "./_install" | ||
213 | help | ||
214 | Define your directory to install BusyBox files/subdirs in. | ||
215 | |||
216 | |||
217 | |||
218 | endmenu | ||
219 | |||
220 | source archival/Config.in | ||
221 | source coreutils/Config.in | ||
222 | source console-tools/Config.in | ||
223 | source debianutils/Config.in | ||
224 | source editors/Config.in | ||
225 | source findutils/Config.in | ||
226 | source my_linux/Config.in | ||
227 | source runlevel/Config.in | ||
228 | source init/Config.in | ||
229 | source loginutils/Config.in | ||
230 | source miscutils/Config.in | ||
231 | source modutils/Config.in | ||
232 | source networking/Config.in | ||
233 | source procps/Config.in | ||
234 | source shell/Config.in | ||
235 | source sysklogd/Config.in | ||
236 | source util-linux/Config.in | ||
237 | |||
238 | menu 'Debugging Options' | ||
239 | |||
240 | config CONFIG_DEBUG | ||
241 | bool "Build BusyBox with Debugging symbols" | ||
242 | default n | ||
243 | help | ||
244 | Say Y here if you wish to compile BusyBox with debugging symbols. | ||
245 | This will allow you to use a debugger to examine BusyBox internals | ||
246 | while applets are running. This increases the size of the binary | ||
247 | considerably and should only be used when doing development. | ||
248 | If you are doing development and want to debug BusyBox, answer Y. | ||
249 | |||
250 | Most people should answer N. | ||
251 | |||
252 | choice | ||
253 | prompt "Additional debugging library" | ||
254 | default CONFIG_NO_DEBUG_LIB | ||
255 | depends on CONFIG_DEBUG | ||
256 | help | ||
257 | Using an additional debugging library will make BusyBox become | ||
258 | considerable larger and will cause it to run more slowly. You | ||
259 | should always leave this option disabled for production use. | ||
260 | |||
261 | dmalloc support: | ||
262 | ---------------- | ||
263 | This enables compiling with dmalloc ( http://dmalloc.com/ ) | ||
264 | which is an excellent public domain mem leak and malloc problem | ||
265 | detector. To enable dmalloc, before running busybox you will | ||
266 | want to properly set your environment, for example: | ||
267 | export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile | ||
268 | The 'debug=' value is generated using the following command | ||
269 | dmalloc -p log-stats -p log-non-free -p log-bad-space -p log-elapsed-time \ | ||
270 | -p check-fence -p check-heap -p check-lists -p check-blank \ | ||
271 | -p check-funcs -p realloc-copy -p allow-free-null | ||
272 | |||
273 | Electric-fence support: | ||
274 | ----------------------- | ||
275 | This enables compiling with Electric-fence support. Electric | ||
276 | fence is another very useful malloc debugging library which uses | ||
277 | your computer's virtual memory hardware to detect illegal memory | ||
278 | accesses. This support will make BusyBox be considerable larger | ||
279 | and run slower, so you should leave this option disabled unless | ||
280 | you are hunting a hard to find memory problem. | ||
281 | |||
282 | |||
283 | config CONFIG_NO_DEBUG_LIB | ||
284 | bool "None" | ||
285 | |||
286 | config CONFIG_DMALLOC | ||
287 | bool "Dmalloc" | ||
288 | |||
289 | config CONFIG_EFENCE | ||
290 | bool "Electric-fence" | ||
291 | |||
292 | endchoice | ||
293 | |||
294 | |||
295 | endmenu | ||
296 | |||