Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
POSIX
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
====POSIX for Microsoft Windows==== *[[Cygwin]] provides a largely POSIX-compliant development and run-time environment for [[Microsoft Windows]]. *[[MinGW]], a [[fork (software development)|fork]] of Cygwin, provides a less POSIX-compliant development environment and supports compatible [[C (programming language)|C]]-programmed applications via [[Msvcrt]], Microsoft's old Visual C [[runtime library]]. *libunistd, a largely POSIX-compliant development library originally created to build the Linux-based C/[[C++]] source code of [[CinePaint]] as is in [[Microsoft Visual Studio]]. A lightweight implementation that has POSIX-compatible header files that map POSIX APIs to call their Windows API counterparts.<ref>{{cite web|url = https://github.com/robinrowe/libunistd|title=libunistd| last=Rowe|first=Robin|date=8 September 2022|website=Github|publisher=|access-date=18 February 2023|quote=If you want to build single codebase C++ code to run on Windows, Linux and MacOS, you need this for Windows}}</ref> *[[Microsoft POSIX subsystem]], an optional Windows subsystem included in Windows NT-based operating systems up to Windows 2000. It supported POSIX.1 as it stood in the 1990 revision, without [[pthreads|threads]] or [[Berkeley socket|sockets]]. *[[Interix]], originally OpenNT by Softway Systems, Inc., is an upgrade and replacement for [[Microsoft POSIX subsystem]] that was purchased by [[Microsoft]] in 1999. It was initially marketed as a stand-alone add-on product and then later included as a component in [[Windows Services for UNIX]] (SFU) and finally incorporated as a component in [[Windows Server 2003 R2]] and later Windows OS releases under the name "Subsystem for UNIX-based Applications" (SUA); later made deprecated in 2012 (Windows 8)<ref>{{cite web|url=https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831568(v=ws.11)|title=Features Removed or Deprecated in Windows Server 2012|date=31 August 2016|website=[[Microsoft Docs]]}}</ref> and dropped in 2013 (2012 R2, 8.1). It enables full POSIX compliance for certain [[Microsoft Windows]] products.{{Citation needed|date=March 2011}} *[[Windows Subsystem for Linux]], also known as WSL, is a compatibility layer for running Linux binary executables natively on Windows 10 and 11 using a Linux image such as Ubuntu, Debian, or OpenSUSE among others, acting as an upgrade and replacement for Windows Services for UNIX. It was released in beta in April 2016. The first distribution available was Ubuntu. *[[UWIN]] from AT&T Research implements a POSIX layer on top of the Win32 APIs. *[[MKS Toolkit]], originally created for MS-DOS, is a software package produced and maintained by [[MKS Inc.]] that provides a [[Unix-like]] environment for scripting, connectivity and porting [[Unix]] and [[Linux]] software to both 32- and 64-bit [[Microsoft Windows]] systems. A subset of it was included in the first release of [[Windows Services for UNIX]] (SFU) in 1998.<ref>{{cite web|url=http://www.microsoft.com/ntserver/nts/exec/overview/sfu.asp|title=Windows NT Services for UNIX Add-On Pack|website=[[Microsoft]]|archive-url=https://web.archive.org/web/19990508011234/http://www.microsoft.com/ntserver/nts/exec/overview/sfu.asp|archive-date=8 May 1999}}</ref><ref>{{cite press release|url=http://mks.com/press/981109a.htm|title=MKS Solves Enterprise Interoperability Challenges|archive-url=https://web.archive.org/web/19990428003638/http://mks.com/press/981109a.htm|archive-date=28 April 1999}}</ref> *[[Microsoft Windows library files#Runtime libraries|Windows C Runtime Library]] and [[Winsock|Windows Sockets API]] implement commonly used POSIX API functions for file, time, environment, and socket access,<ref>{{cite web |url=https://docs.microsoft.com/en-us/previous-versions/ms235384(v=vs.100) |title=Deprecated CRT Functions |date=15 October 2009 |access-date=23 July 2022 |website=[[Microsoft Docs]]}}</ref> although the support remains largely incomplete and not fully interoperable with POSIX-compliant implementations.<ref>{{cite web |url=https://docs.microsoft.com/en-us/windows/win32/winsock/porting-socket-applications-to-winsock?redirectedfrom=MSDN |title=Porting Socket Applications to Winsock |date=7 January 2021 |access-date=23 July 2022 |website=[[Microsoft Docs]]}}</ref><ref>{{cite web|url=https://tangentsoft.net/wskfaq/articles/bsd-compatibility.html|title=Winsock Programmer's FAQ Articles: BSD Sockets Compatibility|date=31 August 2015 |access-date=8 October 2015 |publisher=Warren Young}}</ref>{{discuss|BSD sockets as "POSIX"}}
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)