tl;dr (and read 5th paragraph)-
Code:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 238.5G 0 disk
├─sda1 8:1 0 128M 0 part
├─sda2 8:2 0 1G 0 part
├─sda3 8:3 0 80.7G 0 part
├─sda4 8:4 0 39.9G 0 part
├─sda5 8:5 0 16M 0 part
├─sda6 8:6 0 57.3G 0 part
├─sda7 8:7 0 58.8G 0 part /var
│ /boot
│ /sysroot/ostree/deploy/fedora/var
│ /sysroot
│ /etc
└─sda8 8:8 0 613.2M 0 part /sysroot/boot/efi
/boot/efi
zram0 251:0 0 7.6G 0 disk [SWAP]
I have 2 EFI partitions. sda1 and sda8.
During your manual partitioning are you sure that you allocated enough for the /boot, /root, swap, /var/home, /opt, /tmp....etc partitions?
I didn't setup these many. Only /, /boot, and /boot/efi.
Does your efi boot partition have the boot flag?
I don't know what that means. But from what I can infer, the problem probably seems to be the mount configuration which lead to a wrong GRUB config. I could be wrong.
Users have reported that they couldn't install Fedora Atomic Desktop on an EFI system.
That isn't helpful. What am I supposed to do, boot from legacy BIOS? I don't have that. EFI installation should obviously work.
Can you boot into the Live session of Fedora that you used to install it and run this and post back?
To clarify again, I can boot into the Fedora installation. I am writing this from it. In the GRUB boot menu, I just have to edit $root/ostree/... to $root/boot/ostree/. The ostree directory is under /boot which it doesn't want. But it seems that I also have a /ostree anyway? Seems like only the kernel and initramfs are stored in /boot/ostree while /ostree contains the whole deployment and states. Oh, is /boot supposed to be under /ostree/boot? Because also under /ostree/ I have boot.1/ and boot.1.0/, clearly trying to not collide with "boot".
I had partitions on my drive. I am triple booting. I had to choose the manual partitioning method.
Fedora Atomic doesn't support custom partitioning.
??
Fedora Atomic is a container based distribution and so is the workflow, so either toolbox or distrobox and if you have to layer something you will need to reboot unless you use --app-live.
Yeah I know, and it is tiring and very inefficient to reboot. I use --apply-live but I think it is not a very intended way. Maybe containerization is the intended way. Even on Android I can install gcc in Termux and that is containerization. And why do I think layering is also not really that intended? That's why at least for GUI programs I am using Flatapk and oh my how much space it takes. At least though, I get containerization and bloat management which I really like. One delete operation and nothing remains behind. But besides bloat management, I don't think there is much of a reason to use Flatpak. I am using Fedora in the first place because it has a very stable ABI and package compatibility. All packages are supposed to work together. And Flatpak subsystem itself has some overhead. So I might not end up using Flatpak. Or at least for the programs I will have installed most of the time. And I guess I could manually containerize which I haven't tried.
If anyone remembers I said I wanted to try out Fedora Atomic for the delta updates. It still downloads more data than I expected but still significantly lower than Arch Linux. I just downloaded like a 500 MB update (or it was the extracted size, I don't remember). And I think before I had downloaded like a gigabyte of updates. Fedora updates much faster than I expected. Compared that on Arch, I could have to unpack almost 10 GB of data frequently. Ironically, I find that Windows's updates are more size efficient than Fedora Atomic. I honestly don't remember what used to happen on Ubuntu, because that seems to be the most efficient, or it looks to be at least. Maybe it used to update in background without me noticing. Or it updated much slower than Fedora Atomic. OSTree also has its own overhead.
