[Bug 3241] New: Busybox exceutes an applet instead of an external command when no absolute path is given
bugzilla at busybox.net
bugzilla at busybox.net
Tue Feb 15 04:26:10 UTC 2011
https://bugs.busybox.net/show_bug.cgi?id=3241
Summary: Busybox exceutes an applet instead of an external
command when no absolute path is given
Product: Busybox
Version: 1.18.x
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Standard Compliance
AssignedTo: unassigned at busybox.net
ReportedBy: 404errorqc at gmail.com
CC: busybox-cvs at busybox.net
Estimated Hours: 0.0
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.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the busybox-cvs
mailing list