summaryrefslogtreecommitdiffhomepage
path: root/loginutils
diff options
context:
space:
mode:
authorDenis Vlasenko <vda.linux@googlemail.com>2008-06-15 20:14:26 +0000
committerDenis Vlasenko <vda.linux@googlemail.com>2008-06-15 20:14:26 +0000
commit1dba30f2def3a9d2d476a6035a4d8fc4fa2281f0 (patch)
tree2ae4c4203da8115567b6da860251e06eff770171 /loginutils
parentf54a088429a382b48d34529e228e4900879ce826 (diff)
fix config help text
Diffstat (limited to 'loginutils')
-rw-r--r--loginutils/Config.in28
1 files changed, 16 insertions, 12 deletions
diff --git a/loginutils/Config.in b/loginutils/Config.in
index 89b2b1098..fcdc318c8 100644
--- a/loginutils/Config.in
+++ b/loginutils/Config.in
@@ -36,10 +36,10 @@ config USE_BB_PWD_GRP
(e.g. if user/group database is NOT stored in /etc/passwd etc),
you must NOT use this option.
- If you enable this option, it will add about 1.5k to busybox.
+ If you enable this option, it will add about 1.5k.
config USE_BB_SHADOW
- bool "Use busybox shadow password functions"
+ bool "Use internal shadow password functions"
default y
depends on USE_BB_PWD_GRP && FEATURE_SHADOWPASSWDS
help
@@ -52,28 +52,32 @@ config USE_BB_SHADOW
Enabling this option will cause busybox to directly access the
system's /etc/shadow file when handling shadow passwords. This
- makes your system smaller and I will get fewer emails asking about
+ makes your system smaller (and I will get fewer emails asking about
how glibc NSS works). When this option is enabled, you will not be
able to use PAM to access shadow passwords from remote LDAP
password servers and whatnot.
config USE_BB_CRYPT
- bool "Use internal DES and MD5 crypt functions rather than system functions"
+ bool "Use internal DES and MD5 crypt functions"
default y
help
+ Busybox has internal DES and MD5 crypt functions.
+ They produce results which are identical to corresponding
+ standard C library functions.
+
If you leave this disabled, busybox will use the system's
crypt functions. Most C libraries use large (~70k)
- static buffers in these functions, and also combine them
- with more general DES encryption/decryption routines.
- For busybox, having large static buffers is undesirable,
- especially on NOMMU machines.
+ static buffers there, and also combine them with more general
+ DES encryption/decryption.
- These functions produce results which are identical
- to corresponding C library functions.
+ For busybox, having large static buffers is undesirable,
+ especially so on NOMMU machines. Busybox also doesn't
+ need DES encryption/decryption and can do with smaller code.
- If you enable this option, it will add about 4.8k to busybox
+ If you enable this option, it will add about 4.8k of code
if you are building dynamically linked executable.
- In static build, it makes executable _smaller_ by about 1.2k.
+ In static build, it makes code _smaller_ by about 1.2k,
+ and likely many kilobytes less of bss.
config ADDGROUP
bool "addgroup"