win32: changes to '#!' support

Since the earliest days of busybox-w32 '#!' has searched PATH for
the interpreter.  This doesn't seem to be supported by precedent.
In testing I also found that additional code was needed for the case
where PATH has been altered in the current shell or is modified on
the command line:  PATH has to be extracted from envp rather than
getenv("PATH").  Drop this non-standard feature.

*NIX implementations disagree on whether the interpreter can itself
be a script.  Follow Linux and allow this with a limit of four levels
of nesting.

1 files changed, 1 insertions, 2 deletions

diff --git a/shell/ash.c b/shell/ash.c
index 4f1fe005b..c6f64e202 100644
--- a/shell/ash.c
+++ b/shell/ash.c
@@ -22,8 +22,7 @@
  * - Environment variables from Windows will all be turned to uppercase.
  * - PATH accepts both ; and : as separator, but can't be mixed
  * - command without ".exe" extension is still understood as executable
- * - shell scripts on the path are detected by the presence of '#!';
- *   the path to the interpreter is ignored, PATH is searched to find it
+ * - shell scripts on the path are detected by the presence of '#!'
  * - both / and \ are supported in PATH. Usually you must use /
  * - trap/job does not work
  * - /dev/null is supported for redirection