I open this thread with regards to yesterday's and today's conversation in the devel matrix channel.
In the recent weeks I had to work a few times with the Anaconda Web-UI installer, having been unable to use Fedora in some use cases as I kept running either into limitations of the installer or into crashes. The conversation in the Matrix channel indicates other had experienced comparable issues, that this is maybe not the minor issue of eccentric use cases I assumed earlier, and that there is a lack of contributions to anaconda web-ui, but also considerations of alternatives to web-ui. Some issues I ran into make me question if at some point some users can be forced to switch their distro due to the bottlenecks of anaconda. So I open this thread to ... 1) get an overview of the situation and existing issues (what use cases are broken, what limitations do we have and are they minor or serious, more information of the crashing issues in different cases, user and developer expectations) 2) accumulate ideas how to tackle the issues that need to be tackled My feeling was that this web-ui installer contains great innovation, but I'm currently not convinced if we can develop and maintain it properly, and if the latter can cause noteworthy impact on the long term (that's more of a question than an argument:) ----- Starting with my recent case: I have started to accumulate a few points in a bug report, but quickly experienced this would become a project I have currently not the resources for. The initial issues I found are in https://bugzilla.redhat.com/show_bug.cgi?id=2439682 What I have run into since (the core issues I think could be relevant for other use cases too): I want to install Fedora on a system that has already multiple operating systems (alma, rocky, centos), and while it worked fine that I subsequently installed the other three OS, it breaks with Fedora: I have to prepare everything in advance from encryption to partitions, as the web-ui does only know "one size fits all" or "mount points only": however, ... 1) when trying to set mount points, I need to also create partitions in advance that have different sizes, as the sizes are the only distinct information shown by the web-ui so that it is the only means to clearly distinguish partitions from each other 2) anaconda is able only to work with only one LUKS password: if partitions have different passwords, anaconda runs into a limitation -> to solve this, I need to set all passwords of LUKS devices equally, do anaconda install, and change them later again through cryptsetup. 3) even when tackled all issues, I always run into a crash: I therefore do not yet know if I can re-use an existing /boot partition through the mount points without breaking any of the OS, as I could not yet finish an installation :) Don't know yet of the cause of this, but lack time to do in depth testing (it could be also an incompatibility to use different hard disks in one installation or so, or some of the mount points I use). Testing was done with F43 KDE Spin. Just some initial issues from my side to give incentives for a discussion. Feel free to contribute and discuss everything related to 1) or 2). Best, Chris/py0xc3 -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
