Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Custom" partitioning for the installation destination may be unnecessary in many cases, so improve the GUI #9496

Open
sjvudp opened this issue Oct 7, 2024 · 0 comments
Labels
C: installer C: storage P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. ux User experience

Comments

@sjvudp
Copy link

sjvudp commented Oct 7, 2024

How to file a helpful issue

The problem you're addressing (if any)

When you do not want to give the fully capacity of a device to Qubes OS when installing, one must use the "Custom" method when assigning the destination device, pre-creating most of the structure. And it's not easy to find the steps required (not part of the installation guide).
Also I had encountered a bug that the configuration wasn't accepted after needing several attempts to get the structure right: Installation would not begin, but after I had rebooted the installer, the same configuration was acceptable...

The solution you'd like

If the "Auto" proposal's partition sizes could be adjusted within reasonable size limits, there is no need for "Custom" installations in many cases.
Another case is adjusting some of the parameters of cryptsetup when creating the LUKS device.

The value to a user, and who that user might be

Avoiding the manual steps that are both, time-intensive, and error-prone, could improve the advanced user's experience avoiding unnecessary errors (when maing mistakes while executing manual commands), and saving time (by not having to execute all those steps manually (or repeatedly after an error))

Completion criteria checklist

(This section is for developer use only. Please do not modify it.)

@sjvudp sjvudp added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. labels Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: installer C: storage P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. ux User experience
Projects
None yet
Development

No branches or pull requests

2 participants