This image is based on aurora-dx:stable-daily. A new version / build is released daily.
The linux lineage of this spin therefore looks something like this:
mindmap
root((Linux))
Red Hat
Fedora CoreOS
Fedora Silverblue
Universal Blue
Aurora
Aurora-DX
Galtzo-OS
Debian
Ubuntu
SLS
Slackware
Jurix
SuSE
Enoch
Gentoo
Arch
NOTE: The DX means the "Developer Experience" flavor.
If you are unfamiliar with Universal Blue Linux, or Atomic Fedora, start your journey at universal-blue.org, and download an image that suits you.
If you want to jump right into making your own spin (the water is fine!) start with the Blue Build Workshop, a web tool that will create a repo like this one and build your first image.
Or see the BlueBuild docs for quick manual setup instructions.
This particular configuration layers the following onto aurora-dx:
- NordVPN (also added to systemd) (config taken from jlandahl/aurora)
- 1Password
- 1Password CLI (
op) - Ruby build dependencies (fedora specific)
- autoconf
- gcc
- gcc-c++ (necessary for Ruby < 3.1)
- rust # for oxide-rb, magnus, tree_stump & other crabby things
- patch
- make
- bzip2
- openssl-devel
- libyaml-devel
- libffi-devel
- libicu-devel
- zlib-ng-compat-devel
- readline-devel
- gdbm-devel
- ncurses-devel
- perl-FindBin # Because of OpenSSL!
- java-25 # for JRuby!
- snapper
- asusctl
- asusctl-rog-gui
- ghostty
- earlyoom (Configured to protect JetBrains IDEs from being killed by System OOM assassin)
- Virtual Machine Manager Dependencies
- qemu-kvm
- libvirt
- libvirt-daemon-kvm
- libvirt-daemon-config-network
- virt-manager
- virt-install
- virt-viewer
Virtual Machine Manager is configured to show both local libvirt connections:
qemu:///sessionfor user-owned VMs such asimac-mint-vacationandmint-home-vacationqemu:///systemfor shared system-managed VMs
Both connections are configured to autoconnect, so launching Virtual Machine Manager from the desktop should show VMs from both inventories. Libvirt keeps these inventories separate; a VM defined on one connection does not appear on the other.
It also configures the size of local swap memory (zram) to equal the size of RAM on the system.
| This is an experimental feature, try at your own discretion. |
|---|
To rebase an existing atomic Fedora installation to the latest build:
- First rebase to the unsigned image, to get the proper signing keys and policies installed:
rpm-ostree rebase ostree-unverified-registry:ghcr.io/pboling/galtzo-os:latest - Reboot to complete the rebase:
systemctl reboot - Then rebase to the signed image, like so:
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/pboling/galtzo-os:latest - Reboot again to complete the installation
systemctl reboot
The latest tag will automatically point to the latest build. That build will still always use the Fedora version specified in recipe.yml, so you won't get accidentally updated to the next major version.
Once you have this image installed updating to the latest is a two step process if you want to do it manually.
ujust update
systemctl rebootOtherwise if you just reboot periodically updates will simply happen transparently in the background. Generally there won't be more than one build per day, so a daily reboot will keep your system fresh.
You can generate an offline ISO with the instructions available here. These ISOs cannot unfortunately be distributed on GitHub for free due to large sizes, so for public projects something else has to be used for hosting.
These images are signed with Sigstore's cosign. You can verify the signature by downloading the cosign.pub file from this repo and running the following command:
cosign verify --key cosign.pub ghcr.io/pboling/galtzo-os