On Tue, 27 Jun 2017 13:16:49 -0700 Joe Zeff <joe@xxxxxxx> wrote: > On 06/27/2017 01:05 PM, stan wrote: > > But, I think you might have to fix the /etc/fstab file also before > > you do the above. If you cloned the drive, it will still be using > > the block ids for the previous drive in the /etc/fstab. > > This is why fstab uses the UUID by default, and you should too. > Cloning the drive doesn't change those. Thanks for the correction. That implies that it is possible to have duplicate UUIDs on a system if a drive and its duplicate are mounted, though, doesn't it? What does the system do at boot in that case? First come, first serve? It also means that the only thing William has to do is run the grub-mkconfig command, which is easier for him. As a matter of note, I always use the UUID in fstab, and also create unique labels for each partition. When I want to duplicate a drive, I usually use rsync (sometimes cp) with both drives mounted, and partitions already created on the receiving drive, so the UUIDs, and labels, will differ on the two drives even though the content might be identical. I just looked at blkid output, and I noticed that there are now PARTUUID and PARTLABEL for drives. Even when each partition already has a UUID and a label. Perhaps this is to deal with the cloning issue, so there are unique identifiers even for cloned drives? _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
