On Mon, May 30, 2022 at 09:18:27AM +0200, Peter Boy wrote: > > > > Am 30.05.2022 um 04:28 schrieb Chris Murphy <lists@xxxxxxxxxxxxxxxxx>: > > > > On Sun, May 29, 2022 at 6:56 AM Peter Boy <pboy@xxxxxxxxxxxxx> wrote: > >> > >> > >> > >> > >> Fedora Server WG discussed the proposal and insists that the proposal be deferred until Anaconda can install software raid on biosboot systems with GPT (see https://bugzilla.redhat.com/show_bug.cgi?id=2088113 and https://lists.fedoraproject.org/archives/list/server@xxxxxxxxxxxxxxxxxxxxxxx/thread/VSM473WRHKIIIJYZZCVXAO7XFS4ACHPH/) - at least for Fedora Server where software raid is a common use. > > > > What's the basis for holding up this feature though? > > Sorry, under the current circumstances your „feature“ is effectively a regression. It would make it impossible for many Fedora Server users to continue using Fedora Server as soon as they have to re-install or just want to set up a new additional server. > > And even those who can continue to use Fedora Server via update are under the threat of having to switch distributions overnight in the event of a technical error. Fedora will become unusable for them. A great "feature", that you would like to introduce, obviously at all costs. Is 'inst.mbr' a viable workaround? (The bug mentions 'inst.gpt' to trigger the issue.) Zbyszek _______________________________________________ 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
