This is the mail archive of the
mailing list for the Cygwin project.
Re: behaviour of "for (( exp1; exp2; exp3 )); do COMMANDS; done"
Randall R Schulz <firstname.lastname@example.org> wrote in
in gmane.os.cygwin on Wed, 28 May 2003 06:30:47 -0700:
> The interpretation of #! lines is in the kernel (or, hereabout,
> Cygwin1.dll, a kernel by any other name), just as the kernel would how
> to handle a binary executable by examining its header.
* man execve *
Well, well. I knew that some unices had to be doing this because they
allowed suid scripts. But I thought the behaviour had been phased out
of newer versions. (Because Linux and the like don't allow suid
scripts, I assumed that this whole script-handling behaviour had been
moved out of the kernel.)
I learn something new every day. Thanks. :-)
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html