Bug 1225067 - Add more info to "Select A Disk" dialog during install
Summary: Add more info to "Select A Disk" dialog during install
Status: RESOLVED UPSTREAM
Alias: None
Product: openSUSE Aeon
Classification: openSUSE
Component: Installation (show other bugs)
Version: Current
Hardware: x86-64 Other
: P5 - None : Enhancement
Target Milestone: ---
Assignee: Richard Brown
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-23 03:37 UTC by Mike Watkins
Modified: 2024-05-23 07:57 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Watkins 2024-05-23 03:37:34 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36
Build Identifier: 

Selec A Disk currently displays a string comprised of media type + media name + size + serial number; plus size as another value.

For those of us with multiple drives, whether the others have an OS on them or not (data or backup devices), it would be uber-helpful if this dialog could show a bit more info to support selection. If it were possible to gather information from the partitions on a drive, this would help in decision making too.

lsblk -o name,label,fstype,serial

This would, for example, help one avoid overwriting a drive with a different OS or a file system that obviously doesn't belong to a previous Aeon install.


Reproducible: Always

Steps to Reproduce:
1. Install



To be sure of the disk I was installing to, I aborted the install, restarted my RC1 installation, ran an appropriate lsblk command, and took a photo of the output.
Comment 1 Richard Brown 2024-05-23 07:57:57 UTC
Not truely an "Aeon" bug, in the sense that most Aeon hardware isn't going to have that many disks that such a feature is useful

But, I can see it being more useful for tik in contexts other than Aeon

Therefore closing this bug as RESOLVED UPSTREAM and opened https://github.com/sysrich/tik/issues/17

Also marked as a good first issue because a new contributor should already have a lot of hints as what to do given the awesome quality of the bug report

Thanks!