| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
When the "Use entire disk" partitioning solution is chosen in a UEFI
install, any existing ESP will be deleted, so we must force the
partition suggestions to be updated to ensure we create a new one.
(this matches what is done in the diskdrake auto-allocate routine)
|
|
|
|
|
|
|
|
| |
The compare function doesn't look at the filesystem type, so there's
no need to probe it.
This avoids unwanted udev events when we are checking that the kernel
has been informed of partition table changes.
|
|
|
|
|
|
|
|
| |
If we are upgrading a system on a GPT disk and it doesn't currently
have a BIOS boot partition, the old system must be using a legacy
bootloader (e.g. grub). We support the continued use of legacy
bootloaders in an upgrade, so there is no need to insist on a BIOS
boot partition in this case.
|
|
|
|
|
|
|
| |
This relaxes the rules in fs::any::is_boot_bios_part_needed to allow
the BIOS boot partition to be located on any disk, not just the disk
containing the root partition. It also ensures that a BIOS boot
partition is never forcibly required in a system with non-GPT disks.
|
|
|
|
|
| |
This prevents misreporting of the partition type in diskdrake if they
located on top of an old partition that contained a valid file system.
|
|
|
|
|
|
| |
When doing a UEFI install, we add a fstab entry to mount the ESP on
/boot/EFI. This is neither required nor desirable when doing a legacy
boot install, even if an ESP is present on the disk.
|
|
|
|
|
|
|
| |
The subroutine isEmpty() is used to identify free space on the disk
(not DOS "Empty" partitions). Because we use a string to flag Empty
and BIOS_GRUB partitions, rather than a numeric value, the numeric
equality operator gives false positives.
|
|
|
|
|
|
|
|
|
| |
(mga#20074).
To minimise the changes this close to mga6 release (and until we fix
the bug in partition auto-allocation that mistakenly creates BIOS boot
partitions non-GPT disks), reuse the BIOS_GRUB flag for flagging Empty
partitions, as the real partition ID (0x00) is used to flag free space.
|
| |
|
| |
|
|
|
|
|
| |
we could have exported cannotBeMountable() but it's cleaner to export
another isFoobar() function
|
| |
|
|
|
|
| |
(BIOS boot partition, thus fixing mga#18923)
|
| |
|
| |
|
|
|
|
|
| |
also enable bad blocks checking on JFS (was in one place but not in
other and indeed mkfs.jfs does support it)
|
| |
|
|
|
|
|
|
|
|
|
| |
and explain the purpose of the uniq_() call
see commit 56b573476e2ea63a509ab2f8ec0683397ae7c85e
Rationale: use_pt_type() now returns 0 for common disks (eg: GPT ones)
Under GPT+UEFI, we've 2 important "FS" having vfag as the real FS:
ESP & FAT32
|
| |
|
|
|
|
|
|
| |
we cannot keep UUID when formating btrfs:
- btrfstune -U needs answering "y"
- mkfs.btrfs -u fails with: "non unique UUID: XYZ..."
|
| |
|
| |
|
| |
|
|
|
|
| |
sometimes we end with bogus 'fat32' fs
|
| |
|
|
|
|
| |
...in custom mode (mga#18656)
|
|
|
|
| |
thus guessing better if we need a GRUB_BIOS partition (mga#18656)
|
|
|
|
|
|
| |
this is incomplete: we need to reread $all_hds else we won't add a Boot
BIOS partition to suggestions if there was already one _prior_ to erase
the full disk (mga#18656) ...
|
| |
|
|
|
|
|
| |
also take a $all_hds arg instead of $fstab
needed for next commit
|
| |
|
|
|
|
| |
let's abuse ->{pt_type} for tracking such partitions
|
|
|
|
| |
fixing grub2 faillure resulting in draklive-install crash (mga#16246)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
(mga#16055)
|
|
|
|
| |
split those unknow from udisk2 on next line
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
thus fixing mga#15689 for live installs
The check for whether an ESP needs to be created or not seems to prevent
us to suggest a mount point for the existing one in some cases
to be reviewed for mga6...
diff --git a/perl-install/fs/partitioning_wizard.pm b/perl-install/fs/partitioning_wizard.pm
index f3b9973..b222c07 100644
--- a/perl-install/fs/partitioning_wizard.pm
|
| |
|
| |
|
|
|
|
| |
needed for mga#15257
|
|
|
|
| |
regression introduced in commit ae5b3ce9845669227ef06c90dfaa1065a7ceebe8
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
create_display_box gets called twice. The first time, only the $kind
parameter has a value, the second time all the parameters (including
$button) have values.
On the first time through the partitioning step, the second call to
create_display_box sets the selected_for_resize flag for my NTFS
partition. When returning to the partitioning step, this flag is still
set, so the first call to create_display_box executes the block of code
that ends with
$button->signal_connect('focus-in-event' => sub { ... });
even though it doesn't have a value for $button.
(Martin Whitaker, mga#15919)
|