GNU utilities For Windows with Unix Utils
If you're new here, you may want to subscribe to Windows Reference RSS feed Thanks for visiting!
If you want to use some Linux/Unix Commands in Windows like grep,egrep,find,dc,dd,cp and many more then you are looking for this small utility called Unix Utils
Here are some ports of common GNU utilities to native Win32. In this context, native means the executables do only depend on the Microsoft C-runtime (msvcrt.dll) and not an emulation layer like that provided by Cygwin tools.
Download GNU utilities For Windows from Here
Sample screenshot
Random Posts
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically each day to your feed reader.
Trackbacks & Pingbacks
Comments
Leave a comment
Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Hello,
does the GNU utilities work with the 64-bit version of Windows server 2003?
Thanks,
Karl
I have those utilities that worked fine with 2k, xp.
(I usually put all the *.exe in c:\bin, then I edit
the PATH variable by putting ‘c:\bin;’ at the beginning)
But with vista, after I type in any command in my shell
console (even a simple ls) it crashes.
On the shortcut I use for zsh.exe (I have c:\bin\zsh.exe -i
in the command line) I checked the compatibility with xp
but it didn’t solve anything.
Anybody knows how to fix this?
can this program support multibyte characters, say, Chinese characters? I tried on my desktop, it give me “????”…
Any news on whether this will work on a 64-bit operating system ?
It works ok on my Win 7 Prof. 64-bit. Put the unziped UnxUtils\usr\local\wbin in front of %PATH%, then all the usual unix commands (i.e. ls, which, uname, du, sleep,..) work as expected in the Command Prompt window.
Fantastic cmd line apps. But get them from the source at soruceforge. The tee command errors out if used to output to a file name that uses command line variables (such as %TIME%) due to a problem with 32bit vx 64bit (which is indicated in the error message). But not using the cmd line variable solves the problem. So more complicated logging & automated build software systems will have errors if using tee.exe and variables in the file name.