LSB1.1: /proc/cpuinfo

Stuart Anderson anderson at
Fri Jan 4 08:38:09 PST 2002

On Fri, 4 Jan 2002, Alan Cox wrote:

> The LSB doesn't define what happens when you use a command or library
> function that is not in the LSB. If you use glibc internal functions you
> will get burned (especially if the folks trying to replace glibc with
> something much lighter actually succeed)

>From Chapter 1: Definitions.

Non-LSB-Compliant Application

An application which has been written to include system routines, commands, or
other resources not included in this document, or which has been compiled into
a format different from those specified here, or which does not behave as
specified in this document.

This sort of says it, though in an indirect way.


Stuart R. Anderson                               anderson at

Metro Link Incorporated                          South Carolina Office
5807 North Andrews Way                           129 Secret Cove Drive
Fort Lauderdale, Florida 33309                   Lexington, SC 29072
voice: 954.660.2500                              voice: 803.951.3630                        XFree86 Core Team

More information about the lsb-discuss mailing list