Interix

Last updated
Interix
Other namesOpenNT
Original author(s) Softway Systems
Developer(s) Microsoft
Initial releaseMarch 29, 1996;27 years ago (1996-03-29)
Stable release
Subsystem for UNIX-based Applications in Microsoft Windows 7 and Windows Server 2008 R2 (6.1) / March 11, 2010;13 years ago (2010-03-11)
Operating system Microsoft Windows

Interix was an optional[ citation needed ], POSIX-conformant[ citation needed ] Unix subsystem for Windows NT operating systems. Interix was a component of Windows Services for UNIX, and a superset of the Microsoft POSIX subsystem. Like the POSIX subsystem, Interix was an environment subsystem for the NT kernel. It included numerous open source utility software programs and libraries. Interix was originally developed and sold as OpenNT until purchased by Microsoft in 1999.

Contents

Interix versions 5.2 and 6.0 were respective components of Microsoft Windows Server 2003 R2, Windows Vista Enterprise, Windows Vista Ultimate, and Windows Server 2008 as Subsystem for Unix-based Applications [1] (SUA [2] ). Version 6.1 was included in Windows 7 (Enterprise and Ultimate editions) but disabled by default, [3] and in Windows Server 2008 R2 (all editions). [4] It was available as a deprecated [5] separate download for Windows 8 and Windows Server 2012, and is not available at all on Windows 10.

Details

The complete installation of Interix included (at version 3.5):

The development environment included support for C, C++ and Fortran. Threading was supported using the Pthreads model. Additional languages could be obtained (Python, Ruby, Tcl, etc.). Unix-based software packaging and build tools were available for installing or creating pre-build software packages.

Starting with release 5.2 (Server 2003/R2) the following capabilities were added: [6]

With release 6.0 (Vista and Server 2008) the following new features were added:

Interix release 6.0 for Vista was only available with the Ultimate and Enterprise editions.

Interix release 6.1 was available for Windows Server 2008 R2 and Windows 7 for the Enterprise and Ultimate editions.

Support

Traditional support was provided by Microsoft for a fee or service contract, though released hotfixes can usually be obtained free of charge from Microsoft. Previously, free support could be found via the forums at the SUA Community site [7] and with the FAQ, [8] however this appears to have been withdrawn.

Additions

Additional pre-built applications and development libraries could be obtained for free from the SUA Community site, the Gentoo-prefix site and the Debian-Interix site. These included commonly used applications not part of the Microsoft installation such as OpenSSH, Git, Python and bash.

The SUA Community site included for developers of Interix and the site has been contracted by Microsoft for several Interix and SUA updates of utilities and documentation.

History

This product began to be developed in 1996 under the product name OpenNT by Softway Systems, Inc. before the name was changed to Interix in 1998. The last release by Softway Systems was release 2.2. Softway Systems had virtually completed the next release code-named Firebrand in 1999 which became the basis of Interix 3.0.

The Interix interoperability suite developed by Softway Systems Inc., included substantial code from OpenBSD,. [9] [10] Microsoft acquired Interix in 1999. [11] [12]

Microsoft continued to distribute Interix 2.2 as a standalone product until 2002.

Interix release 3.0 was released as component of Windows Services for Unix (SFU) 3.0 in 2002. Interix release 3.5 was released as component of SFU 3.5 in January, 2004.

Interix became integrated as a component of the regular Windows OS distribution [6] as a component of Windows Server 2003 R2 in December, 2005 at release 5.2 and was a component of the Windows Vista release as release 6.0 (RTM November, 2006). Windows Server 2008 had release 6.0. Windows 7 and Windows Server 2008 R2 included SUA 6.1.

Microsoft announced in 2011 that Interix would not be included in Windows versions after Windows 8 and customers should start migrating their applications to an alternative solution. [13]

Releases

