Skip to content

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.

Merge branch 'v084-pikernel'

Federico Pereira5df325a25a66
diff --cc docs/VM-SETUP.md
index f3b461c,bb05a04..15c4de4
--- a/docs/VM-SETUP.md
+++ b/docs/VM-SETUP.md
@@@ -1372,74 -1372,36 +1372,108 @@@ in `~/LordOS-csd`, built there (`make -
the profiles, the tree, the script and the backup removed, `lordos.service` restarted to the login
screen. No network or Proxmox setting was touched.
-## Step 39 — 0.8.4: the Pi kernel with socket destroy (VM 116 and the Raspberry Pi, October 19)
+## Step 39 — 0.8.4: the browsers' title bar switch in Settings (VM 119 `lordos-spot`, October 19)
+
+See `WAYLAND.md` ("The switch in Settings"). On VM 119 (172.17.0.54), tree in `~/LordOS-brs` (copied
+with `tar` over SSH: the VM has no `rsync`), built there (`make -C server`, `make -C server test`)
+and installed over `/usr/lib/lordos` by `~/deploy-brs-119.sh` (it saved `/usr/lib/lordos` to
+`/var/backups/lordos-brs-bak` and `settings.json` to `/var/tmp` first).
+
+- **Installed for the tests,** as in step 38: `gsettings-desktop-schemas` and `assets/gtk/LordOS*` in
+ `/usr/share/themes/` (Chromium's GTK theme needs them for the traffic lights); both removed at the
+ end.
+- **Session:** `/etc/lordos/session.conf` with `AUTOLOGIN=lord` (it didn't exist; removed at the
+ end), English and light in `settings.json` (restored at the end). A new session for the login-time
+ tidy-up: the session's `lord-server` ended, `/run/lordos/autologin-done` removed, `systemctl
+ restart lordos`.
+- **Browsers,** started from SSH in the session (`WAYLAND_DISPLAY=wayland-0`, the session bus,
+ `GSETTINGS_BACKEND=keyfile`) by `~/brs-run.sh`, quit with `SIGTERM` (Chromium) or Ctrl+Q and
+ Return through `qm monitor 119` `sendkey` (Firefox: mouse clicks don't reach it on this VM).
+ - **Chromium:** the user's `~/.config/chromium` was moved aside to `~/.config/chromium.brs-saved`
+ and a throwaway profile made by starting Chromium; it was turned into a 0.8.3-style profile
+ (`custom_chrome_frame` false) by hand, then: «Change them», the switch turned off while Chromium
+ was open (applied seconds after it quit), and a check that Chromium keeps the edited values when
+ it rewrites `Preferences`. Chromium left a stale `SingletonLock` after `SIGTERM`; it was
+ correctly ignored. At the end the throwaway profile was deleted and the saved folder put back.
+ - **Firefox:** `lord` already had two Firefox ESR profiles in `~/.config/mozilla/firefox` from
+ October 16 (not checked before the first toggle, so the switch wrote to them): `user.js` lines
+ and `user.js.lordos-backup` files, and Firefox ran three times on `eb7mmslg.default-esr` (its
+ normal session files changed; `prefs.js` got `browser.tabs.inTitlebar`). At the end LordOS's
+ files were removed from both profiles (`user.js`, `user.js.lordos-backup`; Firefox never creates a `user.js`, and both
+ backups held only LordOS's line) and the `inTitlebar` line removed from
+ `prefs.js` with Firefox closed, so it follows the default again.
+- **Input and screenshots:** `lord-qmp-input.py 119 1280 800` from the host, `screendump` holding
+ `flock /tmp/sistema-119-screen.lock`.
+- **Undone at the end:** `/usr/lib/lordos` restored from the backup (the 90 paths the deploy added
+ removed, `diff -r` against the backup empty), `settings.json` restored, `gsettings-desktop-schemas`
+ purged, the GTK themes, `session.conf`, the scripts, the tree, the backup and `/tmp/brs-*` removed,
+ `lordos.service` restarted to the login screen (the 0.8.3-era greeter kept running, as before).
+ `eth0` keeps 172.17.0.54; no network or Proxmox setting was touched.
+
+## Step 40 — 0.8.4: remote desktop over WebRTC (VM 122 `lordos-sandbox`, October 19)
+
+See `REMOTE.md`, "Video (WebRTC)". On VM 122 (172.17.0.56), tree in `~/LordOS-rtc` (synced from the
+Mac's `v084-rtc` worktree by a script of its own name, `sync-rtc-122.sh`, kept outside the repo),
+built there (`make -C server`, `make -C server test`) and installed over the package's files by
+`~/deploy-rtc-122.sh`, which saved `/usr/lib/lordos`, `/etc/lordos` and `/var/lib/lordos/remote` to
+`/var/backups/lordos-rtc-20261019` first (`~/restore-rtc-122.sh` put them back). The theme bundles
+were built on the Mac (the VM has no Node).
+
+- **Installed for the build:** `libsrtp2-dev` and `libusrsctp-dev` (with `libsrtp2-1`, `libusrsctp2`,
+ `libnss3-dev`, `libnspr4-dev`); removed at the end with `apt-get purge` + `autoremove`.
+- **Installed for the TURN tests:** `coturn` (`--no-install-recommends`, with its 11 dependencies);
+ its unit was stopped and disabled right after installing, and `turnserver` ran by hand on
+ 172.17.0.56:3478 with a test-only user from `/tmp/turn-rtc.conf`. Purged at the end.
+- **Test-only accounts** `rtest` and `rtest2` (one password, only for these tests); `rtest` was put
+ in `sudo` for the Settings → Sharing screenshots and the `remote-ice` action. Both deleted with
+ their homes at the end.
+- **The GPU path:** a drop-in `/etc/systemd/system/lordos.service.d/rtc-gpu-test.conf`
+ (`Environment=LORD_GPU=1`, llvmpipe on this virtio card) and `rtest` signed in on the login screen
+ through the Proxmox host's `lord-qmp-input.py` and `lord-type.py`; screenshots with `qm monitor 122`
+ (`screendump`). The drop-in was removed.
+- **Browsers:** headless Chrome on the Mac with throwaway profiles in the scratchpad (deleted after
+ each run), driven over the DevTools protocol; CPU and traffic sampled on the VM by
+ `~/cpu-rtc-122.sh` (`/proc/<pid>/stat`, `eth0` counters); the ICE/STUN probes by
+ `/tmp/icetest-rtc.py` from the VM itself.
+- **Configuration changed during the tests** (all restored from the backup): `config` (`net=`
+ switched to `any` by a stray test click and back, `net=list` for one test, the TURN lines),
+ `access` (one test `allow` entry), `turn.key`, `session.conf`.
+- **Undone at the end:** `/usr/lib/lordos` and `/etc/lordos` restored from the backup (`diff -r`
+ empty), `/var/lib/lordos/remote` restored, `/var/lib/lordos/last-user` back to `lord`, the
+ packages above purged, the test accounts, the tree, the scripts, `/tmp` files and the backup
+ removed, `lordos.service` restarted on the package's binaries, at the login screen. eth0 and the
+ VM's network were not touched; VM 123 was not used.
++
++## Step 41 — 0.8.4: the Pi kernel with socket destroy (VM 116 and the Raspberry Pi, October 19)
+
+ See `RASPBERRY.md` ("The LordOS kernel", "Switching kernels on a board") and `FIREWALL.md`
+ ("Existing connections are cut").
+
+ - **VM 116 (172.17.0.52), cross build:** installed `gcc-aarch64-linux-gnu` and
+ `libc6-dev-arm64-cross` (with their dependencies: `binutils-aarch64-linux-gnu`, the arm64 cross
+ libraries) and the kernel build packages it lacked: `bison`, `flex`, `libelf-dev`, `libdw-dev`,
+ `dwarves`, `rsync`, `debhelper`. They stay, for the next cross build. Work folder
+ `/var/tmp/imager-scratch/pik-kernel` (the 24 GB scratch disk; about 16 GB at the peak) with a
+ temporary 4 GB swap file; `RPI_KERNEL_REF=234188315037… tools/rpi/build-kernel.sh … 2712`, 67 min.
+ The swap file and the work folder were removed afterwards; the `.debs` were copied out first.
+ - **Raspberry Pi 5 (172.17.0.24):** a first attempt to build natively (in a tmpfs, the SD card being
+ 86 % full) ended when the card was removed; nothing of it is left. Then:
+ - `/var/tmp/lordos-kernel/out/`: the `-3` image and headers `.debs` and their config added
+ (`SHA256SUMS` regenerated), where `build-img.sh` takes them from.
+ - `dpkg -i linux-image-6.18.57-lordos.3-rpi-2712_6.18.57-3+lordos_arm64.deb`: the hooks put it at
+ the top level of `/boot/firmware` (over Raspberry Pi's 6.18.50 copy there, which is still
+ installed; the October 18 backup is in `/var/tmp/lordos-kernel/bootbak-20261018`). `-2` stays
+ installed.
+ - `/boot/firmware/lordos/` (the `-2` boot files) renamed `lordos-prev/`; `config.txt` lost its
+ `os_prefix=lordos/` lines (a comment explains how to go back); `tryboot.txt` now boots
+ `lordos-prev/` once. Before the change: `/var/tmp/lordos-pik/config.txt.before` and
+ `tryboot.txt.before`. First boot of `-3` through `tryboot`, then a normal boot, a `tryboot` into
+ `-2` (69 modules loaded, everything active) and back.
+ - `lord-netperm` was still the 0.8.2 binary (not restarted by the 0.8.3 upgrade): restarted.
+ - Tests in `/var/tmp/lordos-pik` (tree copy in `src/`, logs): `netperm_cut.sh` as root with a
+ hand-made `lordos-session-0` cgroup (gone at the reboot; `/root/.config/lordos` removed), before
+ (12/15, the stall) and after (15/15); `verify-board`; `lord-fand` `FORCE 1`/`FORCE off`;
+ `make -C server test`.
+ - Not changed: the network configuration, the `lordbasex` account, the partitions, `cmdline.txt`
+ (this board's lacks `cgroup_enable=memory`, so `verify-board` reports the memory controller as
+ FAIL; the image's has it).