The common part of the LSB Specification that describes those parts of the interface that remain constant across all hardware implementations of the LSB.


The architectural part of the LSB Specification which describes the specific parts of the interface that are platform specific. The archLSB is complementary to the gLSB.

LSB Implementation Conformance

An implementation satisfying the following requirements:

  1. The implementation shall implement fully the architecture described in the hardware manual for the target processor architecture.

  2. The implementation shall be capable of executing compiled applications having the format and using the system interfaces described in this document.

  3. The implementation shall provide libraries containing the interfaces specified by this document, and shall provide a dynamic linking mechanism that allows these interfaces to be attached to applications at runtime. All the interfaces shall behave as specified in this document.

  4. The map of virtual memory provided by the implementation shall conform to the requirements of this document.

  5. The implementation's low-level behavior with respect to function call linkage, system traps, signals, and other such activities shall conform to the formats described in this document.

  6. The implementation shall provide all of the mandatory interfaces in their entirety.

  7. The implementation may provide one or more of the optional interfaces. Each optional interface that is provided shall be provided in its entirety. The product documentation shall state which optional interfaces are provided.

  8. The implementation shall provide all files and utilities specified as part of this document in the format defined here and in other referenced documents. All commands and utilities shall behave as required by this document. The implementation shall also provide all mandatory components of an application's runtime environment that are included or referenced in this document.

  9. The implementation, when provided with standard data formats and values at a named interface, shall provide the behavior defined for those values and data formats at that interface. However, a conforming implementation may consist of components which are separately packaged and/or sold. For example, a vendor of a conforming implementation might sell the hardware, operating system, and windowing system as separately packaged items.

  10. The implementation may provide additional interfaces with different names. It may also provide additional behavior corresponding to data values outside the standard ranges, for standard named interfaces.

LSB Application Conformance

An application with the following characteristics:

  1. Its executable files are either shell scripts or object files in the format defined for the Object File Format system interface.

  2. Its object files participate in dynamic linking as defined in the Program Loading and Linking System interface.

  3. It employs only the instructions, traps, and other low-level facilities defined in the Low-Level System interface as being for use by applications.

  4. If it requires any optional interface defined in this document in order to be installed or to execute successfully, the requirement for that optional interface is stated in the application's documentation.

  5. It does not use any interface or data format that is not required to be provided by a conforming implementation, unless:

  6. It must not use any values for a named interface that are reserved for vendor extensions.

A strictly conforming application does not require or use any interface, facility, or implementation-defined extension that is not defined in this document in order to be installed or to execute successfully.


An LSB conforming application is expected to have no dependencies on any vendor extensions to this document. The most common such extensions are additional function entry points and additional libraries other than the ones defined in this document. If an application requires such extensions, it is not portable, since other LSB conforming implementations may not provide those extensions.

An LSB conforming application is required to use system services on the implementation on which it is running, rather than importing system routines from some other implementation. Thus, it must link dynamically to any routines in the implementation that perform system traps to kernel services.

It is to be expected that some applications may be companion applications to other applications. For example, a query application may be a companion to a database application; a preprocessor may be an adjunct to one or more compilers; a data reformatter may convert data from one document manager to another. In such cases, the application may or may not be LSB conforming, regardless of whether the other application on which it is dependent is LSB conforming. If such an application merely uses data produced by another application, the application's compliance is independent of the other application's compliance. If such an application actually invokes another application during execution (as, for example, a third-party math library), the invoking application is LSB conforming only if it also constitutes a LSB conforming application in combination with the invoked application.

Shell Script

A file that is read by an interpreter (e.g., awk). The first line of the shell script includes a reference to its interpreter binary.