Skip to content

UrsaOS v0.1.0-alpha.1

Choose a tag to compare

@spalencsar spalencsar released this 28 Jul 13:01
· 24 commits to main since this release

UrsaOS v0.1.0-alpha.1

Warning

Known installer issue: Systems installed from this image inherit the
temporary live Pacman keyring. Official Arch package transactions can then
fail with unknown trust. Alpha.1 should therefore not be used for a fresh
installation unless the manual repair below is accepted.

Fix for systems installed with alpha.1

Run the following commands in the installed system:

sudo rm -rf /etc/pacman.d/gnupg
sudo pacman-key --init
sudo pacman-key --populate archlinux
sudo pacman -Syu

This removes the copied live keyring, creates a persistent local Pacman master
key and imports the trusted Arch Linux package-signing keys again.

Fix status

The installer has been corrected in ursaos-installer 0.1.0-11. New
installations will create their own persistent Pacman keyring automatically.
The correction will be included in the next UrsaOS release; the alpha.1 ISO
itself remains affected.

The first public UrsaOS development preview provides a graphical Try & Install
live system based on Arch Linux with Niri and Dank Material Shell.

Highlights

  • Branded German and English UEFI GRUB and BIOS Syslinux live boot entries
  • Complete Niri + DMS live desktop without an automatically opened terminal
  • Calamares live-copy installation with Btrfs as the automatic default
  • Installer choice between Snapper, Timeshift and no snapshot manager
  • Branded GRUB, tuigreet login and UrsaOS desktop session
  • Archinstall retained as an advanced online fallback

Validated path

The UEFI path has completed repeated end-to-end tests through live boot,
Calamares installation with Btrfs + Snapper, reboot, GRUB, tuigreet login and
the Niri+DMS desktop.

Known limitations

  • This is an early development preview and is not intended for production use.
  • Legacy BIOS end-to-end installation is not yet validated.
  • The Timeshift and no-snapshot installer choices have not received the same
    end-to-end coverage as the default Snapper path.
  • Hardware coverage currently focuses on QEMU/KVM virtual machines.

Verify the ISO with the accompanying .sha256 file before use.