Every time when using (or having to use) the command line in Windows, it takes time until your eyes adjust to the darkness. There’s one thing, however, I’ll never get accustomed to: Working without the Unix/Linux/GNU (whatever you wanna call it) command-line tools. Fortunately, I don’t have to get accustomed to that: There’s plenty of solution for solving this problem out there. In this article I’m going to elaborate on these three:
- The “classic” solutions – Cygwin and virtual machine
- The lightweight alternative – UnxUtils
- A surprising alternative – Git
When refering to the Unix/Linux/GNU command-line tools, I’ll stick to to the term Unix tools, as the heading predicts.
- The “classic” solutions
The most popular ways of “getting that Linux feeling on Windows” most likely are Cygwin (a linux-like console, that even provides an X-server) or using a virtual machine like VirtualBox or VMWare and a (small) Linux distribution such as Damn Small Linux.
Of course, not using Windows at all would be a decent solution as well 😉
- The lightweight alternative
There are scenarios, where you might not want to or even can’t install Cygwin or a virtual machine. Maybe you’re just looking for a quick way to access these Unix tools from the windows console and have no use for an X-Sever. For this purpose, I use a collection of tools called UnxUtils. Actually, these tools have been there for a long time. The latest version is five and a half years old! Still, it’s downloaded several hundred times a day – impressive!
Now, the nice thing about these tools is, that they are ports to Windows. That is, they are native Windows applications that can run directly from the Windows command prompt (cmd.exe).
Even better, you don’t need to install anything. Just download, extract to some location on your hard drive (in fact, I even carry the utilities around one my flash drive) and you’re almost there. In order not to type the whole path to the UnxUtils binaries every time you intend to use one of them, this path should be added to the beginning of the PATH environment variable. You can either add it permanently (I did this on my Windows computer) or add it temporarily to a specific instance of cmd.exe. To make the UnxUtils portable, I put this small batch script in the UnxUtils folder on my flash drive:
@set PATH=%~dp0\usr\local\wbin;%PATH% @cmd
This script opens a console window where you can execute statements like this:
egrep -in "error|exception" c:\parser.log --context=3 > parserLogErrors
Finally, ending the awful task of analyzing logs with Windows “on-board equipment” 🙂
Note that after adding the path to UnxUtil’s binaries to the beginning of PATH, it’s not possible any more to use Windows-tools that have the same name as one of the UnxUtils, such as find and sort. So, if you prefer the windows-style search tool, you better check the contents of the usr\local\wbin in UnxUtils path first and delete the tools you don’t need.
Unfortunately, I ran into a disadvantage of UnxTools. A rather memory intensive operation like this:
find d:\ | xargs grep "someExpression"
yields an error “xargs cannot fork”. The description for this error at GNU says that the system has run out of process slots, “because the system is very busy and the system has reached its maximum process limit, or because you have a resource limit in place and you’ve reached it”. Not enough memory for cmd.exe? Any ideas?
Someone even filed a bug for that problem, but it obviously has never been fixed (as said, the latest version is more than five years old). So, no solution here, unfortunately 😦
- A surprising alternative
More recently I stumbled upon an alternative to UnxTools – Git for Windows. Isn’t that a source code management system? It is, but on Windows, it ships with a console application. When installing Git, you can choose, to either use Git’s console application (Git Bash) or to integrate the Git console’s binaries to Windows’ PATH variable, just as described in the solution above.
Note that neither Git nor UnxUtils contain a native version of vi(m). One way to use it would be the Git Bash. The Git Bash feels very much like Cygwin – so not as lightweight. You can read more about Git Bash and its differences to Cygwin here: A Windows console that does not suck.
To use the Git’s Windows ports of the Unix command-line tools from your flash drive – like described for UnxTools above, without permanently changing the PATH variable – just copy Git’s bin directory and a batch file like the following to the drive:
@set PATH=%~dp0\bin;%PATH% @cmd
Executing this file will start a console window with the proper PATH set, so you can start finding and greping right away.
Fortunately, the resource error described above doesn’t occur when using the tools provided by Git.
Case closed! 😀
2 thoughts on “Using Unix command-line tools in the Win32 console”
How did I not know about this??!?
This is fantastically useful, especially when something weird happens, like `patch` (from UnixUtils) asks for elevated permissions (something was clearly WRONG).
Necessity is the mother of invention. 🙂
I was just sick of not having the tools available everywhere. VMs/Cygwin were just to bulky to install on every computer (home, work, friends, family, …) That’s when I found UnxUtils. Later I discovered Git Bash, so I decided summarize those solutions for me or anyone else. Glad it helped U out.