Feature added by: Olaf Hering (olh) Feature #315679, revision 1 Title: Add support for same-partition in bootloader config files Requested by: Olaf Hering (olh) Partner organization: openSUSE.org Description: There should be a way for the installer of the first-stage0 bootloader to work with "relative paths", instead of the current "absolute paths", when it translates config file entries describing disks or partitions. Lets take grub1 as example to show what I mean: Bootloader is supposed to be installed into the root partition. Then /etc/grub.conf has something like setup --stage2=/boot/grub/stage2 --force-lba (hd0,8) (hd0,8) to install the files into partition number #9. Here the "(hd0,8)" should be replaced with something that means "same-partition-where-the-files-are-currently-located-on-the-filesystem". Whatever processes grub.conf then goes and translates this into "partition #9 on the underlying disk". The second part of my grub1 example is /boot/grub/device.map, which currently has something like (hd0) /dev/disk/by-id/ata-WDC_WD15EADS-00P8B0_WD-WMAVU0414744 . This means the given installation is bound to a disk that provides the above identification string. If the underlying storage changes, device.map must be adjusted. But this step can be easily avoided if the code which processes device.map would instead see "(hd0) same-disk-where-the-boot-files-are-on-filesystem" Such changes would make it simple to move an installation around, either by copying the filesystem contents around, or by exchanging the underlying hypervisor. Things like device.map are bound to a given hardware emulation and are not stable as experiance has shown. -- openSUSE Feature: https://features.opensuse.org/315679