[Bug 4135] New: Error running some shell scripts directly
bugzilla at busybox.net
bugzilla at busybox.net
Tue Sep 6 14:23:48 UTC 2011
https://bugs.busybox.net/show_bug.cgi?id=4135
Summary: Error running some shell scripts directly
Product: Busybox
Version: 1.19.x
Platform: Other
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at busybox.net
ReportedBy: jabba.nalhutta at gmail.com
CC: busybox-cvs at busybox.net
Estimated Hours: 0.0
Changes to ash in v1.19.x result in scripts not being directly executable if
they don't start with a line pointing to the desired shell (e.g., "#!/bin/sh").
There is a work-around in that these scripts can be executed if they are passed
to "sh" at the command line (e.g., "sh foo.sh"). However, ash should be able to
run such scripts directly if their executable flags are set - and it has been
able to do so until now, when one just gets a "not found" error.
--
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