The Boot Loader Specification
diff --git a/specs/configuration_files_specification/index.html b/specs/configuration_files_specification/index.html
index 65a4fdf..628c4eb 100644
--- a/specs/configuration_files_specification/index.html
+++ b/specs/configuration_files_specification/index.html
@@ -1,6 +1,6 @@
Configuration Files Specification | UAPI Group Specifications
+The purpose of the rules defined here is to allow OS vendors to implement the hermetic-usr pattern, where all vendor files are shipped in the vendor tree itself (/usr/), including configuration files with system defaults, while allowing local or vendor overrides without modifying the original files, for easier management.">Configuration Files Specification | UAPI Group Specifications
Configuration Files Specification
Configuration Files Specification
diff --git a/specs/discoverable_disk_image/index.html b/specs/discoverable_disk_image/index.html
index da965d5..a62f076 100644
--- a/specs/discoverable_disk_image/index.html
+++ b/specs/discoverable_disk_image/index.html
@@ -1,4 +1,4 @@
-Discoverable Disk Image | UAPI Group Specifications
+Discoverable Disk Image | UAPI Group Specifications
Discoverable Disk Image
Discoverable Disk Image (DDI)
diff --git a/specs/discoverable_partitions_specification/index.html b/specs/discoverable_partitions_specification/index.html
index ab678e6..6c4a6f1 100644
--- a/specs/discoverable_partitions_specification/index.html
+++ b/specs/discoverable_partitions_specification/index.html
@@ -1,6 +1,6 @@
Discoverable Partitions Specification | UAPI Group Specifications
+This specification describes the use of GUID Partition Table (GPT) UUIDs to enable automatic discovery of partitions and their intended mountpoints. Traditionally Linux has made little use of partition types, mostly just defining one UUID for file system/data partitions and another one for swap partitions.">Discoverable Partitions Specification | UAPI Group Specifications
Discoverable Partitions Specification
The Discoverable Partitions Specification (DPS)
diff --git a/specs/extension_image/index.html b/specs/extension_image/index.html
index 9a195b9..9b95092 100644
--- a/specs/extension_image/index.html
+++ b/specs/extension_image/index.html
@@ -1,4 +1,4 @@
-Extension Images | UAPI Group Specifications
+Extension Images | UAPI Group Specifications
Extension Images
Extension Images
diff --git a/specs/index.html b/specs/index.html
index 9373e17..b506f10 100644
--- a/specs/index.html
+++ b/specs/index.html
@@ -1,4 +1,4 @@
-Specs | UAPI Group Specifications
+Specs | UAPI Group Specifications
Specs
diff --git a/specs/linux_tpm_pcr_registry/index.html b/specs/linux_tpm_pcr_registry/index.html
index a325bcc..08517da 100644
--- a/specs/linux_tpm_pcr_registry/index.html
+++ b/specs/linux_tpm_pcr_registry/index.html
@@ -1,6 +1,6 @@
Linux TPM PCR Registry | UAPI Group Specifications
+PCRs owned by the firmware, i.">Linux TPM PCR Registry | UAPI Group Specifications
Linux TPM PCR Registry
🔏 Linux TPM PCR Registry 🗒️
diff --git a/specs/sysext/index.html b/specs/sysext/index.html
index 21ccd58..03689bc 100644
--- a/specs/sysext/index.html
+++ b/specs/sysext/index.html
@@ -1,4 +1,4 @@
-Sysext | UAPI Group Specifications
+Sysext | UAPI Group Specifications
Sysext
This content has moved to
diff --git a/specs/unified_kernel_image/index.html b/specs/unified_kernel_image/index.html
index c11f1e5..3fe1064 100644
--- a/specs/unified_kernel_image/index.html
+++ b/specs/unified_kernel_image/index.html
@@ -1,4 +1,4 @@
-
Unified Kernel Image | UAPI Group Specifications
+Unified Kernel Image | UAPI Group Specifications
Unified Kernel Image
Unified Kernel Image (UKI)
@@ -41,11 +41,12 @@
combination with any PE sections of the UKI itself. At UKI invocation time, the EFI stub contained in the UKI
may load additional of these PE Addons and apply them (after authenticating them via UEFI APIs), combining
them with the resources of the UKI.
PE Addons may not contain .linux
PE sections (this may be used to distinguish them from UKIs, which must
-have this section, see above).
PE Addons must contain at least one section of the following types:
.cmdline
.dtb
.ucode
PE Addons should be sorted by their filename, and applied in this order. In case of .cmdline
all command
+have this section, see above).
PE Addons must contain at least one section of the following types:
.cmdline
.dtb
.ucode
.initrd
PE Addons should be sorted by their filename, and applied in this order. In case of .cmdline
all command
lines provided by addons are suffixed in this order to any command line included in the UKI. In case of
.dtb
any such section included in the UKI shall be applied first, and those provided by add-ons should then
by applied in order as a fix-up. In case of .ucode
the contained cpio
archives should be prefixed to the
-regular initrds passed to the kernel, in reverse order.
PE Addons may include sections of multiple types (e.g. both a .cmdline
and a .dtb
section), in which case
+regular initrds passed to the kernel, in reverse order. In case of .initrd
the contained cpio
archives
+should be appended to the regular initrds passed to the kernel.
PE Addons may include sections of multiple types (e.g. both a .cmdline
and a .dtb
section), in which case
all of them should be applied.
Just like UKIs PE Addons should have the Subystem
field of the optional PE header set to 0x0A.
The PE header’s Machine
field should be set to the local CPU type for the target machine of the Addon. When
enumerating PE Addons to apply, candidates should be skipped when their header field reports a non-native CPU
architecture.
PE Addons may contain executable code in a .text
section. This code may be useful to write a friendly error
diff --git a/specs/version_format_specification/index.html b/specs/version_format_specification/index.html
index 9f1cb38..11777a5 100644
--- a/specs/version_format_specification/index.html
+++ b/specs/version_format_specification/index.html
@@ -1,6 +1,6 @@
Version Format Specification | UAPI Group Specifications
+Version Format # The version string is a sequence of zero or more characters.">Version Format Specification | UAPI Group Specifications
Version Format Specification
Version Format Specification
diff --git a/tags/index.html b/tags/index.html
index 5fd7691..7151b79 100644
--- a/tags/index.html
+++ b/tags/index.html
@@ -1,4 +1,4 @@
-Tags | UAPI Group Specifications
+Tags | UAPI Group Specifications
Tags
Configuration Files Specification
diff --git a/specs/discoverable_disk_image/index.html b/specs/discoverable_disk_image/index.html
index da965d5..a62f076 100644
--- a/specs/discoverable_disk_image/index.html
+++ b/specs/discoverable_disk_image/index.html
@@ -1,4 +1,4 @@
-Discoverable Disk Image | UAPI Group Specifications
+Discoverable Disk Image | UAPI Group Specifications
Discoverable Disk Image
Discoverable Disk Image (DDI)
diff --git a/specs/discoverable_partitions_specification/index.html b/specs/discoverable_partitions_specification/index.html
index ab678e6..6c4a6f1 100644
--- a/specs/discoverable_partitions_specification/index.html
+++ b/specs/discoverable_partitions_specification/index.html
@@ -1,6 +1,6 @@
Discoverable Partitions Specification | UAPI Group Specifications
+This specification describes the use of GUID Partition Table (GPT) UUIDs to enable automatic discovery of partitions and their intended mountpoints. Traditionally Linux has made little use of partition types, mostly just defining one UUID for file system/data partitions and another one for swap partitions.">Discoverable Partitions Specification | UAPI Group Specifications
Discoverable Partitions Specification
The Discoverable Partitions Specification (DPS)
diff --git a/specs/extension_image/index.html b/specs/extension_image/index.html
index 9a195b9..9b95092 100644
--- a/specs/extension_image/index.html
+++ b/specs/extension_image/index.html
@@ -1,4 +1,4 @@
-Extension Images | UAPI Group Specifications
+Extension Images | UAPI Group Specifications
Extension Images
Extension Images
diff --git a/specs/index.html b/specs/index.html
index 9373e17..b506f10 100644
--- a/specs/index.html
+++ b/specs/index.html
@@ -1,4 +1,4 @@
-Specs | UAPI Group Specifications
+Specs | UAPI Group Specifications
Specs
diff --git a/specs/linux_tpm_pcr_registry/index.html b/specs/linux_tpm_pcr_registry/index.html
index a325bcc..08517da 100644
--- a/specs/linux_tpm_pcr_registry/index.html
+++ b/specs/linux_tpm_pcr_registry/index.html
@@ -1,6 +1,6 @@
Linux TPM PCR Registry | UAPI Group Specifications
+PCRs owned by the firmware, i.">Linux TPM PCR Registry | UAPI Group Specifications
Linux TPM PCR Registry
🔏 Linux TPM PCR Registry 🗒️
diff --git a/specs/sysext/index.html b/specs/sysext/index.html
index 21ccd58..03689bc 100644
--- a/specs/sysext/index.html
+++ b/specs/sysext/index.html
@@ -1,4 +1,4 @@
-Sysext | UAPI Group Specifications
+Sysext | UAPI Group Specifications
Sysext
This content has moved to
diff --git a/specs/unified_kernel_image/index.html b/specs/unified_kernel_image/index.html
index c11f1e5..3fe1064 100644
--- a/specs/unified_kernel_image/index.html
+++ b/specs/unified_kernel_image/index.html
@@ -1,4 +1,4 @@
-
Unified Kernel Image | UAPI Group Specifications
+Unified Kernel Image | UAPI Group Specifications
Unified Kernel Image
Unified Kernel Image (UKI)
@@ -41,11 +41,12 @@
combination with any PE sections of the UKI itself. At UKI invocation time, the EFI stub contained in the UKI
may load additional of these PE Addons and apply them (after authenticating them via UEFI APIs), combining
them with the resources of the UKI.
PE Addons may not contain .linux
PE sections (this may be used to distinguish them from UKIs, which must
-have this section, see above).
PE Addons must contain at least one section of the following types:
.cmdline
.dtb
.ucode
PE Addons should be sorted by their filename, and applied in this order. In case of .cmdline
all command
+have this section, see above).
PE Addons must contain at least one section of the following types:
.cmdline
.dtb
.ucode
.initrd
PE Addons should be sorted by their filename, and applied in this order. In case of .cmdline
all command
lines provided by addons are suffixed in this order to any command line included in the UKI. In case of
.dtb
any such section included in the UKI shall be applied first, and those provided by add-ons should then
by applied in order as a fix-up. In case of .ucode
the contained cpio
archives should be prefixed to the
-regular initrds passed to the kernel, in reverse order.
PE Addons may include sections of multiple types (e.g. both a .cmdline
and a .dtb
section), in which case
+regular initrds passed to the kernel, in reverse order. In case of .initrd
the contained cpio
archives
+should be appended to the regular initrds passed to the kernel.
PE Addons may include sections of multiple types (e.g. both a .cmdline
and a .dtb
section), in which case
all of them should be applied.
Just like UKIs PE Addons should have the Subystem
field of the optional PE header set to 0x0A.
The PE header’s Machine
field should be set to the local CPU type for the target machine of the Addon. When
enumerating PE Addons to apply, candidates should be skipped when their header field reports a non-native CPU
architecture.
PE Addons may contain executable code in a .text
section. This code may be useful to write a friendly error
diff --git a/specs/version_format_specification/index.html b/specs/version_format_specification/index.html
index 9f1cb38..11777a5 100644
--- a/specs/version_format_specification/index.html
+++ b/specs/version_format_specification/index.html
@@ -1,6 +1,6 @@
Version Format Specification | UAPI Group Specifications
+Version Format # The version string is a sequence of zero or more characters.">Version Format Specification | UAPI Group Specifications
Version Format Specification
Version Format Specification
diff --git a/tags/index.html b/tags/index.html
index 5fd7691..7151b79 100644
--- a/tags/index.html
+++ b/tags/index.html
@@ -1,4 +1,4 @@
-Tags | UAPI Group Specifications
+Tags | UAPI Group Specifications
Tags
Discoverable Disk Image (DDI)
diff --git a/specs/discoverable_partitions_specification/index.html b/specs/discoverable_partitions_specification/index.html
index ab678e6..6c4a6f1 100644
--- a/specs/discoverable_partitions_specification/index.html
+++ b/specs/discoverable_partitions_specification/index.html
@@ -1,6 +1,6 @@
Discoverable Partitions Specification | UAPI Group Specifications
+This specification describes the use of GUID Partition Table (GPT) UUIDs to enable automatic discovery of partitions and their intended mountpoints. Traditionally Linux has made little use of partition types, mostly just defining one UUID for file system/data partitions and another one for swap partitions.">Discoverable Partitions Specification | UAPI Group Specifications
Discoverable Partitions Specification
The Discoverable Partitions Specification (DPS)
diff --git a/specs/extension_image/index.html b/specs/extension_image/index.html
index 9a195b9..9b95092 100644
--- a/specs/extension_image/index.html
+++ b/specs/extension_image/index.html
@@ -1,4 +1,4 @@
-Extension Images | UAPI Group Specifications
+Extension Images | UAPI Group Specifications
Extension Images
Extension Images
diff --git a/specs/index.html b/specs/index.html
index 9373e17..b506f10 100644
--- a/specs/index.html
+++ b/specs/index.html
@@ -1,4 +1,4 @@
-Specs | UAPI Group Specifications
+Specs | UAPI Group Specifications
Specs
diff --git a/specs/linux_tpm_pcr_registry/index.html b/specs/linux_tpm_pcr_registry/index.html
index a325bcc..08517da 100644
--- a/specs/linux_tpm_pcr_registry/index.html
+++ b/specs/linux_tpm_pcr_registry/index.html
@@ -1,6 +1,6 @@
Linux TPM PCR Registry | UAPI Group Specifications
+PCRs owned by the firmware, i.">Linux TPM PCR Registry | UAPI Group Specifications
Linux TPM PCR Registry
🔏 Linux TPM PCR Registry 🗒️
diff --git a/specs/sysext/index.html b/specs/sysext/index.html
index 21ccd58..03689bc 100644
--- a/specs/sysext/index.html
+++ b/specs/sysext/index.html
@@ -1,4 +1,4 @@
-Sysext | UAPI Group Specifications
+Sysext | UAPI Group Specifications
Sysext
This content has moved to
diff --git a/specs/unified_kernel_image/index.html b/specs/unified_kernel_image/index.html
index c11f1e5..3fe1064 100644
--- a/specs/unified_kernel_image/index.html
+++ b/specs/unified_kernel_image/index.html
@@ -1,4 +1,4 @@
-
Unified Kernel Image | UAPI Group Specifications
+Unified Kernel Image | UAPI Group Specifications
Unified Kernel Image
Unified Kernel Image (UKI)
@@ -41,11 +41,12 @@
combination with any PE sections of the UKI itself. At UKI invocation time, the EFI stub contained in the UKI
may load additional of these PE Addons and apply them (after authenticating them via UEFI APIs), combining
them with the resources of the UKI.
PE Addons may not contain .linux
PE sections (this may be used to distinguish them from UKIs, which must
-have this section, see above).
PE Addons must contain at least one section of the following types:
.cmdline
.dtb
.ucode
PE Addons should be sorted by their filename, and applied in this order. In case of .cmdline
all command
+have this section, see above).
PE Addons must contain at least one section of the following types:
.cmdline
.dtb
.ucode
.initrd
PE Addons should be sorted by their filename, and applied in this order. In case of .cmdline
all command
lines provided by addons are suffixed in this order to any command line included in the UKI. In case of
.dtb
any such section included in the UKI shall be applied first, and those provided by add-ons should then
by applied in order as a fix-up. In case of .ucode
the contained cpio
archives should be prefixed to the
-regular initrds passed to the kernel, in reverse order.
PE Addons may include sections of multiple types (e.g. both a .cmdline
and a .dtb
section), in which case
+regular initrds passed to the kernel, in reverse order. In case of .initrd
the contained cpio
archives
+should be appended to the regular initrds passed to the kernel.
PE Addons may include sections of multiple types (e.g. both a .cmdline
and a .dtb
section), in which case
all of them should be applied.
Just like UKIs PE Addons should have the Subystem
field of the optional PE header set to 0x0A.
The PE header’s Machine
field should be set to the local CPU type for the target machine of the Addon. When
enumerating PE Addons to apply, candidates should be skipped when their header field reports a non-native CPU
architecture.
PE Addons may contain executable code in a .text
section. This code may be useful to write a friendly error
diff --git a/specs/version_format_specification/index.html b/specs/version_format_specification/index.html
index 9f1cb38..11777a5 100644
--- a/specs/version_format_specification/index.html
+++ b/specs/version_format_specification/index.html
@@ -1,6 +1,6 @@
Version Format Specification | UAPI Group Specifications
+Version Format # The version string is a sequence of zero or more characters.">Version Format Specification | UAPI Group Specifications
Version Format Specification
Version Format Specification
diff --git a/tags/index.html b/tags/index.html
index 5fd7691..7151b79 100644
--- a/tags/index.html
+++ b/tags/index.html
@@ -1,4 +1,4 @@
-Tags | UAPI Group Specifications
+Tags | UAPI Group Specifications
Tags
The Discoverable Partitions Specification (DPS)
diff --git a/specs/extension_image/index.html b/specs/extension_image/index.html
index 9a195b9..9b95092 100644
--- a/specs/extension_image/index.html
+++ b/specs/extension_image/index.html
@@ -1,4 +1,4 @@
-Extension Images | UAPI Group Specifications
+Extension Images | UAPI Group Specifications
Extension Images
Extension Images
diff --git a/specs/index.html b/specs/index.html
index 9373e17..b506f10 100644
--- a/specs/index.html
+++ b/specs/index.html
@@ -1,4 +1,4 @@
-Specs | UAPI Group Specifications
+Specs | UAPI Group Specifications
Specs
diff --git a/specs/linux_tpm_pcr_registry/index.html b/specs/linux_tpm_pcr_registry/index.html
index a325bcc..08517da 100644
--- a/specs/linux_tpm_pcr_registry/index.html
+++ b/specs/linux_tpm_pcr_registry/index.html
@@ -1,6 +1,6 @@
Linux TPM PCR Registry | UAPI Group Specifications
+PCRs owned by the firmware, i.">Linux TPM PCR Registry | UAPI Group Specifications
Linux TPM PCR Registry
🔏 Linux TPM PCR Registry 🗒️
diff --git a/specs/sysext/index.html b/specs/sysext/index.html
index 21ccd58..03689bc 100644
--- a/specs/sysext/index.html
+++ b/specs/sysext/index.html
@@ -1,4 +1,4 @@
-Sysext | UAPI Group Specifications
+Sysext | UAPI Group Specifications
Sysext
This content has moved to
diff --git a/specs/unified_kernel_image/index.html b/specs/unified_kernel_image/index.html
index c11f1e5..3fe1064 100644
--- a/specs/unified_kernel_image/index.html
+++ b/specs/unified_kernel_image/index.html
@@ -1,4 +1,4 @@
-
Unified Kernel Image | UAPI Group Specifications
+Unified Kernel Image | UAPI Group Specifications
Unified Kernel Image
Unified Kernel Image (UKI)
@@ -41,11 +41,12 @@
combination with any PE sections of the UKI itself. At UKI invocation time, the EFI stub contained in the UKI
may load additional of these PE Addons and apply them (after authenticating them via UEFI APIs), combining
them with the resources of the UKI.
PE Addons may not contain .linux
PE sections (this may be used to distinguish them from UKIs, which must
-have this section, see above).
PE Addons must contain at least one section of the following types:
.cmdline
.dtb
.ucode
PE Addons should be sorted by their filename, and applied in this order. In case of .cmdline
all command
+have this section, see above).
PE Addons must contain at least one section of the following types:
.cmdline
.dtb
.ucode
.initrd
PE Addons should be sorted by their filename, and applied in this order. In case of .cmdline
all command
lines provided by addons are suffixed in this order to any command line included in the UKI. In case of
.dtb
any such section included in the UKI shall be applied first, and those provided by add-ons should then
by applied in order as a fix-up. In case of .ucode
the contained cpio
archives should be prefixed to the
-regular initrds passed to the kernel, in reverse order.
PE Addons may include sections of multiple types (e.g. both a .cmdline
and a .dtb
section), in which case
+regular initrds passed to the kernel, in reverse order. In case of .initrd
the contained cpio
archives
+should be appended to the regular initrds passed to the kernel.
PE Addons may include sections of multiple types (e.g. both a .cmdline
and a .dtb
section), in which case
all of them should be applied.
Just like UKIs PE Addons should have the Subystem
field of the optional PE header set to 0x0A.
The PE header’s Machine
field should be set to the local CPU type for the target machine of the Addon. When
enumerating PE Addons to apply, candidates should be skipped when their header field reports a non-native CPU
architecture.
PE Addons may contain executable code in a .text
section. This code may be useful to write a friendly error
diff --git a/specs/version_format_specification/index.html b/specs/version_format_specification/index.html
index 9f1cb38..11777a5 100644
--- a/specs/version_format_specification/index.html
+++ b/specs/version_format_specification/index.html
@@ -1,6 +1,6 @@
Version Format Specification | UAPI Group Specifications
+Version Format # The version string is a sequence of zero or more characters.">Version Format Specification | UAPI Group Specifications
Version Format Specification
Version Format Specification
diff --git a/tags/index.html b/tags/index.html
index 5fd7691..7151b79 100644
--- a/tags/index.html
+++ b/tags/index.html
@@ -1,4 +1,4 @@
-Tags | UAPI Group Specifications
+Tags | UAPI Group Specifications
Tags
Extension Images
diff --git a/specs/index.html b/specs/index.html
index 9373e17..b506f10 100644
--- a/specs/index.html
+++ b/specs/index.html
@@ -1,4 +1,4 @@
-Specs | UAPI Group Specifications
+Specs | UAPI Group Specifications
Specs
diff --git a/specs/linux_tpm_pcr_registry/index.html b/specs/linux_tpm_pcr_registry/index.html
index a325bcc..08517da 100644
--- a/specs/linux_tpm_pcr_registry/index.html
+++ b/specs/linux_tpm_pcr_registry/index.html
@@ -1,6 +1,6 @@
Linux TPM PCR Registry | UAPI Group Specifications
+PCRs owned by the firmware, i.">Linux TPM PCR Registry | UAPI Group Specifications
Linux TPM PCR Registry
🔏 Linux TPM PCR Registry 🗒️
diff --git a/specs/sysext/index.html b/specs/sysext/index.html
index 21ccd58..03689bc 100644
--- a/specs/sysext/index.html
+++ b/specs/sysext/index.html
@@ -1,4 +1,4 @@
-Sysext | UAPI Group Specifications
+Sysext | UAPI Group Specifications
Sysext
This content has moved to
diff --git a/specs/unified_kernel_image/index.html b/specs/unified_kernel_image/index.html
index c11f1e5..3fe1064 100644
--- a/specs/unified_kernel_image/index.html
+++ b/specs/unified_kernel_image/index.html
@@ -1,4 +1,4 @@
-
Unified Kernel Image | UAPI Group Specifications
+Unified Kernel Image | UAPI Group Specifications
Unified Kernel Image
Unified Kernel Image (UKI)
@@ -41,11 +41,12 @@
combination with any PE sections of the UKI itself. At UKI invocation time, the EFI stub contained in the UKI
may load additional of these PE Addons and apply them (after authenticating them via UEFI APIs), combining
them with the resources of the UKI.
PE Addons may not contain .linux
PE sections (this may be used to distinguish them from UKIs, which must
-have this section, see above).
PE Addons must contain at least one section of the following types:
.cmdline
.dtb
.ucode
PE Addons should be sorted by their filename, and applied in this order. In case of .cmdline
all command
+have this section, see above).
PE Addons must contain at least one section of the following types:
.cmdline
.dtb
.ucode
.initrd
PE Addons should be sorted by their filename, and applied in this order. In case of .cmdline
all command
lines provided by addons are suffixed in this order to any command line included in the UKI. In case of
.dtb
any such section included in the UKI shall be applied first, and those provided by add-ons should then
by applied in order as a fix-up. In case of .ucode
the contained cpio
archives should be prefixed to the
-regular initrds passed to the kernel, in reverse order.
PE Addons may include sections of multiple types (e.g. both a .cmdline
and a .dtb
section), in which case
+regular initrds passed to the kernel, in reverse order. In case of .initrd
the contained cpio
archives
+should be appended to the regular initrds passed to the kernel.
PE Addons may include sections of multiple types (e.g. both a .cmdline
and a .dtb
section), in which case
all of them should be applied.
Just like UKIs PE Addons should have the Subystem
field of the optional PE header set to 0x0A.
The PE header’s Machine
field should be set to the local CPU type for the target machine of the Addon. When
enumerating PE Addons to apply, candidates should be skipped when their header field reports a non-native CPU
architecture.
PE Addons may contain executable code in a .text
section. This code may be useful to write a friendly error
diff --git a/specs/version_format_specification/index.html b/specs/version_format_specification/index.html
index 9f1cb38..11777a5 100644
--- a/specs/version_format_specification/index.html
+++ b/specs/version_format_specification/index.html
@@ -1,6 +1,6 @@
Version Format Specification | UAPI Group Specifications
+Version Format # The version string is a sequence of zero or more characters.">Version Format Specification | UAPI Group Specifications
Version Format Specification
Version Format Specification
diff --git a/tags/index.html b/tags/index.html
index 5fd7691..7151b79 100644
--- a/tags/index.html
+++ b/tags/index.html
@@ -1,4 +1,4 @@
-Tags | UAPI Group Specifications
+Tags | UAPI Group Specifications
Tags
🔏 Linux TPM PCR Registry 🗒️
diff --git a/specs/sysext/index.html b/specs/sysext/index.html
index 21ccd58..03689bc 100644
--- a/specs/sysext/index.html
+++ b/specs/sysext/index.html
@@ -1,4 +1,4 @@
-Sysext | UAPI Group Specifications
+Sysext | UAPI Group Specifications
Sysext
This content has moved to
diff --git a/specs/unified_kernel_image/index.html b/specs/unified_kernel_image/index.html
index c11f1e5..3fe1064 100644
--- a/specs/unified_kernel_image/index.html
+++ b/specs/unified_kernel_image/index.html
@@ -1,4 +1,4 @@
-
Unified Kernel Image | UAPI Group Specifications
+Unified Kernel Image | UAPI Group Specifications
Unified Kernel Image
Unified Kernel Image (UKI)
@@ -41,11 +41,12 @@
combination with any PE sections of the UKI itself. At UKI invocation time, the EFI stub contained in the UKI
may load additional of these PE Addons and apply them (after authenticating them via UEFI APIs), combining
them with the resources of the UKI.
PE Addons may not contain .linux
PE sections (this may be used to distinguish them from UKIs, which must
-have this section, see above).
PE Addons must contain at least one section of the following types:
.cmdline
.dtb
.ucode
PE Addons should be sorted by their filename, and applied in this order. In case of .cmdline
all command
+have this section, see above).
PE Addons must contain at least one section of the following types:
.cmdline
.dtb
.ucode
.initrd
PE Addons should be sorted by their filename, and applied in this order. In case of .cmdline
all command
lines provided by addons are suffixed in this order to any command line included in the UKI. In case of
.dtb
any such section included in the UKI shall be applied first, and those provided by add-ons should then
by applied in order as a fix-up. In case of .ucode
the contained cpio
archives should be prefixed to the
-regular initrds passed to the kernel, in reverse order.
PE Addons may include sections of multiple types (e.g. both a .cmdline
and a .dtb
section), in which case
+regular initrds passed to the kernel, in reverse order. In case of .initrd
the contained cpio
archives
+should be appended to the regular initrds passed to the kernel.
PE Addons may include sections of multiple types (e.g. both a .cmdline
and a .dtb
section), in which case
all of them should be applied.
Just like UKIs PE Addons should have the Subystem
field of the optional PE header set to 0x0A.
The PE header’s Machine
field should be set to the local CPU type for the target machine of the Addon. When
enumerating PE Addons to apply, candidates should be skipped when their header field reports a non-native CPU
architecture.
PE Addons may contain executable code in a .text
section. This code may be useful to write a friendly error
diff --git a/specs/version_format_specification/index.html b/specs/version_format_specification/index.html
index 9f1cb38..11777a5 100644
--- a/specs/version_format_specification/index.html
+++ b/specs/version_format_specification/index.html
@@ -1,6 +1,6 @@
Version Format Specification | UAPI Group Specifications
+Version Format # The version string is a sequence of zero or more characters.">Version Format Specification | UAPI Group Specifications
Version Format Specification
Version Format Specification
diff --git a/tags/index.html b/tags/index.html
index 5fd7691..7151b79 100644
--- a/tags/index.html
+++ b/tags/index.html
@@ -1,4 +1,4 @@
-Tags | UAPI Group Specifications
+Tags | UAPI Group Specifications
Tags
This content has moved to diff --git a/specs/unified_kernel_image/index.html b/specs/unified_kernel_image/index.html index c11f1e5..3fe1064 100644 --- a/specs/unified_kernel_image/index.html +++ b/specs/unified_kernel_image/index.html @@ -1,4 +1,4 @@ -
Unified Kernel Image (UKI) @@ -41,11 +41,12 @@ combination with any PE sections of the UKI itself. At UKI invocation time, the EFI stub contained in the UKI may load additional of these PE Addons and apply them (after authenticating them via UEFI APIs), combining them with the resources of the UKI.
PE Addons may not contain .linux
PE sections (this may be used to distinguish them from UKIs, which must
-have this section, see above).
PE Addons must contain at least one section of the following types:
.cmdline
.dtb
.ucode
PE Addons should be sorted by their filename, and applied in this order. In case of .cmdline
all command
+have this section, see above).
PE Addons must contain at least one section of the following types:
.cmdline
.dtb
.ucode
.initrd
PE Addons should be sorted by their filename, and applied in this order. In case of .cmdline
all command
lines provided by addons are suffixed in this order to any command line included in the UKI. In case of
.dtb
any such section included in the UKI shall be applied first, and those provided by add-ons should then
by applied in order as a fix-up. In case of .ucode
the contained cpio
archives should be prefixed to the
-regular initrds passed to the kernel, in reverse order.
PE Addons may include sections of multiple types (e.g. both a .cmdline
and a .dtb
section), in which case
+regular initrds passed to the kernel, in reverse order. In case of .initrd
the contained cpio
archives
+should be appended to the regular initrds passed to the kernel.
PE Addons may include sections of multiple types (e.g. both a .cmdline
and a .dtb
section), in which case
all of them should be applied.
Just like UKIs PE Addons should have the Subystem
field of the optional PE header set to 0x0A.
The PE header’s Machine
field should be set to the local CPU type for the target machine of the Addon. When
enumerating PE Addons to apply, candidates should be skipped when their header field reports a non-native CPU
architecture.
PE Addons may contain executable code in a .text
section. This code may be useful to write a friendly error
diff --git a/specs/version_format_specification/index.html b/specs/version_format_specification/index.html
index 9f1cb38..11777a5 100644
--- a/specs/version_format_specification/index.html
+++ b/specs/version_format_specification/index.html
@@ -1,6 +1,6 @@