Bug 394639 - No option to view or set partition type (GU)ID
Summary: No option to view or set partition type (GU)ID
Status: CONFIRMED
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (show other bugs)
Version: 3.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Andrius Štikonas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-23 23:08 UTC by Matthew Trescott
Modified: 2022-08-26 08:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Trescott 2018-05-23 23:08:00 UTC
When creating or editing a partition's properties, KDE Partition Manager does not display MBR partition type IDs or GPT partition type GUIDs. I assume that this probably gets determined for new partitions based on the various settings (filesystem, "flags", etc.) but the flags don't represent a realistic picture of the partition table. IMO,
- the flags section should disappear and be replaced with
a drop-down list that allows the user to choose the partition type (https://en.wikipedia.org/wiki/Partition_type). Note that this applies to both MBR and GPT; the only difference is that GPT uses long GUID codes and MBR uses single-byte codes. This would be _in addition_ to the Filesystem drop-down.
- There should be a _separate_ checkbox that toggles the "bootable partition" bit on GPT (search "Legacy BIOS bootable" on the Wikipedia GPT page for more info) and the equivalent bit on MBR.

Reasoning:
- Checkboxes (as shown in the flags option) do not make sense when they are mutually exclusive (because a partition can only be one partition type).
- The flags-based design makes it unclear what "boot" does, since it behaves differently on GPT and MBR: on GPT, it does the same as "esp", which changes the partition type GUID in the partition table to C12A7328-F81F-11D2-BA4B-00A0C93EC93B. On MBR, I assume that it flips bit 7 in byte offset 0 of the partition entry. But it's unclear whether it does the equivalent operation on GPT, which, like MBR has a separate "bootable" bit in addition to partition type GUID.
- The "flags" imply that partition tables have such a structure as "flags," which is not the case, at least for GPT and MBR.
Comment 1 Andrius Štikonas 2018-05-23 23:15:19 UTC
Yes, this is the long term plan, but some other things have to be completed first.

Next version (4.0) will use sfdisk backend instead of libparted backend which is necessary for this migration.
Comment 2 Matthew Trescott 2018-05-23 23:45:49 UTC
Nice to know, thanks.