OpenNT Commands & Utilities, Release 1.0 (1.0)
1996-03-29 OpenNT Commands & Utilities, Release 1.0 for WinNT POSIX Subsystem
1996-07 X11R6 Server (Win32)
1996-08 telnetd (and inetd)
OpenNT 1.1 and SDK (1.1)
1996-09 OpenNT 1.1 and SDK for WinNT i386, alpha
OpenNT 2.0 (2.0)
1997-05 OpenNT 2.0 (Apache httpd and xv) for WinNT i386, alpha
1997-08-12 "OpenNT: UNIX Application Portability to Windows NT via an Alternative Environment Subsystem" Usenix paper [14]
1997-08-12 "OpenNT: UNIX Application Portability to Windows NT" Usenix presentation [15] (again 1998-06)
1997-11 "inetd and telnetd on Windows NT with OpenNT"
OpenNT 2.1 (2.1)
1997-12 OpenNT 2.1 for WinNT i386, alpha
1998-01 OpenNT 2.1
1998-02 "Technical Note #9: inetd and the Daemon Package"
1998-spring paper update
1998-06 Interix 2.1 rebranding
Interix 2.2 (2.2)
1998-06 Interix 2.2(.0)?
1999-02 SFU 1.0 en for WinNT 4.0(SP3+) i386, alpha (does not contain Interix; included for historical purposes with MS acquisition)
1999-09-17 Acquired by Microsoft
1999-12 Interix 2.2(.0) for WinNT 3.51(SP5+),4.0(SP3+),5.0
Interix 2.2 Service Pack 1 (2.2.4)
Interix 2.2.5 (2.2.5)
2000-02 Interix 2.2.5 for WinNT 4.0(SP5+),5.0
2000-04 SFU 2.0 en for WinNT 4.0(SP4+),5.0 i386 (does not contain Interix; included for historical purposes with MS acquisition)
2000-06 SFU 2.0 ja for WinNT 4.0(SP4+),5.0 i386 (does not contain Interix; included for historical purposes with MS acquisition)
2001-06-30 "Strangely Enough It All Turns Out Well" Usenix talk [16]
Microsoft Windows Services for UNIX 3.0 (3.0)
2002-05 SFU 3.0 en for WinNT 4.0(SP6a+),5.0,5.1 i386
  • Interix 3.0 (AKA Firebrand)
2002-10 SFU 3.0 ja for WinNT 4.0(SP6a+),5.0,5.1 i386
Microsoft Windows Services for UNIX 3.5 (3.5)
2004-01 SFU 3.5 en, ja for WinNT 5.0,5.1,5.2 i386
Windows Server 2003 R2 (all editions) Subsystem for UNIX-based Applications (5.2)
2005-12-06 WinNT 5.2 R2
Windows Vista (Ultimate and Enterprise editions) Subsystem for UNIX-based Applications (6.0)
2006-11-08 WinNT 6.0 (2007-01-30)
Windows Server 2008 (all editions) Subsystem for UNIX-based Applications (6.0)
2008-02-04 WinNT 6.0
Subsystem for UNIX-based Applications in Microsoft Windows 7 and Windows Server 2008 R2 (6.1)
2010-03-11 WinNT 6.1

See also

Related Research Articles

Microsoft Windows was announced by Bill Gates on November 10, 1983. Microsoft introduced Windows as a graphical user interface for MS-DOS, which had been introduced two years earlier. The product line evolved in the 1990s from an operating environment into a fully complete, modern operating system over two lines of development, each with their own separate codebase.

<span class="mw-page-title-main">KornShell</span> Bourne shell backward compatible Unix shell created by David Korn

KornShell (ksh) is a Unix shell which was developed by David Korn at Bell Labs in the early 1980s and announced at USENIX on July 14, 1983. The initial development was based on Bourne shell source code. Other early contributors were Bell Labs developers Mike Veach and Pat Sullivan, who wrote the Emacs and vi-style line editing modes' code, respectively. KornShell is backward-compatible with the Bourne shell and includes many features of the C shell, inspired by the requests of Bell Labs users.

