Installing Kinoite/COSMIC-atomic with windows in parallel

[pramodvu1502 (Pramod V. U.)]

@hricky

If you’ve done the necessary research and are confident that you can overcome any issues you might encounter, it’s probably worth a try.

$(bootctl -x)/grub2/grub.cfg only concerns GRUB itself, the boot entries as per the UAPI BLS.
systemd-boot supports BLS layout, infact even before GRUB.

$(bootctl -p)/loader/loader.conf is it’s config file, which is well-documented, and declarative. Unlike using $(bootctl -x)/grub2/user.cfg.
[PS $(bootctl -p) is /efi or /boot/efi depending on when system was installed]

So infact systemd-boot is the better bootloader than GRUB. More suited for immutable distros.

As for testing,
Since I installed gentoo alongside until I deleted Kinoite, the last time I previously used it, that’s exactly how I used it. No issues.

@hricky

I’m not sure I fully understand this question, but in terms of using sysexts, there should be no difference between Fedora Bootable Container (bootc) systems and classic ostree/rpm-ostree systems.

What is the difference between “bootc” systems and “classic” rpm-ostree systems? Aren’t both present in any given system right now?

@hricky

At least as far as I am aware, rpm-ostree is not going away anytime soon and will continue to coexist with bootc for the foreseeable future.

Oh! Great… I’ll just use rpm-ostree install then and avoid bothering with bootc and Containerfiles and all…
Problem solved (almost)…

@hricky

As I mentioned before, since it’s available and documented, it’s probably worth at least trying. If it doesn’t work as expected, file an issue so we can try to reproduce it. You can find the link to instructions on how to install and update syxexts in my previous post.

The post is highly informative, thanks.
BUT, I need automatic updates… I could help with it except that IDK SELinux…
But what’s it’s purpose when RPMs already exist? bootc I guess…

@hricky

Actually, if you don’t want to make any changes to the base image, you won’t need to build a derived container image to rebase/switch to a Fedora Atomic bootable container. Upgrades should then be performed using the bootc upgrade command.

I don’t want any changes… JUST I want iwd package to be installed… AND maybe NetworkManager config snippets if supported in /usr/lib/wherever/else to use iwd.
AND distrobox installed.

@hricky

rpm-ostree IS great and as you may already know, it has container native capabilities.

Why bootc then?
What is it trying to solve over rpm-ostree+ostree?

@hricky

Currently, bootc is a rather simple tool which shares a lot of the same underlying code from the ostree project.

What’s it purpose?
I really think that ostree supports everything needed for container-native desktop booting, etc.. etc.. and rpm-ostree on it is really great. sysext could be used when needed, it has it’s own great uses…

I don’t understand the need for reinventing half of ostree and rpm-ostree, and using ostree anyways for the remaining half… or even reimplementing the same concept over and over again…
What was it’s issue? RPMs only? rpm-ostree usroverlay solved that already.
Container-native needed? ostree already supports that.
What else? Rust rewrite? IDK

Another thread here: Why replace ostree with bootc? Doesn't ostree do it's job well? - #3 by pramodvu1502