That mounting drives with their uuid as the mount location is insane
Why tho? Kernel sometimes can index drives in different order (if you have multiple drives), screwing your mount locations. But UUID is always the same
But why would I even try to remember them? Just look them up. Nowadays I don’t even see them since I use Gnome Disk Utility or KDE partition manager to automount them (they both just write to your /etc/fstab)
But why would I even try to remember them? Just look them up.
For me, I used labels when setting up those volumes manually. Creating a LUKS container, setting up LVM groups and volumes, configuring my bootloader to decrypt the correct encrypted disk, etc. It was just easier to remember which device label was my encrypted container, which was the group, and what the different volumes were. And once the labels were made, well, I just used them.
Why tho? Kernel sometimes can index drives in different order (if you have multiple drives), screwing your mount locations. But UUID is always the same
You can give your partitions labels and mount by label. Labels are persistent, like UUIDs, but are also easier to remember and copy.
But why would I even try to remember them? Just look them up. Nowadays I don’t even see them since I use Gnome Disk Utility or KDE partition manager to automount them (they both just write to your /etc/fstab)
For me, I used labels when setting up those volumes manually. Creating a LUKS container, setting up LVM groups and volumes, configuring my bootloader to decrypt the correct encrypted disk, etc. It was just easier to remember which device label was my encrypted container, which was the group, and what the different volumes were. And once the labels were made, well, I just used them.
It’s just really long is all. I wish I had given it something shorter but descriptive.