On Fri, 11 Jan 2008, Sven Köhler wrote:
> > Now i wonder, if it's already safe or if it would be possible to use
> > cygwin API (for example execve) from run.exe. To fix all the issues,
> > run.exe really would have to use cygwin to start the command since only
> > that will resolv all the issues (analysing the shebang, following
> > symlinks, etc.).
>
> OK, we cannot use execve, right? If we would, it would open yet another
> console window will be opened for the program we'd like to exec, right?
Exactly.
> So is there any cygwin call to analyse a path? A call, that simply
> returns the program to execute, the parameters to pass, etc.?
>
> It really would really be better pass all the work (finding shebang,
> etc.) to cygwin so that it's consistent.
Yes, there is a well-known extensively tested way of handling shell
scripts, symlinks, etc. It's called "using a shell". Just execve your
favorite shell (/bin/bash is most likely to be present in all installs,
and /bin/sh in Cygwin is the same as bash), and pass it the executable
path as an argument.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ [EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"That which is hateful to you, do not do to your neighbor. That is the whole
Torah; the rest is commentary. Go and study it." -- Rabbi Hillel
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
