gnuwin32

We need to support a legacy app that provides a Unix and a Win32 port. Unfortunately, later in the game, a lot of glue code was written in ksh scripts for the unix port only, and the Win32 port has lost parity. I've been trying to revive it, and I've been trying some ksh-for-windows solutions (a native build of Zsh used to work in the past), but nothing seems to work properly under Windows 7: Cygwin refuses to use both Win32 and unix-style paths, so some convoluted scripts break. Same situation for SUA/SFU. UWin doesn't work on Windows 7. The older native ports I used to use (WinZsh) also no

I can't seem to get a handle on the difference between the two. It seems that one ( GNUWin32 ) is an layer on top of windows (like MSYS ) and the other (cygwin) is something else (?) What does that mean? When would I use one over the other? Are they both suited for the same thing? I want to use it mainly for git but want to keep my options open for learning and doing all thing *nixy. Is there another tool for this? Will msysgit be better suited for this? Are there any resources that go through the differences of all of these *nix platforms exhaustively? Michael Slade Cygwin is a library that

I am using Gnuwin32 binaries on a Windows environment. When I want to find files of a certain type, let's say PDF, I usually run: find . -iname '*.pdf' -print This works perfectly on any UNIX system. find.exe . -iname "*.pdf" -print But under Windows, having replaced single quotes with double-quotes, it only works when there is no pdf file in the current directory, otherwise the * gets expanded . Worse: when there is exactly one PDF file in the current directory, it will expand, there will be no syntax error and you will get wrong results. I have tried escaping the * with a caret, a backslash,

I am trying to use the GnuWin32 version of OpenSSL to fetch certificates from several WebSphere MQ queue managers. All attempts result in OpenSSL keeping the connection open until I manually hit ENTER. I tried piping various text into the command as per this SO question and this SO question , but with no luck. Ideally, OpenSSL would close the connection once the input file or piped text hit EOF. Examples: echo QUIT | openssl s_client -connect qmgrhost:1414 -showcerts openssl s_client -connect qmgrhost:1414 -showcerts < responsefile.txt The examples using the QUIT command appear to work in the