Bug 3241

Summary:	Busybox executes an applet instead of an external command when no absolute path is given
Product:	Busybox	Reporter:	404errorqc
Component:	Standard Compliance	Assignee:	unassigned
Status:	RESOLVED INVALID
Severity:	normal	CC:	busybox-cvs
Priority:	P5
Version:	1.18.x
Target Milestone:	---
Hardware:	PC
OS:	Linux
Host:		Target:
Build:

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.