diff options
Diffstat (limited to 'libbb')
| -rw-r--r-- | libbb/Config.src | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/libbb/Config.src b/libbb/Config.src index 18a40f2ac..00804e31e 100644 --- a/libbb/Config.src +++ b/libbb/Config.src | |||
| @@ -7,6 +7,30 @@ menu "Busybox Library Tuning" | |||
| 7 | 7 | ||
| 8 | INSERT | 8 | INSERT |
| 9 | 9 | ||
| 10 | choice | ||
| 11 | prompt "Buffer allocation policy" | ||
| 12 | default FEATURE_BUFFERS_USE_MALLOC | ||
| 13 | help | ||
| 14 | There are 3 ways BusyBox can handle buffer allocations: | ||
| 15 | - Use malloc. This costs code size for the call to xmalloc. | ||
| 16 | - Put them on stack. For some very small machines with limited stack | ||
| 17 | space, this can be deadly. For most folks, this works just fine. | ||
| 18 | - Put them in BSS. This works beautifully for computers with a real | ||
| 19 | MMU (and OS support), but wastes runtime RAM for uCLinux. This | ||
| 20 | behavior was the only one available for BusyBox versions 0.48 and | ||
| 21 | earlier. | ||
| 22 | |||
| 23 | config FEATURE_BUFFERS_USE_MALLOC | ||
| 24 | bool "Allocate with Malloc" | ||
| 25 | |||
| 26 | config FEATURE_BUFFERS_GO_ON_STACK | ||
| 27 | bool "Allocate on the Stack" | ||
| 28 | |||
| 29 | config FEATURE_BUFFERS_GO_IN_BSS | ||
| 30 | bool "Allocate in the .bss section" | ||
| 31 | |||
| 32 | endchoice | ||
| 33 | |||
| 10 | config PASSWORD_MINLEN | 34 | config PASSWORD_MINLEN |
| 11 | int "Minimum password length" | 35 | int "Minimum password length" |
| 12 | default 6 | 36 | default 6 |