rpm-ostree
ABRoot
Our great sponsors
rpm-ostree | ABRoot | |
---|---|---|
47 | 3 | |
800 | 244 | |
1.1% | 5.7% | |
9.6 | 9.2 | |
5 days ago | 6 days ago | |
C | Go | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rpm-ostree
-
What do you prefer more and why?
I definitely agree that immutability offers considerable value in regards to improving security. But arguably it's insufficient to pull the win over mutable Fedora due to the losses caused by the inability to install the kernel-hardened package and the lack of UKI (Unified Kernel Image) support.
-
What is the difference between Immutable Desktops and non Immutable Desktops?
Oversimplifying might have been the most sensible in this context. However, you might have gone a little bit too far as your description fits only NixOS, Guix and distros that utilize rpm-ostree.
- Fedora Linux 38 released!
-
Flatcar Container Linux
ublue is based off of fedora and rpm-ostree, which is what "CoreOS" is today.
What happened was old school CoreOS was A/B partition based: https://github.com/coreos/docs/blob/master/os/sdk-disk-parti...
My memory is hazy but here's how I remember it: After Red Hat acquired CoreOS they rebased the entire thing around rpm-ostree, which is the CoreOS people know today: https://coreos.github.io/rpm-ostree/
At the time there was some anxiety in the community as to what would happen, as there was no direct upgrade path from old CoreOS to new CoreOS. Theoretically if we all believed the kool-aid we were drinking it's just a redeploy, no pets!
Kinvolk came along, forked it, and made Flatcar Linux, which kept the A/B partitioning system, and more crucially, let you just change a config file and all your old CoreOS nodes would just move to Flatcar and then you were good to go. So now if you wanted to stay on the system you were comfortable with you could just use Flatcar. If the composability of rpm-ostree attracted you then new CoreOS have you covered. Red Hat deserves a hat tip here because in their documentation/blog they explicitly mentioned Flatcar as an option for people who wanted to stick with what they know, which I thought was cool and how I discovered it!
Later on Microsoft acquired Kinvolk and and then people raised eyebrows. I have not checked in a while but the folks involved continued to do their thing and run it like a good OSS project, hold public meetings, all that stuff.
I use both and they're both high quality.
-
Immutable Linux Distributions for Those Looking to Embrace the Future
Whenever I was looking at using CoreOS, I was somewhat disheartened that automatic reboots weren't built in: https://github.com/coreos/rpm-ostree/issues/2831. Has this changed? I know zincati has maintenance window support, which would also be nice to have.
-
[HELP] AMD REST BUG
Doesn't look like it https://github.com/coreos/rpm-ostree/issues/1091
-
Opinions on Kinoite?
If you've got this far, please go read the rpm-ostree docs and perhaps read some github issues, it will show you what rpm-ostree truly is, better than I could.
-
What are good resources for silverblue ?
3 - https://coreos.github.io/rpm-ostree/
-
Is there a standardized, fool-proof and no-brainer way to achieve either one of these things: snapshots and hibernation?
Now I've switched to Kinoite and it's more robust. No problems with packages not getting updated properly. If there aren't Flatpak or AppImage options available, rpm-ostree works well for adding packages.
-
Fedora Planning Ahead For The Next 5 Years
The apply live stuff is the experimental command I was referring to. But looking into it a bit more it looks like apply-live was declared stable last year and they're just supporting the older rpm-ostree ex apply-live for the next bit. So I guess that at least partially addresses the issue. It's an extra command to run but I guess it's ok for now.
ABRoot
-
What do you prefer more and why?
Maybe in the future , using a tool like abroot would allow the user to do such modifications as they prefer.
-
VanillaOS: Immutable Ubuntu-Based Linux
It says it uses abroot rather than ostree
What are some alternatives?
ostree - Operating system and container binary deployment and upgrades
vscode-remote-release - Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
openvpn-install - OpenVPN road warrior installer for Ubuntu, Debian, AlmaLinux, Rocky Linux, CentOS and Fedora
cxx - Safe interop between Rust and C++
tectonic - A modernized, complete, self-contained TeX/LaTeX engine, powered by XeTeX and TeXLive.
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
com.unity.UnityHub
ostree-rs-ext - Rust library with higher level APIs on top of the core ostree API
freedesktop-sdk
issue-tracker - Fedora Silverblue issue tracker
nix - Nix, the purely functional package manager