Bug 2184190

Summary:	Allow empty strings, *, or "max" as partition size values for "automatically expand to maximum possible size"
Product:	[Fedora] Fedora	Reporter:	Jean-François Fortin Tam <nekohayo>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	39	CC:	anaconda-maint-list, vponcova, vslavik, w
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.