The Portable Operating System Interface is a family of standards specified by the IEEE Computer Society for maintaining compatibility between operating systems. POSIX defines both the system and user-level application programming interfaces (APIs), along with command line shells and utility interfaces, for software compatibility (portability) with variants of Unix and other operating systems. POSIX is also a trademark of the IEEE. POSIX is intended to be used by both application and system developers.

Distributed Component Object Model (DCOM) is a proprietary Microsoft technology for communication between software components on networked computers. DCOM, which originally was called "Network OLE", extends Microsoft's COM, and provides the communication substrate under Microsoft's COM+ application server infrastructure.

Remote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft Corporation which provides a user with a graphical interface to connect to another computer over a network connection. The user employs RDP client software for this purpose, while the other computer must run RDP server software.

<span class="mw-page-title-main">Windows NT 3.1</span> First major release of Windows NT, released in 1993

Windows NT 3.1 is the first major release of the Windows NT operating system developed by Microsoft, released on July 27, 1993.

Windows Services for UNIX (SFU) is a discontinued software package produced by Microsoft which provided a Unix environment on Windows NT and some of its immediate successor operating-systems.

<span class="mw-page-title-main">Architecture of Windows NT</span> Overview of the architecture of the Microsoft Windows NT line of operating systems

The architecture of Windows NT, a line of operating systems produced and sold by Microsoft, is a layered design that consists of two main components, user mode and kernel mode. It is a preemptive, reentrant multitasking operating system, which has been designed to work with uniprocessor and symmetrical multiprocessor (SMP)-based computers. To process input/output (I/O) requests, it uses packet-driven I/O, which utilizes I/O request packets (IRPs) and asynchronous I/O. Starting with Windows XP, Microsoft began making 64-bit versions of Windows available; before this, there were only 32-bit versions of these operating systems.

System File Checker (SFC) is a utility in Microsoft Windows that allows users to scan for and restore corrupted Windows system files.

A hybrid kernel is an operating system kernel architecture that attempts to combine aspects and benefits of microkernel and monolithic kernel architectures used in operating systems.

Resource Kit is a term used by Microsoft for a set of software resources and documentation released for their software products, but which is not part of that product. Resource kits offer supplementary resources such as technical guidance, compatibility and troubleshooting information, management, support, maintenance and deployment guides and multipurpose useful administrative utilities, which are available separately.

NTBackup is the built-in backup application introduced in Windows NT 3.51 and included in Windows NT 4.0, Windows 2000, Windows XP, and Windows Server 2003. NTBackup comprises a command-line utility and a set of wizard interfaces that provide multiple options to create, customize, and manage backups, and it is integrated with Shadow Copy and Task Scheduler. NTBackup creates backups in a proprietary BKF file format to external sources including floppy disks, hard drives, tape drives, and ZIP drives.

Windows Vista contains a range of new technologies and features that are intended to help network administrators and power users better manage their systems. Notable changes include a complete replacement of both the Windows Setup and the Windows startup processes, completely rewritten deployment mechanisms, new diagnostic and health monitoring tools such as random access memory diagnostic program, support for per-application Remote Desktop sessions, a completely new Task Scheduler, and a range of new Group Policy settings covering many of the features new to Windows Vista. Subsystem for UNIX Applications, which provides a POSIX-compatible environment is also introduced.

UWIN is a computer software package created by David Korn which allows programs written for the operating system Unix to be built and run on Microsoft Windows with few, if any, changes. Some of the software development was subcontracted to Wipro, India. References, correct or not, to the software as U/Win and AT&T Unix for Windows can be found in some cases, especially from the early days of its existence.

Security Support Provider Interface (SSPI) is a component of Windows API that performs security-related operations such as authentication.

<span class="mw-page-title-main">Microsoft POSIX subsystem</span> Subsystem shipped with the first versions of Windows NT

