diff options
Diffstat (limited to 'upstream/opensuse-tumbleweed/man5/os-release.5')
| -rw-r--r-- | upstream/opensuse-tumbleweed/man5/os-release.5 | 43 |
1 files changed, 39 insertions, 4 deletions
diff --git a/upstream/opensuse-tumbleweed/man5/os-release.5 b/upstream/opensuse-tumbleweed/man5/os-release.5 index 97864860..795363d3 100644 --- a/upstream/opensuse-tumbleweed/man5/os-release.5 +++ b/upstream/opensuse-tumbleweed/man5/os-release.5 @@ -1,5 +1,5 @@ '\" t -.TH "OS\-RELEASE" "5" "" "systemd 254" "os-release" +.TH "OS\-RELEASE" "5" "" "systemd 255" "os-release" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -99,7 +99,8 @@ too\&. plays the same role for extension images as os\-release for the main system, and follows the syntax and rules as described in the -\m[blue]\fBPortable Services Documentation\fR\m[]\&\s-2\u[3]\d\s+2\&. The purpose of this file is to identify the extension and to allow the operating system to verify that the extension image matches the base OS\&. This is typically implemented by checking that the +\m[blue]\fBPortable Services\fR\m[]\&\s-2\u[3]\d\s+2 +page\&. The purpose of this file is to identify the extension and to allow the operating system to verify that the extension image matches the base OS\&. This is typically implemented by checking that the \fIID=\fR options match, and either \fISYSEXT_LEVEL=\fR @@ -208,6 +209,8 @@ Examples: Note: this field is for display purposes only\&. The \fIVARIANT_ID\fR field should be used for making programmatic decisions\&. +.sp +Added in version 220\&. .RE .PP \fIVARIANT_ID=\fR @@ -217,6 +220,8 @@ A lower\-case string (no spaces or other characters outside of 0\(en9, a\(enz, " Examples: "VARIANT_ID=server", "VARIANT_ID=embedded"\&. +.sp +Added in version 220\&. .RE .SS "Information about the version of the operating system" .PP @@ -245,6 +250,8 @@ A lower\-case string (no spaces or other characters outside of 0\(en9, a\(enz, " Examples: "VERSION_CODENAME=buster", "VERSION_CODENAME=xenial"\&. +.sp +Added in version 231\&. .RE .PP \fIBUILD_ID=\fR @@ -264,6 +271,8 @@ would not\&. This field is optional\&. Examples: "BUILD_ID="2013\-03\-20\&.3"", "BUILD_ID=201303203"\&. +.sp +Added in version 200\&. .RE .PP \fIIMAGE_ID=\fR @@ -273,6 +282,8 @@ A lower\-case string (no spaces or other characters outside of 0\(en9, a\(enz, " Examples: "IMAGE_ID=vendorx\-cashier\-system", "IMAGE_ID=netbook\-image"\&. +.sp +Added in version 249\&. .RE .PP \fIIMAGE_VERSION=\fR @@ -284,6 +295,8 @@ described above, to discern different versions of the same image\&. Examples: "IMAGE_VERSION=33", "IMAGE_VERSION=47\&.1rc1"\&. +.sp +Added in version 249\&. .RE .PP To summarize: if the image updates are built and shipped as comprehensive units, @@ -334,6 +347,8 @@ provided\&. For example, "SUPPORT_END=2001\-01\-01" means that the system was supported until the end of the last day of the previous millennium\&. +.sp +Added in version 252\&. .RE .PP \fILOGO=\fR @@ -344,6 +359,8 @@ A string, specifying the name of an icon as defined by Examples: "LOGO=fedora\-logo", "LOGO=distributor\-logo\-opensuse" +.sp +Added in version 240\&. .RE .PP \fIANSI_COLOR=\fR @@ -370,6 +387,8 @@ Examples: for Fedora Linux, "VENDOR_NAME="Canonical"" for Ubuntu\&. +.sp +Added in version 254\&. .RE .PP \fIVENDOR_URL=\fR @@ -388,6 +407,8 @@ URLs\&. Only one URL shall be listed in the setting\&. Examples: "VENDOR_URL="https://fedoraproject\&.org/"", "VENDOR_URL="https://canonical\&.com/""\&. +.sp +Added in version 254\&. .RE .SS "Distribution\-level defaults and metadata" .PP @@ -402,6 +423,8 @@ See for a description of how \fBsystemd-hostnamed.service\fR(8) determines the fallback hostname\&. +.sp +Added in version 248\&. .RE .PP \fIARCHITECTURE=\fR @@ -410,6 +433,8 @@ A string that specifies which CPU architecture the userspace binaries require\&. \fIConditionArchitecture=\fR described in \fBsystemd.unit\fR(5)\&. The field is optional and should only be used when just single architecture is supported\&. It may provide redundant information when used in a GPT partition with a GUID type that already encodes the architecture\&. If this is not the case, the architecture should be specified in e\&.g\&., an extension image, to prevent an incompatible host from loading it\&. +.sp +Added in version 252\&. .RE .PP \fISYSEXT_LEVEL=\fR @@ -423,6 +448,8 @@ and Examples: "SYSEXT_LEVEL=2", "SYSEXT_LEVEL=15\&.14"\&. +.sp +Added in version 248\&. .RE .PP \fICONFEXT_LEVEL=\fR @@ -436,6 +463,8 @@ for more information\&. Examples: "CONFEXT_LEVEL=2", "CONFEXT_LEVEL=15\&.14"\&. +.sp +Added in version 254\&. .RE .PP \fISYSEXT_SCOPE=\fR @@ -449,6 +478,8 @@ extension\-release\&.d/ files and indicates what environments the system extension is applicable to: i\&.e\&. to regular systems, to initrds, or to portable service images\&. If unspecified, "SYSEXT_SCOPE=system portable" is implied, i\&.e\&. any system extension without this field is applicable to regular systems and to portable service environments, but not to initrd environments\&. +.sp +Added in version 250\&. .RE .PP \fICONFEXT_SCOPE=\fR @@ -456,13 +487,17 @@ is implied, i\&.e\&. any system extension without this field is applicable to re Semantically the same as \fISYSEXT_SCOPE=\fR but for confext images\&. +.sp +Added in version 254\&. .RE .PP \fIPORTABLE_PREFIXES=\fR .RS 4 Takes a space\-separated list of one or more valid prefix match strings for the -\m[blue]\fBPortable Services Documentation\fR\m[]\&\s-2\u[3]\d\s+2 +\m[blue]\fBPortable Services\fR\m[]\&\s-2\u[3]\d\s+2 logic\&. This field serves two purposes: it is informational, identifying portable service images as such (and thus allowing them to be distinguished from other OS images, such as bootable system images)\&. It is also used when a portable service image is attached: the specified or implied portable service prefix is checked against the list specified here, to enforce restrictions how images may be attached to a system\&. +.sp +Added in version 250\&. .RE .SS "Notes" .PP @@ -656,7 +691,7 @@ initrd \%https://docs.kernel.org/admin-guide/initrd.html .RE .IP " 3." 4 -Portable Services Documentation +Portable Services .RS 4 \%https://systemd.io/PORTABLE_SERVICES .RE |