Michael wrote: > On Thursday, 2 May 2024 00:45:29 BST Dale wrote: >> Grant Edwards wrote: >>> On 2024-05-01, Dale <rdalek1...@gmail.com> wrote: >>>> Grant Edwards wrote: >>>>> The partition type code for 'swap' is wrong -- it should be >>>>> 8200. According to the gdisk help info Linux /home is supposed to be >>>>> 8302, but I've always used the same generic "Linux filesystem" type >>>>> for both /home and root. >>>>> >>>>> Is the 'boot' partition for future possible UEFI use, for Linux /boot, >>>>> or both? [I've never used a separate partition for Linux /boot, I >>>>> just use a /boot directory on the root FS.] >>>> I noticed the other day that some new ones was added. I always leave it >>>> as 8300 and it works. It even works for swap. I dunno. > In the legacy DOS partition tables the space available was limited to 32 > bits, > while the GPT table specification provides 128 bytes for each block entry. > The extra space can be used to store information related to the intended OS > usage of each partition, by adding the corresponding Partition Type UUID. > > This has a number of benefits, described here: > > https://uapi-group.org/specifications/specs/ > discoverable_partitions_specification/ > > Besides the automation this feature affords, I find it useful to know what a > partition contains without having to mount it. On GPT labelled disks I make > use both of the Partition Type UUID and the Partition Name. A quick glance > at > the gdisk output and if need be its 'i' option has saved my day from > formatting the wrong partition more than once! ;-)
I always use labels which show up with cgdisk. If I'm unsure how I partitioned a drive for some reason, I just check it with cgdisk to see what is what. I use labels even tho a lot of the time I put UUIDs in fstab. I do similar when using LVM as well. There is more than one way to organize things tho. ;-) Dale :-) :-)
