In the scenario of having to constantly update an fstab yes it is. As an end user I shouldn’t have to keep updating configuration files because something on a lower level keeps changing its alias.
No granted I’m not familiar with this type of mount. Maybe there is a better way to do it that absolves needing to use the UUID but if not that’s shit architecture IMHO.
If filesystem UUIDs are IP equivalents. Then device paths are MAC addresses. FS labels are DNS. Device mapper entries are service discovery.
In the scenario of having to constantly update an fstab yes it is. As an end user I shouldn’t have to keep updating configuration files because something on a lower level keeps changing its alias.
No granted I’m not familiar with this type of mount. Maybe there is a better way to do it that absolves needing to use the UUID but if not that’s shit architecture IMHO.
What? Using uuids is the solution to having to change the file (that, or stable name rules). You can also use labels if you want to.
The UUID never fucking changes. It is a hardware level identier use the UUID in your configs and they will work until the day you change drives.