A compatibility layer is a term that refers to components that allow for non-native support of components.
In software engineering, a compatibility layer allows binaries for a legacy or foreign system to run on a host system. This translates system calls for the foreign system into native system calls for the host system. With some libraries for the foreign system, this will often be sufficient to run foreign binaries on the host system.
Hardware compatibility layers involve tools that allow hardware emulation.
Contents |
Software
Examples include:
- Wine, which runs some Microsoft Windows binaries on Unix-like systems using a program loader and the Windows API implemented in DLLs
- Cygwin, which allows unix applications to run under Windows.
- Windows's application compatibility layers (Application Compatibility Toolkit) to attempt to run poorly written applications, or those written for earlier versions of the platform.[1]
- Lina, which runs some Linux binaries with native look and feel on Windows, Mac OS X and Unix-like systems.
- Compatibility layer in kernel
- Linuxulator, the Linux compatibility layer on the FreeBSD, which enables binaries built specifically for Linux to run on FreeBSD[2] with the same way as the native FreeBSD API layer[3]. FreeBSD also has some Unix-like system emulations includes NDIS, NetBSD, PECoff, SVR4 and different CPU version of FreeBSD[4].
- NetBSD has some Unix-like system emulations[5].
- Mach and Darwin binary compatibility for NetBSD/powerpc and NetBSD/i386.
- The PEACE Project(aka COMPAT_PECOFF) has Win32 compatible layer for NetBSD. The project is now inactive.
A compatibility layer avoids both the complexity and the speed penalty of full hardware emulation. Some programs may even run faster than the original, e.g. some Linux applications running on FreeBSD's Linux compatibility layer may or may not perform better than the same applications on Red Hat Linux, and benchmarks are occasionally run on Wine to compare it to Windows NT-based operating systems[6].
Even on similar systems, the details of implementing a compatibility layer can be quite intricate and troublesome; a good example is the IRIX binary compatibility layer in the MIPS architecture version of NetBSD.[7]
A compatibility layer requires the host system's CPU to be (upwardly) compatible to that of the foreign system. Thus, for example, an MS Windows compatibility layer is not possible on PowerPC hardware, since MS Windows requires an x86 CPU; in that case, full emulation is needed.
Hardware
Hardware compatibility layers involve tools that allow hardware emulation. Some hardware compatibility layers involve breakout boxes, since breakout boxes can provide compatibility for certain computer buses that are otherwise incompatible with the machine.
See also
- Hypervisor
- Paravirtualization
- Emulator
- Cross-platform virtualization
- Computing platform
- Shim (computing)
References
- ^ Charlie Russel, Microsoft MVP for Windows Server and Tablet PC (2002-02-18). "Application Compatibility in Windows XP". http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/russel_02february18.mspx.
- ^ "Linux emulation in FreeBSD". http://www.freebsd.org/doc/en/articles/linux-emulation/index.html.
- ^ Emulation
- ^ A look inside...
- ^ NetBSD Binary Emulation
- ^ BenchMark-0.9.5 - The Official Wine Wiki
- ^ Emmanuel Dreyfus, ONLamp. "IRIX Binary Compatibility". http://www.onlamp.com/pub/a/bsd/2002/08/08/irix.html.
External links
- Windows XP Application Compatibility Technologies (Dave Morehouse and Todd Phillips, Microsoft Corporation, 1 June 2001)
This entry is from Wikipedia, the leading user-contributed encyclopedia. It may not have been reviewed by professional editors (see full disclaimer)
