rpm-ostree
freedesktop-sdk
Our great sponsors
rpm-ostree | freedesktop-sdk | |
---|---|---|
47 | 53 | |
813 | - | |
2.1% | - | |
9.6 | - | |
7 days ago | - | |
C | ||
GNU General Public License v3.0 or later | - |
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.
-
Looking to test out fedora Silverblue. I have only 1 question
Issue: https://github.com/coreos/rpm-ostree/issues/3944
-
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.
-
Universal Blue is a new paradigm for the Linux desktop and it's brilliant
here's the documentation of ostree (the package manager)
-
Fedora Silverblue 38: rpm-ostree crashes
Now... this was VERY alarming to say the least, so I went online and did indeed find an issue on GitHub.
- Fedora Linux 38 released!
-
The New website is here, with modern UI. And getfedora.org redirect to fedoraproject.org with fresh look.๐
And there are still some issues with layering. Some packages that don't behave or follow standards will modify files in /usr/local, which isn't supported, so you simply won't be able to install them on Silverblue. I think it's the same for /opt as well. (https://github.com/coreos/rpm-ostree/issues/233) This means it fundamentally can't do everything Workstation can, which is unfortunate.
-
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
freedesktop-sdk
-
The Return of the Frame Pointers
I think I might have confused two unrelated posts. The one that references Polar Signals is this one:
https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/...
So not a perf issue there, but they don't think the workflow is suitable for whole-system profiling. Perf issues were in the context of `perf` using DWARF:
https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/...
- Finally mesa version 23.1.1 for fedora 38 has been published for testing 11 hours ago. It comes with quite important features like vulkan gpl for RADV to fight stutters in games and for better performance.
-
Yocto
But the fd-sdk https://gitlab.com/freedesktop-sdk/freedesktop-sdk and gnome build meta https://gitlab.gnome.org/GNOME/gnome-build-meta projects can prove as good references.
-
Rant: Desktop Sandboxing
With all of these hypothetical features out of the way and looking just at current release software, Flatpak allows you to do so much stuff that isn't accessible for a not-so-techy user. Custom installation folder? Yep. Running mesa-git GPU drivers? You got it. Any way to easily do this via GUI? In typical Linux fashion, nope. For a GUI focused packaging format this is a big letdown.
- Issue found for: Steam Deck Issue With Flatpak Hardware Decoding
- Steam Flatpak. Tried RADV_PERFTEST=gpl with proton-ge-54 but doesnt seem to be working when compared to using it with Bottles. Please see if I did it right.
-
Is there any way to force a specific Mesa driver for applications when multiple Mesa driver versions have been installed?
Link to (official?) how-to: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/wikis/Mesa-git
-
Fedora Workstation 38 Is Shaping Up To Be Another Fantastic Release
You can load up Mesa GIT using environment variables, see here. Honestly what I miss the most from flatpak Steam is properly working non-Steam shortcuts, but I've given up on that.
- Are all AMD GPUs equally well supported?
-
PSA: The new OBS update breaks VA-API encoding when used with the Flatpak
It was my understanding that the packages for vaapi are just put into the -extra version of the sdk so app maintainers can opt out, but they are still available if they want to use them. See https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/10616
What are some alternatives?
ostree - Operating system and container binary deployment and upgrades
flatpak - Linux application sandboxing and distribution framework
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.
Flatseal - Manage Flatpak permissions
openvpn-install - OpenVPN road warrior installer for Ubuntu, Debian, AlmaLinux, Rocky Linux, CentOS and Fedora
argos-translate - Open-source offline translation library written in Python
cxx - Safe interop between Rust and C++
xdg-desktop-portal-gtk - Gtk implementation of xdg-desktop-portal
tectonic - A modernized, complete, self-contained TeX/LaTeX engine, powered by XeTeX and TeXLive.
us.zoom.Zoom
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
oneTBB - oneAPI Threading Building Blocks (oneTBB)