-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathlsb_release.examples
93 lines (73 loc) · 2.77 KB
/
lsb_release.examples
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
[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.
[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
[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.