this post was submitted on 15 Mar 2024
992 points (97.2% liked)
linuxmemes
20880 readers
8 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
A yes, my beloved nvme1p2 partition that changes name every reboot
thats a reason to use the uuid in the fstab
Anyone else chuckle on the parallel in saying to use the UUID is no different than saying "just hardcore the IP bro"
I'm not hating on you, but it's an extremely flawed system where you are forced to use a direct ID mapping as a reference.
From what I'm understanding from people you can assign an alias to the UUID that sounds better?
It's more like setting a static IP. The UUID is set when you create the partition and won't change unless you force it to change.
You can also use any of the GUI utilities which can add it to your fstab.
There's a lot of things that are made way too difficult on Linux for seemingly no reason. This isn't one of them.
I mean you can also use partition labels but who does that
Oh really? That seems interesting and better than a random uuid
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.
The alternative being running
os-proberat boottime, on every boot.Currently, we set UUID using
os-proberwhenever we remakegrub.cfg, analogous to that would be registering web-server static IPs with a DNS, which provides the domain name aliases (we don't need to see UUID in the GRUB menu right? We see the OS names).An analogy to the alternative would be to ask all devices on the internet to send their usage methods everytime you try to look for another site.
Lol I seem to remember that I once had /home mapped to a partition that did that for all sorts of fun and games for a while.
my nvme is always nvme1pX, with X being 1-4 depending on the partition, and its always the same.
Wonder why? Weird that some change and some dont.
I got two drives with one being nvme1pX and the other nvme2pX and I don't know why but they just swap names sometime. I'm new to linux though so it may be some misconfiguration on my part and I rarely need to access them with their name.
Ah, sorry. I only have 1 nvme drive, so thats probably why. Didnt realize until your post that it was a multi-drive issue.