Re: Why sh failed 'Process Substitution'?

["Mark J. Reed" <markjreed at gmail dot com>]

>> Pan ruochen wrote:
>>> Why sh failed to recognize Process Substitution, even if /bin/sh.exe
>>> is a copy of /bin/bash.exe?

It's very common in UNIXland for a program to change its behavior
depending on the name by which it is invoked.  ln, mv, and rm are
often links to the same command; there's at least one embedded
UNIXalike where all the commands in /bin are links to the same
executable.

The script has a #!/bin/bash at the top, indicating that it is meant
to be run by bash in bash mode.  If you make it executable and run it
directly, that line will be honored and the shell will be invoked as
bash.  Or you can run it by typing "bash ./scriptname".

None of this, of course, is at all Cygwin-specific.

-- 
Mark J. Reed <markjreed@gmail.com>

--
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/