hush: allow hush to run embedded scripts
Embedded scripts require a shell to be present in the BusyBox binary. Allow either ash or hush to be used for this purpose. If both are enabled ash takes precedence. The size of the binary is unchanged in the default configuration: both ash and hush are present but support for embedded scripts isn't compiled into hush. Signed-off-by: Ron Yorston <rmy@pobox.com> Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
This commit is contained in:
committed by
Denys Vlasenko
parent
f4709d78cb
commit
71df2d3589
@@ -161,6 +161,20 @@ config FEATURE_SH_HISTFILESIZE
|
||||
to set shell history size. Note that its max value is capped
|
||||
by "History size" setting in library tuning section.
|
||||
|
||||
config FEATURE_SH_EMBEDDED_SCRIPTS
|
||||
bool "Embed scripts in the binary"
|
||||
default y
|
||||
depends on ASH || HUSH || SH_IS_ASH || BASH_IS_ASH || SH_IS_HUSH || BASH_IS_HUSH
|
||||
help
|
||||
Allow scripts to be compressed and embedded in the busybox
|
||||
binary. The scripts should be placed in the 'embed' directory
|
||||
at build time. Like applets, scripts can be run as
|
||||
'busybox SCRIPT ...' or by linking their name to the binary.
|
||||
|
||||
This also allows applets to be implemented as scripts: place
|
||||
the script in 'applets_sh' and a stub C file containing
|
||||
configuration in the appropriate subsystem directory.
|
||||
|
||||
endif # Options common to all shells
|
||||
|
||||
endmenu
|
||||
|
Reference in New Issue
Block a user