BusyBox ash as subshell for mc (midnight commander)?

[Denys Vlasenko]

On Wednesday 29 February 2012 18:40, Alexander Kriegisch wrote:
> I have asked this question years ago on the MC mailing list, but got no
> answer: http://www.mail-archive.com/mc@gnome.org/msg02261.html
> 
> > MC FAQ:
> >> 6.6 When I use Ctrl-O I don't get a subshell.  How do I fix this?
> >> 
> >> Only bash, tcsh and zsh can be used as subshell.  Use one of those
> >> shells as your default shell, and it will be used as subshell in
> >> GNU Midnight Commander.
> > 
> > What is the reason for that? I use BusyBox ash on an embedded
> > platform (DSL/LAN/WLAN router) and would like to have a Ctrl-O
> > subshell. What would be technically required from a candidate shell
> > in order to make it work?
> 
> Can anybody from this list tell me if this is somehow possible? I know
> how to compile and run Bash for my target platform, but I dislike the
> though of using it just for mc subshell support. I do not need it for
> any other purpose. Is there any way to trick so as for it to use BusyBox
> ash (my /bin/sh)?

Try enabling CONFIG_FEATURE_BASH_IS_ASH or CONFIG_FEATURE_BASH_IS_HUSH.

This will merely create a bash applet, which will be aliased
to ash or hush.

Without that options enabled, you'll get "bash: applet not found".

-- 
vda