config FEATURE_VERBOSE_USAGE
bool "Show verbose applet usage messages"
- default n
- select SHOW_USAGE
+ default y
+ depends on SHOW_USAGE
help
All BusyBox applets will show more verbose help messages when
busybox is invoked with --help. This will add a lot of text to the
config FEATURE_INSTALLER
bool "Support --install [-s] to install applet links at runtime"
- default n
+ default y
help
Enable 'busybox --install [-s]' support. This will allow you to use
busybox at runtime to create hard links or symlinks for all the
Enable this if your system has locale support and you would like
busybox to support locale settings.
-config FEATURE_ASSUME_UNICODE
+config UNICODE_SUPPORT
bool "Support Unicode"
- default n
+ default y
help
This makes various applets aware that one byte is not
one character on screen.
Probably by the time when busybox will be fully Unicode-clean,
other encodings will be mainly of historic interest.
+config UNICODE_USING_LOCALE
+ bool "Use libc routines for Unicode (else uses internal ones)"
+ default n
+ depends on UNICODE_SUPPORT && LOCALE_SUPPORT
+ help
+ With this option on, Unicode support is implemented using libc
+ routines. Otherwise, internal implementation is used.
+
config FEATURE_CHECK_UNICODE_IN_ENV
bool "Check $LANG environment variable"
- default y
- depends on FEATURE_ASSUME_UNICODE && !LOCALE_SUPPORT
+ default n
+ depends on UNICODE_SUPPORT && !UNICODE_USING_LOCALE
help
With this option on, Unicode support is activated
only if LANG variable has the value of the form "xxxx.utf8"
config SUBST_WCHAR
int "Character code to substitute unprintable characters with"
- range 1 4294967295
- depends on FEATURE_ASSUME_UNICODE
+ depends on UNICODE_SUPPORT
default 63
help
Typical values are 63 for '?' (works with any output device),
config LAST_SUPPORTED_WCHAR
int "Range of supported Unicode characters"
- range 0 4294967295
- depends on FEATURE_ASSUME_UNICODE
+ depends on UNICODE_SUPPORT
default 767
help
Any character with Unicode value bigger than this is assumed
The idea is that many valid printable Unicode chars are
nevertheless are not displayed correctly. Think about
- combining charachers, double-wide hieroglyphs and such.
- Many terminals, xterms and such will fail to handle them
- correctly.
+ combining charachers, double-wide hieroglyphs, obscure
+ characters in dozens of ancient scripts...
+ Many terminals, terminal emulators, xterms etc will fail
+ to handle them correctly. Choose the smallest value
+ which suits your needs.
Typical values are:
126 - ASCII only
code is ~700 bytes smaller for this case.
4351 (0x10ff) - there are no double-wide chars in [0..4351] range,
code is ~300 bytes smaller for this case.
+ 12799 (0x31ff) - nearly all non-ideographic characters are
+ available in [0..12799] range, including
+ East Asian scripts like katakana, hiragana, hangul,
+ bopomofo...
0 - off, any valid printable Unicode character will be printed.
config UNICODE_COMBINING_WCHARS
bool "Allow zero-width Unicode characters on output"
default n
- depends on FEATURE_ASSUME_UNICODE
+ depends on UNICODE_SUPPORT
help
With this option off, any Unicode char with width of 0
is substituted on output.
config UNICODE_WIDE_WCHARS
bool "Allow wide Unicode characters on output"
default n
- depends on FEATURE_ASSUME_UNICODE
+ depends on UNICODE_SUPPORT
help
With this option off, any Unicode char with width > 1
is substituted on output.
+config UNICODE_BIDI_SUPPORT
+ bool "Bidirectional character-aware line input"
+ default n
+ depends on UNICODE_SUPPORT && !UNICODE_USING_LOCALE
+ help
+ With this option on, right-to-left Unicode characters
+ are treated differently on input (e.g. cursor movement).
+
+config UNICODE_NEUTRAL_TABLE
+ bool "In bidi input, support non-ASCII neutral chars too"
+ default n
+ depends on UNICODE_BIDI_SUPPORT
+ help
+ In most cases it's enough to treat only ASCII non-letters
+ (i.e. punctuation, numbers and space) as characters
+ with neutral directionality.
+ With this option on, more extensive (and bigger) table
+ of neutral chars will be used.
+
+config UNICODE_PRESERVE_BROKEN
+ bool "Make it possible to enter sequences of chars which are not Unicode"
+ default n
+ depends on UNICODE_SUPPORT
+ help
+ With this option on, invalid UTF-8 bytes are not substituted
+ with the selected substitution character.
+ For example, this means that entering 'l', 's', ' ', 0xff, [Enter]
+ at shell prompt will list file named 0xff (single char name
+ with char value 255), not file named '?'.
+
config LONG_OPTS
bool "Support for --long-options"
default y
Don't enable this unless you have a really good reason to clean
things up manually.
+config FEATURE_UTMP
+ bool "Support utmp file"
+ default y
+ help
+ The file /var/run/utmp is used to track who is currently logged in.
+ With this option on, certain applets (getty, login, telnetd etc)
+ will create and delete entries there.
+ "who" applet requires this option.
+
+config FEATURE_WTMP
+ bool "Support wtmp file"
+ default y
+ select FEATURE_UTMP
+ help
+ The file /var/run/wtmp is used to track when users have logged into
+ and logged out of the system.
+ With this option on, certain applets (getty, login, telnetd etc)
+ will append new entries there.
+ "last" applet requires this option.
+
config FEATURE_PIDFILE
bool "Support writing pidfiles"
- default n
+ default y
help
This option makes some applets (e.g. crond, syslogd, inetd) write
a pidfile in /var/run. Some applications rely on them.
config FEATURE_SUID
bool "Support for SUID/SGID handling"
- default n
+ default y
help
With this option you can install the busybox binary belonging
to root with the suid bit set, and it will automatically drop
config FEATURE_SUID_CONFIG
bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
- default n if FEATURE_SUID
+ default y if FEATURE_SUID
depends on FEATURE_SUID
help
Allow the SUID / SGID state of an applet to be determined at runtime
config LFS
bool "Build with Large File Support (for accessing files > 2 GB)"
- default n
+ default y
select FDISK_SUPPORT_LARGE_DISKS
help
If you want to build BusyBox with large file support, then enable
projects / oweals / busybox.git / blobdiff