diff options
| author | Martin Whitaker <mageia@martin-whitaker.me.uk> | 2017-02-04 23:46:14 +0000 |
|---|---|---|
| committer | Martin Whitaker <mageia@martin-whitaker.me.uk> | 2017-02-25 11:42:48 +0000 |
| commit | daf8670c08e54ac64407f7f209aaf9b460abdcc6 (patch) | |
| tree | 24090050514848c12135a81e8c522330b1a7c287 /docs | |
| parent | b0c38fdecf52eaff16597fbd9d0e9772e107fc34 (diff) | |
| download | drakx-daf8670c08e54ac64407f7f209aaf9b460abdcc6.tar drakx-daf8670c08e54ac64407f7f209aaf9b460abdcc6.tar.gz drakx-daf8670c08e54ac64407f7f209aaf9b460abdcc6.tar.bz2 drakx-daf8670c08e54ac64407f7f209aaf9b460abdcc6.tar.xz drakx-daf8670c08e54ac64407f7f209aaf9b460abdcc6.zip | |
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 'docs')
0 files changed, 0 insertions, 0 deletions