By default, Windows.
With certain add-ons, however, Windows can be made POSIX-compliant.
POSIX stands for Portable Operating System Interface for UniX. It is an IEEE 1003.1 standard that defines the language interface between application programs and the Unix operating system. Adherence to the POSIX ensures compatibility when programs are moved/migrated from one unix computer to another.AnswerStrictly speaking, POSIX is an API specification, in conjunction with a specification of certain specific utility programs which must be present. While originally based on the UNIX Operating System, POSIX does not have to mean a UNIX system. For example, both certain versions of Windows NT and IBM's OS/360 have received POSIX certification as complying with the specification. As noted above, POSIX is about insuring compatibility of programs between systems, allowing a POSIX-compliant program to run on any POSIX-compliant Operating System.
Without getting into too much detail, it's largely a choice made by developers of the system whether or not providing a POSIX-compliant or at least POSIX-compatible system is worth the effort. The aim of POSIX is not to be a standard defining operating systems themselves so much as standard for a suitable environment for source compatibility between different operating systems, primarily those of a Unix-compliant or Unix-like design. I believe full POSIX compliance is a requirement of the Single Unix Specification in turn, the SUS being a standard that actually DOES define what an operating system should be (In this case, to be considered a real UNIX system. Needless to say Windows is nowhere in the neighborhood of SUS compliance.). The idea behind POSIX is to make it much easier for Unix/Unix-like software developers to write software and have it available for those who provide selections of software for any given Unix platform. Program written for POSIX OS A can be built for POSIX OS B with little or no changes to the source code of the program, usually the only changes needed are bits closer to the metal or usage of libraries not concerned with POSIX compliance. POSIX does not concern itself or define any standard for binary compatibility. This is not just a matter of scope but the fact that such an application of the standard would only be useful on OS-to-OS ports of a program being made on the same system architectute, which would make POSIX less useful for Unix systems, which are frequently deployed in mixed-architecture environments. Windows has a POSIX layer available as a download, but generally it's a limited, only halfway-compliant POSIX system. Windows itself is not designed in a way that is generally POSIX-compatible, since it's software architecture is a fundamentally very different thing from Unix. For most Windows users and developers: POSIX compliance is of very little practical use, as Windows' design still requires some very POSIX-unfriendly additions to source code to build correctly on Windows. For Windows to become a POSIX system would require Windows itself to be completely remade in ways that breaks all backwards compatibility with previous versions of Windows, something most users would not like. When open source software is ported to Windows, one generally uses MinGW or tools like cmake that provide build scripts/files for POSIX and non-POSIX systems alike.
The goal of POSIX is to ease the task of cross-platform software development by establishing a set of guidelines for operating system vendors to follow. Ideally, a developer should have to write a program only once to run on all POSIX-compliant systems.
QNX's shell is POSIX compliant, so you can use Unix commands on the system. To "rename" a file, you move it. mv oldfilename newfilename is equivalent to renaming the file.
POSIX was designed as a standard to enhance portability. That is why it is portable if you use the POSIX standard.
POSIX stands for Portable Operating System Interface..
I'm not sure what you are referring to by "structure." System binaries, like all other binaries in Linux, are in ELF class. The binaries are typically placed in /bin or /sbin. Almost all programs in Linux are POSIX-compliant.
o/s2,posix
Sorry that's a very broad question. Linux aims to be fully POSIX compatible, and so a Google search regarding POSIX system calls or a POSIX reference book should cover your question. Good Luck! =)
"posix" is a latest version of a operating system of "unix",published by ieee 1003.2 standard. Specifically, it's an acronym for Portable Operating Systems Interface. When used, it should specify which version of the specification is being referenced. E.g. POSIX.1-2008 is the latest.
Comparison: What's best or correct use of "Compliant", is it "Compliant with"? or "Compliant to"?The answer is: "Compliant with": "compliant with" is correct use. e.g. "People used to be compliant with nature's laws, and thus there used to be a harmony between human beings and nature. (See Ref @ "http://www.thefreedictionary.com/compliant")
POSIX threads are user level threads, because had a interface library and the operating systems don't control his ejecution and does not know