Bug 3241 - Busybox executes an applet instead of an external command when no absolute path is given
Summary: Busybox executes an applet instead of an external command when no absolute pa...
Status: RESOLVED INVALID
Alias: None
Product: Busybox
Classification: Unclassified
Component: Standard Compliance (show other bugs)
Version: 1.18.x
Hardware: PC Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-15 04:26 UTC by 404errorqc
Modified: 2011-02-15 13:01 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description 404errorqc 2011-02-15 04:26:09 UTC 
Actually, when inside a BusyBox shell (ash), an external command which has the same name as a BB applet is launched by its single name (e.g. fdisk instead of /sbin/fdisk), BB assumes it must run the applet and not the external command.

When the external command is launched using its full path (e.g. /bin/fdisk instead of fdisk), everything works like a charm.

Itching behavior bug because I use environments where several applets are "replaced" by an external counterpart and the users have to launch the commands in question with an absolute path to circumvent all BB applets having the same name.
Comment 1 Denys Vlasenko 2011-02-15 09:25:54 UTC 
Do you have CONFIG_FEATURE_SH_STANDALONE=y in your .config?
Comment 2 404errorqc 2011-02-15 13:01:38 UTC 
Yes after some research on the system, I found it was set. Thank you for pointing that out, I close the ticket.