system-wide locale settings. It is read at early boot by
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
- <para>The basic file format of <filename>locale.conf</filename> is
- a newline-separated list of environment-like shell-compatible
- variable assignments, ignoring comments and empty lines.
- 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.</para>
+ <para>The format of <filename>locale.conf</filename> is a newline-separated list of environment-like
+ shell-compatible variable assignments, ignoring comments and empty lines. 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. See
+ <citerefentry><refentrytitle>os-release</refentrytitle><manvolnum>5</manvolnum></citerefentry> for a
+ detailed description of the format.</para>
<para>Note that the kernel command line options
<varname>locale.LANG=</varname>,
<para>The locale settings configured in
<filename>/etc/locale.conf</filename> are system-wide and are
inherited by every service or user, unless overridden or unset by
- individual programs or individual users.</para>
+ individual programs or users.</para>
<para>Depending on the operating system, other configuration files
might be checked for locale configuration as well, however only as
<citerefentry><refentrytitle>systemd-firstboot</refentrytitle><manvolnum>1</manvolnum></citerefentry>
</para>
</refsect1>
-
</refentry>
<para>The <filename>/etc/machine-info</filename> file contains
machine metadata.</para>
- <para>The basic file format of <filename>machine-info</filename>
- 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.</para>
+ <para>The format of <filename>machine-info</filename> is a newline-separated list of environment-like
+ shell-compatible variable assignments, ignoring comments and empty lines. 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. See
+ <citerefentry><refentrytitle>os-release</refentrytitle><manvolnum>5</manvolnum></citerefentry> for a
+ detailed description of the format.</para>
<para><filename>/etc/machine-info</filename> contains metadata about the machine that is set by the user
or administrator. The settings configured here have the highest precedence. When not set, appropriate
<filename>/usr/lib/os-release</filename> files contain operating
system identification data.</para>
- <para>The basic file format of <filename>os-release</filename> is a newline-separated list of
+ <para>The format of <filename>os-release</filename> is a newline-separated list of
environment-like shell-compatible variable assignments. It is possible to source the configuration from
Bourne 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
0–9. (Assignments that do not include these special characters may be enclosed in quotes too, but this is
optional.) Shell special characters ("$", quotes, backslash, backtick) must be escaped with backslashes,
following shell style. All strings should be in UTF-8 encoding, and non-printable characters should not
- be used. It is not supported to concatenate multiple individually quoted strings. Lines beginning with
- "#" shall be ignored as comments. Blank lines are permitted and ignored.</para>
+ be used. Concatenation of multiple individually quoted strings is not supported. Lines beginning with "#"
+ are treated as comments. Blank lines are permitted and ignored.</para>
<para>The file <filename>/etc/os-release</filename> takes
precedence over <filename>/usr/lib/os-release</filename>.
You can safely mask this file if you want to avoid this kind of initialization.
</para>
- <para>The basic file format of the
- <filename>vconsole.conf</filename> 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.</para>
+ <para>The format of <filename>vconsole.conf</filename> is a newline-separated list of environment-like
+ shell-compatible variable assignments, ignoring comments and empty lines. 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. See
+ <citerefentry><refentrytitle>os-release</refentrytitle><manvolnum>5</manvolnum></citerefentry> for a
+ detailed description of the format.</para>
<para>Note that the kernel command line options
<varname>vconsole.keymap=</varname>,
projects / thirdparty / systemd.git / commitdiff
