.\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.022.
.TH FSG "1" "July 2023" "FSG lsb_release v2.0" FSG
.SH NAME
FSG \- manual page for FSG lsb_release v2.0
.SH SYNOPSIS
.B lsb_release
[\fIOPTION\fR]...
.SH DESCRIPTION
FSG lsb_release v2.0 prints certain LSB (Linux Standard Base) and
Distribution information.
.PP
With no OPTION specified defaults to \fB\-v\fR.
.SH OPTIONS
.HP
\fB\-v\fR, \fB\-\-version\fR
.IP
Display the version of the LSB specification against which the distribution is compliant.
.HP
\fB\-i\fR, \fB\-\-id\fR
.IP
Display the string id of the distributor.
.HP
\fB\-d\fR, \fB\-\-description\fR
.IP
Display the single line text description of the distribution.
.HP
\fB\-r\fR, \fB\-\-release\fR
.IP
Display the release number of the distribution.
.HP
\fB\-c\fR, \fB\-\-codename\fR
.IP
Display the codename according to the distribution release.
.HP
\fB\-a\fR, \fB\-\-all\fR
.IP
Display all of the above information.
.HP
\fB\-s\fR, \fB\-\-short\fR
.IP
Use short output format for information requested by other options (or version if none).
.HP
\fB\-h\fR, \fB\-\-help\fR
.IP
Display this message.
.SH FILES

If the installation is LSB compliant, the \fB"/etc/lsb-release"\fR
file should contain the \fBLSB_VERSION\fR field. 
The value of the field should be a colon separated list of
supported module versions indicating the LSB specification 
modules to which the installation is compliant. If the installation is not
compliant, the above field should 
.B not
be present.

Optional fields are \fBDISTRIB_ID\fR, \fBDISTRIB_RELEASE\fR,
\fBDISTRIB_CODENAME\fR, \fBDISTRIB_DESCRIPTION\fR and can be used to
override information which is parsed from the 
\fB"/etc/\fIdistrib\fB-release"\fR file.

If the \fB"/etc/lsb-release.d"\fR directory exists, it is
searched for filenames which are taken as additional module-version
strings to add to \fBLSB_VERSION\fR.
 
The \fB"/etc/\fIdistrib\fB-release"\fR file contains a description line
which is parsed to get information (especially on currently non-LSB
compliant systems).

The required line style is:
.br 
"\fIDistributor\fR \fBrelease\fR \fIx.x\fR \fB(\fR\fICodename\fR\fB)\fR"

Where \fIDistributor\fR can be a couple of words, but then concatenated
(i.e. Linux Foo BarLinux Linux -> FooBarLinux),
.br
\fIx.x\fR starts with a digit followed by any non-blank characters,
\fICodename\fR will also be concatenated (blanks cleanup only).

\fBrelease\fR may not be used as a keyword in \fBDISTRIB_DESCRIPTION\fR
if you don't want to override \fB"/etc/\fIdistrib\fB-release"\fR data.

\fBNotice:\fR To support the \fBDebian\fR distributions' lack of
information (see "/etc/debian_version" file) some have been directly
added into the \fBlsb_release\fR script.
.SH EXAMPLES
If the "\fB/etc/lsb-release\fR" file contains:

LSB_VERSION="core-2.0-ia64:core-2.0-noarch"
.br
DISTRIB_DESCRIPTION="I enjoy using my distrib"

and the "\fB/etc/lsb-release.d\fR" directory contains:

graphics-2.0-ia64    graphics-2.0-noarch

and the "\fB/etc/foobar-release\fP" file contains:

My Linux Distrib release 1.0RC4 (TryIt)

Then the results of various options will be:

.B $ ./lsb_release --all
.br
LSB Version:    core-2.0-ia64:core-2.0-noarch:graphics-2.0-ia64:graphics-2.0-noarch
.br
Distributor ID: MyDistrib
.br
Description:    I enjoy using my distrib
.br
Release:        1.0RC4
.br
Codename:       TryIt

.B $ ./lsb_release -a -s
.br
1.0 MyDistrib "I enjoy using my distrib" 1.0RC4 TryIt

If the "/etc/lsb-release" file is absent (indicating this is
not an LSB compliant distribution), the result will be:

.B $ ./lsb_release -a
.br
LSB Version:    n/a
.br
Distributor ID: MyDistrib
.br
Description:    My Linux Distrib release 1.0RC4 (TryIt)
.br
Release:        1.0RC4
.br
Codename:       TryIt
.SH "REPORTING BUGS"
Report bugs at http://bugs.linuxbase.org.
Please include a complete, self-contained example that will allow the
bug to be reproduced, and say which version of lsb_release you are using.
.SH COPYRIGHT
Copyright \(co 2000, 2002, 2004 Free Standards Group, Inc.
.br
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
.PP
Originally written by Dominique MASSONIE.