-
26.20-alpha
Pre-releaseAll checks were successfulCI / lint (pull_request) Successful in 24sCI / test (pull_request) Successful in 1m19sCI / validate-json (pull_request) Successful in 21sCI / markdown-links (pull_request) Successful in 14sBuild ISO / build-iso (push) Successful in 18m15sDeploy site / deploy (push) Successful in 4sCI / lint (push) Successful in 23sCI / test (push) Successful in 1m17sCI / validate-json (push) Successful in 21sCI / markdown-links (push) Successful in 13sRelease / release (push) Successful in 12m2sreleased this
2026-08-25 17:12:48 +02:00 | 9 commits to main since this releaseFirst release shaped by a real-hardware install (old laptop mainboard, BIOS boot,
SSD with a previous Proxmox VE on it). All four fixes are things an empty
Proxmox VM never shows.Fixed
- First catalog sync no longer dies silently at boot. On dual-stack
LANsnetwork-online.targetis satisfied by the IPv6 SLAAC address a
second before DHCPv4 lands, sofurtka-catalog-sync.serviceran into
Network is unreachable, exited, and the next attempt was the daily timer
— up to 6 h of jitter later. Meanwhilecatalog-state.jsonstayed on
checkingand the apps page showed "checking…" with nothing running
(first hardware bench, 2026-08-25). The service now retries on failure
(every 20 s, up to 8 times in 15 min), a failed sync is recorded as stage
errorwith the message, and the apps page shows "last sync failed: …"
instead of a fake in-progress state. - Installer frees the target disk before partitioning. The live ISO
auto-activates whatever an attached drive carries (LVM volume groups, md
arrays, swap) — the first hardware bench's SSD still had a Proxmox VE
pveVG on it — and archinstall then failed at 12 % withunable to inform the kernel of the change, probably because it/they are in use.
install_runnow runsdiskprep.release_disk()first: swapoff/umount
leaves-first,dmsetup remove/mdadm --stopfor every dm/md node
stacked on the disk,wipefs -aon partitions + disk, then
blockdev --rereadpt. Every step is written to the top of the install
log. The progress page also names this failure explicitly instead of a
bare "hit a snag" if it does still happen. - Console banner always shows the IP fallback. On both the live ISO and
the installed system the/etc/issuewelcome was written once, after
network-online.target, and simply omitted thehttp://<ip>line when no
address existed yet — so on a slow-DHCP NIC (first hardware bench,
2026-08-24) the screen only ever offeredproksi.local. The banner script
now runs from a timer (furtka-issue.timeron the ISO,
furtka-welcome.timeron the installed box, every 5 s) and always prints
a fallback line: every global IPv4 address once there is one, or a
"no IP address yet — check the cable / DHCP" hint until then. It only
rewrites/etc/issueand nudges agetty when the text changed, so the
login prompt doesn't flicker. The live ISO no longer auto-logsrootin
on tty1 (releng default) — that handed the console to a shell before the
banner could update; tty1 now stays at the login prompt with a live
banner, and the banner tells you a shell isroot+ Enter away. Boxes
that self-update get the new timer linked + enabled automatically; the
refresh loop takes effect after their next reboot.
Downloads
-
Source code (ZIP)
2 downloads
-
Source code (TAR.GZ)
2 downloads
-
furtka-26.20-alpha.iso
4 downloads · 1.5 GiB
-
furtka-26.20-alpha.tar.gz
4 downloads · 73 KiB
-
furtka-26.20-alpha.tar.gz.sha256
9 downloads · 92 B
-
release.json
10 downloads · 173 B
- First catalog sync no longer dies silently at boot. On dual-stack