I would say "It depends". I am not an expert here, just my own opinion from my experiences.
The benefit of using the label is that you are not 'hard coding' the system to mount a disk at a specified location or can be used as an alias of sorts. Using a label can be more flexible in dynamic environments where things can change. For example: There could be an environment where USB storage is randomly inserted in the system and rather than have the user's work through fdisk and decide which drive is which, label each partition with a label and have them mount it that way. I have seen FC attached drives from a SAN go a bit crazy with which device name they show up as that day (sdX, sdY, sdZ) due to the order they were loaded in and labels can also help in that scenario (though that is just a workaround to the 'real' issue). If you are on a desktop system and don't notice any problems I would say that you can use whatever your heart desires. I'm interested to hear if anyone else has other things to say as well since I have never really had a reason to use blkid. Chad ________________________________ From: [email protected] [[email protected]] on behalf of Clift, Tom CIV NSWCDD, K55 [[email protected]] Sent: Friday, January 04, 2013 2:22 PM To: [email protected] Subject: adding to fstab All, I have created a new partition on a spare drive and want to add it to the fstab. I basically see three(3) different ways to do it. All work but what is the preferred way. 1. Use Blkid 2. Use Label 3. Use physical device (/dev/sdb1) All seem to work fine.Any preference?
-- redhat-sysadmin-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/redhat-sysadmin-list
