> Am 03.06.2022 um 07:17 schrieb Neal Gompa <ngompa13@xxxxxxxxx>: > > > It's not *that* typical in my experience. Most of the SME server > environments I know of don't have that. It's more common in larger > server environments, but they also typically use hardware RAID there > instead of software RAID. We don’t have detailed numbers how Fedora is used. But we know from questions and discussions that people use software raid. And software raid is supported by Anaconda for years now. And in my memory, these were all cases in the private or SME environment, and often with rented hardware in some commercial data centers, where hardware raid is usually offered at a considerable price premium. Anyway, we have users who use software raid and rely on us as a distribution, and they should be able to continue to do so in my opinion. > If we care about this behavior, we should have a test case to verify > this behavior for all three Anaconda install modes (MBR+BIOS, > GPT+BIOS, UEFI). If this is truly something we care about, then we > should have communicated this need to the Anaconda team so that they > would care about it, independent of this feature. We have test cases for the former 2 in issue #87 (https://pagure.io/fedora-server/issue/87) and Stephen Gallagher copied it to a bugzilla bug report (https://bugzilla.redhat.com/show_bug.cgi?id=2092116). I’ll add a UEFI test case to a separate issue this weekend. I’ve it already in place on my test equipment here and have just to copy and paste it. > dmraid has been unmaintained … Yes, of course, it’s mdadm. That was a slip into the good old days. Don’t mind. > calling it "mischief" is disingenuous, since until this week, nobody > ever mentioned this case at all. We even discussed the GPT thing > before I proposed the Change and it did not come up. > Yes, when we discussed this in the server IRC meeting before the change proposal was published, I hadn't thought of it either. But all of us know it since about one year. But we missed to pick it up carry it forward. > You know why I want this Change, and I even wrote it into the > proposal. We have to do *something* to start preparing new installs > for a world when legacy BIOS is *gone*, and switching to GPT is a > simple first step to doing that. Yes, I know, and we completely agree on that from the very beginning. My only suggestion is to organize this changeover process in such a way that our users are not negatively affected in any way. And about this there were (hopefully just) misunderstandings, which we could clarify by now. The changeover only affects Workstation and Server anyway. All others are either spins of Workstation or do not use Anaconda. So, let’s try to convince the Anaconda team to fix the GPT biosboot issue until beta. And if they need more time, let’s either postpone the switch to F38 or switch Workstation now (provided there are no software raid users) and switch Server as soon as the Anaconda bug is fixed. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
