(05/09/2013 02:20 PM)Joom Wrote:  I just threw "setup.exe" in C:\cygwin. Any time it needs an update, I just run it. It should do everything for you. And it's not emulation. Cygwin sets up an actual POSIX compliant environment.

Woops, this is why I should stay away from assumptions, thanks jooms for pointing that out. I guess the thing that I was getting at was this part of an answer on stack overflow

Quote:My original intent was to include a set of Unix tools in Windows and be done with it (a number of us on the team have deep Unix backgrounds and a healthy dose of respect for that community.) What I found was that this didn't really help much. The reason for that is that awk/grep/said don't work against COM, WMI, ADSI, the Registry, the cert store, etc, etc. In other words, UNIX is an entire ecosystem self-tuned around text files. As such, text processing tools are effectively management tools. Windows is a completely different ecosystem self-tuned around APIs and Objects. That's why wee invented PowerShell.

What I think you'll find is that there will be lots of occasions when text-processing won't get you what you want on Windows. At that point, you'll want to pick up PowerShell. NOTE - it is not an all or nothing deal. Within PowerShell, you can call out to your Unix tools (and use their text process or PowerShell's text processing). Also you can call PowerShell from your Unix tools and get text.

http://stackoverflow.com/questions/57362...on-windows