On 10/24/2016 07:59 PM, L.A. Walsh wrote:
Others will tell you to use UUIDS or other names, but those can change and fail as well. (UUID's can change and be changed by the user), and names require that you have a booted OS running that can interpret the names (usually hidden from users via the pre-boot-OS that boots off of ram disk and non-deterministically loads the drivers which change order -- causing the problem you see).
You're being ridiculous and outrageous again, Linda. Yes its possible to change a UUID, but why would you? Why would you want to in the normal course of events? In a boundary case where you had to update a new drive to look *exactly* like the old drive all the way down to the UUID, yes I can see that, but its not part of the 'everyday' or the 'normal course of events'. Certainly not part of a normal, regular upgrade cycle. Yes you can chnage names, but that's an acto of volition as well[1]. And as for reading the labels on disks, partitions and file systems, yes, that will take -- shock/horror -- *software*. It might e 'fdisk', it might be the second stage boot after the MBR; sometimes the BIOS can read disk labels. Its all just in the software. Never say Never. [1] Here's an example. I have a BtrFS boot partition and I want to change it to Ext4. So I make a new partition (easy with LVM) and rsync the files across. The original partition is labelled ROOT, the new ROOT4. I test boot editing the command line since my grub.config uses "by-label', so its easy to do -- 'e' and 'f10' and all that. All goes well. So I rename ROOT4->ROOT and ROOT->OLDRT. I don't even have to edit the on-disk grub.cfg or do a new mkinitrd. A serious change made simple. But not a common occurrence. KISS. Oh, and document everything you do as you go along. -- Experience teaches only the teachable. Aldous Huxley (1894 - 1963) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org