To make sure the workaround is still working, I’ve just run a test in a VM: fresh install of Silverblue on the same disk as another OS. These are roughly the steps to be taken:
- Make unallocated free space available on the existing drive for the new OS, using the available tooling (e.g. Fedora Workstation ISO booted into a live environment)[1];
- Boot the Fedora Silverblue (or another Fedora Atomic) installation media;
- In the Installation Destination window, select the Custom option for Storage Configuration. Press Done;
- In the Manual partitioning window, click the option to create the mount points automatically (Click here to create them automatically);
- The installer will propose the mount points. Among them there is the
/boot/efimount point, referencing the existing EFI partition used by the other OS. Remove this mount point with the “-” button; - Select the root partition, press Modify, change the Size policy to Fixed, and enter a value about 1GiB smaller then the proposed value. Save;
- With the “+” sign, add a new mount point
/boot/efi, with desired capacity up to but no more than 1024MiB (the system proposes by default 977MiB). - Press Done in the top left of the window. A Summary of Changes will be displayed. Accept the changes;
- Proceed with the installation;
- After Silverblue gets installed, select the non-default boot OS by accessing the UEFI Boot Manager.
Feel free to use whatever you find useful from the above in your guide.
Free space can also be obtained directly within Anaconda, by choosing the Blivet-GUI storage configuration, but that would keep the storage setup in the Blivet interface, which needs manual allocation of the partitions. ↩︎