41
41
The basic file format of
43
is a newline\-separated list of environment\-like shell\-compatible variable assignments\&. It is possible to source the configuration from shell scripts, however, beyond mere variable assignments no shell features are supported, allowing applications to read the file without implementing a shell compatible execution engine\&.
43
is a newline\-separated list of environment\-like shell\-compatible variable assignments\&. It is possible to source the configuration from shell scripts, however, beyond mere variable assignments no shell features are supported (this means variable expansion is explicitly not supported), allowing applications to read the file without implementing a shell compatible execution engine\&. Variable assignment values should be enclosed in double or single quotes if they include spaces, semicolons or other special characters outside of A\-Z, a\-z, 0\-9\&. All strings should be in UTF\-8 format, and non\-printable characters should not be used\&. If double or single quotes or backslashes are to be used within variable assignments they should be escaped with backslashes, following shell style\&. It is not supported to concatenate multiple individually quoted strings\&. Lines beginning with "#" shall be ignored as comments\&.
46
46
contains data that is defined by the operating system vendor and should not be changed by the administrator\&.
48
Depending on the operating system other configuration files might be checked for OS identification as well, however only as fallback\&.
48
As this file only encodes names and identifiers it should not be localized\&.
52
might be a symlink to another file, but it is important that the file is available from earliest boot on, and hence must be located on the root file system\&.
54
For a longer rationale for
57
\m[blue]\fBAnnouncement of /etc/os\-release\fR\m[]\&\s-2\u[1]\d\s+2\&.
51
60
The following OS identifications parameters may be set using
65
A string identifying the operating system version, excluding any name information and suitable for presentation to the user\&. Example:
68
VERSION="15 (Rawhide)"\&.
73
A lower\-case string (no spaces) identifying the operating system, excluding any version information and suitable for processing by scripts or usage in generated file names\&. If not set defaults to
74
A string identifying the operating system version, excluding any OS name information, possibly including a release code name, and suitable for presentation to the user\&. This field is optional\&. Example:
77
VERSION="17 (Beefy Miracle)"\&.
82
A lower\-case string (no spaces or other characters outside of 0\-9, a\-z, "\&.", "_" and "\-") identifying the operating system, excluding any version information and suitable for processing by scripts or usage in generated file names\&. If not set defaults to
91
A space\-separated list of operating system identifiers in the same syntax as the
93
setting\&. Should list identifiers of operating systems that are closely related to the local operating system in regards to packaging and programming interfaces, for example listing one or more OS identifiers the local OS is a derivative from\&. An OS should generally only list other OS identifiers it itself is a derivative from, and not any OSes that are derived from it, but symmetric relationships are possible\&. Build scripts and similar should check this variable if they need to identify the local operating system and the value of
95
is not recognized\&. Operating systems should be listed in order of how closely the local operating system relates to the listed ones, starting with the closest\&. This field is optional\&. Example: for an operating system with
99
would be appropriate\&. For an operating system with
80
A lower\-case string (mostly numeric, no spaces) identifying the operating system version, excluding any name information and suitable for processing by scripts or usage in generated file names\&. Example:
108
A lower\-case string (mostly numeric, no spaces or other characters outside of 0\-9, a\-z, "\&.", "_" and "\-") identifying the operating system version, excluding any OS name information or release code name, and suitable for processing by scripts or usage in generated file names\&. This field is optional\&. Example:
111
VERSION_ID=11\&.04\&.
84
114
\fIPRETTY_NAME=\fR
86
A pretty operating system name in a format suitable for presentation to the user\&. May or may not contain an OS version of some kind, as suitable\&. If not set defaults to
88
PRETTY_NAME=Fedora 15 (Rawhide)\&.
116
A pretty operating system name in a format suitable for presentation to the user\&. May or may not contain a release code name or OS version of some kind, as suitable\&. If not set defaults to
117
PRETTY_NAME="Linux"\&. Example:
118
PRETTY_NAME="Fedora 17 (Beefy Miracle)"\&.
93
A suggested presentation color when showing the distribution name on the console\&. This should be specified as string suitable for inclusion in the ESC [ m ANSI/ECMA\-48 escape code for setting graphical rendition\&. Example:
123
A suggested presentation color when showing the OS name on the console\&. This should be specified as string suitable for inclusion in the ESC [ m ANSI/ECMA\-48 escape code for setting graphical rendition\&. This field is optional\&. Example:
100
If you are reading this file from code or a shell script to determine the OS or a specific version of it, use the ID and VERSION_ID fields\&. When looking for an OS identification string for presentation to the user use the PRETTY_NAME field\&.
132
A CPE name for the operating system, following the
133
\m[blue]\fBCommon Platform Enumeration Specification\fR\m[]\&\s-2\u[2]\d\s+2
134
as proposed by the MITRE Corporation\&. This field is optional\&. Example:
135
CPE_NAME="cpe:/o:fedoraproject:fedora:17"
138
\fIHOME_URL=\fR, \fISUPPORT_URL=\fR, \fIBUG_REPORT_URL=\fR
140
Links to resources on the Internet related the operating system\&.
142
should refer to the homepage of the of operating system, or alternatively some homepage of the specific version of the operating system\&.
144
should refer to the main support page for the operating system, if there is any\&. This is primarily intended for operating systems which vendors provide support for\&.
145
\fIBUG_REPORT_URL=\fR
146
should refer to the main bug reporting page for the operating system, if there is any\&. This is primarily intended for operating systems that rely on community QA\&. These settings are optional, and providing only some of these settings is common\&. These URLs are intended to be exposed in "About this system" UIs behind links with captions such as "About this Operating System", "Obtain Support" resp\&. "Report a Bug"\&. The values should be in
147
\m[blue]\fBRFC3986 format\fR\m[]\&\s-2\u[3]\d\s+2, and should be
154
tel:\&. Only one URL shall be listed in each setting\&. If multiple resources need to be referenced it is recommended to provide an online landing page linking all available resources\&. Examples:
155
HOME_URL="https://fedoraproject\&.org/"
157
BUG_REPORT_URL="https://bugzilla\&.redhat\&.com/"
160
If you are reading this file from C code or a shell script to determine the OS or a specific version of it, use the ID and VERSION_ID fields, possibly with ID_LIKE as fallback for ID\&. When looking for an OS identification string for presentation to the user use the PRETTY_NAME field\&.
102
162
Note that operating system vendors may choose not to provide version information, for example to accommodate for rolling releases\&. In this case VERSION and VERSION_ID may be unset\&. Applications should not rely on these fields to be set\&.
164
Operating system vendors may extend the file format and introduce new fields\&. It is highly recommended to prefix new fields with an OS specific name in order to avoid name clashes\&. Applications reading this file must ignore unknown fields\&. Example:
165
DEBIAN_BTS="debbugs://bugs\&.debian\&.org/"
added
removed
man/os-release.5
