%% Alexander Kotelnikov <[EMAIL PROTECTED]> writes:
Mikhael> This is not correct. It is standard for unux kernels to pass
Mikhael> a text executable script to /bin/sh by default.
ak> LIE. Read standards, please.
Single UNIX says:
If the process image file is not a valid executable object, execlp()
and execvp() use the contents of that file as standard input to a
command interpreter conforming to system(). In this case, the
command interpreter becomes the new process image.
I can't recall any UNIX in the last 10+ years that didn't do this.
For example, from various exec* man pages:
If the header of a file isn't recognized (the attempted execve
returned ENOEXEC), these functions will execute the shell with the
path of the file as its first argument. (If this attempt fails, no
further searching is done.)
Or:
If the new process file is not an executable object file, execlp()
and execvp() use the contents of that file as standard input to the
shell.
--
-------------------------------------------------------------------------------
Paul D. Smith <[EMAIL PROTECTED]> HASMAT--HA Software Mthds & Tools
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
