#371 Anaconda Web UI requirement: Dual boot support
Closed: Fixed a year ago by aday. Opened a year ago by jkonecny.

Based on these two requirements https://pagure.io/fedora-workstation/issue/362#comment-847926:

  • I'd also like to raise the general topic of appropriateness for new Linux users, which is an important group for us. Dual boot is important for this group. So is having an approachable installer that doesn't require technical knowledge.

Our proposal:

What Anaconda team could do is to support similar case what we have now. That is to support dual-boot without shrinking. So, if user creates the space where Anaconda can install than the existing system should be added into bootloader automatically.

I would like to avoid shrinking because that could go wrong easily and won't be able to support everything. It could be complex to create a solution which wouldn't put too much complexity to users but still being able to do the work correctly.

Questions:

  • Do the Workstation SIG agree with dual-boot when the new system is installed next to the current one?

@catanzaro could we get this to next Workstation meeting agenda please?

Metadata Update from @catanzaro:
- Issue tagged with: meeting-request

a year ago

We have some other business at tomorrow's meeting. I've added the meeting-request tag to suggest it for next week's meeting (but next week's meeting agenda will be set by our new chair, not by me).

We can't not support shrinking existing volumes. This is a table stakes feature that all Linux distribution installers support.

Just for clarification, I'm not writing we can't support that. Just that we would like to avoid that at least from the beginning. This could be changed in the future and I'm not 100% confident that this is so important feature for the users. (Based on our data it is not at all between the most used partitioning methods).

Right now Bitlocker encryption metadata is read-only on Linux. Last I asked cryptsetup folks, they were not ever planning on modifying Bitlocker metadata, I guess because it's insufficiently documented (?) Going forward, I think it will become standard practice for all distros to defer to Windows utilities doing the shrink in advance of installation.

Thanks for bringing it here Chris. Yes, this is one of the main reasons why we are not so thrilled to do that.

Without the data backup, but IMHO dual-boot with Windows is the most required. However, if it won't work in the near future there is not a big reason to invest into this. We can definitely revisit this later but right now, we have to focus on more priority issues.

Anaconda doesn't have to add a shrinking as it is RFE right now. We should add that to later release.

What is required:
- show information what other systems are already installed
- solve how to select bootable device

We discussed this at last week's WG meeting (2 May 2023). Consensus there was that the main initial requirement for the new web ui is not to regress compared with the current Anaconda. It should be technically possible to dual boot, even if the experience isn't polished or guided.

We would like there to be documentation for what dual boot scenarios are supported. It would also be nice if the installer could show information about which other systems are installed.

Dual boot remains a priority for Workstation and we would welcome a guided dual boot experience further down the line..

I think that the working group has provided the requested information here - closing.

Metadata Update from @aday:
- Issue untagged with: meeting-request
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

We have done first analysis of the current state. It can be useful for regression checking, documentation, and further implementation of guided partitioning feature.
https://docs.google.com/document/d/1cNfKt-EUz0XwU0N5APpjp4eSC0gvDK94W8Wd-ZI457k/edit#

We have done first analysis of the current state. It can be useful for regression checking, documentation, and further implementation of guided partitioning feature.
https://docs.google.com/document/d/1cNfKt-EUz0XwU0N5APpjp4eSC0gvDK94W8Wd-ZI457k/edit#
better link:
https://docs.google.com/document/d/e/2PACX-1vTTzEfRYTQ-IjMFTjGZc_rakHaFj3NDJ1JKe_mukXoP8uTjkvt6BTHWEAAn9fLjH_0BpImYcfe2tndl/pub

@aday the above document is basically description of how Anaconda behaves right now and we think it should be fine to go with this with the first Web UI iteration. However, if there will be some questions around this we are fine to go to the SIG meeting to talk about them.

Login to comment on this ticket.

Metadata