every Arctic Linux image, newest first, and what changed in each
A1 TESTING has been pulled from
this list: it shipped broken on real hardware - wifi never worked on a
real install, only the live image; the chroot backspace fix didn't take;
arctic-shell couldn't run anything it had just installed. This is A1: no
qualifier claiming more verification than it has actually had, replacing
the broken build rather than adding a second testing label on top of
it.
A1latest
x86_64 · 696 MiB · live image and installer
wifi on a real install had three separate causes, all fixed: linux-firmware never actually landed on the target (the mirror's size limit 404d it silently, now copied from the live medium directly), wifi-connect had no privilege handling for the account arctic-install creates and "Operation not permitted" read as "no networks found - move closer" (it re-execs itself through doas now), and a soft-blocked radio looked like no hardware at all (rfkill is unblocked before every scan)
backspace inside arctic-chroot still moved the cursor forward after an earlier fix for exactly that - zsh's own bindkey fix was undone eight lines later by a pre-existing binding that bindkey applies in order; the stray line is gone
arctic-shell dropped you into an environment where id, which, ls and grep all failed with a missing-library error immediately after reporting a clean install (glibc dropped crypt(), the environment never got the package that provides it); and a session killed outright left mounts behind that had to be found by hand from lsblk - every invocation now sweeps and cleans those up on its own
alpm system fix - which conflated "what's pending" with "apply it" - is now three verbs: system get, system check (a real dry run), system upgrade (applies everything, including a system.conf reconciliation at the end)
networking, the graphics driver, microcode and boot timeout join hostname/packages/services as things system.conf declares and arctic-rebuild reconciles - install.conf's equivalents used to apply once and never again
A_NTP defaulted to on and enabled a service (ntpd) nothing packages yet; off by default now
boot services start together and are waited on afterward instead of one at a time, so a slow network association no longer holds up everything after it