Mapping back gptid -> device

[Dan Nelson]

In the last episode (Feb 26), kpneal at pobox.com said:
> If I have this:
> 
> [root at gunsight1 /etc]# ls -la /dev/gptid/
> total 1
> dr-xr-xr-x  2 root  wheel          512 Feb  1 12:44 .
> dr-xr-xr-x  9 root  wheel          512 Feb  1 12:44 ..
> crw-r-----  1 root  operator    0, 118 Feb  1 12:44 7050cab7-4add-11e1-8919-d4bed9aca1e9
> crw-r-----  1 root  operator    0, 122 Feb  1 12:44 d78fd637-4a40-11e1-ab9b-d4bed9aca1e9
> crw-r-----  1 root  operator    0, 106 Feb  1 12:44 e1ec4071-4cfb-11e1-b4ca-d4bed9aca1e9
> crw-r-----  1 root  operator    0, 112 Feb  1 12:44 f96b3a2c-4cfb-11e1-b4ca-d4bed9aca1e9
> [root at gunsight1 /etc]# 
> 
> How do I determine which of those /gptid/ entries corresponds to which
> listed in kernel messages printed at boot.
> 
> I have tried "gpart show -r", but it doesn't give the gptid of the entire
> drive -- only the partitions:
> 
> =>       34  877920189  mfid0  GPT  (419G)
>          34        256      1  83bd6b9d-7f41-11dc-be0b-001560b84f0f  (128K)
>         290   44041950      2  516e7cb5-6ecf-11d6-8ff8-00022d09712b  (21G)
>    44042240  817889280      3  516e7cba-6ecf-11d6-8ff8-00022d09712b  (390G)
>   861931520   15988703         - free -  (7.6G)

Try "gpart list" instead, and look at the "rawuuid" field.

-- 
	Dan Nelson
	dnelson at allantgroup.com