#cygWINNING!

Latest response

I've got to say, one of the coolest things about working here at Red Hat has been FINALLY getting a corporate-supplied desktop that runs a non-proprietary operating system. Having worked in large companies for years now, one of the largest complaints my teams have had is the productivity loss not having native *NIX tools at their fingertips (scripters and developers especially). It's very powerful to be able to accurately model and test something right on your desktop.

So most of us have to deal with alternate methods of mocking up Linux. Perhaps you use a virtual machine or you dual-boot, but more likely you're using an SSH-client to hop over to some *NIX box you've got rights to so you can do your thing. One cool alternative is a tool called Cygwin. It offers a full standard UNIX/Linux shell environment right on your desktop. It runs on lots of flavours of Windows, so it might be just the fit you need to get your job done more quickly and efficiently if you can "go native".

I've used Cygwin off an on for years, it's been pretty nice. One problem has been the lack of management and upkeep to it (IE- unlike most modern OSes that have self-updating capabilities baked in now, with Cygwin it's all manual) so it quite often lagged behind on updates and bugfixes since I was too lazy or too busy to update it. So one cool solution I recently found out about was that Red Hat offers up support for Cygwin and can provide consistent updates. It's cool that many people might never need that extra hand, but for those that do we can certainly help you out. Details can be found here for those so interested:

http://www.redhat.com/services/custom/cygwin/

So my question to you all: Have you used Cygwin in managing your *NIX? Was it useful to have a shell at your fingertips whenever you needed it? There are lots of options out there, but they all have varying price-points and features/disadventages. If you don't use Cygwin, what are some other good tools to help with connectivity and management (Lot's of folks use Putty or SecureSSH)? We'd love to hear from you!

Responses

In environments where using a NIX desktop isn't an option I had historically used a combination of PuTTY and Cygwin(for X).

However a few years ago I happened across MobaXterm and I find it meets my needs quite well. Built in X server, sftp, rdp, multiexec across sessions, Tunneling.

Recently the developer limited saved sessions and such on the free version but still, it gets the job done. So much so I thought about buying it but I'm not sure I want to fork out 60 some odd bucks annually for a 'Pro subscription".

Been using Cygwin for coming up on a decade - basically, since all of the other previously free X for Windows solutions disappeared - either into pay-models or oblivion. For me, Cygwin was primarily for running X applications on Windows, not as a local development solution. And, while Cygwin's good for basic shell- or Perl-scripting mockups, the differential between a "real" target environment and Cygwin made using it for closer-to-the-metal coding mostly a non-starter.

That said, aside from coding types of tasks, it's really nice having vi, sed and the like available when you want to take minimally-structured data and convert it into a format that's more cleanly importable into tools like Excel.

Still: when I'm looking to connect to remote systems for CLI-based access, I usually find myself using PuTTY. Cygwin's lack of cut-n-paste within its xterms just makes it a pain in the rear.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.