Microsoft POSIX subsystem is one of four subsystems shipped with the first versions of Windows NT, the other three being the Win32 subsystem which provided the primary API for Windows NT, plus the OS/2 and security subsystems.

Windows NT is a proprietary graphical operating system produced by Microsoft, the first version of which was released on July 27, 1993. It is a processor-independent, multiprocessing and multi-user operating system.

<span class="mw-page-title-main">Unix-like</span> Operating system that behaves in a manner similar to a Unix system

A Unix-like operating system is one that behaves in a manner similar to a Unix system, although not necessarily conforming to or being certified to any version of the Single UNIX Specification. A Unix-like application is one that behaves like the corresponding Unix command or shell. Although there are general philosophies for Unix design, there is no technical standard defining the term, and opinions can differ about the degree to which a particular operating system or application is Unix-like.

Environmental subsystems are central components of operating systems of the Windows NT type. They allow the operating system to run software developed for the platform in question. For example, Windows NT 4.0 has four environmental subsystems, viz Win32, DOS or Win16, OS/2, and POSIX, the latter of which is a Unix standard. The latter resides primarily in the Dynamic Link Library posix.dll.

<span class="mw-page-title-main">Windows Subsystem for Linux</span> Compatibility layer for running Linux binary executables natively on Windows

Windows Subsystem for Linux (WSL) is a feature of Windows that allows developers to run a Linux environment without the need for a separate virtual machine or dual booting. There are two versions of WSL: WSL 1 and WSL 2. WSL 1 was first released on August 2, 2016, and acts as a compatibility layer for running Linux binary executables by implementing Linux system calls on the Windows kernel. It is available on Windows 10, Windows 10 LTSB/LTSC, Windows 11, Windows Server 2016, Windows Server 2019 and Windows Server 2022.

References

  1. ↑ Windows Server 2003 R2 UNIX Interoperability Components
  2. ↑ "Subsystem for UNIX-based Applications". Archived from the original on 2006-03-23. Retrieved 2006-01-31.
  3. ↑ "LBW: Installing Interix". Lbw.sourceforge.net. Retrieved 2014-03-31.
  4. ↑ Utilities and SDK for Subsystem for UNIX-based Applications in Microsoft Windows 7 and Windows Server 2008 R2
  5. ↑ Features Removed or Deprecated in Windows Server 2012
  6. 1 2 "Windows 2003 R2 + Interix". Archived from the original on 2006-10-24. Retrieved 2006-10-15.
  7. ↑ SUA Community site
  8. ↑ Interix/SUA FAQ Page
  9. ↑ Dohnert, Roberto J. (2004-01-21), "Review of Windows Services for UNIX 3.5", OSNews , David Adams, archived from the original on 2008-02-11, retrieved 2020-07-19
  10. ↑ Reiter, Brian (2010-01-26). "WONTFIX: select(2) in SUA 5.2 ignores timeout". brianreiter.org.
  11. ↑ "Microsoft Acquires Softway Systems To Strengthen Future Customer Interoperability Solutions", Microsoft News Center, Microsoft, 1999-09-17
  12. ↑ "Milltech Consulting Inc". 2019. Archived from the original on 2020-09-18. Retrieved 2020-06-23.
  13. ↑ Installing SUA components on Windows 8
  14. ↑ Walli, Stephen R. (August 12, 1997). OPENNT: UNIX Application Portability to Windows NT via an Alternative Environment Subsystem. We're Not in Kansas Anymore. USENIX Windows NT Workshop, 1997. Retrieved 2022-05-20.
  15. ↑ Walli, Stephen R. (August 12, 1997). OPENNT: UNIX Application Portability to Windows NT. We're Not in Kansas Anymore. USENIX Windows NT Workshop, 1997. Retrieved 2022-05-20.
  16. ↑ Walli, Stephen R. (June 30, 2001). Strangely Enough, It All Turns Out Well (PDF). USENIX Technical Conference, 2001. Retrieved 2022-05-20.

Further reading

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.