Branch: refs/heads/better_raid_proposal
Home: https://github.com/yast/yast-bootloader
Commit: 76c89926a9a837da7395b64334ef0c9b5c02f2fd
https://github.com/yast/yast-bootloader/commit/76c89926a9a837da7395b64334ef0...
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: 03437b1b39d6d04cc6967879277bada4fd5b3249
https://github.com/yast/yast-bootloader/commit/03437b1b39d6d04cc6967879277ba...
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/39e6ac67f6f9...03437b1b39d6
