On Tuesday, 24 November 2020 10:43:25 GMT Michael wrote: > On Tuesday, 24 November 2020 09:20:52 GMT Peter Humphrey wrote: > > My workstation has one NVMe drive and two SATAs. They're always detected > > in the same order, so I've no need to render my fstab illegible with > > UUIDs. I could use labels, but why bother? The old system ain't broke, so > > I've no need to fix it. > > It depends on the bus and disk technology. I have an ARM driven box with a > conventional 1TB spinning SATA drive and a USB stick. You can never tell > which one will be detected as /dev/sda and which as /dev/sdb. If you have > more than one pluggable devices the same identification problem is likely to > arise. LABELs and/or UUIDs solve this problem - reliably.
Yes, I have several USB sticks, but specifically because they're transient I expect those to have sdX assigned chronologically. I don't boot with them inserted, so I still don't need anything more than /dev/sdX in fstab. > > Can you imagine an fstab with 22 partitions specified with UUIDs? Doesn't > > bear thinking about. > > Copying and pasting the output of blkid helps complete the fstab easily and > commented lines allow me to explain to myself block device location and > purpose, should I need to revisit it some months/years later. That's still much more complex than my setup, and less legible. To a degree, this is a hobby machine, so I create, delete and move partitions more often than many people do. I couldn't possibly work with UUIDs; it'd be as bad as trying to read someone else's perl code. :) -- Regards, Peter.
