daniel/furtka
1
1
Fork 0
Code Issues 2 Pull requests 2 Projects 1 Releases 18 Packages Wiki Activity Actions
furtka/iso/overlay/airootfs/etc/issue

8 lines
192 B
Text
Raw Normal View History

feat: console welcome with proksi.local + post-install reboot flow Two user-visible polish passes on top of the walking-skeleton install: - Console welcome: live ISO's getty no longer shows the bare Arch prompt. `/etc/hostname` is now `proksi` so avahi advertises `proksi.local`; a systemd oneshot (`furtka-issue.service`, runs after network-online.target) regenerates `/etc/issue` via `/usr/local/bin/furtka-update-issue` to show both `http://proksi.local:5000` (preferred, via mDNS — avahi and nss-mdns are already in `packages.extra`) and the raw IP as a fallback for networks where mDNS is flaky. `agetty --reload` nudges the already- running login prompt to redraw. - /install/log now polls a JSON endpoint (`/install/log.json`) every 3 s instead of meta-refresh, so expanding the collapsed log `<details>` doesn't get eaten by the refresh. Noscript fallback keeps the meta-refresh for JS-off users. When the install finishes, the Done state shows a Reboot-now button that POSTs to `/install/reboot` (guarded server-side to only reboot once status is "done", so a panicked click mid-pacstrap can't brick the box). A confirm() reminds the user to pull the USB / eject the ISO first. End-to-end tested on a Proxmox VM 2026-04-14: boot → wizard → archinstall → Done state → Reboot now → VM came back up → login as created user → `docker ps` worked. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-14 18:08:59 +02:00
Furtka Live Installer starting…
Once ready, open http://proksi.local:5000 on another device
fix(console): always show the IP fallback on the welcome banner The /etc/issue banner on both the live ISO and the installed system was a oneshot after network-online.target that simply dropped the http://<ip> line when DHCP hadn't delivered yet — so a slow NIC (first hardware bench, 2026-08-24) left the screen offering only proksi.local. On the ISO, releng's root autologin on tty1 also made agetty --reload a no-op. - furtka-issue.timer (ISO) / furtka-welcome.timer (target) re-run the banner script every 5 s; services drop RemainAfterExit + network wait - fallback line is always present: every global IPv4, or a 'no IP yet — check cable / DHCP' hint; only rewrites + reloads on change - build.sh removes releng's getty@tty1 autologin drop-in; banner tells users a shell is root + Enter away Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MScAinbyMdeNc7H2BZdnnG
2026-08-25 15:18:39 +02:00
on your network. The exact URL (and an IP fallback) will
appear here in a few seconds.
feat: console welcome with proksi.local + post-install reboot flow Two user-visible polish passes on top of the walking-skeleton install: - Console welcome: live ISO's getty no longer shows the bare Arch prompt. `/etc/hostname` is now `proksi` so avahi advertises `proksi.local`; a systemd oneshot (`furtka-issue.service`, runs after network-online.target) regenerates `/etc/issue` via `/usr/local/bin/furtka-update-issue` to show both `http://proksi.local:5000` (preferred, via mDNS — avahi and nss-mdns are already in `packages.extra`) and the raw IP as a fallback for networks where mDNS is flaky. `agetty --reload` nudges the already- running login prompt to redraw. - /install/log now polls a JSON endpoint (`/install/log.json`) every 3 s instead of meta-refresh, so expanding the collapsed log `<details>` doesn't get eaten by the refresh. Noscript fallback keeps the meta-refresh for JS-off users. When the install finishes, the Done state shows a Reboot-now button that POSTs to `/install/reboot` (guarded server-side to only reboot once status is "done", so a panicked click mid-pacstrap can't brick the box). A confirm() reminds the user to pull the USB / eject the ISO first. End-to-end tested on a Proxmox VM 2026-04-14: boot → wizard → archinstall → Done state → Reboot now → VM came back up → login as created user → `docker ps` worked. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-14 18:08:59 +02:00
Reference in a new issue Copy permalink