Branch: refs/heads/better_raid_proposal Home: https://github.com/yast/yast-bootloader Commit: a50da5512634d01b376a863280071f8dc3d7fdb0 https://github.com/yast/yast-bootloader/commit/a50da5512634d01b376a863280071... Author: Martin Vidner Date: 2018-01-05 (Fri, 05 Jan 2018) Changed paths: M src/modules/BootStorage.rb Log Message: ----------- Explain why write stage1 to several devices Before this whole bug fix, the code remembered the "boot partition" and installed stage 1 to one of its underlying devices. Now, it remembers the "boot mount point" (which is / or /boot*) and uses #stage1_disks_for or #stage1_partitions_for (according to a UI choice) to get ALL underlying devices for it (as an Array) so that the (Legacy) BIOS does not have a chance to pick an empty BR to boot from. *) more correctly, the Filesystem corresponding to that mount point Commit: 39e6ac67f6f9df2ea9fdb8b72bde925ae929f532 https://github.com/yast/yast-bootloader/commit/39e6ac67f6f9df2ea9fdb8b72bde9... Author: Martin Vidner Date: 2018-01-05 (Fri, 05 Jan 2018) Changed paths: M src/lib/bootloader/stage1.rb M src/modules/BootStorage.rb Log Message: ----------- Pluralized to #stage1_devices_for_name because it returns an Array Compare: https://github.com/yast/yast-bootloader/compare/31441b6cb985...39e6ac67f6f9