emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

config: trim/improve item names and help texts.

Browse Source 
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
This commit is contained in:
Denys Vlasenko
2017-07-27 02:59:13 +02:00
parent 488e609203
commit 86d5bf4246
2 changed files with 48 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
libbb/Config.src
View File

@@ -11,14 +11,13 @@ choice
prompt "Buffer allocation policy"
default FEATURE_BUFFERS_USE_MALLOC
help
There are 3 ways BusyBox can handle buffer allocations:
There are 3 ways busybox can handle buffer allocations:
- Use malloc. This costs code size for the call to xmalloc.
- Put them on stack. For some very small machines with limited stack
space, this can be deadly. For most folks, this works just fine.
- Put them in BSS. This works beautifully for computers with a real
MMU (and OS support), but wastes runtime RAM for uCLinux. This
behavior was the only one available for BusyBox versions 0.48 and
earlier.
behavior was the only one available for versions 0.48 and earlier.
config FEATURE_BUFFERS_USE_MALLOC
bool "Allocate with Malloc"