Linked by Kroc Camen on Wed 17th Dec 2008 19:43 UTC, submitted by weildish
General Unix IBM's primer to Cygwin. Cygwin is a UNIX-like environment for the Microsoft Windows operating system. Cygwin includes a real UNIX shell, a Portable Operating System Interface (POSIX) emulation library, and thousands of UNIX utilities ported to Windows. Learn how to drop to Cygwin and use its UNIX-like command line to manipulate the system.
Order by: Score:
by poundsmack on Wed 17th Dec 2008 20:04 UTC
Member since:

while most of the IBM articles are just blatent advertising for their company, this was actuayl helpfull and nice to see teh step by step. thanks IBM

Reply Score: 3

by DoctorPepper on Wed 17th Dec 2008 20:46 UTC
Member since:

I loves my Cygwin!!! I work with hundreds of Unix and Linux servers at work, but access them through my Windows XP laptop. Installing Cygwin on it made it much easier to tolerate.

Reply Score: 2

RE: Cygwin
by beowuff on Wed 17th Dec 2008 21:18 UTC in reply to "Cygwin"
beowuff Member since:

As I often joke to my IT department...

Cygwin makes Windows usable! :-P

Reply Score: 3

Comment by f2racer
by f2racer on Wed 17th Dec 2008 21:25 UTC
Member since:

Anybody else find Cygwin very slow. We migrated over to MinGW/MSYS and halved the time of long-running shell scripts.

Reply Score: 3

RE: Comment by f2racer
by PlatformAgnostic on Wed 17th Dec 2008 21:28 UTC in reply to "Comment by f2racer"
PlatformAgnostic Member since:

Cygwin is not particularly well (or securely) implemented. Windows Services for Unix is better integrated (though you might need a higher SKU of Windows to use the recent ones).

Reply Score: 3

RE[2]: Comment by f2racer
by Bill Shooter of Bul on Thu 18th Dec 2008 18:53 UTC in reply to "RE: Comment by f2racer"
Bill Shooter of Bul Member since:

But not as good. When Developers make an attempt to ensure a linux app works on windows, they typically test it against cygwin, not Unix services for windows. Cygwin also comes with its own package manager.

Reply Score: 1

RE: Comment by f2racer
by b0ne on Wed 17th Dec 2008 21:30 UTC in reply to "Comment by f2racer"
b0ne Member since:

fork()ing on CYGWIN is extremely slow, which you end up doing a lot whenever you run a makefile or any shell script for that matter.

Reply Score: 3

v .
by enx23 on Wed 17th Dec 2008 21:40 UTC
by andyk on Wed 17th Dec 2008 23:26 UTC
Member since:

Anyone not happy with Cygwin's builtin terminal that runs in a Windows console window might want to give MinTTY a try:

It's still in development, but pretty usable already. Feedback via the issue tracker much welcome.

Reply Score: 1

by asgillett on Wed 17th Dec 2008 23:57 UTC in reply to "MinTTY"
asgillett Member since:

cygwin has an excellent terminal emulator called rxvt - unfortunately it's not the default ;)

Reply Score: 1

RE[2]: MinTTY
by -oblio- on Thu 18th Dec 2008 07:01 UTC in reply to "RE: MinTTY"
-oblio- Member since:
by spiderman on Thu 18th Dec 2008 06:28 UTC in reply to "MinTTY"
spiderman Member since:
Comment by joekiser
by joekiser on Thu 18th Dec 2008 04:11 UTC
Member since:

Nice article, it made me download and install Cygwin for the first time in years. I always felt that SFU was better integrated but unfortunately it won't be updated in the future.

By the way, for those of us who prefer tcsh, here is a quick lesson on replacing bash as the default shell:

Reply Score: 1

I have used it... Didn't care much for it.
by theTSF on Thu 18th Dec 2008 14:04 UTC
Member since:

I think if it were a little better integrated with Windows and vice versa it would be better. Most of the open source tools that I use also have windows ports to them which are often easier to install in Windows, and accessible outside of Cigwin.

I think it is mostly the case for me that when I am on a different Operating system my though process for that OS is different. Thus I tend to dislike Linux systems trying to look like or act like Macs or Windows, And Windows trying to act like Linux/Unix etc...

Reply Score: 2

UltraZelda64 Member since:

I tend to think the same way. I prefer to go all-out; if I'm using Windows, I want plain old Windows with COMMAND.COM, CMD.EXE, or maybe the PowerShell. If I'm using Linux, I want it pure. If I'm using DOS, well, same thing. I hate how FreeDOS installs the GNU utilities by default (and lots of other unnecessary crap unless you go through a list and spend a few minutes un-checking stuff). It just doesn't feel right, it's way out of place.

On the other hand, I do like playing around with virtual machines and DOSBox (which looks, feels and acts just like the real thing), but then, those are self-contained and can be kept pure. I can see the use in PuTTY, as it allows you to log into a UNIX/Linux machine and use it as if you were actually on it (all in a little Unix-like command window), but I have a hard time seeing the use of Cygwin myself. Sounds like just using UNIX/Linux would be a better choice, and maybe Windows in a VM if absolutely required.

Honestly, although I don't think it's well-maintained (if at all), I think UnxUtils provides better integration with Windows. It's made up of Windows-native .exe versions of common GNU utilities, which can be used in the regular command prompt by simply dropping them in C:\WINDOWS or (better yet) extracting them to a new folder and adding it to the PATH. These don't require a special program like Cygwin just to run, and again, they're native Windows binaries.

Edited 2008-12-18 19:51 UTC

Reply Score: 2

by sm42 on Sat 20th Dec 2008 15:31 UTC
Member since:

All the "terminal" you need:

Reply Score: 1