I recently switched from arch to kionite and I quite like it a lot. There is defenitly more stability and security. Although rpm-ostree I quite a learning curve compared to pacman.
Either way for anyone curious ask NY anything about the distro / the switch to it.
Why Kinoite over say uBlue’s Aurora, Bazzite or even uBlue’s base[1] Kinoite image?
That just includes a bunch of basic stuff you’d most likely want anyways. ↩︎
For my Laptop I wanted to stick with the basics and go from there so I didnt really checket wether there where any distros based of off kinoite or silverblue. I want to use only packages I need. I guess aurora bazzite etc would remove the fedora flatpaks out of the box which would have saved maybe 5 minutes vut either way I dont want to install derivatives from derivatives etc. for example mint or cachy(I know these have different bases the point is I want to stick to the source as close as possible)
Now on my pc on the other hand I just installed bazitte because I do play video games on it.
Fedora licensing cripples the stock Silverblue offerings. Using an immutable without the drivers and codecs baked in is not great. Sure you can add these with ostree, but then why use an immutable …
yeah I get that for my laptop it works out just fine. however for my pc I use bazzite as it has an nvidia gpu.
overall thats a good point and definitly something people should consider.
honestly, it’s going to take a lot for me to switch distros. i had Gentoo for 5y. finally ran out of time to compile and dispatch config. used Debian for 10y. finally bought a new machine where I needed latest Wayland, kernel and drivers, and Debian testing didn’t cut it. switched to arch.
to switch now id need something essential that absolutely can’t be done in arch.
aka nothing
because distrobox and virt-manager go brrrrrr
I tried Kinoite a while back and the included Box Buddy couldn’t clone containers. I took it all the way back to the docker command that was cloning and it would just fail out. Same version of Box Buddy/Distrobox/docker on regular Fedora worked fine. Pinged the developer of Box Buddy and he figured it was something about how Kinoite worked that was messing with it and I should ask the Kinoite maintainers. At that point my curiosity was exhausted and I’d run into the software install annoyances with rpm-ostree based distros, and just went back to Fedora.
Ah, I did the exact same about a week ago. To be fair, I installed Kinoite on a second laptop, because I really need my working setup for the next couple of weeks. So I am not forced to use the Kinoite.
The thing that mostly drives me back to Arch, ist that I dont really understand the different appoaches of flatpak, toolbox and the package layering, or more their specific pros and cons and when I want/have to use what, depending also on my threat model.
I even struggled to get my Thunderbird working with my old config, because it wouldn’t recognize my
.thunderbirdin/var/apps/net.thunderbird.Thunderbird/...Although Fedora has a quite good documentation, which I read with joy (which is not usual) I feel that I am missing some graphical depiction, or something :D
I think the last 2 days I didn’t touch this, because I was thinking about writing a lemmy post, with the following:
- What are the most obvious things one has to learn/understand, before switching from arch to immutable (esp. kinoite) ?
- What steps in your workflow changed, and how do you feel about them? Like do you like them? Is it annoying, but you know it’s for good so you still do it? Do you really don’t like something?
Thanks for your post, it came just at the right time :D
I tried bazzite, which is very close to kinoite, as Fedora itself had a great out of box experience, even on laptops.
Whilst there was a way to get most setups, apps and configs working it was clear I would eventually run into a piece of software that the effort to get it working was not worth it. Some software and development tools are not (yet) designed and maintained to easily work in an immutable environment.
My biggest gripe was that any interaction with os-tree meant that updates now started to take a really long time building the image with high CPU/power usage. I wasn’t ditching Windows to go back to a world of unnecessarily long updates.
For some, I can see the immutable can work well if they want an Android like experience and can accept the software catalog available. It wasn’t the right model for me, as I expected my machine to do more than point and click app install. I would be curious how your typical arch user would find it.
I haven’t yet run into any piece of software that’s fundamentally incompatible with the immutable model thanks to distrobox. This also means I don’t have any packages layered, so updates are very quick.
I just can’t recommend Aurora, Bluefin and Bazzite enough. Go read Bazzite’s docs. If you had ever used MacOS as a developer and wanted to use Linux tooling, the way you are supposed to work with atomic distros will be suddenly clear to you.
Idea of this distro different Rpm-ostree mostly not supposed to use at all or used in rare case to install some system driver or etc packages ,everything else .to install software it supposed to use flatpak,appimages and toolbox(I prefer distrobox which possible to install either and work both using podman) to create containers in which will be small copies of OSes ,u can install any u need Debian/arch/Ubuntu/fedora and they would be mutable in container and not touching with binaries libs and etc main system.
Can you install system packages?
do you want to customize an image yet?
I mean I alredy have As my vpn provider has no flatpak
Did you also switch to another keyboard driver or wby did you write kionite?😋
*why
