4 ms·
I don't see why anyone would use something else than UUIDs Some partitions don't have UUIDs, such as LUKS volumes with a detached header or plain dm-crypt volu
by tremon 6y ago
I don't see why anyone would use something else than UUIDs
Some partitions don't have UUIDs, such as LUKS volumes with a detached header or plain dm-crypt volumes. In that case, I use a /by-id/wwn-* path to uniquely identify the partition. Of course, those lines are in /etc/crypttab, not in /etc/fstab.
- MayeulC 6y agoOK, I re-read the thread, and noticed where the confusion comes from. https://wiki.archlinux.org/index.php/Persistent_block_device_naming https://wiki.archlinux.org/index.php/Persistent_block_device... I am talking about UUIDs, that basically any (Linux at least) filesystem has. Those are a bit like filesystem labels, but generated during filesystem creation. Their format makes collisions virtually impossible. LUKS volumes have one, and partitions inside them have a different one too. This is my prefered way of identifying partitions, as they are persistent even when you move them around with lvm, dd, or others. I think that's also the default in many distributions. PARTUUID is also a nice way to identify partitions when you can't rely on a partition UUID for some reason. It works like UUIDs, but instead of being stored inside the partition, that information is part of the GPT (GUID partition table). If you are more interested in the drives than the partition content, by-id makes sense, though I think the use-case is rather narrow :)
- m463 6y agowith /dev/disk/by-id you get a unique name for the physical hardware. like /dev/disk/by-id/ata-Samsund_SSD_blah...<serialno> uuid is different but you can access it with /dev/disk/by-uuid