Grub PARTUUID vs UUID

[FireIcer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey

I am looking at the impact in general with changing the grub-mkconfig
scan not to pickup and update the grub.cfg with the UUID code but the
PARTUUID code instead.

At present the situation forces the user to enable a working initramfs
to work around grub2.

Why is this a problem? well because initramfs can be used to decorate
ones boot display and many other things other than it's intended use.
This means that UUID as a parameter in the grub.cfg wont work. I
understand that Windows partitions use a shortened UUID only, so
compatibility needs to be able to differentiate between the two types.
UUID for windows partitions and PARTUUID for other GPT partitions.

I cant understand why UUID's were used rather than PARTUUID's. If the
code was modified to use PARTUUID's instead, what would be the impact
on compatibility on a large scale.

If people enable the option in Grub to use PARTUUID's then surely they
would know to setup GPT disks. I feel it should be encouraged to
remove the MBR tables as it is old and useless not to mention tied in
to microsoft products. Now we have an Intel contribution "GPT" which
works much better is it not right that we encourage the use of GPT
over MBR?

The point of this post is to raise alarm to the fact UUID's wont work
without initramfs or initrd as so to read the UUID but the kernel can
read PARTUUID without the use of initrd. Would that not be far better
to not rely on init ram filesystem?

A option/switch parameter when using mkconfig to output the cfg file
maybe?

Thanks

f1r31c3r

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSaGuyAAoJEBzkvPKQNuh2JVcH+gOj1QwfH0jRXDcq1Usm3A0c
EOktkEkz+5yMPbWIPOEQev9ZzIb18Ef6+eNVAEAmTuDVaF3i8stEv+wsnLixhj/R
AR2qjHtTtGcJcq7O+6O6s+HziOEnbMVwdb0Yeg8m/qgr7Xx3MpNxjHQsyhdhMuxU
xw6Mgy/A4TIp4qdyPFEpSYfRdu55LRkQATvP6+j5Vt7OcJn3Qkife+Vy4akdd07G
WY1nq43aiYZP5DjOqeIlE8lq/e28RNJmtn6w8V1DlTC2oj4SM3Dpc96SGPSevNmw
VLegioKa/vztyapJAZAVZ4tgtXnNpXeHxreo0G9HA8C3DkaMlY817Steko9C5cU=
=ah6L
-----END PGP SIGNATURE-----