LordOS — a free, fast and secure GNU/Linux distribution based on Debian, with its own desktop environment: display server and Wayland compositor in C, a React UI engine on QuickJS, and private native apps.
C cdebiandesktop-environmentebpffirewalllandlocklinuxlinux-distributionopen-sourceprivacyquickjsraspberry-pi-5reactsecuritywaylandwayland-compositor
ISO.md: which 0.8.4 ISO was installed and which was boot-tested
Federico Pereira6fbf3e1884be
diff --git a/docs/ISO.md b/docs/ISO.mdindex f957613..cf8ab53 100644--- a/docs/ISO.md+++ b/docs/ISO.md@@ -467,7 +467,7 @@ October 25 with the final build (it adds the Pi HDMI wait, 4d17d2d, and strips `| Migration 005 on the upgraded system: `/etc/chromium/master_preferences` `custom_chrome_frame` false → true, `/etc/firefox-esr/lordos.js` `inTitlebar` 0 → 1. Settings → Appearance → "Browsers: tabs in the title bar" lists "1 Chromium profile still uses the LordOS frame" (a profile opened on 0.8.3); **Change them** → Chromium opens with a single bar and LordOS's traffic lights | pass || Smoke checks: XTerm opens (Xwayland `:0`, `app-lordos-debian-xterm.scope`); the native LordOS Imager opens (Device step); the overlay scroll bar shows while scrolling and is gone once the pointer leaves; smartmontools installed and smartd forced past its virtualization check: it stays off | pass || Remote desktop on the upgraded VM 120 (Settings → Sharing on, "Local network"), from the maintainer's machine in headless Chrome: H.264 video over UDP, 1280×800, the data channel up, audio packets flowing; with UDP and every TCP connection to 5673 beyond the first dropped (`iptables` on the VM, for the test only) the page shows "Couldn't connect to the remote desktop" with why and what to do, and Try again | pass |-| VM 117, OVMF: live desktop from the 0.8.4 ISO; install on the disk (en_US, Buenos Aires, 2 GB swap) in under 2 minutes; installed: login screen, `lordos` 0.8.4, `xwayland` and `libsrtp2-1` installed, Chromium's new-profile default `custom_chrome_frame: true`, `lordos-firstrun` present, 0 failed units, boot 6.8 s, 4.6 GB used | pass |+| VM 117, OVMF: the final ISO boots to the live desktop, About "Version 0.8.4 · Beta", build `20261025.ca52be13`, **Verified**; the install itself was tested with the first build's ISO (`20261019.13bdd697`, the same installer): install on the disk (en_US, Buenos Aires, 2 GB swap) in under 2 minutes; installed: login screen, `lordos` 0.8.4, `xwayland` and `libsrtp2-1` installed, Chromium's new-profile default `custom_chrome_frame: true`, `lordos-firstrun` present, 0 failed units, boot 6.8 s, 4.6 GB used | pass || Raspberry Pi 5 (lordos 0.8.3, kernel `6.18.57-lordos.3-rpi-2712`): `apt-get install lordos` from staging: 0.8.4 in 13 s, migration 005, `sshd -t` clean, `lord-server --check-code` verified; `lordos`, `lord-netperm`, `lord-fand` restarted (no reboot), `display: /dev/dri/card1`; then the source switched back to the live repository: `lordos 0.8.4` installed and candidate | pass || Pi firewall cut on kernel `-3` with 0.8.4 (`server/tests/netperm_cut.sh` as root with a hand-made session cgroup, removed afterwards): TCP download cut 0.34 s after the rule, idle session 0.02 s, HTTP/3 0.07 s, a domain rule cuts only that destination, "no internet" keeps the LAN; 15/15 | pass || Raspberry Pi 5 image (build `20261019.13bdd697`): decompressed and attached as a loop device on the Pi; a first-run file written by the Imager's own writer (`apps/imager/core/firstrun.js`: Spanish, Classic, user with autologin, hidden Wi-Fi, SSH keys only, remote desktop, active cooler with the performance profile and overclock) applied by the image's own arm64 `lordos-firstrun` with `--root/--boot`: 26/26 checks (every file, owners and modes, no Wi-Fi password, the file shredded, a broken file applies nothing) | pass |