Quote:
Originally Posted by DMcCunney
(MKS no longer exists as such, but the Toolkit became the basis for Interix, which underlay Microsoft Services for Unix package.)
______
Dennis
|
Well, not strictly true. The developers of Interix were former MKS folks who wanted a "purer" solution, but they didn't use any MKS code that I'm aware of.
To set qualifications for this comment, I should state that I ran Interix (called OpenNT at that point) in it's first semi-public implementation, and again when it officially released. I was later the first (and only) Microsoft MVP for Services for Unix (SFU), and was involved as their contract tech writer from the very beginning, writing the initial whitepapers for SFU v1 (which was based on a very limited subset of the MKS Toolkit). MS acquired Softway Systems shortly after the release of Interix 2.2 and just about the time of Services for UNIX 2.0, which did NOT include any Interix code, but was purely based on the MKS code they had licensed.
It wasn't until SFU v3.0 was released that the Interix subsystem was included in the product, completely replacing the MKS code. With SFUv3 and later SFUv3.5 (the final release), the Interix subsystem completely replaced the (less than satisfactory) NT POSIX subsystem, giving Windows Server a fully POSIX compliant subsystem that ran as an equal partner to the Windows subsystem.
ETA: I should also add that some of the people acquired when MS bought out Softway Systems ended up being key in the development of PowerShell, for which I am still a Microsoft MVP.