On Wed, Apr 02, Andrey Borzenkov wrote:
On Wed, Apr 02, Andrey Borzenkov wrote:
grub2 is using filesystem UUID to find partition where files actually reside. grub2 is the thing in /usr/*bin, not what runs in firmware context. It is using OS device names. It will consult device.map only if called with deprecated (hdX) disk designation. openSUSE today
В Wed, 2 Apr 2014 18:34:45 +0200 Olaf Hering <olaf@aepfle.de> пишет: puts /dev/disk/by-id in bootloader configuration.
I think the bootloader part has three sides: #1 is first stage. Something has to configure the blocklists, for that it needs some block device name. This is tricky, and requires the smartass bootloader configurator, which will need no device.map. #2 is second stage. Something has to tell second stage where the files to load are located. Since second stage runs in firmware context this can either be filesystem specifc data like UUID or LABEL. Or some firmware accessible path. The latter has to be translated from Linux to firmware notation. I tend to think that the current approach to use filesystem UUID to access the partitions is a usable approach. If the partition content is copied around its required anyway to update the bootloader. If that includes also second stage in addtion to just first stage, thats fine. #3 is passing a cmdline to the OS. And I think thats Sashas point. If fstab contains LABE=X for /, then the bootloader has to follow. Or it should not pass anything at all, leaving everything to the code which actually mounts /, which is the initrd. Olaf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org