Debian Codegraph @

upstream/debian-unstable/man8/systemd-gpt-auto-generator.8

raw
1 '\" t
2 .TH "SYSTEMD\-GPT\-AUTO\-GENERATOR" "8" "" "systemd 261~rc3" "systemd-gpt-auto-generator"
3 .\" -----------------------------------------------------------------
4 .\" * Define some portability stuff
5 .\" -----------------------------------------------------------------
6 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7 .\" http://bugs.debian.org/507673
8 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
9 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10 .ie \n(.g .ds Aq \(aq
11 .el .ds Aq '
12 .\" -----------------------------------------------------------------
13 .\" * set default formatting
14 .\" -----------------------------------------------------------------
15 .\" disable hyphenation
16 .nh
17 .\" disable justification (adjust text to left margin only)
18 .ad l
19 .\" -----------------------------------------------------------------
20 .\" * MAIN CONTENT STARTS HERE *
21 .\" -----------------------------------------------------------------
22 .SH "NAME"
23 systemd-gpt-auto-generator \- Generator for automatically discovering and mounting root, /home/, /srv/, /var/ and /var/tmp/ partitions, as well as discovering and enabling swap partitions, based on GPT partition type GUIDs
24 .SH "SYNOPSIS"
25 .PP
26 /usr/lib/systemd/system\-generators/systemd\-gpt\-auto\-generator
27 .SH "DESCRIPTION"
28 .PP
29 systemd\-gpt\-auto\-generator
30 is a unit generator that automatically discovers the root partition,
31 /home/,
32 /srv/,
33 /var/,
34 /var/tmp/, the EFI System Partition (ESP), the Extended Boot Loader Partition (XBOOTLDR), and swap partitions and creates mount and swap units for them, based on the partition type GUIDs of GUID partition tables (GPT)\&. See
35 \m[blue]\fBUEFI Specification\fR\m[]\&\s-2\u[1]\d\s+2, chapter 5 for more details\&. It implements the
36 \m[blue]\fBUAPI\&.2 Discoverable Partitions Specification\fR\m[]\&\s-2\u[2]\d\s+2\&.
37 .PP
38 Note that this generator has no effect on non\-GPT systems\&. It will also not create mount point configuration for directories which already contain files or if the mount point is explicitly configured in
39 \fBfstab\fR(5)\&. Additionally no unit will be created for the ESP or the XBOOTLDR partition if mount entries are found in the
40 /boot/
41 or
42 /efi/
43 hierarchies in
44 \fBfstab\fR(5)\&.
45 .PP
46 If the units this generator creates are overridden, for example by units in directories with higher precedence, drop\-ins and additional dependencies created by this generator might still be used\&.
47 .PP
48 When run in the initial RAM disk (initrd) this generator can automatically search for the root file system\&. Specifically:
49 .sp
50 .RS 4
51 .ie n \{\
52 \h'-04'\(bu\h'+03'\c
53 .\}
54 .el \{\
55 .sp -1
56 .IP \(bu 2.3
57 .\}
58 It will look for the root partition on the same physical disk where the EFI System Partition (ESP) is located\&. Note that support from the boot loader is required for this to work: the EFI variable
59 \fILoaderDevicePartUUID\fR
60 of the
61 \fB4a67b082\-0a4c\-41cf\-b6c7\-440b29bb8c4f\fR
62 vendor UUID is used to determine from which partition (and hence disk) the system was booted\&. If the boot loader does not set this variable, this generator will not be able to detect the root partition\&. See the
63 \m[blue]\fBBoot Loader Interface\fR\m[]\&\s-2\u[3]\d\s+2
64 for details\&.
65 .RE
66 .sp
67 .RS 4
68 .ie n \{\
69 \h'-04'\(bu\h'+03'\c
70 .\}
71 .el \{\
72 .sp -1
73 .IP \(bu 2.3
74 .\}
75 Alternatively, it will look for the root file system on a loopback block device whose
76 "\&.lo_name"
77 field is set to one of the literal strings
78 "rootdisk"
79 or
80 "rootdisk\&.raw"\&. This field can be set via
81 \fBlosetup\fR\*(Aqs
82 \fB\-\-loop\-ref=\fR
83 string\&. For images downloaded via
84 \fBsystemd-import-generator\fR(8)
85 make sure to set the
86 "blockdev"
87 option and set the local name string to
88 "rootdisk"
89 to achieve this effect\&. Note that discovery of the root file system on loopback block devices like this is only done if
90 "root=gpt\-auto"
91 or
92 "root=dissect"
93 is specified explicitly on the kernel command line, unlike the discovery based on the boot loader reported ESP which is also enabled if no
94 "root="
95 parameter is specified at all\&. (The latter relies on
96 \fBsystemd\-udevd\&.service\fR\*(Aqs
97 /dev/gpt\-auto\-root
98 block device symlink generation)\&.
99 .RE
100 .sp
101 .RS 4
102 .ie n \{\
103 \h'-04'\(bu\h'+03'\c
104 .\}
105 .el \{\
106 .sp -1
107 .IP \(bu 2.3
108 .\}
109 It will also generate a unit file mounting the EFI System Partition (ESP) to
110 /sysefi/, if applicable\&. Unlike the file systems mentioned above this mount is not activated by default however, but can be pulled in by services requiring ESP access from within the initrd\&. Note that this mount point is initrd\-specific and does not make use of autofs\&. The ESP is typically mounted at a different place and via autofs once the system transitions out of the initrd\&.
111 .RE
112 .PP
113 When run on the host system (i\&.e\&. after successfully transitioning out of the initrd into the root filesystem) this generator will look for all other partitions on the same physical disk as the root partition\&. For this discovery, boot loader support is not required\&. Moreover, it is not required that the root partition was automatically discovered by the initrd (as described above) for the discovery of the non\-root file partitions to take place\&. Or in other words: automatic discovery of the root file system and of the non\-root file systems are independent operations, that do not rely on each other, and are done during two distinct phases of the boot process (one in the initrd, the other after)\&. These partitions will not be searched for on systems where the root file system is distributed on multiple disks, for example via btrfs RAID\&.
114 .PP
115 The root partition can be configured explicitly by symlinking
116 /run/systemd/volatile\-root
117 to
118 /dev/block/$major:$minor\&. This is especially useful if the root mount has been replaced by some form of volatile file system (overlayfs)\&.
119 .PP
120 systemd\-gpt\-auto\-generator
121 is useful for centralizing file system configuration in the partition table and making configuration in
122 /etc/fstab
123 or on the kernel command line unnecessary\&.
124 .PP
125 This generator looks for the partitions based on their partition type GUID\&. The following partition type GUIDs are identified:
126 .sp
127 .it 1 an-trap
128 .nr an-no-space-flag 1
129 .nr an-break-flag 1
130 .br
131 .B Table\ \&1.\ \&Partition Type GUIDs
132 .TS
133 allbox tab(:);
134 lB lB lB lB lB.
135 T{
136 Partition Type
137 T}:T{
138 GUID
139 T}:T{
140 Name
141 T}:T{
142 Mount Point
143 T}:T{
144 Explanation
145 T}
146 .T&
147 l l l l l
148 l l l l l
149 l l l l l
150 l l l l l
151 l l l l l
152 l l l l l
153 l l l l l
154 l l l l l
155 l l l l l
156 l l l l l.
157 T{
158 \fBSD_GPT_ROOT_X86_64\fR
159 T}:T{
160 \fB4f68bce3\-e8cd\-4db1\-96e7\-fbcaf984b709\fR
161 T}:T{
162 Root Partition (x86\-64)
163 T}:T{
164 /
165 T}:T{
166 The first partition with this type UUID, located on the same disk as the ESP used for booting, is used as the root file system / on AMD64 / 64\-bit x86 systems\&.
167 T}
168 T{
169 \fBSD_GPT_ROOT_ARM64\fR
170 T}:T{
171 \fBb921b045\-1df0\-41c3\-af44\-4c6f280d3fae\fR
172 T}:T{
173 Root Partition (64\-bit ARM)
174 T}:T{
175 /
176 T}:T{
177 The first partition with this type UUID, located on the same disk as the ESP used for booting, is used as the root file system / on AArch64 / 64\-bit ARM systems\&.
178 T}
179 T{
180 \fBSD_GPT_ROOT_ALPHA\fR \fBSD_GPT_ROOT_ARC\fR \fBSD_GPT_ROOT_ARM\fR \fBSD_GPT_ROOT_ARM64\fR \fBSD_GPT_ROOT_IA64\fR \fBSD_GPT_ROOT_LOONGARCH64\fR \fBSD_GPT_ROOT_MIPS\fR \fBSD_GPT_ROOT_MIPS64\fR \fBSD_GPT_ROOT_MIPS_LE\fR \fBSD_GPT_ROOT_MIPS64_LE\fR \fBSD_GPT_ROOT_PARISC\fR \fBSD_GPT_ROOT_PPC\fR \fBSD_GPT_ROOT_PPC64\fR \fBSD_GPT_ROOT_PPC64_LE\fR \fBSD_GPT_ROOT_RISCV32\fR \fBSD_GPT_ROOT_RISCV64\fR \fBSD_GPT_ROOT_S390\fR \fBSD_GPT_ROOT_S390X\fR \fBSD_GPT_ROOT_TILEGX\fR \fBSD_GPT_ROOT_X86\fR \fBSD_GPT_ROOT_X86_64\fR \fBSD_GPT_USR_ALPHA\fR \fBSD_GPT_USR_ARC\fR \fBSD_GPT_USR_ARM\fR \fBSD_GPT_USR_IA64\fR \fBSD_GPT_USR_LOONGARCH64\fR \fBSD_GPT_USR_MIPS_LE\fR \fBSD_GPT_USR_MIPS64_LE\fR \fBSD_GPT_USR_PARISC\fR \fBSD_GPT_USR_PPC\fR \fBSD_GPT_USR_PPC64\fR \fBSD_GPT_USR_PPC64_LE\fR \fBSD_GPT_USR_RISCV32\fR \fBSD_GPT_USR_RISCV64\fR \fBSD_GPT_USR_S390\fR \fBSD_GPT_USR_S390X\fR \fBSD_GPT_USR_TILEGX\fR \fBSD_GPT_USR_X86\fR
181 T}:T{
182 \&...
183 T}:T{
184 Root partitions for other architectures
185 T}:T{
186 /
187 T}:T{
188 The first partition with the type UUID matching the architecture, located on the same disk as the ESP used for booting, is used as the root file system /\&. For the full list and constant values, see \m[blue]\fBUAPI\&.2 Discoverable Partitions Specification\fR\m[]\&\s-2\u[2]\d\s+2\&.
189 T}
190 T{
191 \fBSD_GPT_HOME\fR
192 T}:T{
193 \fB933ac7e1\-2eb4\-4f13\-b844\-0e14e2aef915\fR
194 T}:T{
195 Home Partition
196 T}:T{
197 /home/
198 T}:T{
199 The first partition with this type UUID on the same disk as the root partition is mounted to /home/\&.
200 T}
201 T{
202 \fBSD_GPT_SRV\fR
203 T}:T{
204 \fB3b8f8425\-20e0\-4f3b\-907f\-1a25a76f98e8\fR
205 T}:T{
206 Server Data Partition
207 T}:T{
208 /srv/
209 T}:T{
210 The first partition with this type UUID on the same disk as the root partition is mounted to /srv/\&.
211 T}
212 T{
213 \fBSD_GPT_VAR\fR
214 T}:T{
215 \fB4d21b016\-b534\-45c2\-a9fb\-5c16e091fd2d\fR
216 T}:T{
217 Variable Data Partition
218 T}:T{
219 /var/
220 T}:T{
221 The first partition with this type UUID on the same disk as the root partition is mounted to /var/ \(em under the condition its partition UUID matches the first 128 bit of the HMAC\-SHA256 of the GPT type uuid of this partition keyed by the machine ID of the installation stored in \fBmachine-id\fR(5)\&. This can be generated using \fBsystemd-id128\fR(1)\&.
222 T}
223 T{
224 \fBSD_GPT_TMP\fR
225 T}:T{
226 \fB7ec6f557\-3bc5\-4aca\-b293\-16ef5df639d1\fR
227 T}:T{
228 Temporary Data Partition
229 T}:T{
230 /var/tmp/
231 T}:T{
232 The first partition with this type UUID on the same disk as the root partition is mounted to /var/tmp/\&.
233 T}
234 T{
235 \fBSD_GPT_SWAP\fR
236 T}:T{
237 \fB0657fd6d\-a4ab\-43c4\-84e5\-0933c84b4f4f\fR
238 T}:T{
239 Swap
240 T}:T{
241 n/a
242 T}:T{
243 All partitions with this type UUID on the same disk as the root partition are used as swap\&.
244 T}
245 T{
246 \fBSD_GPT_ESP\fR
247 T}:T{
248 \fBc12a7328\-f81f\-11d2\-ba4b\-00a0c93ec93b\fR
249 T}:T{
250 EFI System Partition (ESP)
251 T}:T{
252 /efi/ or /boot/ once the system transitioned out of the initrd, /sysefi/ before
253 T}:T{
254 The first partition with this type UUID located on the same disk as the root partition is mounted to /boot/ or /efi/, see below\&.
255 T}
256 T{
257 \fBSD_GPT_XBOOTLDR\fR
258 T}:T{
259 \fBbc13c2ff\-59e6\-4262\-a352\-b275fd6f7172\fR
260 T}:T{
261 Extended Boot Loader Partition
262 T}:T{
263 /boot/
264 T}:T{
265 The first partition with this type UUID located on the same disk as the root partition is mounted to /boot/, see below\&.
266 T}
267 .TE
268 .sp 1
269 .PP
270 This generator understands the following attribute flags for partitions:
271 .sp
272 .it 1 an-trap
273 .nr an-no-space-flag 1
274 .nr an-break-flag 1
275 .br
276 .B Table\ \&2.\ \&Partition Attribute Flags
277 .TS
278 allbox tab(:);
279 lB lB lB lB.
280 T{
281 Flag
282 T}:T{
283 Value
284 T}:T{
285 Applicable to
286 T}:T{
287 Explanation
288 T}
289 .T&
290 l l l l
291 l l l l
292 l l l l.
293 T{
294 \fBSD_GPT_FLAG_READ_ONLY\fR
295 T}:T{
296 \fB0x1000000000000000\fR
297 T}:T{
298 /, /home/, /srv/, /var/, /var/tmp/, Extended Boot Loader Partition
299 T}:T{
300 Partition is mounted read\-only
301 T}
302 T{
303 \fBSD_GPT_FLAG_NO_AUTO\fR
304 T}:T{
305 \fB0x8000000000000000\fR
306 T}:T{
307 /, /home/, /srv/, /var/, /var/tmp/, Extended Boot Loader Partition
308 T}:T{
309 Partition is not mounted automatically
310 T}
311 T{
312 \fBSD_GPT_FLAG_NO_BLOCK_IO_PROTOCOL\fR
313 T}:T{
314 \fB0x0000000000000002\fR
315 T}:T{
316 EFI System Partition (ESP)
317 T}:T{
318 Partition is not mounted automatically
319 T}
320 .TE
321 .sp 1
322 .PP
323 The
324 /home/,
325 /srv/,
326 /var/,
327 /var/tmp/
328 and swap partitions may be encrypted in LUKS format\&. In this case, a device mapper device is set up under the names
329 /dev/mapper/home,
330 /dev/mapper/srv,
331 /dev/mapper/var,
332 /dev/mapper/tmp
333 or
334 /dev/mapper/swap\&. Note that this might create conflicts if the same partition is listed in
335 /etc/crypttab
336 with a different device mapper device name\&.
337 .PP
338 When systemd is running in the initrd the
339 /
340 partition may be encrypted with LUKS as well\&. In this case, a device mapper device is set up under the name
341 /dev/mapper/root, and a
342 sysroot\&.mount
343 is set up that mounts the device under
344 /sysroot\&. For more information, see
345 \fBbootup\fR(7)\&.
346 .PP
347 Mount and automount units for the EFI System Partition (ESP) and Extended Boot Loader Partition (XBOOTLDR) are generated on EFI systems\&. If the disk contains an XBOOTLDR partition, as defined in the
348 \m[blue]\fBUAPI\&.1 Boot Loader Specification\fR\m[]\&\s-2\u[4]\d\s+2, it is made available at
349 /boot/\&. This generator creates an automount unit; the mount will only be activated on\-demand when accessed\&. The mount point will be created if necessary\&.
350 .PP
351 The ESP is mounted to
352 /boot/
353 if that directory exists and is not used for XBOOTLDR, and otherwise to
354 /efi/\&. Same as for
355 /boot/, an automount unit is used\&. The mount point will be created if necessary\&. These apply once the system transitioned out of the initrd phase\&. Before that, if components in the initrd require ESP access, it will be mounted to
356 /sysefi/\&.
357 .PP
358 No configuration is created for mount points that are configured in
359 \fBfstab\fR(5)
360 or when the target directory contains files\&.
361 .PP
362 When using this generator in conjunction with btrfs file systems, make sure to set the correct default subvolumes on them, using
363 \fBbtrfs subvolume set\-default\fR\&.
364 .PP
365 If the system was booted via
366 \fBsystemd-stub\fR(7)
367 and the stub reported to userspace that the kernel image was measured to a TPM2 PCR, then any discovered root and
368 /var/
369 volume identifiers (and volume encryption keys, in case they are encrypted) will be automatically measured into PCR 15 on activation, via
370 \[email protected]\fR(8)\&. Moreover, information about the LUKS key slot used to unlock the volume is measured into NvPCR
371 "cryptsetup"\&. Finally, if the root or
372 /usr/
373 partition is protected via Verity its root hash and the serial/issuer of the key used for the provided root hash signature (if any) are measured into the NvPCR
374 "verity"\&.
375 .PP
376 Mount constraint metadata contained in the file systems is validated by pulling in
377 \[email protected]\fR(8)
378 for generated mounts\&.
379 .PP
380 systemd\-gpt\-auto\-generator
381 implements
382 \fBsystemd.generator\fR(7)\&.
383 .SH "KERNEL COMMAND LINE"
384 .PP
385 systemd\-gpt\-auto\-generator
386 understands the following kernel command line parameters:
387 .PP
388 \fIsystemd\&.gpt_auto\fR, \fIrd\&.systemd\&.gpt_auto\fR
389 .RS 4
390 Those options take an optional boolean argument, and default to yes\&. The generator is enabled by default, and a false value may be used to disable it (e\&.g\&.
391 "systemd\&.gpt_auto=0")\&.
392 .sp
393 Added in version 242\&.
394 .RE
395 .PP
396 \fIsystemd\&.image_policy=\fR
397 .RS 4
398 Takes an image dissection policy string as argument (as per
399 \fBsystemd.image-policy\fR(7)), and allows enforcing a policy on dissection and use of the automatically discovered GPT partition table entries\&.
400 .sp
401 Note that the specified image policy is not taken into account for automatic root or
402 /usr/
403 file system discovery unless
404 \fIroot=dissect\fR/\fImount\&.usr=dissect\fR
405 (or
406 \fIroot=dissect\-force\fR) are specified\&. (The policy will always be applied to the other auto\-discoverable partition types\&.)
407 .sp
408 Added in version 254\&.
409 .RE
410 .PP
411 \fIsystemd\&.image_filter=\fR
412 .RS 4
413 Takes an image dissection filter string as argument (as per
414 \fBsystemd.image-filter\fR(7)), and allows enforcing a set of globbing patterns on the partition matching of the automatically discovered GPT partition table entries\&.
415 .sp
416 Note that the specified image filter is not taken into account for automatic root or
417 /usr/
418 file system discovery unless
419 \fIroot=dissect\fR/\fImount\&.usr=dissect\fR
420 (or
421 \fIroot=dissect\-force\fR) are specified\&. (The filter will always be applied to the other auto\-discoverable partition types\&.)
422 .sp
423 Added in version 258\&.
424 .RE
425 .PP
426 \fIroot=\fR, \fIrootfstype=\fR, \fIrootflags=\fR
427 .RS 4
428 When
429 \fIroot=\fR
430 is used with the special value
431 "gpt\-auto", basic automatic discovery of the root partition based on the GPT partition type is enabled\&. Use of the root partition is delayed until factory reset mode is left, in case it is enabled during the current boot\&. See
432 \m[blue]\fBFactory Reset\fR\m[]\&\s-2\u[5]\d\s+2
433 for more information on that\&. If
434 "gpt\-auto\-force"
435 is specified automatic discovery of the root partition is enabled, ignoring any factory reset mode\&.
436 .sp
437 If
438 \fIroot=\fR
439 is set to the special value
440 "dissect"
441 full automatic discovery of the root partition based on GPT partition information is enabled\&. This is a superset of
442 \fIroot=gpt\-auto\fR, as it automatically configures Verity partitions (including signature\-based setup) following the logic defined for that in the
443 \m[blue]\fBUAPI\&.2 Discoverable Partitions Specification\fR\m[]\&\s-2\u[6]\d\s+2\&. Moreover it takes the configured image policy and image filter into account for all partition types, including the root file system\&.
444 "root=dissect"
445 will wait for the factory reset phase to be completed if it is in effect before activating the root file system\&. Use
446 "root=dissect\-force"
447 to ignore the factory reset phase and activate the root file system immediately\&.
448 .sp
449 Any other value (i\&.e\&. besides
450 "gpt\-auto",
451 "gpt\-auto\-force",
452 "dissect",
453 "dissect\-force") disables automatic root file system discovery\&.
454 .sp
455 If
456 \fIroot=\fR
457 is not specified at all on the kernel command line automatic discovery of the root partition via the ESP reported by the boot loader is also enabled (taking factory reset state into account, i\&.e\&. equivalent to
458 "root=gpt\-auto"), however in this case discovery based on the loopback block device
459 "\&.lo_name"
460 field is not enabled\&.
461 .sp
462 The
463 \fIrootfstype=\fR
464 and
465 \fIrootflags=\fR
466 options are used to select the file system type and options when the root file system is automatically discovered\&.
467 .sp
468 Added in version 242\&.
469 .RE
470 .PP
471 \fImount\&.usr=\fR, \fImount\&.usrfstype=\fR, \fImount\&.usrflags=\fR
472 .RS 4
473 Similar to
474 \fIroot=\fR,
475 \fIrootfstype=\fR,
476 \fIrootflags=\fR
477 (see above), but applies to the
478 /usr/
479 partition instead\&. Note that the
480 "gpt\-auto",
481 "gpt\-auto\-force",
482 "dissect\-force"
483 settings that
484 root=
485 understands are not supported by
486 \fImount\&.usr=\fR
487 (however
488 "dissect"
489 is)\&.
490 .sp
491 Also note that automatic partition discovery for
492 /usr/
493 must be enabled explicitly, unlike the discovery for the root file system, which is enabled if no
494 \fIroot=\fR
495 parameter is passed at all\&.
496 .sp
497 Added in version 258\&.
498 .RE
499 .PP
500 \fIrw\fR, \fIro\fR
501 .RS 4
502 Mount the root partition read\-write or read\-only
503 \fIinitially\fR\&.
504 .sp
505 Note that unlike most kernel command line options these settings do not override configuration in the file system, and the file system may be remounted later\&. See
506 \fBsystemd-remount-fs.service\fR(8)\&.
507 .sp
508 Added in version 242\&.
509 .RE
510 .PP
511 \fIsystemd\&.swap=\fR
512 .RS 4
513 Takes a boolean argument or enables the option if specified without an argument\&. If disabled, automatic discovery of swap partition(s) based on GPT partition type is disabled\&. Defaults to enabled\&.
514 .sp
515 Added in version 254\&.
516 .RE
517 .SH "SEE ALSO"
518 .PP
519 \fBsystemd\fR(1), \fBsystemd.mount\fR(5), \fBsystemd.swap\fR(5), \fBsystemd-fstab-generator\fR(8), \[email protected]\fR(8), \[email protected]\fR(8), \[email protected]\fR(8), \fBmachine-id\fR(5), \fBcryptsetup\fR(8), \fBfstab\fR(5), \fBbtrfs\fR(8)
520 .SH "NOTES"
521 .IP " 1." 4
522 UEFI Specification
523 .RS 4
524 \%https://uefi.org/specifications
525 .RE
526 .IP " 2." 4
527 UAPI.2 Discoverable Partitions Specification
528 .RS 4
529 \%https://uapi-group.org/specifications/specs/discoverable_partitions_specification
530 .RE
531 .IP " 3." 4
532 Boot Loader Interface
533 .RS 4
534 \%https://systemd.io/BOOT_LOADER_INTERFACE
535 .RE
536 .IP " 4." 4
537 UAPI.1 Boot Loader Specification
538 .RS 4
539 \%https://uapi-group.org/specifications/specs/boot_loader_specification
540 .RE
541 .IP " 5." 4
542 Factory Reset
543 .RS 4
544 \%https://systemd.io/FACTORY_RESET
545 .RE
546 .IP " 6." 4
547 UAPI.2 Discoverable Partitions Specification
548 .RS 4
549 \%https://uapi-group.org/specifications/specs/discoverable_partitions_specification/
550 .RE