usr/ Verity Partition (64-bit PowerPC LittleEndian) usr/ Verity Partition (64-bit MIPS LittleEndian (mips64el)) usr/ Verity Partition (32-bit MIPS LittleEndian (mipsel)) usr/ Verity Partition (LoongArch 64-bit) usr/ Verity Partition (64-bit ARM/AArch64) Similar semantics to root Verity partition, but just for the /usr/ partition.
Root Verity Partition (64-bit PowerPC BigEndian) Root Verity Partition (64-bit PowerPC LittleEndian)
Root Verity Partition (64-bit MIPS LittleEndian (mips64el)) Root Verity Partition (32-bit MIPS LittleEndian (mipsel)) Root Verity Partition (64-bit ARM/AArch64) If this feature is used the partition UUID of the root partition should be the first 128 bits of the root hash of the dm-verity hash data, and the partition UUID of this dm-verity partition should be the final 128 bits of it, so that the root partition and its Verity partition can be discovered easily, simply by specifying the root hash. usr/ Partition (64-bit PowerPC LittleEndian)Ī dm-verity superblock followed by hash dataĬontains dm-verity integrity hash data for the matching root partition. usr/ Partition (64-bit PowerPC BigEndian)
usr/ Partition (64-bit MIPS LittleEndian (mips64el)) usr/ Partition (32-bit MIPS LittleEndian (mipsel)) Similar semantics to root partition, but just the /usr/ partition. Root Partition (64-bit PowerPC LittleEndian) Root Partition (64-bit PowerPC BigEndian) Root Partition (64-bit MIPS LittleEndian (mips64el)) Root Partition (32-bit MIPS LittleEndian (mipsel)) If the partition is encrypted with LUKS or has dm-verity integrity data (see below), the device mapper file will be named /dev/mapper/root. On systems with matching architecture, the first partition with this type UUID on the disk containing the active EFI ESP is automatically mounted to the root directory /. Defined Partition Type UUIDs Partition Type UUID Note that automatic discovery of the root only works if theīoot loader communicates this information to the OS, by implementing the Boot Note that the OS side of this specification is currently implemented in As a help to administrators and users partition manager tools can show moreĭescriptive information about partitions tables.Images between physical machines and Linux containers. This enables true, natural portability of disk Right places, thus allowing booting the same, identical images on bare metalĪnd in Linux containers. Container managers (such as nspawn and libvirt-lxc) can introspect and set upįile systems contained in GPT disk images automatically and mount them to the.Or incomplete /etc/fstab file and without the root= kernel command line The OS can discover and mount the necessary file systems with a non-existent.OS installers can automatically discover and make sense of partitions of.With this specification, we introduce additional partition typesįor specific uses. Traditionally Linux has made little use of partition types, mostly justĭefining one UUID for file system/data partitions and another one for swap This specification describes the use of GUID Partition Table (GPT) UUIDs toĮnable automatic discovery of partitions and their intended mountpoints. home/, /srv/, /var/ and /var/tmp/ and the swap partitions based on TL DR: Let’s automatically discover, mount and enable the root partition, The Discoverable Partitions Specification (DPS)