[1] https://uapi-group.org/specifications/specs/discoverable_partitions_specification/ My personal preference is this *is* the best way to do things; the main reason why we have blkid is because of the disaster which is the MSDOS FAT partition table, where there was only a single byte used for the partition type, that (a) was largely ignored by other x86 operating systems, and (b) wasn't under our control, so we couldn't define a new partition type each time we introduced a new Linux file system. In general, having explicit file system types, whether it is in /etc/fstab, or in the GPT partition table, is the better way to go. Using blkid is ideally the fallback when the best possible way doesn't work, since it will ultimately always be a "best efforts" sort of thing. That being said, I suspect that if you ask, file system maintainers will be happy to try to make things work better --- just send us a patch or tell us what we need to do. ZFS is not a native Linux file system, and blkid pre-dates ZFS, so it's not something that I bothered testing. It doesn't help that I had absolutely zero interest in dealing with Sun deliberately making the CDDL incompatible with the GPL, and Larry Elison potentially trying to sue us into the ground. :-) Cheers, - Ted
