I will take a look at it, but the fundamental issue is it screws with the iommu groups too and then I have to go fix that in proxmox. If I can at least guarantee a network connection then I can remote in and fix it in the event something goes really wrong.
It's a lot better than the system that just randomly throws in your USB drives with your SCSI/SAS/SATA/PATA drives. Or the systems that calls everything a SCSI drive when it usually isn't a SCSI drive.
Yeah wasn't it something like SATA and USB got lumped in with the SATA SCSI storage controller or whatever which is why it's practically all /dev/sdx? Back in the days of yore when men were men and sheep were scared there'd be /dev/hdx and /dev/fdx for hard and floppy drives?
Namespaces are the construct in NVMe technology that hold user data. An NVMe controller can have multiple namespaces attached to it. Most NVMe SSDs today just use a single namespace, but multi-tenant applications, virtualization and security have use cases for multiple namespaces.
device v
/dev/nvme0n1p1 < partition
namespace ^
There are two types of people: Those who are able to identify gaps in their knowledge and actively seek to fill them... and whatever this meme is.
Funny? In a meme? C'mon man, we're trying to be serious here and know which technologies we can shame to feel good about ourselves. Stop ruining my quest for self-egrandifying tech-snobbery with your so-called humour!!1!
P.S. thanks to @vampire even so; that was interesting to learn
I once had to do GRUB related stuff with CentOS 5 (or was it 3?).
Stuff started with 0 in it and I was kept wondering what I was selecting, because the naming convention in GRUB was different from that in the OS.
In short; sd stands for SCSI Disk and SSD and USB all use the SCSI protocol. While SD-cards/emmc (flash-on-CPU) are named emmcblkpX for emmc block device, partition X. And NVME have additionally namespaces, which is the nX part.
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.
The alternative being running os-prober at boottime, on every boot.
Currently, we set UUID using os-prober whenever we remake grub.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.
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.