Bug 2184190 - Allow empty strings, *, or "max" as partition size values for "automatically expand to maximum possible size"
Summary: Allow empty strings, *, or "max" as partition size values for "automatically ...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 39
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-03 21:37 UTC by Jean-François Fortin Tam
Modified: 2023-08-16 08:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jean-François Fortin Tam 2023-04-03 21:37:18 UTC
This is the UX portion of the struggles I had with bug #1137579 a decade ago.

I clean-install Fedora very, very, very infrequently, so I have difficulty remembering how to tell its guided ("custom") partitioning tool to set a particular partition to fill the available space, and for many users I think it would be counterintuitive to think "I'm going to type in a big fake number that vastly exceeds the capacity, just so that it clamps to the max available capacity". It's a bit of a mind twist.

Short of showing a nice "Set to max" button next to those size GtkEntry fields, I would like to request these values to be acceptable in the syntax:

* `` (empty string / empty field - this currently displays a warning)
* `*` (wildcard)
* `max`
* `all`

...typing them in, and pressing Enter or clicking the Update button, would then transform them to the max value.

See also: the fields would benefit from having a tooltip, bug #2184188

Comment 1 Fedora Release Engineering 2023-08-16 08:08:57 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.


Note You need to log in before you can comment on or make changes to this bug.