[BusyBox] ash is not executing internal apps.

Sven Oliver Moll svolli at svolli.de
Wed Sep 26 01:44:33 UTC 2001


Hello!

I stumbled over the following inconvieniance:
bash$ nc
bash: nc: command not found
(ok, no "nc" in PATH)

$ ./busybox ash


BusyBox v0.61.pre (2001.09.26-07:30+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

$ nc
nc: No such file or directory

$ exit
$ ./busybox msh


BusyBox v0.61.pre (2001.09.26-07:30+0000) Built-in shell (msh)
Enter 'help' for a list of built-in commands.

$ nc
BusyBox v0.61.pre (2001.09.07-12:21+0000) multi-call binary

Usage: nc [IP] [port]

Netcat opens a pipe to IP:port

$ exit
$ ./busybox lash


BusyBox v0.61.pre (2001.09.26-07:30+0000) Built-in shell (lash)
Enter 'help' for a list of built-in commands.

$ nc
BusyBox v0.61.pre (2001.09.07-12:21+0000) multi-call binary

Usage: nc [IP] [port]

Netcat opens a pipe to IP:port

$ exit
$ ./busybox hush

hush -- the humble shell v0.01 (testing)

$ nc
BusyBox v0.61.pre (2001.09.07-12:21+0000) multi-call binary

Usage: nc [IP] [port]

Netcat opens a pipe to IP:port

$ exit

So what I want to state is that the ash does not execute internal apps if
configured as a standalone shell, like every other shell does. Is it
really meant to be that way? I don't think so.

It is always the same executable that is called. The Version is from the
CVS updated about half an hour ago. My Config.h is among other things:

#define BB_ASH
#define BB_HUSH
#define BB_LASH
#define BB_MSH
#define BB_NC
#define BB_FEATURE_SH_IS_ASH
#define BB_FEATURE_SH_STANDALONE_SHELL
//#define BB_FEATURE_SH_APPLETS_ALWAYS_WIN
#define BB_FEATURE_SH_FANCY_PROMPT
#define BB_FEATURE_COMMAND_EDITING
#define BB_FEATURE_COMMAND_TAB_COMPLETION
#define BB_FEATURE_SH_STANDALONE_SHELL


Happy hunting,
SvOlli
-- 
  _______
 (  /\           | It's hard to say you love someone,
__)v\/lli a.k.a. | and it's hard to say you don't.
Sven Oliver Moll |   -- Del Amitri, "Driving With The Brakes On"






More information about the busybox mailing list