Comment # 34 on bug 1076779 from Michael Chang

(In reply to Michael Chang from comment #29)
> (In reply to Franck Bui from comment #28)
> 
> > I would use the partition type GUID which is
> > C12A7328-F81F-11D2-BA4B-00A0C93EC93B for ESP.
> 
> The problem is partition type GUID not always available in udev info (And
> that's what leading to the bug report). Are you saying to use blkid to
> retrieve instead ?

Worse. :(
blkid doesn't provide info about PART "TYPE" GUID, it has only PART "ENTRY"
GUID, which is unique to every partition, not useful at all here.

lsblk seems to provide PARTTYPE, but the man page looks a bit scary as it also
depend on udev to function properly ... In opposite to what we wanted to avoid
here.

"The lsblk command reads the sysfs filesystem and udev db to gather
information."
"Note that lsblk might be executed in time when udev does not have all
information about recently added or modified devices yet. In this case it is
recommended to use udevadm settle before lsblk to synchronize with udev."

And even more worse ..
Both utility seems not providing PARTTYPE for "msdos" partition scheme, as
least it shows empty on my test. I have problem to detect EFI System Partition
Table on MSDOS scheme using both tools.

I felt literally done with it.