As I recall in mid-2010 Microsoft stopped funding the SUA Community, then
backtracked. I thought I had stashed this info away, but I cannot find
it. Here is what I can find though:
http://blogs.msdn.com/b/sfu/archive/2010/07/06/suacommunity-com-
closure.aspx
--- start quote ---
6 Jul 2010 3:58 PM
0
SUACommunity.com Closure
Last week, I was equally surprised when I received the word that
SUACommunity.com is not getting the funds to continue functioning."
Yet, SUACommunity.com is still up. The forum section is broken though.
--- end quote ---
and
http://brianreiter.org/2010/08/24/the-sad-history-of-the-microsoft-posix-
subsystem/
--- start quote ---
The Sad History of the Microsoft POSIX Subsystem
...
Slowly Going Off the Rails
With Windows Server 2003 R2 (and only R2), Interix became a core
operating system component, rebranded as “Subsystem for UNIX
Applications” (SUA). Around this time, the core development team was
reformed in India rather than Redmond and some of the key Softway
developers moved on to other projects like Monad (PowerShell) or left
Microsoft. Interix for Windows Server 2003 R2 (aka Interix 5.2) was
broken. It shipped with corrupt libraries and a number of new but flawed
APIs and broke some previously stable APIs like select(). Also, related
to the inclusion of Interix as an OS component, SP2 for Windows Server
2003 clobbers Interix 3.5 installations.
--- end quote ---
1. Things broke after moving development to India. Sound familiar?
2. The OP may be seeing artefacts of the broken releases mentioned above.
and to round it off:
http://brianreiter.org/2011/09/15/sua-deprecated-in-windows-8/
--- quote ---
SUA Deprecated in Windows 8
One obvious reason to deprecate SUA is that loading the extra subsystem
makes Windows take a noticeably longer time to boot. The architecture is
very much at odds with the instant boot goals of Windows 8.
There have been a number of developments over the last few years that
makes Interix less compelling. Things like fast-CGI on IIS and an
official PHP port from Zend, lots of dynamic languages with native
Windows runtimes, mySQL and PostgreSQL for WIndows, C libraries like
pthreads for win32 and msys which have made Interix less necessary. For
perl-heads there is even Strawberry Perl which is supposed to be a lot
more CPAN friendly than ActiveState perl. I think Hyper-V and PowerShell
are the real strategic replacements for SUA, though. PowerShell
integrates with COM and WMI and fits the object nature of Windows better
than any POSIX shell could. Hyper-V lets you actually run your UNIX app
on Windows on a supported Linux platform which I’m sure smells much less
MacGuyver to CIOs than this weird Interix POSIX on Windows thing that
nobody ever heard of.
From the time that Hyper-V officially supported RHEL with hast
enlightened drivers and Jeffrey Snover decided that the new shell and
automation for Windows would be based on .NET and pivoted to build Monad/
PowerShell rather than putting KSH on every Windows machine, Interix’s
days were numbered. Now it’s official, Interix will be gone from the
world about 11 years when Windows 8 reaches end-of-life but if you are
smart you will jump ship now because this product will have the minimum
life support staff imaginable.
--- end quote ---
There's that boot time goal again :-)
--
Paul Sture