gnome-randr-rust VS distribution-spec

TIL about various things for ostree distros:

https://github.com/maxwellainatchi/gnome-randr-rust :

> gnome-randr-rust: `xrandr` for Gnome/wayland, on distros that don't support `wlr-randr`*

Kernel-fsync: https://copr.fedorainfracloud.org/coprs/sentry/kernel-fsync/

gnome-vrr:

Changing the orientation: Gnome is currently using Wayland rather than X as the default, so using xrandr has no effect. However, I can use gnome-randr-rust (available in nixpkgs via nix-shell -p gnome-randr). The following is sufficient to change the orientation when I run it from Console in the desktop session:

On wayland, there seem to be many options, unfortunately none work. xrandr --output XWAYLAND0 --off simply has no effect, wlr-randr is not supported because of compositor doesn't support wlr-output-management-unstable-v1, and gnome-randr modify HDMI-1 --mode='-1' (or --off) is not available yet (See: https://github.com/maxwellainatchi/gnome-randr-rust/issues/13)

Hey, I might've actually found a way to do this! Want to open a new issue on my repo and I'll dig into it a bit further? I need a little help checking out this solution since I don't have an Intel card so I can't actually see if my theory is correct.

A project to write a wayland compositor for gnome I wouldn't use it, but it shows the need is there.

Back in 2013, a little company called Docker made it really easy to start using containers to package up applications. A big key to their success was the OCI (you can learn about that here), an industry wide initiative to have standards around how we package up our applications. Because of OCI standards, we have hundreds (maybe thousands?) of tools that can be combined to manage and deploy applications. So why aren’t we using this for packaging up Notebooks and AI models as well? It would make deploying, sharing, and managing our models easier for everyone involved.

Kubernetes on the backend used to utilize docker for much of its container runtime solutions. One of the modular features of Kubernetes is the ability to utilize a Container Runtime Interface or CRI. The problem was that Docker didn't really meet the spec properly and they had to maintain a shim to translate properly. Instead users could utilize the popular containerd or cri-o runtimes. These follow the Open Container Initiative or OCI's guidelines on container formats.

OCI stands for Open Container Initiative, and its goal as an organization is to define a specification for container formats and runtime.

https://opencontainers.org/

Here is Containerfile from the repo: https://github.com/ublue-os/bazzite/blob/main/Containerfile

apko allows us to build OCI container images from .apk packages.

Flagger's load testing service can be installed via a Kustomization resource based on manifests packaged as an artifact in an Open Container Initiative (OCI) registry

CRI-O is a lightweight container runtime for Kubernetes. It is an implementation of Kubernetes CRI to use Open Container Initiative (OCI) compatible runtimes for running pods. It supports runc and Kata Containers as the container runtimes, but any OCI-compatible runtime can be integrated.

So somebody else created runj (runj is an experimental, proof-of-concept OCI-compatible runtime for FreeBSD jails.) https://github.com/samuelkarp/runj