Cygwin 1.7 Released
jensend writes "The 1.7 branch of Cygwin, the Unix-like environment for Windows, has reached stable status after about 3 1/2 years of effort. Among many other changes, this release drops support for Windows 9x. Since the NT API and NT-based versions of Windows are more capable and somewhat less of a mismatch with POSIX (for instance, they include a security model), this has allowed for code path simplifications, better performance (particularly noticeable with pipe I/O), better security, and better POSIX compatibility."
Windows has had a POSIX layer of its own for awhile now, as "Services for Unix".
On the lighter-weight end, mingw can give you the basics, and they usually run much faster (even bash!) than Cygwin did. Maybe Cygwin is better now, it's just that I don't really see what it has over, well, any other way of running POSIX apps on Windows.
Don't thank God, thank a doctor!
For a while, I've been using a modified version of Cygwin in order to get proper UTF-8 support. Does the new version finally integrate a similar feature?
Let's be honest -- whether Linux or BSD is ready for the desktop, ready for the laptop is something slightly lacking, and I mostly have laptops these days. I couldn't take it anymore with Linux or BSD on my laptop, so I bought Vista. Of course, I can't live without a command line, because that's what I'm used to. I remembered having used Cygwin years ago, back in the Win95 days, and so I tried to give it ago.
No dice -- it doesn't really integrate with the rest of the system very well, I find. Maybe I'm just not doing it right, but whatever. Then I gave up and grabbed SFU off of Microsoft's website. It was OK, but not really stellar. It's more for running batch jobs and giving something to code against than for interactive use, same as Cygwin I guess.
Eventually I got so pissed sick of it all that I just bought a MacBook Pro so that I could have a Unix-ish environment without having to worry about power management or weird wifi issues that I'd had with Fedora, CentOS, Ubuntu, Slackware, ZenWalk, Mint, FreeBSD, OpenBSD and PC-BSD on the Toshiba hardware.
So, I guess my question is -- is Cygwin meant for interactive use, or just to give the POSIX API and build environment so you can see whether or not your code will compile against a Unix machine? Because it seems like they've been putting an awful lot of effort into this for a very long time for it to suck so bad if its meant to be an interactive method of accessing a Windows machine by Unix commands.
No, SFU/SUA is not the same as Cygwin... it is an implementation of a POSIX(?) userland that sits directly on top of the NT kernel. Also unlike Cygwin, it does not rely on the Win32 subsystem. It comes with numerous GNU, System V, and BSD utilities. One of its design goals is to be "source compatible", so that in general only a recompile of Unix apps is required. And I, like many others, would like to know when the release of all the actual tools for Windows 7 and Server 2008 R2 version of SUA will show up... it has now been over 2 months since general release of Windows 7. Sigh.
For *nix users, however, the reverse is usually true.
Making the half-assed GUI so lousy that people will actually prefer a command line interface is not the right way to go about doing things
Copy and paste: getclip and putclip. But I usually abbreviate them to p and c with a couple of wrappers.
I find Cygwin integrates really well with the rest of Windows, particularly when you mount the right drives in directories off the root, so that you have /c/ etc., but still have access to Win32 apps. I practically live in my bash/rxvt shell.