On Sat, Oct 29, 2022, at 1:18 AM, Tim via users wrote: > Here's some more advice you probably won't like: Multi-booting (any > computer, any OS) can be a pain, and it may be best to only attempt > that after you've learnt how a system works. Your safest approach to > learning a new system is to get a second hard drive, unplug your first > one, install onto a fresh drive in isolation, and learn how the system > works. Multiboot is probably fragile. Or at least it is inclined toward chaos, in that we cannot account for everything. Fedora only tests and blocks releases against Windows and macOS existing first, and Fedora second. As there's no manifestation of support beyond community support, is anything supported? We more or less say things that we are willing to block release on are supported, as in they have to work at the time a version is released. But there's lots of buts. And one of those buts is, if you're setting up a system in a way we aren't testing, we certainly aren't going to block release on such edge cases that affect few users. Triboot is definitely one of those. But case in point, lets say you have a completely clean system. Install Fedora copy A, and then you want to do a dual boot of two Fedoras. Say, Fedora Workstation and KDE. Or Fedora 35 and 36. Dual boot Fedoras. Supported? Nope. We have no release criterion for that. Only bugs that happen independent of that configuration would be blockers, not bugs that only manifest as part of a dual boot Fedora installation. -- Chris Murphy _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
