Neverne Tome neka duboko udahnu:
SFU is substantially POSIX-compliant. If your LOB applications were written to take advantage of this portable standard, you will reap the benefits of that effort as you migrate to Windows—but not if you migrate to Linux, which is not yet POSIX compliant.
...
POSIX
Unlike Red Hat and other Linux distributions, which are not yet fully POSIX compliant, SFU contains a POSIX.1-conformant subsystem that includes support for both the full POSIX specification but also supports additional extensions and features, including sockets, Berkeley Software Distribution (BSD) 4.4 interfaces, System V interprocess communication (IPC) mechanisms, pseudo terminals, and memory mapped files that are not part of the POSIX.1 standard.
Both applications that are written to conform to the pure POSIX.1 specification, and those that use some combination of conditional compilation (#ifdef preprocessor commands) or wrapper functions to deal with possible alternatives, can be ported without modification to the SFU’s subsystem. Porting software to the SFU subsystem involves:
• Making the source as portable as possible.
If you’ve written a pure POSIX application, it should simply re-compile under Interix, but few applications are pure POSIX applications. Understanding where your application differs from POSIX, and using the guidelines for migration provided, can help your migration go smoothly.
• Using the extensions to POSIX that are supported. While SFU supports POSIX, it also supports common extensions and APIs taken from other standards, including the Single UNIX Specification and extensions taken from traditional UNIX systems, such as BSD or System V derivatives.
...
http://www.microsoft.com/techn...ions/interop/sfu/migun2wi.mspx
Commercial-Free !!!