summaryrefslogtreecommitdiffstats
path: root/ChangeLog
diff options
context:
space:
mode:
authorMartin Whitaker <mageia@martin-whitaker.me.uk>2017-02-04 23:46:14 +0000
committerMartin Whitaker <mageia@martin-whitaker.me.uk>2017-02-12 11:54:53 +0000
commit02ba0f311a04e3fe93985bb75b6e7e99c6315b73 (patch)
tree3a6b398284cd4d146839a77a5a144c970f357da4 /ChangeLog
parentaeccd33e13b5bd532fe08e5b3f1630935bbd9cfb (diff)
downloaddrakx-02ba0f311a04e3fe93985bb75b6e7e99c6315b73.tar
drakx-02ba0f311a04e3fe93985bb75b6e7e99c6315b73.tar.gz
drakx-02ba0f311a04e3fe93985bb75b6e7e99c6315b73.tar.bz2
drakx-02ba0f311a04e3fe93985bb75b6e7e99c6315b73.tar.xz
drakx-02ba0f311a04e3fe93985bb75b6e7e99c6315b73.zip
Fix auto-allocation of BIOS boot partitions (mga#20161, mga#19888).
This adds a specific subroutine, fsedit::auto_allocate_boot_bios_parts that detects if a BIOS boot partition is needed and allocates it if so. This allows us to relax the rules in fs::any::is_boot_bios_part_needed to allow the user to manually allocate the BIOS boot partition on a different device if they so wish. In the normal case that installation is confined to a single disk, this will allocate a single BIOS boot partition on that disk. In the rare case that installation is spread over multiple disks, it will allocate a BIOS boot partition on every disk. Given that the BIOS boot partitions are very small and that this is not a normal use case (see mga#16055), this seems an acceptable quirk - and does allow the user to then choose any disk when installing the boot loader.
Diffstat (limited to 'ChangeLog')
0 files changed, 0 insertions, 0 deletions