Andrey Borzenkov wrote:
It is using OS device names. It will consult device.map only if called with deprecated (hdX) disk designation. openSUSE today puts /dev/disk/by-id in bootloader configuration.
Which ones are the OS device names? In /dev/disks, I see * by-path + by-id -- (2 variants of the same info, both based off HW part numbers: changes with new HW and relocated HW (different slot or controller) * by-label -- user specified labels; can stay same w/new hardware, but require OS to be booted (often a ramdisk/initrd version) to read. * by-partlabel -- looks like labels on GPT based partitions (but ignores labels on old-PCBIOS-partitions or LVM partitions). * by-partuuid -- uuid equiv of by-partlable -- limited usefulness * by-uuid - recognized by modern bootloaders w/o OS support, as well as by the UEFI based bios's; Doesn't change w/hardware, but defaults to a new number on creation, but is user-settable. Of the above, only the UUID is recognized by both new BIOS's and modern boot loaders without an OS. by-label requires one to have mounted udev on a running OS with all the drivers for the filesystems one is querying. I would gather that only the UUID is stored in a filesystem-independent format which is why OS-drivers aren't needed. It isn't 'hardwired' like 'by-path' or 'by-id' to specific HW & location. I.e. trying to boot by label when you need the OS to read the label is a bit of a chicken and egg problem -- as you have to specify someplace to load a ramdisk from, *first*, and that won't be by label. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org