I think the simplest scheme and less conflicting with current TC "standards" would be as follows:
1) Assume a boot option that currently holds a partition "name" (home, tce, local, ...) has the value x
2) Use the output from "blkid" and "grep" for x. This will give you a line of text with both the /dev/yyyy and the corresponding UUID
3) Filter out the yyyy from this line of text and you have the partition "name" independently if the bootcode value was the partition name or the uuid.
There are few things to remember when it comes to disk device naming schemes:
1)The actuall namning of the disks devices (/dev/hda, /dev/sdb, /dev/hdc, ...) depdends on
* The hardware configuration
* The order in which the BIOS finds the devices
* The kernel, its drivers and the hwdetect features of the distro in use
As long as you do not change any of the above, you could assume that you what disk /dev/xxxx actually is.
I am used to systems where the hardware configuration changes (plug in/out USB disks) and I also run different Linux distros at different times. This means that I have since long do not view the device names as carved in stone - I must be flexible
The main problem I wanted to solve was that if I plugin (on an arbitrary computer) a USB stick with TC on it and boot, I would need to be sure that tce, home and local would point to some areas on the stick itself and not on any other disk.
There is of course another side of the problem and that is that if you plugin a USB disk or if you open the box and install an additional disk or remove an existing disk, you will likely modify the naming scheme of the system. This would mean that if you have an fstab that refers to a device name, that system might get corrupted since it relies an a naming scheme no longer valid. This is exactly why distributions like Ubuntu have choosen to use UUID as the "mount"-specifiers.
The use case I am looking for is to plugin a USB stick, boot and run everything from the stick (I do not want to use any other disks on the system) and for that purpose the solution I outlined would be good.
If TC would go for a solution in the future to use UUIDs as mount-specifiers in fstab, in order to secure survival in case of hardware modifications, I am fine with that, but it is not on my "requirement"-list today
Kind Regards
/Lars